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