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