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