blob: 8334496a7e0aee02b42ca7b4953a165d2efb91e1 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Sensor device configuration
3#
4
5menu "I2C Hardware Bus support"
6 depends on I2C
7
8config I2C_ALI1535
9 tristate "ALI 1535"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000010 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070011 help
12 If you say yes to this option, support will be included for the SMB
13 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
14 controller is part of the 7101 device, which is an ACPI-compliant
15 Power Management Unit (PMU).
16
17 This driver can also be built as a module. If so, the module
18 will be called i2c-ali1535.
19
20config I2C_ALI1563
21 tristate "ALI 1563"
22 depends on I2C && PCI && EXPERIMENTAL
23 help
24 If you say yes to this option, support will be included for the SMB
25 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
26 controller is part of the 7101 device, which is an ACPI-compliant
27 Power Management Unit (PMU).
28
29 This driver can also be built as a module. If so, the module
30 will be called i2c-ali1563.
31
32config I2C_ALI15X3
33 tristate "ALI 15x3"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000034 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070035 help
36 If you say yes to this option, support will be included for the
37 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
38
39 This driver can also be built as a module. If so, the module
40 will be called i2c-ali15x3.
41
42config I2C_AMD756
43 tristate "AMD 756/766/768/8111 and nVidia nForce"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000044 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070045 help
46 If you say yes to this option, support will be included for the AMD
47 756/766/768 mainboard I2C interfaces. The driver also includes
48 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
49 the nVidia nForce I2C interface.
50
51 This driver can also be built as a module. If so, the module
52 will be called i2c-amd756.
53
54config I2C_AMD756_S4882
55 tristate "SMBus multiplexing on the Tyan S4882"
56 depends on I2C_AMD756 && EXPERIMENTAL
57 help
58 Enabling this option will add specific SMBus support for the Tyan
59 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
60 over 8 different channels, where the various memory module EEPROMs
61 and temperature sensors live. Saying yes here will give you access
62 to these in addition to the trunk.
63
64 This driver can also be built as a module. If so, the module
65 will be called i2c-amd756-s4882.
66
67config I2C_AMD8111
68 tristate "AMD 8111"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +000069 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -070070 help
71 If you say yes to this option, support will be included for the
72 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
73
74 This driver can also be built as a module. If so, the module
75 will be called i2c-amd8111.
76
77config I2C_AU1550
78 tristate "Au1550 SMBus interface"
79 depends on I2C && SOC_AU1550
80 help
81 If you say yes to this option, support will be included for the
82 Au1550 SMBus interface.
83
84 This driver can also be built as a module. If so, the module
85 will be called i2c-au1550.
86
87config I2C_ELEKTOR
88 tristate "Elektor ISA card"
89 depends on I2C && ISA && BROKEN_ON_SMP
90 select I2C_ALGOPCF
91 help
92 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
93 such an adapter.
94
95 This support is also available as a module. If so, the module
96 will be called i2c-elektor.
97
98config I2C_HYDRA
99 tristate "CHRP Apple Hydra Mac I/O I2C interface"
100 depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
101 select I2C_ALGOBIT
102 help
103 This supports the use of the I2C interface in the Apple Hydra Mac
104 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
105 have such a machine.
106
107 This support is also available as a module. If so, the module
108 will be called i2c-hydra.
109
110config I2C_I801
111 tristate "Intel 82801 (ICH)"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000112 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113 help
114 If you say yes to this option, support will be included for the Intel
115 801 family of mainboard I2C interfaces. Specifically, the following
116 versions of the chipset are supported:
117 82801AA
118 82801AB
119 82801BA
120 82801CA/CAM
121 82801DB
122 82801EB/ER (ICH5/ICH5R)
123 6300ESB
124 ICH6
125 ICH7
Jason Gastonb0a70b52005-04-16 15:24:45 -0700126 ESB2
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127
128 This driver can also be built as a module. If so, the module
129 will be called i2c-i801.
130
131config I2C_I810
132 tristate "Intel 810/815"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000133 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134 select I2C_ALGOBIT
135 help
136 If you say yes to this option, support will be included for the Intel
137 810/815 family of mainboard I2C interfaces. Specifically, the
138 following versions of the chipset is supported:
139 i810AA
140 i810AB
141 i810E
142 i815
143
144 This driver can also be built as a module. If so, the module
145 will be called i2c-i810.
146
Russell Kingb652b432005-06-15 12:38:14 +0100147config I2C_PXA
148 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
149 depends on I2C && EXPERIMENTAL && ARCH_PXA
150 help
151 If you have devices in the PXA I2C bus, say yes to this option.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-pxa.
154
155config I2C_PXA_SLAVE
156 bool "Intel PXA2XX I2C Slave comms support"
157 depends on I2C_PXA
158 help
159 Support I2C slave mode communications on the PXA I2C bus. This
160 is necessary for systems where the PXA may be a target on the
161 I2C bus.
162
Linus Torvalds1da177e2005-04-16 15:20:36 -0700163config I2C_PIIX4
164 tristate "Intel PIIX4"
165 depends on I2C && PCI
166 help
167 If you say yes to this option, support will be included for the Intel
168 PIIX4 family of mainboard I2C interfaces. Specifically, the following
169 versions of the chipset are supported:
170 Intel PIIX4
171 Intel 440MX
172 Serverworks OSB4
173 Serverworks CSB5
174 Serverworks CSB6
175 SMSC Victory66
176
177 This driver can also be built as a module. If so, the module
178 will be called i2c-piix4.
179
180config I2C_IBM_IIC
181 tristate "IBM PPC 4xx on-chip I2C interface"
182 depends on IBM_OCP && I2C
183 help
184 Say Y here if you want to use IIC peripheral found on
185 embedded IBM PPC 4xx based systems.
186
187 This driver can also be built as a module. If so, the module
188 will be called i2c-ibm_iic.
189
190config I2C_IOP3XX
191 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
192 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
193 help
194 Say Y here if you want to use the IIC bus controller on
195 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
196
197 This driver can also be built as a module. If so, the module
198 will be called i2c-iop3xx.
199
200config I2C_ISA
Jean Delvare5042c7d2005-07-19 23:53:07 +0200201 tristate
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000202 depends on I2C
Linus Torvalds1da177e2005-04-16 15:20:36 -0700203
204config I2C_ITE
205 tristate "ITE I2C Adapter"
206 depends on I2C && MIPS_ITE8172
207 select I2C_ALGOITE
208 help
209 This supports the ITE8172 I2C peripheral found on some MIPS
210 systems. Say Y if you have one of these. You should also say Y for
211 the ITE I2C driver algorithm support above.
212
213 This support is also available as a module. If so, the module
214 will be called i2c-ite.
215
216config I2C_IXP4XX
217 tristate "IXP4xx GPIO-Based I2C Interface"
218 depends on I2C && ARCH_IXP4XX
219 select I2C_ALGOBIT
220 help
221 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
222 system and are using GPIO lines for an I2C bus.
223
224 This support is also available as a module. If so, the module
225 will be called i2c-ixp4xx.
226
227config I2C_IXP2000
228 tristate "IXP2000 GPIO-Based I2C Interface"
229 depends on I2C && ARCH_IXP2000
230 select I2C_ALGOBIT
231 help
232 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
233 system and are using GPIO lines for an I2C bus.
234
235 This support is also available as a module. If so, the module
236 will be called i2c-ixp2000.
237
238config I2C_KEYWEST
239 tristate "Powermac Keywest I2C interface"
240 depends on I2C && PPC_PMAC
241 help
242 This supports the use of the I2C interface in the combo-I/O
243 chip on recent Apple machines. Say Y if you have such a machine.
244
245 This support is also available as a module. If so, the module
246 will be called i2c-keywest.
247
248config I2C_MPC
249 tristate "MPC107/824x/85xx/52xx"
Al Virob5a48da2005-04-24 12:28:35 -0700250 depends on I2C && PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700251 help
252 If you say yes to this option, support will be included for the
253 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
254 MPC85xx family processors. The driver may also work on 52xx
255 family processors, though interrupts are known not to work.
256
257 This driver can also be built as a module. If so, the module
258 will be called i2c-mpc.
259
260config I2C_NFORCE2
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000261 tristate "Nvidia nForce2, nForce3 and nForce4"
262 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700263 help
264 If you say yes to this option, support will be included for the Nvidia
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000265 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700266
267 This driver can also be built as a module. If so, the module
268 will be called i2c-nforce2.
269
270config I2C_PARPORT
271 tristate "Parallel port adapter"
272 depends on I2C && PARPORT
273 select I2C_ALGOBIT
274 help
275 This supports parallel port I2C adapters such as the ones made by
276 Philips or Velleman, Analog Devices evaluation boards, and more.
277 Basically any adapter using the parallel port as an I2C bus with
278 no extra chipset is supported by this driver, or could be.
279
280 This driver is a replacement for (and was inspired by) an older
281 driver named i2c-philips-par. The new driver supports more devices,
282 and makes it easier to add support for new devices.
283
284 Another driver exists, named i2c-parport-light, which doesn't depend
285 on the parport driver. This is meant for embedded systems. Don't say
286 Y here if you intend to say Y or M there.
287
288 This support is also available as a module. If so, the module
289 will be called i2c-parport.
290
291config I2C_PARPORT_LIGHT
292 tristate "Parallel port adapter (light)"
293 depends on I2C
294 select I2C_ALGOBIT
295 help
296 This supports parallel port I2C adapters such as the ones made by
297 Philips or Velleman, Analog Devices evaluation boards, and more.
298 Basically any adapter using the parallel port as an I2C bus with
299 no extra chipset is supported by this driver, or could be.
300
301 This driver is a light version of i2c-parport. It doesn't depend
302 on the parport driver, and uses direct I/O access instead. This
303 might be prefered on embedded systems where wasting memory for
304 the clean but heavy parport handling is not an option. The
305 drawback is a reduced portability and the impossibility to
306 dasiy-chain other parallel port devices.
307
308 Don't say Y here if you said Y or M to i2c-parport. Saying M to
309 both is possible but both modules should not be loaded at the same
310 time.
311
312 This support is also available as a module. If so, the module
313 will be called i2c-parport-light.
314
315config I2C_PROSAVAGE
316 tristate "S3/VIA (Pro)Savage"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000317 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700318 select I2C_ALGOBIT
319 help
320 If you say yes to this option, support will be included for the
321 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
322 graphics processors.
323 chipsets supported:
324 S3/VIA KM266/VT8375 aka ProSavage8
325 S3/VIA KM133/VT8365 aka Savage4
326
327 This support is also available as a module. If so, the module
328 will be called i2c-prosavage.
329
330config I2C_RPXLITE
331 tristate "Embedded Planet RPX Lite/Classic support"
332 depends on (RPXLITE || RPXCLASSIC) && I2C
333 select I2C_ALGO8XX
334
335config I2C_S3C2410
336 tristate "S3C2410 I2C Driver"
337 depends on I2C && ARCH_S3C2410
338 help
339 Say Y here to include support for I2C controller in the
340 Samsung S3C2410 based System-on-Chip devices.
341
342config I2C_SAVAGE4
343 tristate "S3 Savage 4"
344 depends on I2C && PCI && EXPERIMENTAL
345 select I2C_ALGOBIT
346 help
347 If you say yes to this option, support will be included for the
348 S3 Savage 4 I2C interface.
349
350 This driver can also be built as a module. If so, the module
351 will be called i2c-savage4.
352
353config I2C_SIBYTE
354 tristate "SiByte SMBus interface"
355 depends on SIBYTE_SB1xxx_SOC && I2C
356 help
357 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
358
359config SCx200_I2C
360 tristate "NatSemi SCx200 I2C using GPIO pins"
361 depends on SCx200_GPIO && I2C
362 select I2C_ALGOBIT
363 help
364 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
365
366 If you don't know what to do here, say N.
367
368 This support is also available as a module. If so, the module
369 will be called scx200_i2c.
370
371config SCx200_I2C_SCL
372 int "GPIO pin used for SCL"
373 depends on SCx200_I2C
374 default "12"
375 help
376 Enter the GPIO pin number used for the SCL signal. This value can
377 also be specified with a module parameter.
378
379config SCx200_I2C_SDA
380 int "GPIO pin used for SDA"
381 depends on SCx200_I2C
382 default "13"
383 help
384 Enter the GPIO pin number used for the SSA signal. This value can
385 also be specified with a module parameter.
386
387config SCx200_ACB
388 tristate "NatSemi SCx200 ACCESS.bus"
389 depends on I2C && PCI
390 help
391 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
392
393 If you don't know what to do here, say N.
394
395 This support is also available as a module. If so, the module
396 will be called scx200_acb.
397
398config I2C_SIS5595
399 tristate "SiS 5595"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000400 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700401 help
402 If you say yes to this option, support will be included for the
403 SiS5595 SMBus (a subset of I2C) interface.
404
405 This driver can also be built as a module. If so, the module
406 will be called i2c-sis5595.
407
408config I2C_SIS630
409 tristate "SiS 630/730"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000410 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700411 help
412 If you say yes to this option, support will be included for the
413 SiS630 and SiS730 SMBus (a subset of I2C) interface.
414
415 This driver can also be built as a module. If so, the module
416 will be called i2c-sis630.
417
418config I2C_SIS96X
419 tristate "SiS 96x"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000420 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700421 help
422 If you say yes to this option, support will be included for the SiS
423 96x SMBus (a subset of I2C) interfaces. Specifically, the following
424 chipsets are supported:
425 645/961
426 645DX/961
427 645DX/962
428 648/961
429 650/961
430 735
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000431 745
Linus Torvalds1da177e2005-04-16 15:20:36 -0700432
433 This driver can also be built as a module. If so, the module
434 will be called i2c-sis96x.
435
436config I2C_STUB
437 tristate "I2C/SMBus Test Stub"
438 depends on I2C && EXPERIMENTAL && 'm'
439 default 'n'
440 help
441 This module may be useful to developers of SMBus client drivers,
442 especially for certain kinds of sensor chips.
443
444 If you do build this module, be sure to read the notes and warnings
445 in <file:Documentation/i2c/i2c-stub>.
446
447 If you don't know what to do here, definitely say N.
448
449config I2C_VIA
450 tristate "VIA 82C586B"
451 depends on I2C && PCI && EXPERIMENTAL
452 select I2C_ALGOBIT
453 help
454 If you say yes to this option, support will be included for the VIA
455 82C586B I2C interface
456
457 This driver can also be built as a module. If so, the module
458 will be called i2c-via.
459
460config I2C_VIAPRO
461 tristate "VIA 82C596/82C686/823x"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000462 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700463 help
464 If you say yes to this option, support will be included for the VIA
465 82C596/82C686/823x I2C interfaces. Specifically, the following
466 chipsets are supported:
467 82C596A/B
468 82C686A/B
469 8231
470 8233
471 8233A
472 8235
473 8237
474
475 This driver can also be built as a module. If so, the module
476 will be called i2c-viapro.
477
478config I2C_VOODOO3
479 tristate "Voodoo 3"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000480 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700481 select I2C_ALGOBIT
482 help
483 If you say yes to this option, support will be included for the
484 Voodoo 3 I2C interface.
485
486 This driver can also be built as a module. If so, the module
487 will be called i2c-voodoo3.
488
489config I2C_PCA_ISA
490 tristate "PCA9564 on an ISA bus"
491 depends on I2C
492 select I2C_ALGOPCA
493 help
494 This driver supports ISA boards using the Philips PCA 9564
495 Parallel bus to I2C bus controller
496
497 This driver can also be built as a module. If so, the module
498 will be called i2c-pca-isa.
499
500config I2C_MV64XXX
501 tristate "Marvell mv64xxx I2C Controller"
502 depends on I2C && MV64X60 && EXPERIMENTAL
503 help
504 If you say yes to this option, support will be included for the
505 built-in I2C interface on the Marvell 64xxx line of host bridges.
506
507 This driver can also be built as a module. If so, the module
508 will be called i2c-mv64xxx.
509
510endmenu