Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Sensor device configuration | |
3 | # | |
4 | ||
5 | menu "I2C Hardware Bus support" | |
1da177e4 LT |
6 | |
7 | config I2C_ALI1535 | |
8 | tristate "ALI 1535" | |
16538e6b | 9 | depends on PCI |
1da177e4 LT |
10 | help |
11 | If you say yes to this option, support will be included for the SMB | |
12 | Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB | |
13 | controller is part of the 7101 device, which is an ACPI-compliant | |
14 | Power Management Unit (PMU). | |
15 | ||
16 | This driver can also be built as a module. If so, the module | |
17 | will be called i2c-ali1535. | |
18 | ||
19 | config I2C_ALI1563 | |
20 | tristate "ALI 1563" | |
16538e6b | 21 | depends on PCI && EXPERIMENTAL |
1da177e4 LT |
22 | help |
23 | If you say yes to this option, support will be included for the SMB | |
24 | Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB | |
25 | controller is part of the 7101 device, which is an ACPI-compliant | |
26 | Power Management Unit (PMU). | |
27 | ||
28 | This driver can also be built as a module. If so, the module | |
29 | will be called i2c-ali1563. | |
30 | ||
31 | config I2C_ALI15X3 | |
32 | tristate "ALI 15x3" | |
16538e6b | 33 | depends on PCI |
1da177e4 LT |
34 | help |
35 | If you say yes to this option, support will be included for the | |
36 | Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces. | |
37 | ||
38 | This driver can also be built as a module. If so, the module | |
39 | will be called i2c-ali15x3. | |
40 | ||
41 | config I2C_AMD756 | |
42 | tristate "AMD 756/766/768/8111 and nVidia nForce" | |
16538e6b | 43 | depends on PCI |
1da177e4 LT |
44 | help |
45 | If you say yes to this option, support will be included for the AMD | |
46 | 756/766/768 mainboard I2C interfaces. The driver also includes | |
47 | support for the first (SMBus 1.0) I2C interface of the AMD 8111 and | |
48 | the nVidia nForce I2C interface. | |
49 | ||
50 | This driver can also be built as a module. If so, the module | |
51 | will be called i2c-amd756. | |
52 | ||
53 | config I2C_AMD756_S4882 | |
54 | tristate "SMBus multiplexing on the Tyan S4882" | |
55 | depends on I2C_AMD756 && EXPERIMENTAL | |
56 | help | |
57 | Enabling this option will add specific SMBus support for the Tyan | |
58 | S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed | |
59 | over 8 different channels, where the various memory module EEPROMs | |
60 | and temperature sensors live. Saying yes here will give you access | |
61 | to these in addition to the trunk. | |
62 | ||
63 | This driver can also be built as a module. If so, the module | |
64 | will be called i2c-amd756-s4882. | |
65 | ||
66 | config I2C_AMD8111 | |
67 | tristate "AMD 8111" | |
16538e6b | 68 | depends on PCI |
1da177e4 LT |
69 | help |
70 | If you say yes to this option, support will be included for the | |
71 | second (SMBus 2.0) AMD 8111 mainboard I2C interface. | |
72 | ||
73 | This driver can also be built as a module. If so, the module | |
74 | will be called i2c-amd8111. | |
75 | ||
813e30e9 AV |
76 | config I2C_AT91 |
77 | tristate "Atmel AT91 I2C Two-Wire interface (TWI)" | |
24d0fb42 | 78 | depends on ARCH_AT91 && EXPERIMENTAL && BROKEN |
813e30e9 AV |
79 | help |
80 | This supports the use of the I2C interface on Atmel AT91 | |
81 | processors. | |
82 | ||
24d0fb42 DB |
83 | This driver is BROKEN because the controller which it uses |
84 | will easily trigger RX overrun and TX underrun errors. Using | |
85 | low I2C clock rates may partially work around those issues | |
86 | on some systems. Another serious problem is that there is no | |
87 | documented way to issue repeated START conditions, as needed | |
88 | to support combined I2C messages. Use the i2c-gpio driver | |
89 | unless your system can cope with those limitations. | |
90 | ||
1da177e4 | 91 | config I2C_AU1550 |
a294de4e | 92 | tristate "Au1550/Au1200 SMBus interface" |
16538e6b | 93 | depends on SOC_AU1550 || SOC_AU1200 |
1da177e4 LT |
94 | help |
95 | If you say yes to this option, support will be included for the | |
a294de4e | 96 | Au1550 and Au1200 SMBus interface. |
1da177e4 LT |
97 | |
98 | This driver can also be built as a module. If so, the module | |
99 | will be called i2c-au1550. | |
100 | ||
d24ecfcc BW |
101 | config I2C_BLACKFIN_TWI |
102 | tristate "Blackfin TWI I2C support" | |
d4ce220d | 103 | depends on BLACKFIN |
4d2bee58 | 104 | depends on !BF561 && !BF531 && !BF532 && !BF533 |
d24ecfcc | 105 | help |
4d2bee58 | 106 | This is the I2C bus driver for Blackfin on-chip TWI interface. |
d4ce220d | 107 | |
d24ecfcc BW |
108 | This driver can also be built as a module. If so, the module |
109 | will be called i2c-bfin-twi. | |
110 | ||
111 | config I2C_BLACKFIN_TWI_CLK_KHZ | |
112 | int "Blackfin TWI I2C clock (kHz)" | |
113 | depends on I2C_BLACKFIN_TWI | |
114 | range 10 400 | |
115 | default 50 | |
116 | help | |
117 | The unit of the TWI clock is kHz. | |
118 | ||
95a7f10e VB |
119 | config I2C_DAVINCI |
120 | tristate "DaVinci I2C driver" | |
121 | depends on ARCH_DAVINCI | |
122 | help | |
123 | Support for TI DaVinci I2C controller driver. | |
124 | ||
125 | This driver can also be built as a module. If so, the module | |
126 | will be called i2c-davinci. | |
127 | ||
128 | Please note that this driver might be needed to bring up other | |
129 | devices such as DaVinci NIC. | |
130 | For details please see http://www.ti.com/davinci | |
131 | ||
1da177e4 LT |
132 | config I2C_ELEKTOR |
133 | tristate "Elektor ISA card" | |
16538e6b | 134 | depends on ISA && BROKEN_ON_SMP |
1da177e4 LT |
135 | select I2C_ALGOPCF |
136 | help | |
137 | This supports the PCF8584 ISA bus I2C adapter. Say Y if you own | |
138 | such an adapter. | |
139 | ||
4c03f68f | 140 | This support is also available as a module. If so, the module |
1da177e4 LT |
141 | will be called i2c-elektor. |
142 | ||
1c23af90 HS |
143 | config I2C_GPIO |
144 | tristate "GPIO-based bitbanging I2C" | |
145 | depends on GENERIC_GPIO | |
146 | select I2C_ALGOBIT | |
147 | help | |
148 | This is a very simple bitbanging I2C driver utilizing the | |
149 | arch-neutral GPIO API to control the SCL and SDA lines. | |
150 | ||
1da177e4 LT |
151 | config I2C_HYDRA |
152 | tristate "CHRP Apple Hydra Mac I/O I2C interface" | |
16538e6b | 153 | depends on PCI && PPC_CHRP && EXPERIMENTAL |
1da177e4 LT |
154 | select I2C_ALGOBIT |
155 | help | |
156 | This supports the use of the I2C interface in the Apple Hydra Mac | |
157 | I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you | |
158 | have such a machine. | |
159 | ||
160 | This support is also available as a module. If so, the module | |
161 | will be called i2c-hydra. | |
162 | ||
163 | config I2C_I801 | |
164 | tristate "Intel 82801 (ICH)" | |
16538e6b | 165 | depends on PCI |
1da177e4 LT |
166 | help |
167 | If you say yes to this option, support will be included for the Intel | |
168 | 801 family of mainboard I2C interfaces. Specifically, the following | |
169 | versions of the chipset are supported: | |
170 | 82801AA | |
171 | 82801AB | |
172 | 82801BA | |
173 | 82801CA/CAM | |
174 | 82801DB | |
175 | 82801EB/ER (ICH5/ICH5R) | |
176 | 6300ESB | |
177 | ICH6 | |
178 | ICH7 | |
b0a70b57 | 179 | ESB2 |
8254fc4a | 180 | ICH8 |
adbc2a10 | 181 | ICH9 |
d28dc711 GJ |
182 | Tolapai |
183 | ICH10 | |
1da177e4 LT |
184 | |
185 | This driver can also be built as a module. If so, the module | |
186 | will be called i2c-i801. | |
187 | ||
b652b438 RK |
188 | config I2C_PXA |
189 | tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)" | |
16538e6b | 190 | depends on EXPERIMENTAL && ARCH_PXA |
b652b438 RK |
191 | help |
192 | If you have devices in the PXA I2C bus, say yes to this option. | |
193 | This driver can also be built as a module. If so, the module | |
194 | will be called i2c-pxa. | |
195 | ||
196 | config I2C_PXA_SLAVE | |
197 | bool "Intel PXA2XX I2C Slave comms support" | |
198 | depends on I2C_PXA | |
199 | help | |
200 | Support I2C slave mode communications on the PXA I2C bus. This | |
201 | is necessary for systems where the PXA may be a target on the | |
202 | I2C bus. | |
203 | ||
1da177e4 | 204 | config I2C_PIIX4 |
02e0c5d5 | 205 | tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)" |
16538e6b | 206 | depends on PCI |
1da177e4 LT |
207 | help |
208 | If you say yes to this option, support will be included for the Intel | |
209 | PIIX4 family of mainboard I2C interfaces. Specifically, the following | |
5f7ea3c5 MD |
210 | versions of the chipset are supported (note that Serverworks is part |
211 | of Broadcom): | |
1da177e4 LT |
212 | Intel PIIX4 |
213 | Intel 440MX | |
02e0c5d5 RM |
214 | ATI IXP200 |
215 | ATI IXP300 | |
216 | ATI IXP400 | |
4e6697fc | 217 | ATI SB600 |
c29c2221 | 218 | ATI SB700 |
60693e5a | 219 | ATI SB800 |
1da177e4 LT |
220 | Serverworks OSB4 |
221 | Serverworks CSB5 | |
222 | Serverworks CSB6 | |
5f7ea3c5 | 223 | Serverworks HT-1000 |
1da177e4 LT |
224 | SMSC Victory66 |
225 | ||
226 | This driver can also be built as a module. If so, the module | |
227 | will be called i2c-piix4. | |
228 | ||
229 | config I2C_IBM_IIC | |
230 | tristate "IBM PPC 4xx on-chip I2C interface" | |
838349b5 | 231 | depends on 4xx |
1da177e4 | 232 | help |
4c03f68f WS |
233 | Say Y here if you want to use IIC peripheral found on |
234 | embedded IBM PPC 4xx based systems. | |
1da177e4 LT |
235 | |
236 | This driver can also be built as a module. If so, the module | |
237 | will be called i2c-ibm_iic. | |
238 | ||
239 | config I2C_IOP3XX | |
285f5fa7 | 240 | tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" |
16538e6b | 241 | depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX |
1da177e4 LT |
242 | help |
243 | Say Y here if you want to use the IIC bus controller on | |
285f5fa7 | 244 | the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. |
1da177e4 LT |
245 | |
246 | This driver can also be built as a module. If so, the module | |
247 | will be called i2c-iop3xx. | |
248 | ||
1da177e4 | 249 | config I2C_IXP2000 |
11de70bd | 250 | tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)" |
16538e6b | 251 | depends on ARCH_IXP2000 |
1da177e4 LT |
252 | select I2C_ALGOBIT |
253 | help | |
4c03f68f | 254 | Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based |
1da177e4 LT |
255 | system and are using GPIO lines for an I2C bus. |
256 | ||
257 | This support is also available as a module. If so, the module | |
258 | will be called i2c-ixp2000. | |
259 | ||
11de70bd JD |
260 | This driver is deprecated and will be dropped soon. Use i2c-gpio |
261 | instead. | |
262 | ||
a28d3af2 BH |
263 | config I2C_POWERMAC |
264 | tristate "Powermac I2C interface" | |
16538e6b | 265 | depends on PPC_PMAC |
a28d3af2 | 266 | default y |
1da177e4 | 267 | help |
a28d3af2 | 268 | This exposes the various PowerMac i2c interfaces to the linux i2c |
01dd2fbf ML |
269 | layer and to userland. It is used by various drivers on the PowerMac |
270 | platform, and should generally be enabled. | |
0365ba7f BH |
271 | |
272 | This support is also available as a module. If so, the module | |
a28d3af2 | 273 | will be called i2c-powermac. |
0365ba7f | 274 | |
1da177e4 | 275 | config I2C_MPC |
2097c7f0 | 276 | tristate "MPC107/824x/85xx/52xx/86xx" |
16538e6b | 277 | depends on PPC32 |
1da177e4 LT |
278 | help |
279 | If you say yes to this option, support will be included for the | |
280 | built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and | |
2097c7f0 | 281 | MPC85xx/MPC8641 family processors. The driver may also work on 52xx |
1da177e4 LT |
282 | family processors, though interrupts are known not to work. |
283 | ||
284 | This driver can also be built as a module. If so, the module | |
285 | will be called i2c-mpc. | |
286 | ||
287 | config I2C_NFORCE2 | |
5d740fe9 | 288 | tristate "Nvidia nForce2, nForce3 and nForce4" |
16538e6b | 289 | depends on PCI |
1da177e4 LT |
290 | help |
291 | If you say yes to this option, support will be included for the Nvidia | |
5d740fe9 | 292 | nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. |
1da177e4 LT |
293 | |
294 | This driver can also be built as a module. If so, the module | |
295 | will be called i2c-nforce2. | |
296 | ||
279e9024 JD |
297 | config I2C_NFORCE2_S4985 |
298 | tristate "SMBus multiplexing on the Tyan S4985" | |
299 | depends on I2C_NFORCE2 && EXPERIMENTAL | |
300 | help | |
301 | Enabling this option will add specific SMBus support for the Tyan | |
302 | S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed | |
303 | over 4 different channels, where the various memory module EEPROMs | |
304 | live. Saying yes here will give you access to these in addition | |
305 | to the trunk. | |
306 | ||
307 | This driver can also be built as a module. If so, the module | |
308 | will be called i2c-nforce2-s4985. | |
309 | ||
18f98b1e PK |
310 | config I2C_OCORES |
311 | tristate "OpenCores I2C Controller" | |
16538e6b | 312 | depends on EXPERIMENTAL |
18f98b1e PK |
313 | help |
314 | If you say yes to this option, support will be included for the | |
315 | OpenCores I2C controller. For details see | |
316 | http://www.opencores.org/projects.cgi/web/i2c/overview | |
317 | ||
318 | This driver can also be built as a module. If so, the module | |
319 | will be called i2c-ocores. | |
320 | ||
010d442c KS |
321 | config I2C_OMAP |
322 | tristate "OMAP I2C adapter" | |
16538e6b | 323 | depends on ARCH_OMAP |
010d442c KS |
324 | default y if MACH_OMAP_H3 || MACH_OMAP_OSK |
325 | help | |
326 | If you say yes to this option, support will be included for the | |
327 | I2C interface on the Texas Instruments OMAP1/2 family of processors. | |
328 | Like OMAP1510/1610/1710/5912 and OMAP242x. | |
329 | For details see http://www.ti.com/omap. | |
330 | ||
1da177e4 LT |
331 | config I2C_PARPORT |
332 | tristate "Parallel port adapter" | |
16538e6b | 333 | depends on PARPORT |
1da177e4 LT |
334 | select I2C_ALGOBIT |
335 | help | |
336 | This supports parallel port I2C adapters such as the ones made by | |
337 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
338 | Basically any adapter using the parallel port as an I2C bus with | |
339 | no extra chipset is supported by this driver, or could be. | |
340 | ||
341 | This driver is a replacement for (and was inspired by) an older | |
342 | driver named i2c-philips-par. The new driver supports more devices, | |
343 | and makes it easier to add support for new devices. | |
e97b81dd MH |
344 | |
345 | An adapter type parameter is now mandatory. Please read the file | |
346 | Documentation/i2c/busses/i2c-parport for details. | |
347 | ||
1da177e4 LT |
348 | Another driver exists, named i2c-parport-light, which doesn't depend |
349 | on the parport driver. This is meant for embedded systems. Don't say | |
350 | Y here if you intend to say Y or M there. | |
351 | ||
4c03f68f | 352 | This support is also available as a module. If so, the module |
1da177e4 LT |
353 | will be called i2c-parport. |
354 | ||
355 | config I2C_PARPORT_LIGHT | |
356 | tristate "Parallel port adapter (light)" | |
1da177e4 LT |
357 | select I2C_ALGOBIT |
358 | help | |
359 | This supports parallel port I2C adapters such as the ones made by | |
360 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
361 | Basically any adapter using the parallel port as an I2C bus with | |
362 | no extra chipset is supported by this driver, or could be. | |
363 | ||
364 | This driver is a light version of i2c-parport. It doesn't depend | |
365 | on the parport driver, and uses direct I/O access instead. This | |
09509603 | 366 | might be preferred on embedded systems where wasting memory for |
1da177e4 LT |
367 | the clean but heavy parport handling is not an option. The |
368 | drawback is a reduced portability and the impossibility to | |
09509603 | 369 | daisy-chain other parallel port devices. |
4c03f68f | 370 | |
1da177e4 LT |
371 | Don't say Y here if you said Y or M to i2c-parport. Saying M to |
372 | both is possible but both modules should not be loaded at the same | |
373 | time. | |
374 | ||
4c03f68f | 375 | This support is also available as a module. If so, the module |
1da177e4 LT |
376 | will be called i2c-parport-light. |
377 | ||
beb58aa3 OJ |
378 | config I2C_PASEMI |
379 | tristate "PA Semi SMBus interface" | |
16538e6b | 380 | depends on PPC_PASEMI && PCI |
beb58aa3 OJ |
381 | help |
382 | Supports the PA Semi PWRficient on-chip SMBus interfaces. | |
383 | ||
1da177e4 LT |
384 | config I2C_S3C2410 |
385 | tristate "S3C2410 I2C Driver" | |
16538e6b | 386 | depends on ARCH_S3C2410 |
1da177e4 LT |
387 | help |
388 | Say Y here to include support for I2C controller in the | |
389 | Samsung S3C2410 based System-on-Chip devices. | |
390 | ||
1da177e4 LT |
391 | config I2C_SIBYTE |
392 | tristate "SiByte SMBus interface" | |
16538e6b | 393 | depends on SIBYTE_SB1xxx_SOC |
1da177e4 LT |
394 | help |
395 | Supports the SiByte SOC on-chip I2C interfaces (2 channels). | |
396 | ||
bcda9f1e BD |
397 | config I2C_SIMTEC |
398 | tristate "Simtec Generic I2C interface" | |
399 | select I2C_ALGOBIT | |
400 | help | |
01dd2fbf | 401 | If you say yes to this option, support will be included for |
bcda9f1e BD |
402 | the Simtec Generic I2C interface. This driver is for the |
403 | simple I2C bus used on newer Simtec products for general | |
404 | I2C, such as DDC on the Simtec BBD2016A. | |
405 | ||
01dd2fbf | 406 | This driver can also be built as a module. If so, the module |
bcda9f1e BD |
407 | will be called i2c-simtec. |
408 | ||
1da177e4 | 409 | config SCx200_I2C |
11de70bd | 410 | tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)" |
16538e6b | 411 | depends on SCx200_GPIO |
1da177e4 LT |
412 | select I2C_ALGOBIT |
413 | help | |
414 | Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. | |
415 | ||
416 | If you don't know what to do here, say N. | |
417 | ||
4c03f68f | 418 | This support is also available as a module. If so, the module |
1da177e4 LT |
419 | will be called scx200_i2c. |
420 | ||
11de70bd JD |
421 | This driver is deprecated and will be dropped soon. Use i2c-gpio |
422 | (or scx200_acb) instead. | |
423 | ||
1da177e4 LT |
424 | config SCx200_I2C_SCL |
425 | int "GPIO pin used for SCL" | |
426 | depends on SCx200_I2C | |
427 | default "12" | |
428 | help | |
429 | Enter the GPIO pin number used for the SCL signal. This value can | |
430 | also be specified with a module parameter. | |
431 | ||
432 | config SCx200_I2C_SDA | |
433 | int "GPIO pin used for SDA" | |
434 | depends on SCx200_I2C | |
435 | default "13" | |
436 | help | |
437 | Enter the GPIO pin number used for the SSA signal. This value can | |
438 | also be specified with a module parameter. | |
439 | ||
440 | config SCx200_ACB | |
a417bbd3 | 441 | tristate "Geode ACCESS.bus support" |
16538e6b | 442 | depends on X86_32 && PCI |
1da177e4 | 443 | help |
a417bbd3 BG |
444 | Enable the use of the ACCESS.bus controllers on the Geode SCx200 and |
445 | SC1100 processors and the CS5535 and CS5536 Geode companion devices. | |
1da177e4 LT |
446 | |
447 | If you don't know what to do here, say N. | |
448 | ||
4c03f68f | 449 | This support is also available as a module. If so, the module |
1da177e4 LT |
450 | will be called scx200_acb. |
451 | ||
452 | config I2C_SIS5595 | |
453 | tristate "SiS 5595" | |
16538e6b | 454 | depends on PCI |
1da177e4 | 455 | help |
4c03f68f | 456 | If you say yes to this option, support will be included for the |
1da177e4 LT |
457 | SiS5595 SMBus (a subset of I2C) interface. |
458 | ||
459 | This driver can also be built as a module. If so, the module | |
460 | will be called i2c-sis5595. | |
461 | ||
462 | config I2C_SIS630 | |
463 | tristate "SiS 630/730" | |
16538e6b | 464 | depends on PCI |
1da177e4 | 465 | help |
4c03f68f | 466 | If you say yes to this option, support will be included for the |
1da177e4 LT |
467 | SiS630 and SiS730 SMBus (a subset of I2C) interface. |
468 | ||
469 | This driver can also be built as a module. If so, the module | |
470 | will be called i2c-sis630. | |
471 | ||
472 | config I2C_SIS96X | |
473 | tristate "SiS 96x" | |
16538e6b | 474 | depends on PCI |
1da177e4 LT |
475 | help |
476 | If you say yes to this option, support will be included for the SiS | |
477 | 96x SMBus (a subset of I2C) interfaces. Specifically, the following | |
478 | chipsets are supported: | |
479 | 645/961 | |
480 | 645DX/961 | |
481 | 645DX/962 | |
482 | 648/961 | |
483 | 650/961 | |
484 | 735 | |
5d740fe9 | 485 | 745 |
1da177e4 LT |
486 | |
487 | This driver can also be built as a module. If so, the module | |
488 | will be called i2c-sis96x. | |
489 | ||
b9cdad74 JD |
490 | config I2C_TAOS_EVM |
491 | tristate "TAOS evaluation module" | |
492 | depends on EXPERIMENTAL | |
493 | select SERIO | |
494 | select SERIO_SERPORT | |
495 | default n | |
496 | help | |
497 | This supports TAOS evaluation modules on serial port. In order to | |
498 | use this driver, you will need the inputattach tool, which is part | |
499 | of the input-utils package. | |
500 | ||
501 | If unsure, say N. | |
502 | ||
503 | This support is also available as a module. If so, the module | |
504 | will be called i2c-taos-evm. | |
505 | ||
1da177e4 LT |
506 | config I2C_STUB |
507 | tristate "I2C/SMBus Test Stub" | |
16538e6b | 508 | depends on EXPERIMENTAL && m |
1da177e4 LT |
509 | default 'n' |
510 | help | |
511 | This module may be useful to developers of SMBus client drivers, | |
512 | especially for certain kinds of sensor chips. | |
513 | ||
514 | If you do build this module, be sure to read the notes and warnings | |
515 | in <file:Documentation/i2c/i2c-stub>. | |
516 | ||
517 | If you don't know what to do here, definitely say N. | |
518 | ||
e8c76eed TH |
519 | config I2C_TINY_USB |
520 | tristate "I2C-Tiny-USB" | |
521 | depends on USB | |
522 | help | |
523 | If you say yes to this option, support will be included for the | |
524 | i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See | |
525 | http://www.harbaum.org/till/i2c_tiny_usb for hardware details. | |
526 | ||
527 | This driver can also be built as a module. If so, the module | |
528 | will be called i2c-tiny-usb. | |
529 | ||
6b65cd74 RK |
530 | config I2C_VERSATILE |
531 | tristate "ARM Versatile/Realview I2C bus support" | |
16538e6b | 532 | depends on ARCH_VERSATILE || ARCH_REALVIEW |
6b65cd74 RK |
533 | select I2C_ALGOBIT |
534 | help | |
535 | Say yes if you want to support the I2C serial bus on ARMs Versatile | |
536 | range of platforms. | |
537 | ||
538 | This driver can also be built as a module. If so, the module | |
539 | will be called i2c-versatile. | |
540 | ||
8d91cbad | 541 | config I2C_ACORN |
2a9915c8 | 542 | tristate "Acorn IOC/IOMD I2C bus support" |
16538e6b | 543 | depends on ARCH_ACORN |
8d91cbad RK |
544 | default y |
545 | select I2C_ALGOBIT | |
546 | help | |
547 | Say yes if you want to support the I2C bus on Acorn platforms. | |
548 | ||
549 | If you don't know, say Y. | |
550 | ||
1da177e4 LT |
551 | config I2C_VIA |
552 | tristate "VIA 82C586B" | |
16538e6b | 553 | depends on PCI && EXPERIMENTAL |
1da177e4 LT |
554 | select I2C_ALGOBIT |
555 | help | |
556 | If you say yes to this option, support will be included for the VIA | |
557 | 82C586B I2C interface | |
558 | ||
559 | This driver can also be built as a module. If so, the module | |
560 | will be called i2c-via. | |
561 | ||
562 | config I2C_VIAPRO | |
ab6a6ed2 | 563 | tristate "VIA VT82C596/82C686/82xx and CX700" |
16538e6b | 564 | depends on PCI |
1da177e4 LT |
565 | help |
566 | If you say yes to this option, support will be included for the VIA | |
ab6a6ed2 | 567 | VT82C596 and later SMBus interface. Specifically, the following |
1da177e4 | 568 | chipsets are supported: |
c243353a RM |
569 | VT82C596A/B |
570 | VT82C686A/B | |
571 | VT8231 | |
572 | VT8233/A | |
573 | VT8235 | |
0d227a7e | 574 | VT8237R/A/S |
c243353a | 575 | VT8251 |
ab6a6ed2 | 576 | CX700 |
1da177e4 LT |
577 | |
578 | This driver can also be built as a module. If so, the module | |
579 | will be called i2c-viapro. | |
580 | ||
581 | config I2C_VOODOO3 | |
582 | tristate "Voodoo 3" | |
16538e6b | 583 | depends on PCI |
1da177e4 LT |
584 | select I2C_ALGOBIT |
585 | help | |
586 | If you say yes to this option, support will be included for the | |
587 | Voodoo 3 I2C interface. | |
588 | ||
589 | This driver can also be built as a module. If so, the module | |
590 | will be called i2c-voodoo3. | |
591 | ||
592 | config I2C_PCA_ISA | |
593 | tristate "PCA9564 on an ISA bus" | |
16538e6b | 594 | depends on ISA |
1da177e4 | 595 | select I2C_ALGOPCA |
aee62305 | 596 | default n |
1da177e4 | 597 | help |
244fbbb8 WS |
598 | This driver supports ISA boards using the Philips PCA9564 |
599 | parallel bus to I2C bus controller. | |
4c03f68f | 600 | |
1da177e4 LT |
601 | This driver can also be built as a module. If so, the module |
602 | will be called i2c-pca-isa. | |
603 | ||
aee62305 JD |
604 | This device is almost undetectable and using this driver on a |
605 | system which doesn't have this device will result in long | |
606 | delays when I2C/SMBus chip drivers are loaded (e.g. at boot | |
607 | time). If unsure, say N. | |
608 | ||
244fbbb8 WS |
609 | config I2C_PCA_PLATFORM |
610 | tristate "PCA9564 as platform device" | |
611 | select I2C_ALGOPCA | |
612 | default n | |
613 | help | |
614 | This driver supports a memory mapped Philips PCA9564 | |
615 | parallel bus to I2C bus controller. | |
616 | ||
617 | This driver can also be built as a module. If so, the module | |
618 | will be called i2c-pca-platform. | |
619 | ||
1da177e4 LT |
620 | config I2C_MV64XXX |
621 | tristate "Marvell mv64xxx I2C Controller" | |
8791ed32 | 622 | depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL |
1da177e4 LT |
623 | help |
624 | If you say yes to this option, support will be included for the | |
625 | built-in I2C interface on the Marvell 64xxx line of host bridges. | |
626 | ||
627 | This driver can also be built as a module. If so, the module | |
628 | will be called i2c-mv64xxx. | |
629 | ||
41561f28 VW |
630 | config I2C_PNX |
631 | tristate "I2C bus support for Philips PNX targets" | |
16538e6b | 632 | depends on ARCH_PNX4008 |
41561f28 VW |
633 | help |
634 | This driver supports the Philips IP3204 I2C IP block master and/or | |
635 | slave controller | |
636 | ||
637 | This driver can also be built as a module. If so, the module | |
638 | will be called i2c-pnx. | |
639 | ||
1b144df1 MSJ |
640 | config I2C_PMCMSP |
641 | tristate "PMC MSP I2C TWI Controller" | |
642 | depends on PMC_MSP | |
643 | help | |
644 | This driver supports the PMC TWI controller on MSP devices. | |
645 | ||
646 | This driver can also be built as module. If so, the module | |
647 | will be called i2c-pmcmsp. | |
648 | ||
a26c20b1 ML |
649 | config I2C_SH7760 |
650 | tristate "Renesas SH7760 I2C Controller" | |
651 | depends on CPU_SUBTYPE_SH7760 | |
652 | help | |
653 | This driver supports the 2 I2C interfaces on the Renesas SH7760. | |
654 | ||
655 | This driver can also be built as a module. If so, the module | |
656 | will be called i2c-sh7760. | |
657 | ||
da672773 MD |
658 | config I2C_SH_MOBILE |
659 | tristate "SuperH Mobile I2C Controller" | |
660 | depends on SUPERH | |
661 | help | |
662 | If you say yes to this option, support will be included for the | |
663 | built-in I2C interface on the Renesas SH-Mobile processor. | |
664 | ||
665 | This driver can also be built as a module. If so, the module | |
666 | will be called i2c-sh_mobile. | |
667 | ||
1da177e4 | 668 | endmenu |