blob: ff92735c7c85706c2424e3b8445ac30e7d36eaca [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
Jason Gaston8254fc42006-01-09 10:58:08 -0800127 ICH8
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128
129 This driver can also be built as a module. If so, the module
130 will be called i2c-i801.
131
132config I2C_I810
133 tristate "Intel 810/815"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000134 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700135 select I2C_ALGOBIT
136 help
137 If you say yes to this option, support will be included for the Intel
138 810/815 family of mainboard I2C interfaces. Specifically, the
Jean Delvare142078f2005-10-26 21:21:50 +0200139 following versions of the chipset are supported:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700140 i810AA
141 i810AB
142 i810E
143 i815
Jean Delvare142078f2005-10-26 21:21:50 +0200144 i845G
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145
146 This driver can also be built as a module. If so, the module
147 will be called i2c-i810.
148
Russell Kingb652b432005-06-15 12:38:14 +0100149config I2C_PXA
150 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
151 depends on I2C && EXPERIMENTAL && ARCH_PXA
152 help
153 If you have devices in the PXA I2C bus, say yes to this option.
154 This driver can also be built as a module. If so, the module
155 will be called i2c-pxa.
156
157config I2C_PXA_SLAVE
158 bool "Intel PXA2XX I2C Slave comms support"
159 depends on I2C_PXA
160 help
161 Support I2C slave mode communications on the PXA I2C bus. This
162 is necessary for systems where the PXA may be a target on the
163 I2C bus.
164
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165config I2C_PIIX4
166 tristate "Intel PIIX4"
167 depends on I2C && PCI
168 help
169 If you say yes to this option, support will be included for the Intel
170 PIIX4 family of mainboard I2C interfaces. Specifically, the following
171 versions of the chipset are supported:
172 Intel PIIX4
173 Intel 440MX
174 Serverworks OSB4
175 Serverworks CSB5
176 Serverworks CSB6
177 SMSC Victory66
178
179 This driver can also be built as a module. If so, the module
180 will be called i2c-piix4.
181
182config I2C_IBM_IIC
183 tristate "IBM PPC 4xx on-chip I2C interface"
184 depends on IBM_OCP && I2C
185 help
186 Say Y here if you want to use IIC peripheral found on
187 embedded IBM PPC 4xx based systems.
188
189 This driver can also be built as a module. If so, the module
190 will be called i2c-ibm_iic.
191
192config I2C_IOP3XX
193 tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
194 depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
195 help
196 Say Y here if you want to use the IIC bus controller on
197 the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
198
199 This driver can also be built as a module. If so, the module
200 will be called i2c-iop3xx.
201
202config I2C_ISA
Jean Delvare5042c7d2005-07-19 23:53:07 +0200203 tristate
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000204 depends on I2C
Linus Torvalds1da177e2005-04-16 15:20:36 -0700205
206config I2C_ITE
207 tristate "ITE I2C Adapter"
208 depends on I2C && MIPS_ITE8172
209 select I2C_ALGOITE
210 help
211 This supports the ITE8172 I2C peripheral found on some MIPS
212 systems. Say Y if you have one of these. You should also say Y for
213 the ITE I2C driver algorithm support above.
214
215 This support is also available as a module. If so, the module
216 will be called i2c-ite.
217
218config I2C_IXP4XX
219 tristate "IXP4xx GPIO-Based I2C Interface"
220 depends on I2C && ARCH_IXP4XX
221 select I2C_ALGOBIT
222 help
223 Say Y here if you have an Intel IXP4xx(420,421,422,425) based
224 system and are using GPIO lines for an I2C bus.
225
226 This support is also available as a module. If so, the module
227 will be called i2c-ixp4xx.
228
229config I2C_IXP2000
230 tristate "IXP2000 GPIO-Based I2C Interface"
231 depends on I2C && ARCH_IXP2000
232 select I2C_ALGOBIT
233 help
234 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
235 system and are using GPIO lines for an I2C bus.
236
237 This support is also available as a module. If so, the module
238 will be called i2c-ixp2000.
239
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100240config I2C_POWERMAC
241 tristate "Powermac I2C interface"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700242 depends on I2C && PPC_PMAC
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100243 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -0700244 help
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100245 This exposes the various PowerMac i2c interfaces to the linux i2c
246 layer and to userland. It is used by various drivers on the powemac
247 platform, thus should generally be enabled.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700248
249 This support is also available as a module. If so, the module
Benjamin Herrenschmidta28d3af2006-01-07 11:35:26 +1100250 will be called i2c-powermac.
Benjamin Herrenschmidt0365ba72005-09-22 21:44:06 -0700251
Linus Torvalds1da177e2005-04-16 15:20:36 -0700252config I2C_MPC
253 tristate "MPC107/824x/85xx/52xx"
Al Virob5a48da2005-04-24 12:28:35 -0700254 depends on I2C && PPC32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700255 help
256 If you say yes to this option, support will be included for the
257 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
258 MPC85xx family processors. The driver may also work on 52xx
259 family processors, though interrupts are known not to work.
260
261 This driver can also be built as a module. If so, the module
262 will be called i2c-mpc.
263
264config I2C_NFORCE2
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000265 tristate "Nvidia nForce2, nForce3 and nForce4"
266 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700267 help
268 If you say yes to this option, support will be included for the Nvidia
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000269 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700270
271 This driver can also be built as a module. If so, the module
272 will be called i2c-nforce2.
273
274config I2C_PARPORT
275 tristate "Parallel port adapter"
276 depends on I2C && PARPORT
277 select I2C_ALGOBIT
278 help
279 This supports parallel port I2C adapters such as the ones made by
280 Philips or Velleman, Analog Devices evaluation boards, and more.
281 Basically any adapter using the parallel port as an I2C bus with
282 no extra chipset is supported by this driver, or could be.
283
284 This driver is a replacement for (and was inspired by) an older
285 driver named i2c-philips-par. The new driver supports more devices,
286 and makes it easier to add support for new devices.
287
288 Another driver exists, named i2c-parport-light, which doesn't depend
289 on the parport driver. This is meant for embedded systems. Don't say
290 Y here if you intend to say Y or M there.
291
292 This support is also available as a module. If so, the module
293 will be called i2c-parport.
294
295config I2C_PARPORT_LIGHT
296 tristate "Parallel port adapter (light)"
297 depends on I2C
298 select I2C_ALGOBIT
299 help
300 This supports parallel port I2C adapters such as the ones made by
301 Philips or Velleman, Analog Devices evaluation boards, and more.
302 Basically any adapter using the parallel port as an I2C bus with
303 no extra chipset is supported by this driver, or could be.
304
305 This driver is a light version of i2c-parport. It doesn't depend
306 on the parport driver, and uses direct I/O access instead. This
307 might be prefered on embedded systems where wasting memory for
308 the clean but heavy parport handling is not an option. The
309 drawback is a reduced portability and the impossibility to
310 dasiy-chain other parallel port devices.
311
312 Don't say Y here if you said Y or M to i2c-parport. Saying M to
313 both is possible but both modules should not be loaded at the same
314 time.
315
316 This support is also available as a module. If so, the module
317 will be called i2c-parport-light.
318
319config I2C_PROSAVAGE
320 tristate "S3/VIA (Pro)Savage"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000321 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700322 select I2C_ALGOBIT
323 help
324 If you say yes to this option, support will be included for the
325 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
326 graphics processors.
327 chipsets supported:
328 S3/VIA KM266/VT8375 aka ProSavage8
329 S3/VIA KM133/VT8365 aka Savage4
330
331 This support is also available as a module. If so, the module
332 will be called i2c-prosavage.
333
334config I2C_RPXLITE
335 tristate "Embedded Planet RPX Lite/Classic support"
336 depends on (RPXLITE || RPXCLASSIC) && I2C
337 select I2C_ALGO8XX
338
339config I2C_S3C2410
340 tristate "S3C2410 I2C Driver"
341 depends on I2C && ARCH_S3C2410
342 help
343 Say Y here to include support for I2C controller in the
344 Samsung S3C2410 based System-on-Chip devices.
345
346config I2C_SAVAGE4
347 tristate "S3 Savage 4"
348 depends on I2C && PCI && EXPERIMENTAL
349 select I2C_ALGOBIT
350 help
351 If you say yes to this option, support will be included for the
352 S3 Savage 4 I2C interface.
353
354 This driver can also be built as a module. If so, the module
355 will be called i2c-savage4.
356
357config I2C_SIBYTE
358 tristate "SiByte SMBus interface"
359 depends on SIBYTE_SB1xxx_SOC && I2C
360 help
361 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
362
363config SCx200_I2C
364 tristate "NatSemi SCx200 I2C using GPIO pins"
365 depends on SCx200_GPIO && I2C
366 select I2C_ALGOBIT
367 help
368 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
369
370 If you don't know what to do here, say N.
371
372 This support is also available as a module. If so, the module
373 will be called scx200_i2c.
374
375config SCx200_I2C_SCL
376 int "GPIO pin used for SCL"
377 depends on SCx200_I2C
378 default "12"
379 help
380 Enter the GPIO pin number used for the SCL signal. This value can
381 also be specified with a module parameter.
382
383config SCx200_I2C_SDA
384 int "GPIO pin used for SDA"
385 depends on SCx200_I2C
386 default "13"
387 help
388 Enter the GPIO pin number used for the SSA signal. This value can
389 also be specified with a module parameter.
390
391config SCx200_ACB
392 tristate "NatSemi SCx200 ACCESS.bus"
393 depends on I2C && PCI
394 help
395 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
396
397 If you don't know what to do here, say N.
398
399 This support is also available as a module. If so, the module
400 will be called scx200_acb.
401
402config I2C_SIS5595
403 tristate "SiS 5595"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000404 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700405 help
406 If you say yes to this option, support will be included for the
407 SiS5595 SMBus (a subset of I2C) interface.
408
409 This driver can also be built as a module. If so, the module
410 will be called i2c-sis5595.
411
412config I2C_SIS630
413 tristate "SiS 630/730"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000414 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700415 help
416 If you say yes to this option, support will be included for the
417 SiS630 and SiS730 SMBus (a subset of I2C) interface.
418
419 This driver can also be built as a module. If so, the module
420 will be called i2c-sis630.
421
422config I2C_SIS96X
423 tristate "SiS 96x"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000424 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700425 help
426 If you say yes to this option, support will be included for the SiS
427 96x SMBus (a subset of I2C) interfaces. Specifically, the following
428 chipsets are supported:
429 645/961
430 645DX/961
431 645DX/962
432 648/961
433 650/961
434 735
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000435 745
Linus Torvalds1da177e2005-04-16 15:20:36 -0700436
437 This driver can also be built as a module. If so, the module
438 will be called i2c-sis96x.
439
440config I2C_STUB
441 tristate "I2C/SMBus Test Stub"
442 depends on I2C && EXPERIMENTAL && 'm'
443 default 'n'
444 help
445 This module may be useful to developers of SMBus client drivers,
446 especially for certain kinds of sensor chips.
447
448 If you do build this module, be sure to read the notes and warnings
449 in <file:Documentation/i2c/i2c-stub>.
450
451 If you don't know what to do here, definitely say N.
452
453config I2C_VIA
454 tristate "VIA 82C586B"
455 depends on I2C && PCI && EXPERIMENTAL
456 select I2C_ALGOBIT
457 help
458 If you say yes to this option, support will be included for the VIA
459 82C586B I2C interface
460
461 This driver can also be built as a module. If so, the module
462 will be called i2c-via.
463
464config I2C_VIAPRO
465 tristate "VIA 82C596/82C686/823x"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000466 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700467 help
468 If you say yes to this option, support will be included for the VIA
469 82C596/82C686/823x I2C interfaces. Specifically, the following
470 chipsets are supported:
471 82C596A/B
472 82C686A/B
473 8231
474 8233
475 8233A
476 8235
477 8237
478
479 This driver can also be built as a module. If so, the module
480 will be called i2c-viapro.
481
482config I2C_VOODOO3
483 tristate "Voodoo 3"
R.Marek@sh.cvut.cz5d740fe2005-05-28 11:26:24 +0000484 depends on I2C && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700485 select I2C_ALGOBIT
486 help
487 If you say yes to this option, support will be included for the
488 Voodoo 3 I2C interface.
489
490 This driver can also be built as a module. If so, the module
491 will be called i2c-voodoo3.
492
493config I2C_PCA_ISA
494 tristate "PCA9564 on an ISA bus"
495 depends on I2C
496 select I2C_ALGOPCA
497 help
498 This driver supports ISA boards using the Philips PCA 9564
499 Parallel bus to I2C bus controller
500
501 This driver can also be built as a module. If so, the module
502 will be called i2c-pca-isa.
503
504config I2C_MV64XXX
505 tristate "Marvell mv64xxx I2C Controller"
506 depends on I2C && MV64X60 && EXPERIMENTAL
507 help
508 If you say yes to this option, support will be included for the
509 built-in I2C interface on the Marvell 64xxx line of host bridges.
510
511 This driver can also be built as a module. If so, the module
512 will be called i2c-mv64xxx.
513
514endmenu