Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Sensor device configuration | |
3 | # | |
4 | ||
5 | menu "I2C Hardware Bus support" | |
6 | depends on I2C | |
7 | ||
8 | config I2C_ALI1535 | |
9 | tristate "ALI 1535" | |
5d740fe9 | 10 | depends on I2C && PCI |
1da177e4 LT |
11 | 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 | ||
20 | config 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 | ||
32 | config I2C_ALI15X3 | |
33 | tristate "ALI 15x3" | |
5d740fe9 | 34 | depends on I2C && PCI |
1da177e4 LT |
35 | 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 | ||
42 | config I2C_AMD756 | |
43 | tristate "AMD 756/766/768/8111 and nVidia nForce" | |
5d740fe9 | 44 | depends on I2C && PCI |
1da177e4 LT |
45 | 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 | ||
54 | config 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 | ||
67 | config I2C_AMD8111 | |
68 | tristate "AMD 8111" | |
5d740fe9 | 69 | depends on I2C && PCI |
1da177e4 LT |
70 | 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 | ||
77 | config 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 | ||
87 | config 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 | ||
98 | config 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 | ||
110 | config I2C_I801 | |
111 | tristate "Intel 82801 (ICH)" | |
5d740fe9 | 112 | depends on I2C && PCI |
1da177e4 LT |
113 | 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 | |
b0a70b57 | 126 | ESB2 |
1da177e4 LT |
127 | |
128 | This driver can also be built as a module. If so, the module | |
129 | will be called i2c-i801. | |
130 | ||
131 | config I2C_I810 | |
132 | tristate "Intel 810/815" | |
5d740fe9 | 133 | depends on I2C && PCI |
1da177e4 LT |
134 | 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 | |
142078f6 | 138 | following versions of the chipset are supported: |
1da177e4 LT |
139 | i810AA |
140 | i810AB | |
141 | i810E | |
142 | i815 | |
142078f6 | 143 | i845G |
1da177e4 LT |
144 | |
145 | This driver can also be built as a module. If so, the module | |
146 | will be called i2c-i810. | |
147 | ||
b652b438 RK |
148 | config 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 | ||
156 | config 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 | ||
1da177e4 LT |
164 | config 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 | ||
181 | config 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 | ||
191 | config 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 | ||
201 | config I2C_ISA | |
5042c7d7 | 202 | tristate |
5d740fe9 | 203 | depends on I2C |
1da177e4 LT |
204 | |
205 | config 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 | ||
217 | config 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 | ||
228 | config 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 | ||
a28d3af2 BH |
239 | config I2C_POWERMAC |
240 | tristate "Powermac I2C interface" | |
1da177e4 | 241 | depends on I2C && PPC_PMAC |
a28d3af2 | 242 | default y |
1da177e4 | 243 | help |
a28d3af2 BH |
244 | This exposes the various PowerMac i2c interfaces to the linux i2c |
245 | layer and to userland. It is used by various drivers on the powemac | |
246 | platform, thus should generally be enabled. | |
0365ba7f BH |
247 | |
248 | This support is also available as a module. If so, the module | |
a28d3af2 | 249 | will be called i2c-powermac. |
0365ba7f | 250 | |
1da177e4 LT |
251 | config I2C_MPC |
252 | tristate "MPC107/824x/85xx/52xx" | |
b5a48dad | 253 | depends on I2C && PPC32 |
1da177e4 LT |
254 | help |
255 | If you say yes to this option, support will be included for the | |
256 | built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and | |
257 | MPC85xx family processors. The driver may also work on 52xx | |
258 | family processors, though interrupts are known not to work. | |
259 | ||
260 | This driver can also be built as a module. If so, the module | |
261 | will be called i2c-mpc. | |
262 | ||
263 | config I2C_NFORCE2 | |
5d740fe9 M |
264 | tristate "Nvidia nForce2, nForce3 and nForce4" |
265 | depends on I2C && PCI | |
1da177e4 LT |
266 | help |
267 | If you say yes to this option, support will be included for the Nvidia | |
5d740fe9 | 268 | nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. |
1da177e4 LT |
269 | |
270 | This driver can also be built as a module. If so, the module | |
271 | will be called i2c-nforce2. | |
272 | ||
273 | config I2C_PARPORT | |
274 | tristate "Parallel port adapter" | |
275 | depends on I2C && PARPORT | |
276 | select I2C_ALGOBIT | |
277 | help | |
278 | This supports parallel port I2C adapters such as the ones made by | |
279 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
280 | Basically any adapter using the parallel port as an I2C bus with | |
281 | no extra chipset is supported by this driver, or could be. | |
282 | ||
283 | This driver is a replacement for (and was inspired by) an older | |
284 | driver named i2c-philips-par. The new driver supports more devices, | |
285 | and makes it easier to add support for new devices. | |
286 | ||
287 | Another driver exists, named i2c-parport-light, which doesn't depend | |
288 | on the parport driver. This is meant for embedded systems. Don't say | |
289 | Y here if you intend to say Y or M there. | |
290 | ||
291 | This support is also available as a module. If so, the module | |
292 | will be called i2c-parport. | |
293 | ||
294 | config I2C_PARPORT_LIGHT | |
295 | tristate "Parallel port adapter (light)" | |
296 | depends on I2C | |
297 | select I2C_ALGOBIT | |
298 | help | |
299 | This supports parallel port I2C adapters such as the ones made by | |
300 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
301 | Basically any adapter using the parallel port as an I2C bus with | |
302 | no extra chipset is supported by this driver, or could be. | |
303 | ||
304 | This driver is a light version of i2c-parport. It doesn't depend | |
305 | on the parport driver, and uses direct I/O access instead. This | |
306 | might be prefered on embedded systems where wasting memory for | |
307 | the clean but heavy parport handling is not an option. The | |
308 | drawback is a reduced portability and the impossibility to | |
309 | dasiy-chain other parallel port devices. | |
310 | ||
311 | Don't say Y here if you said Y or M to i2c-parport. Saying M to | |
312 | both is possible but both modules should not be loaded at the same | |
313 | time. | |
314 | ||
315 | This support is also available as a module. If so, the module | |
316 | will be called i2c-parport-light. | |
317 | ||
318 | config I2C_PROSAVAGE | |
319 | tristate "S3/VIA (Pro)Savage" | |
5d740fe9 | 320 | depends on I2C && PCI |
1da177e4 LT |
321 | select I2C_ALGOBIT |
322 | help | |
323 | If you say yes to this option, support will be included for the | |
324 | I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8 | |
325 | graphics processors. | |
326 | chipsets supported: | |
327 | S3/VIA KM266/VT8375 aka ProSavage8 | |
328 | S3/VIA KM133/VT8365 aka Savage4 | |
329 | ||
330 | This support is also available as a module. If so, the module | |
331 | will be called i2c-prosavage. | |
332 | ||
333 | config I2C_RPXLITE | |
334 | tristate "Embedded Planet RPX Lite/Classic support" | |
335 | depends on (RPXLITE || RPXCLASSIC) && I2C | |
336 | select I2C_ALGO8XX | |
337 | ||
338 | config I2C_S3C2410 | |
339 | tristate "S3C2410 I2C Driver" | |
340 | depends on I2C && ARCH_S3C2410 | |
341 | help | |
342 | Say Y here to include support for I2C controller in the | |
343 | Samsung S3C2410 based System-on-Chip devices. | |
344 | ||
345 | config I2C_SAVAGE4 | |
346 | tristate "S3 Savage 4" | |
347 | depends on I2C && PCI && EXPERIMENTAL | |
348 | select I2C_ALGOBIT | |
349 | help | |
350 | If you say yes to this option, support will be included for the | |
351 | S3 Savage 4 I2C interface. | |
352 | ||
353 | This driver can also be built as a module. If so, the module | |
354 | will be called i2c-savage4. | |
355 | ||
356 | config I2C_SIBYTE | |
357 | tristate "SiByte SMBus interface" | |
358 | depends on SIBYTE_SB1xxx_SOC && I2C | |
359 | help | |
360 | Supports the SiByte SOC on-chip I2C interfaces (2 channels). | |
361 | ||
362 | config SCx200_I2C | |
363 | tristate "NatSemi SCx200 I2C using GPIO pins" | |
364 | depends on SCx200_GPIO && I2C | |
365 | select I2C_ALGOBIT | |
366 | help | |
367 | Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. | |
368 | ||
369 | If you don't know what to do here, say N. | |
370 | ||
371 | This support is also available as a module. If so, the module | |
372 | will be called scx200_i2c. | |
373 | ||
374 | config SCx200_I2C_SCL | |
375 | int "GPIO pin used for SCL" | |
376 | depends on SCx200_I2C | |
377 | default "12" | |
378 | help | |
379 | Enter the GPIO pin number used for the SCL signal. This value can | |
380 | also be specified with a module parameter. | |
381 | ||
382 | config SCx200_I2C_SDA | |
383 | int "GPIO pin used for SDA" | |
384 | depends on SCx200_I2C | |
385 | default "13" | |
386 | help | |
387 | Enter the GPIO pin number used for the SSA signal. This value can | |
388 | also be specified with a module parameter. | |
389 | ||
390 | config SCx200_ACB | |
391 | tristate "NatSemi SCx200 ACCESS.bus" | |
392 | depends on I2C && PCI | |
393 | help | |
394 | Enable the use of the ACCESS.bus controllers of a SCx200 processor. | |
395 | ||
396 | If you don't know what to do here, say N. | |
397 | ||
398 | This support is also available as a module. If so, the module | |
399 | will be called scx200_acb. | |
400 | ||
401 | config I2C_SIS5595 | |
402 | tristate "SiS 5595" | |
5d740fe9 | 403 | depends on I2C && PCI |
1da177e4 LT |
404 | help |
405 | If you say yes to this option, support will be included for the | |
406 | SiS5595 SMBus (a subset of I2C) interface. | |
407 | ||
408 | This driver can also be built as a module. If so, the module | |
409 | will be called i2c-sis5595. | |
410 | ||
411 | config I2C_SIS630 | |
412 | tristate "SiS 630/730" | |
5d740fe9 | 413 | depends on I2C && PCI |
1da177e4 LT |
414 | help |
415 | If you say yes to this option, support will be included for the | |
416 | SiS630 and SiS730 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-sis630. | |
420 | ||
421 | config I2C_SIS96X | |
422 | tristate "SiS 96x" | |
5d740fe9 | 423 | depends on I2C && PCI |
1da177e4 LT |
424 | help |
425 | If you say yes to this option, support will be included for the SiS | |
426 | 96x SMBus (a subset of I2C) interfaces. Specifically, the following | |
427 | chipsets are supported: | |
428 | 645/961 | |
429 | 645DX/961 | |
430 | 645DX/962 | |
431 | 648/961 | |
432 | 650/961 | |
433 | 735 | |
5d740fe9 | 434 | 745 |
1da177e4 LT |
435 | |
436 | This driver can also be built as a module. If so, the module | |
437 | will be called i2c-sis96x. | |
438 | ||
439 | config I2C_STUB | |
440 | tristate "I2C/SMBus Test Stub" | |
441 | depends on I2C && EXPERIMENTAL && 'm' | |
442 | default 'n' | |
443 | help | |
444 | This module may be useful to developers of SMBus client drivers, | |
445 | especially for certain kinds of sensor chips. | |
446 | ||
447 | If you do build this module, be sure to read the notes and warnings | |
448 | in <file:Documentation/i2c/i2c-stub>. | |
449 | ||
450 | If you don't know what to do here, definitely say N. | |
451 | ||
452 | config I2C_VIA | |
453 | tristate "VIA 82C586B" | |
454 | depends on I2C && PCI && EXPERIMENTAL | |
455 | select I2C_ALGOBIT | |
456 | help | |
457 | If you say yes to this option, support will be included for the VIA | |
458 | 82C586B I2C interface | |
459 | ||
460 | This driver can also be built as a module. If so, the module | |
461 | will be called i2c-via. | |
462 | ||
463 | config I2C_VIAPRO | |
464 | tristate "VIA 82C596/82C686/823x" | |
5d740fe9 | 465 | depends on I2C && PCI |
1da177e4 LT |
466 | help |
467 | If you say yes to this option, support will be included for the VIA | |
468 | 82C596/82C686/823x I2C interfaces. Specifically, the following | |
469 | chipsets are supported: | |
470 | 82C596A/B | |
471 | 82C686A/B | |
472 | 8231 | |
473 | 8233 | |
474 | 8233A | |
475 | 8235 | |
476 | 8237 | |
477 | ||
478 | This driver can also be built as a module. If so, the module | |
479 | will be called i2c-viapro. | |
480 | ||
481 | config I2C_VOODOO3 | |
482 | tristate "Voodoo 3" | |
5d740fe9 | 483 | depends on I2C && PCI |
1da177e4 LT |
484 | select I2C_ALGOBIT |
485 | help | |
486 | If you say yes to this option, support will be included for the | |
487 | Voodoo 3 I2C interface. | |
488 | ||
489 | This driver can also be built as a module. If so, the module | |
490 | will be called i2c-voodoo3. | |
491 | ||
492 | config I2C_PCA_ISA | |
493 | tristate "PCA9564 on an ISA bus" | |
494 | depends on I2C | |
495 | select I2C_ALGOPCA | |
496 | help | |
497 | This driver supports ISA boards using the Philips PCA 9564 | |
498 | Parallel bus to I2C bus controller | |
499 | ||
500 | This driver can also be built as a module. If so, the module | |
501 | will be called i2c-pca-isa. | |
502 | ||
503 | config I2C_MV64XXX | |
504 | tristate "Marvell mv64xxx I2C Controller" | |
505 | depends on I2C && MV64X60 && EXPERIMENTAL | |
506 | help | |
507 | If you say yes to this option, support will be included for the | |
508 | built-in I2C interface on the Marvell 64xxx line of host bridges. | |
509 | ||
510 | This driver can also be built as a module. If so, the module | |
511 | will be called i2c-mv64xxx. | |
512 | ||
513 | endmenu |