]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Sensor device configuration | |
3 | # | |
4 | ||
5 | menu "I2C Hardware Bus support" | |
3ddb59d4 | 6 | depends on HAS_IOMEM |
1da177e4 | 7 | |
f5b728a1 JD |
8 | comment "PC SMBus host controller drivers" |
9 | depends on PCI | |
10 | ||
1da177e4 LT |
11 | config I2C_ALI1535 |
12 | tristate "ALI 1535" | |
16538e6b | 13 | depends on PCI |
1da177e4 LT |
14 | help |
15 | If you say yes to this option, support will be included for the SMB | |
16 | Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB | |
17 | controller is part of the 7101 device, which is an ACPI-compliant | |
18 | Power Management Unit (PMU). | |
19 | ||
20 | This driver can also be built as a module. If so, the module | |
21 | will be called i2c-ali1535. | |
22 | ||
23 | config I2C_ALI1563 | |
24 | tristate "ALI 1563" | |
417e86ce | 25 | depends on PCI |
1da177e4 LT |
26 | help |
27 | If you say yes to this option, support will be included for the SMB | |
28 | Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB | |
29 | controller is part of the 7101 device, which is an ACPI-compliant | |
30 | Power Management Unit (PMU). | |
31 | ||
32 | This driver can also be built as a module. If so, the module | |
33 | will be called i2c-ali1563. | |
34 | ||
35 | config I2C_ALI15X3 | |
36 | tristate "ALI 15x3" | |
16538e6b | 37 | depends on PCI |
1da177e4 LT |
38 | help |
39 | If you say yes to this option, support will be included for the | |
40 | Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces. | |
41 | ||
42 | This driver can also be built as a module. If so, the module | |
43 | will be called i2c-ali15x3. | |
44 | ||
45 | config I2C_AMD756 | |
46 | tristate "AMD 756/766/768/8111 and nVidia nForce" | |
16538e6b | 47 | depends on PCI |
1da177e4 LT |
48 | help |
49 | If you say yes to this option, support will be included for the AMD | |
50 | 756/766/768 mainboard I2C interfaces. The driver also includes | |
51 | support for the first (SMBus 1.0) I2C interface of the AMD 8111 and | |
52 | the nVidia nForce I2C interface. | |
53 | ||
54 | This driver can also be built as a module. If so, the module | |
55 | will be called i2c-amd756. | |
56 | ||
57 | config I2C_AMD756_S4882 | |
58 | tristate "SMBus multiplexing on the Tyan S4882" | |
417e86ce | 59 | depends on I2C_AMD756 && X86 |
1da177e4 LT |
60 | help |
61 | Enabling this option will add specific SMBus support for the Tyan | |
62 | S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed | |
63 | over 8 different channels, where the various memory module EEPROMs | |
64 | and temperature sensors live. Saying yes here will give you access | |
65 | to these in addition to the trunk. | |
66 | ||
67 | This driver can also be built as a module. If so, the module | |
68 | will be called i2c-amd756-s4882. | |
69 | ||
70 | config I2C_AMD8111 | |
71 | tristate "AMD 8111" | |
16538e6b | 72 | depends on PCI |
1da177e4 LT |
73 | help |
74 | If you say yes to this option, support will be included for the | |
75 | second (SMBus 2.0) AMD 8111 mainboard I2C interface. | |
76 | ||
77 | This driver can also be built as a module. If so, the module | |
78 | will be called i2c-amd8111. | |
79 | ||
1da177e4 | 80 | config I2C_I801 |
39376434 | 81 | tristate "Intel 82801 (ICH/PCH)" |
16538e6b | 82 | depends on PCI |
8eacfceb | 83 | select CHECK_SIGNATURE if X86 && DMI |
1da177e4 LT |
84 | help |
85 | If you say yes to this option, support will be included for the Intel | |
86 | 801 family of mainboard I2C interfaces. Specifically, the following | |
87 | versions of the chipset are supported: | |
88 | 82801AA | |
89 | 82801AB | |
90 | 82801BA | |
91 | 82801CA/CAM | |
92 | 82801DB | |
93 | 82801EB/ER (ICH5/ICH5R) | |
94 | 6300ESB | |
95 | ICH6 | |
96 | ICH7 | |
b0a70b57 | 97 | ESB2 |
8254fc4a | 98 | ICH8 |
adbc2a10 | 99 | ICH9 |
cb04e95b | 100 | EP80579 (Tolapai) |
d28dc711 | 101 | ICH10 |
cb04e95b | 102 | 5/3400 Series (PCH) |
662cda8a | 103 | 6 Series (PCH) |
e30d9859 | 104 | Patsburg (PCH) |
662cda8a | 105 | DH89xxCC (PCH) |
6e2a851e | 106 | Panther Point (PCH) |
062737fb | 107 | Lynx Point (PCH) |
4a8f1ddd | 108 | Lynx Point-LP (PCH) |
c2db409c | 109 | Avoton (SOC) |
a3fc0ff0 | 110 | Wellsburg (PCH) |
f39901c1 | 111 | Coleto Creek (PCH) |
1da177e4 LT |
112 | |
113 | This driver can also be built as a module. If so, the module | |
114 | will be called i2c-i801. | |
115 | ||
5bc12008 AD |
116 | config I2C_ISCH |
117 | tristate "Intel SCH SMBus 1.0" | |
0244ad00 | 118 | depends on PCI |
fd46a006 | 119 | select LPC_SCH |
5bc12008 AD |
120 | help |
121 | Say Y here if you want to use SMBus controller on the Intel SCH | |
122 | based systems. | |
123 | ||
124 | This driver can also be built as a module. If so, the module | |
125 | will be called i2c-isch. | |
126 | ||
13f35ac1 NH |
127 | config I2C_ISMT |
128 | tristate "Intel iSMT SMBus Controller" | |
129 | depends on PCI && X86 | |
130 | help | |
131 | If you say yes to this option, support will be included for the Intel | |
132 | iSMT SMBus host controller interface. | |
133 | ||
134 | This driver can also be built as a module. If so, the module will be | |
135 | called i2c-ismt. | |
136 | ||
1da177e4 | 137 | config I2C_PIIX4 |
76b3e28f | 138 | tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" |
16538e6b | 139 | depends on PCI |
1da177e4 LT |
140 | help |
141 | If you say yes to this option, support will be included for the Intel | |
142 | PIIX4 family of mainboard I2C interfaces. Specifically, the following | |
5f7ea3c5 MD |
143 | versions of the chipset are supported (note that Serverworks is part |
144 | of Broadcom): | |
1da177e4 LT |
145 | Intel PIIX4 |
146 | Intel 440MX | |
02e0c5d5 RM |
147 | ATI IXP200 |
148 | ATI IXP300 | |
149 | ATI IXP400 | |
4e6697fc | 150 | ATI SB600 |
2a2f7404 | 151 | ATI SB700/SP5100 |
60693e5a | 152 | ATI SB800 |
3806e94b | 153 | AMD Hudson-2 |
b996ac90 | 154 | AMD CZ |
1da177e4 LT |
155 | Serverworks OSB4 |
156 | Serverworks CSB5 | |
157 | Serverworks CSB6 | |
5f7ea3c5 | 158 | Serverworks HT-1000 |
506a8b6c | 159 | Serverworks HT-1100 |
1da177e4 LT |
160 | SMSC Victory66 |
161 | ||
2a2f7404 AA |
162 | Some AMD chipsets contain two PIIX4-compatible SMBus |
163 | controllers. This driver will attempt to use both controllers | |
164 | on the SB700/SP5100, if they have been initialized by the BIOS. | |
165 | ||
1da177e4 LT |
166 | This driver can also be built as a module. If so, the module |
167 | will be called i2c-piix4. | |
168 | ||
1da177e4 | 169 | config I2C_NFORCE2 |
5d740fe9 | 170 | tristate "Nvidia nForce2, nForce3 and nForce4" |
16538e6b | 171 | depends on PCI |
1da177e4 LT |
172 | help |
173 | If you say yes to this option, support will be included for the Nvidia | |
5d740fe9 | 174 | nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. |
1da177e4 LT |
175 | |
176 | This driver can also be built as a module. If so, the module | |
177 | will be called i2c-nforce2. | |
178 | ||
279e9024 JD |
179 | config I2C_NFORCE2_S4985 |
180 | tristate "SMBus multiplexing on the Tyan S4985" | |
417e86ce | 181 | depends on I2C_NFORCE2 && X86 |
279e9024 JD |
182 | help |
183 | Enabling this option will add specific SMBus support for the Tyan | |
184 | S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed | |
185 | over 4 different channels, where the various memory module EEPROMs | |
186 | live. Saying yes here will give you access to these in addition | |
187 | to the trunk. | |
188 | ||
189 | This driver can also be built as a module. If so, the module | |
190 | will be called i2c-nforce2-s4985. | |
191 | ||
f5b728a1 JD |
192 | config I2C_SIS5595 |
193 | tristate "SiS 5595" | |
194 | depends on PCI | |
18f98b1e PK |
195 | help |
196 | If you say yes to this option, support will be included for the | |
f5b728a1 | 197 | SiS5595 SMBus (a subset of I2C) interface. |
18f98b1e PK |
198 | |
199 | This driver can also be built as a module. If so, the module | |
f5b728a1 | 200 | will be called i2c-sis5595. |
18f98b1e | 201 | |
f5b728a1 | 202 | config I2C_SIS630 |
974d6a37 | 203 | tristate "SiS 630/730/964" |
f5b728a1 | 204 | depends on PCI |
010d442c KS |
205 | help |
206 | If you say yes to this option, support will be included for the | |
974d6a37 | 207 | SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface. |
010d442c | 208 | |
f5b728a1 JD |
209 | This driver can also be built as a module. If so, the module |
210 | will be called i2c-sis630. | |
211 | ||
212 | config I2C_SIS96X | |
213 | tristate "SiS 96x" | |
214 | depends on PCI | |
215 | help | |
216 | If you say yes to this option, support will be included for the SiS | |
217 | 96x SMBus (a subset of I2C) interfaces. Specifically, the following | |
218 | chipsets are supported: | |
219 | 645/961 | |
220 | 645DX/961 | |
221 | 645DX/962 | |
222 | 648/961 | |
223 | 650/961 | |
224 | 735 | |
225 | 745 | |
226 | ||
227 | This driver can also be built as a module. If so, the module | |
228 | will be called i2c-sis96x. | |
229 | ||
230 | config I2C_VIA | |
231 | tristate "VIA VT82C586B" | |
417e86ce | 232 | depends on PCI |
1da177e4 LT |
233 | select I2C_ALGOBIT |
234 | help | |
f5b728a1 JD |
235 | If you say yes to this option, support will be included for the VIA |
236 | 82C586B I2C interface | |
1da177e4 | 237 | |
f5b728a1 JD |
238 | This driver can also be built as a module. If so, the module |
239 | will be called i2c-via. | |
e97b81dd | 240 | |
f5b728a1 | 241 | config I2C_VIAPRO |
01d56a6a | 242 | tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900" |
f5b728a1 JD |
243 | depends on PCI |
244 | help | |
245 | If you say yes to this option, support will be included for the VIA | |
246 | VT82C596 and later SMBus interface. Specifically, the following | |
247 | chipsets are supported: | |
248 | VT82C596A/B | |
249 | VT82C686A/B | |
250 | VT8231 | |
251 | VT8233/A | |
252 | VT8235 | |
253 | VT8237R/A/S | |
254 | VT8251 | |
255 | CX700 | |
a231591f HW |
256 | VX800/VX820 |
257 | VX855/VX875 | |
01d56a6a | 258 | VX900 |
e97b81dd | 259 | |
f5b728a1 JD |
260 | This driver can also be built as a module. If so, the module |
261 | will be called i2c-viapro. | |
1da177e4 | 262 | |
cfd550ed JD |
263 | if ACPI |
264 | ||
265 | comment "ACPI drivers" | |
266 | ||
267 | config I2C_SCMI | |
268 | tristate "SMBus Control Method Interface" | |
269 | help | |
270 | This driver supports the SMBus Control Method Interface. It needs the | |
271 | BIOS to declare ACPI control methods as described in the SMBus Control | |
272 | Method Interface specification. | |
273 | ||
274 | To compile this driver as a module, choose M here: | |
275 | the module will be called i2c-scmi. | |
276 | ||
277 | endif # ACPI | |
278 | ||
f5b728a1 JD |
279 | comment "Mac SMBus host controller drivers" |
280 | depends on PPC_CHRP || PPC_PMAC | |
1da177e4 | 281 | |
f5b728a1 JD |
282 | config I2C_HYDRA |
283 | tristate "CHRP Apple Hydra Mac I/O I2C interface" | |
417e86ce | 284 | depends on PCI && PPC_CHRP |
1da177e4 LT |
285 | select I2C_ALGOBIT |
286 | help | |
f5b728a1 JD |
287 | This supports the use of the I2C interface in the Apple Hydra Mac |
288 | I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you | |
289 | have such a machine. | |
4c03f68f | 290 | |
f5b728a1 JD |
291 | This support is also available as a module. If so, the module |
292 | will be called i2c-hydra. | |
293 | ||
294 | config I2C_POWERMAC | |
295 | tristate "Powermac I2C interface" | |
296 | depends on PPC_PMAC | |
297 | default y | |
298 | help | |
299 | This exposes the various PowerMac i2c interfaces to the linux i2c | |
300 | layer and to userland. It is used by various drivers on the PowerMac | |
301 | platform, and should generally be enabled. | |
1da177e4 | 302 | |
4c03f68f | 303 | This support is also available as a module. If so, the module |
f5b728a1 JD |
304 | will be called i2c-powermac. |
305 | ||
306 | comment "I2C system bus drivers (mostly embedded / system-on-chip)" | |
307 | ||
308 | config I2C_AT91 | |
309 | tristate "Atmel AT91 I2C Two-Wire interface (TWI)" | |
417e86ce | 310 | depends on ARCH_AT91 |
f5b728a1 JD |
311 | help |
312 | This supports the use of the I2C interface on Atmel AT91 | |
313 | processors. | |
314 | ||
fac368a0 NV |
315 | A serious problem is that there is no documented way to issue |
316 | repeated START conditions for more than two messages, as needed | |
f5b728a1 | 317 | to support combined I2C messages. Use the i2c-gpio driver |
fac368a0 NV |
318 | unless your system can cope with this limitation. |
319 | ||
320 | Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices | |
321 | don't have clock stretching in transmission mode. For that reason, | |
322 | you can encounter underrun issues causing premature stop sendings if | |
323 | the latency to fill the transmission register is too long. If you | |
324 | are facing this situation, use the i2c-gpio driver. | |
f5b728a1 JD |
325 | |
326 | config I2C_AU1550 | |
809f36c6 | 327 | tristate "Au1550/Au1200/Au1300 SMBus interface" |
37663860 | 328 | depends on MIPS_ALCHEMY |
f5b728a1 JD |
329 | help |
330 | If you say yes to this option, support will be included for the | |
809f36c6 | 331 | Au1550/Au1200/Au1300 SMBus interface. |
f5b728a1 JD |
332 | |
333 | This driver can also be built as a module. If so, the module | |
334 | will be called i2c-au1550. | |
335 | ||
f3b54b9a SW |
336 | config I2C_BCM2835 |
337 | tristate "Broadcom BCM2835 I2C controller" | |
338 | depends on ARCH_BCM2835 | |
339 | help | |
340 | If you say yes to this option, support will be included for the | |
341 | BCM2835 I2C controller. | |
342 | ||
343 | If you don't know what to do here, say N. | |
344 | ||
345 | This support is also available as a module. If so, the module | |
346 | will be called i2c-bcm2835. | |
347 | ||
f5b728a1 JD |
348 | config I2C_BLACKFIN_TWI |
349 | tristate "Blackfin TWI I2C support" | |
350 | depends on BLACKFIN | |
351 | depends on !BF561 && !BF531 && !BF532 && !BF533 | |
352 | help | |
353 | This is the I2C bus driver for Blackfin on-chip TWI interface. | |
354 | ||
355 | This driver can also be built as a module. If so, the module | |
356 | will be called i2c-bfin-twi. | |
357 | ||
358 | config I2C_BLACKFIN_TWI_CLK_KHZ | |
359 | int "Blackfin TWI I2C clock (kHz)" | |
360 | depends on I2C_BLACKFIN_TWI | |
9528d1c7 | 361 | range 21 400 |
f5b728a1 JD |
362 | default 50 |
363 | help | |
364 | The unit of the TWI clock is kHz. | |
365 | ||
0857ba3c AK |
366 | config I2C_CBUS_GPIO |
367 | tristate "CBUS I2C driver" | |
76ec9d18 | 368 | depends on GPIOLIB |
0857ba3c AK |
369 | help |
370 | Support for CBUS access using I2C API. Mostly relevant for Nokia | |
371 | Internet Tablets (770, N800 and N810). | |
372 | ||
373 | This driver can also be built as a module. If so, the module | |
374 | will be called i2c-cbus-gpio. | |
375 | ||
61045dbe JF |
376 | config I2C_CPM |
377 | tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" | |
378 | depends on (CPM1 || CPM2) && OF_I2C | |
379 | help | |
380 | This supports the use of the I2C interface on Freescale | |
381 | processors with CPM1 or CPM2. | |
382 | ||
383 | This driver can also be built as a module. If so, the module | |
384 | will be called i2c-cpm. | |
385 | ||
f5b728a1 JD |
386 | config I2C_DAVINCI |
387 | tristate "DaVinci I2C driver" | |
d654b548 | 388 | depends on ARCH_DAVINCI || ARCH_KEYSTONE |
f5b728a1 JD |
389 | help |
390 | Support for TI DaVinci I2C controller driver. | |
391 | ||
392 | This driver can also be built as a module. If so, the module | |
393 | will be called i2c-davinci. | |
394 | ||
395 | Please note that this driver might be needed to bring up other | |
396 | devices such as DaVinci NIC. | |
397 | For details please see http://www.ti.com/davinci | |
398 | ||
e68bb91b AL |
399 | config I2C_DESIGNWARE_CORE |
400 | tristate | |
401 | ||
2373f6b9 | 402 | config I2C_DESIGNWARE_PLATFORM |
6b2aac42 | 403 | tristate "Synopsys DesignWare Platform" |
47749b14 | 404 | depends on HAVE_CLK |
e68bb91b | 405 | select I2C_DESIGNWARE_CORE |
1ab52cf9 BS |
406 | help |
407 | If you say yes to this option, support will be included for the | |
408 | Synopsys DesignWare I2C adapter. Only master mode is supported. | |
409 | ||
410 | This driver can also be built as a module. If so, the module | |
2373f6b9 | 411 | will be called i2c-designware-platform. |
1ab52cf9 | 412 | |
fe20ff5c DB |
413 | config I2C_DESIGNWARE_PCI |
414 | tristate "Synopsys DesignWare PCI" | |
415 | depends on PCI | |
e68bb91b | 416 | select I2C_DESIGNWARE_CORE |
fe20ff5c DB |
417 | help |
418 | If you say yes to this option, support will be included for the | |
419 | Synopsys DesignWare I2C adapter. Only master mode is supported. | |
420 | ||
421 | This driver can also be built as a module. If so, the module | |
422 | will be called i2c-designware-pci. | |
1ab52cf9 | 423 | |
3e1b76be J |
424 | config I2C_EG20T |
425 | tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" | |
426 | depends on PCI | |
427 | help | |
428 | This driver is for PCH(Platform controller Hub) I2C of EG20T which | |
429 | is an IOH(Input/Output Hub) for x86 embedded processor. | |
430 | This driver can access PCH I2C bus device. | |
431 | ||
432 | This driver also can be used for LAPIS Semiconductor IOH(Input/ | |
433 | Output Hub), ML7213, ML7223 and ML7831. | |
434 | ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is | |
435 | for MP(Media Phone) use and ML7831 IOH is for general purpose use. | |
436 | ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. | |
437 | ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. | |
438 | ||
f5b728a1 JD |
439 | config I2C_GPIO |
440 | tristate "GPIO-based bitbanging I2C" | |
76ec9d18 | 441 | depends on GPIOLIB |
f5b728a1 JD |
442 | select I2C_ALGOBIT |
443 | help | |
444 | This is a very simple bitbanging I2C driver utilizing the | |
445 | arch-neutral GPIO API to control the SCL and SDA lines. | |
446 | ||
4ad48e6a PM |
447 | config I2C_HIGHLANDER |
448 | tristate "Highlander FPGA SMBus interface" | |
449 | depends on SH_HIGHLANDER | |
450 | help | |
451 | If you say yes to this option, support will be included for | |
452 | the SMBus interface located in the FPGA on various Highlander | |
453 | boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL | |
454 | FPGAs. This is wholly unrelated to the SoC I2C. | |
455 | ||
456 | This driver can also be built as a module. If so, the module | |
457 | will be called i2c-highlander. | |
458 | ||
f5b728a1 JD |
459 | config I2C_IBM_IIC |
460 | tristate "IBM PPC 4xx on-chip I2C interface" | |
461 | depends on 4xx | |
462 | help | |
463 | Say Y here if you want to use IIC peripheral found on | |
464 | embedded IBM PPC 4xx based systems. | |
465 | ||
466 | This driver can also be built as a module. If so, the module | |
467 | will be called i2c-ibm_iic. | |
468 | ||
aa11e38c DA |
469 | config I2C_IMX |
470 | tristate "IMX I2C interface" | |
471 | depends on ARCH_MXC | |
472 | help | |
473 | Say Y here if you want to use the IIC bus controller on | |
474 | the Freescale i.MX/MXC processors. | |
475 | ||
476 | This driver can also be built as a module. If so, the module | |
477 | will be called i2c-imx. | |
478 | ||
f5b728a1 JD |
479 | config I2C_IOP3XX |
480 | tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" | |
481 | depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX | |
482 | help | |
483 | Say Y here if you want to use the IIC bus controller on | |
484 | the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. | |
485 | ||
486 | This driver can also be built as a module. If so, the module | |
487 | will be called i2c-iop3xx. | |
488 | ||
e0b9b7b0 KS |
489 | config I2C_KEMPLD |
490 | tristate "Kontron COM I2C Controller" | |
491 | depends on MFD_KEMPLD | |
492 | help | |
493 | This enables support for the I2C bus interface on some Kontron ETX | |
494 | and COMexpress (ETXexpress) modules. | |
495 | ||
496 | This driver can also be built as a module. If so, the module | |
497 | will be called i2c-kempld. | |
498 | ||
f5b728a1 | 499 | config I2C_MPC |
f00d738f | 500 | tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" |
0724d464 | 501 | depends on PPC |
f5b728a1 JD |
502 | help |
503 | If you say yes to this option, support will be included for the | |
f00d738f WG |
504 | built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, |
505 | MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. | |
f5b728a1 JD |
506 | |
507 | This driver can also be built as a module. If so, the module | |
508 | will be called i2c-mpc. | |
509 | ||
510 | config I2C_MV64XXX | |
511 | tristate "Marvell mv64xxx I2C Controller" | |
3d66ac7d | 512 | depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI) |
f5b728a1 JD |
513 | help |
514 | If you say yes to this option, support will be included for the | |
515 | built-in I2C interface on the Marvell 64xxx line of host bridges. | |
3d66ac7d | 516 | This driver is also used for Allwinner SoCs I2C controllers. |
f5b728a1 JD |
517 | |
518 | This driver can also be built as a module. If so, the module | |
519 | will be called i2c-mv64xxx. | |
520 | ||
a8da7fec WS |
521 | config I2C_MXS |
522 | tristate "Freescale i.MX28 I2C interface" | |
523 | depends on SOC_IMX28 | |
6b866c15 | 524 | select STMP_DEVICE |
a8da7fec WS |
525 | help |
526 | Say Y here if you want to use the I2C bus controller on | |
527 | the Freescale i.MX28 processors. | |
528 | ||
529 | This driver can also be built as a module. If so, the module | |
530 | will be called i2c-mxs. | |
531 | ||
3f9900f1 | 532 | config I2C_NOMADIK |
533 | tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" | |
419408ed | 534 | depends on ARM_AMBA |
3f9900f1 | 535 | help |
536 | If you say yes to this option, support will be included for the | |
419408ed AR |
537 | I2C interface from ST-Ericsson's Nomadik and Ux500 architectures, |
538 | as well as the STA2X11 PCIe I/O HUB. | |
3f9900f1 | 539 | |
ededad3e WZ |
540 | config I2C_NUC900 |
541 | tristate "NUC900 I2C Driver" | |
542 | depends on ARCH_W90X900 | |
543 | help | |
544 | Say Y here to include support for I2C controller in the | |
545 | Winbond/Nuvoton NUC900 based System-on-Chip devices. | |
546 | ||
f5b728a1 JD |
547 | config I2C_OCORES |
548 | tristate "OpenCores I2C Controller" | |
f5b728a1 JD |
549 | help |
550 | If you say yes to this option, support will be included for the | |
551 | OpenCores I2C controller. For details see | |
552 | http://www.opencores.org/projects.cgi/web/i2c/overview | |
553 | ||
554 | This driver can also be built as a module. If so, the module | |
555 | will be called i2c-ocores. | |
556 | ||
557 | config I2C_OMAP | |
558 | tristate "OMAP I2C adapter" | |
559 | depends on ARCH_OMAP | |
560 | default y if MACH_OMAP_H3 || MACH_OMAP_OSK | |
561 | help | |
562 | If you say yes to this option, support will be included for the | |
563 | I2C interface on the Texas Instruments OMAP1/2 family of processors. | |
564 | Like OMAP1510/1610/1710/5912 and OMAP242x. | |
565 | For details see http://www.ti.com/omap. | |
1da177e4 | 566 | |
beb58aa3 OJ |
567 | config I2C_PASEMI |
568 | tristate "PA Semi SMBus interface" | |
16538e6b | 569 | depends on PPC_PASEMI && PCI |
beb58aa3 OJ |
570 | help |
571 | Supports the PA Semi PWRficient on-chip SMBus interfaces. | |
572 | ||
35bfc353 WS |
573 | config I2C_PCA_PLATFORM |
574 | tristate "PCA9564/PCA9665 as platform device" | |
575 | select I2C_ALGOPCA | |
576 | default n | |
577 | help | |
578 | This driver supports a memory mapped Philips PCA9564/PCA9665 | |
579 | parallel bus to I2C bus controller. | |
580 | ||
581 | This driver can also be built as a module. If so, the module | |
582 | will be called i2c-pca-platform. | |
583 | ||
584 | config I2C_PMCMSP | |
585 | tristate "PMC MSP I2C TWI Controller" | |
586 | depends on PMC_MSP | |
587 | help | |
588 | This driver supports the PMC TWI controller on MSP devices. | |
589 | ||
590 | This driver can also be built as module. If so, the module | |
591 | will be called i2c-pmcmsp. | |
592 | ||
f5b728a1 | 593 | config I2C_PNX |
c115167a | 594 | tristate "I2C bus support for Philips PNX and NXP LPC targets" |
d684f05f | 595 | depends on ARCH_LPC32XX |
f5b728a1 JD |
596 | help |
597 | This driver supports the Philips IP3204 I2C IP block master and/or | |
598 | slave controller | |
599 | ||
600 | This driver can also be built as a module. If so, the module | |
601 | will be called i2c-pnx. | |
602 | ||
d10e4a66 G |
603 | config I2C_PUV3 |
604 | tristate "PKUnity v3 I2C bus support" | |
605 | depends on UNICORE32 && ARCH_PUV3 | |
606 | select I2C_ALGOBIT | |
607 | help | |
608 | This driver supports the I2C IP inside the PKUnity-v3 SoC. | |
609 | This I2C bus controller is under AMBA/AXI bus. | |
610 | ||
611 | This driver can also be built as a module. If so, the module | |
612 | will be called i2c-puv3. | |
613 | ||
f5b728a1 | 614 | config I2C_PXA |
d7c46ddd | 615 | tristate "Intel PXA2XX I2C adapter" |
7e94dd15 | 616 | depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF) |
f5b728a1 JD |
617 | help |
618 | If you have devices in the PXA I2C bus, say yes to this option. | |
619 | This driver can also be built as a module. If so, the module | |
620 | will be called i2c-pxa. | |
621 | ||
7e94dd15 SAS |
622 | config I2C_PXA_PCI |
623 | def_bool I2C_PXA && X86_32 && PCI && OF | |
624 | ||
f5b728a1 JD |
625 | config I2C_PXA_SLAVE |
626 | bool "Intel PXA2XX I2C Slave comms support" | |
7e94dd15 | 627 | depends on I2C_PXA && !X86_32 |
f5b728a1 JD |
628 | help |
629 | Support I2C slave mode communications on the PXA I2C bus. This | |
630 | is necessary for systems where the PXA may be a target on the | |
631 | I2C bus. | |
632 | ||
4b623926 NKC |
633 | config HAVE_S3C2410_I2C |
634 | bool | |
635 | help | |
636 | This will include I2C support for Samsung SoCs. If you want to | |
637 | include I2C support for any machine, kindly select this in the | |
638 | respective Kconfig file. | |
639 | ||
1da177e4 LT |
640 | config I2C_S3C2410 |
641 | tristate "S3C2410 I2C Driver" | |
4b623926 | 642 | depends on HAVE_S3C2410_I2C |
1da177e4 LT |
643 | help |
644 | Say Y here to include support for I2C controller in the | |
4b623926 | 645 | Samsung SoCs. |
1da177e4 | 646 | |
b486ddbc OS |
647 | config I2C_S6000 |
648 | tristate "S6000 I2C support" | |
649 | depends on XTENSA_VARIANT_S6000 | |
650 | help | |
651 | This driver supports the on chip I2C device on the | |
652 | S6000 xtensa processor family. | |
653 | ||
654 | To compile this driver as a module, choose M here. The module | |
655 | will be called i2c-s6000. | |
656 | ||
f5b728a1 JD |
657 | config I2C_SH7760 |
658 | tristate "Renesas SH7760 I2C Controller" | |
659 | depends on CPU_SUBTYPE_SH7760 | |
1da177e4 | 660 | help |
f5b728a1 JD |
661 | This driver supports the 2 I2C interfaces on the Renesas SH7760. |
662 | ||
663 | This driver can also be built as a module. If so, the module | |
664 | will be called i2c-sh7760. | |
665 | ||
666 | config I2C_SH_MOBILE | |
667 | tristate "SuperH Mobile I2C Controller" | |
0924fada | 668 | depends on SUPERH || ARCH_SHMOBILE |
f5b728a1 JD |
669 | help |
670 | If you say yes to this option, support will be included for the | |
671 | built-in I2C interface on the Renesas SH-Mobile processor. | |
672 | ||
673 | This driver can also be built as a module. If so, the module | |
674 | will be called i2c-sh_mobile. | |
1da177e4 | 675 | |
bcda9f1e BD |
676 | config I2C_SIMTEC |
677 | tristate "Simtec Generic I2C interface" | |
678 | select I2C_ALGOBIT | |
679 | help | |
01dd2fbf | 680 | If you say yes to this option, support will be included for |
bcda9f1e BD |
681 | the Simtec Generic I2C interface. This driver is for the |
682 | simple I2C bus used on newer Simtec products for general | |
683 | I2C, such as DDC on the Simtec BBD2016A. | |
684 | ||
01dd2fbf | 685 | This driver can also be built as a module. If so, the module |
bcda9f1e BD |
686 | will be called i2c-simtec. |
687 | ||
979b907f ZS |
688 | config I2C_SIRF |
689 | tristate "CSR SiRFprimaII I2C interface" | |
c5dece37 | 690 | depends on ARCH_SIRF |
979b907f ZS |
691 | help |
692 | If you say yes to this option, support will be included for the | |
693 | CSR SiRFprimaII I2C interface. | |
694 | ||
695 | This driver can also be built as a module. If so, the module | |
696 | will be called i2c-sirf. | |
697 | ||
18904c0e LW |
698 | config I2C_STU300 |
699 | tristate "ST Microelectronics DDC I2C interface" | |
4eaad8ad | 700 | depends on MACH_U300 |
18904c0e LW |
701 | default y if MACH_U300 |
702 | help | |
703 | If you say yes to this option, support will be included for the | |
704 | I2C interface from ST Microelectronics simply called "DDC I2C" | |
705 | supporting both I2C and DDC, used in e.g. the U300 series | |
706 | mobile platforms. | |
707 | ||
708 | This driver can also be built as a module. If so, the module | |
709 | will be called i2c-stu300. | |
710 | ||
db811ca0 CC |
711 | config I2C_TEGRA |
712 | tristate "NVIDIA Tegra internal I2C controller" | |
713 | depends on ARCH_TEGRA | |
714 | help | |
715 | If you say yes to this option, support will be included for the | |
716 | I2C controller embedded in NVIDIA Tegra SOCs | |
717 | ||
f5b728a1 JD |
718 | config I2C_VERSATILE |
719 | tristate "ARM Versatile/Realview I2C bus support" | |
ceade897 | 720 | depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS |
1da177e4 LT |
721 | select I2C_ALGOBIT |
722 | help | |
f5b728a1 JD |
723 | Say yes if you want to support the I2C serial bus on ARMs Versatile |
724 | range of platforms. | |
1da177e4 | 725 | |
f5b728a1 JD |
726 | This driver can also be built as a module. If so, the module |
727 | will be called i2c-versatile. | |
1da177e4 | 728 | |
560746eb TP |
729 | config I2C_WMT |
730 | tristate "Wondermedia WM8xxx SoC I2C bus support" | |
731 | depends on ARCH_VT8500 | |
732 | help | |
733 | Say yes if you want to support the I2C bus on Wondermedia 8xxx-series | |
734 | SoCs. | |
735 | ||
736 | This driver can also be built as a module. If so, the module will be | |
737 | called i2c-wmt. | |
738 | ||
85660f43 RB |
739 | config I2C_OCTEON |
740 | tristate "Cavium OCTEON I2C bus support" | |
9ddebc46 | 741 | depends on CAVIUM_OCTEON_SOC |
85660f43 RB |
742 | help |
743 | Say yes if you want to support the I2C serial bus on Cavium | |
744 | OCTEON SOC. | |
745 | ||
746 | This driver can also be built as a module. If so, the module | |
747 | will be called i2c-octeon. | |
748 | ||
e1d5b659 RR |
749 | config I2C_XILINX |
750 | tristate "Xilinx I2C Controller" | |
417e86ce | 751 | depends on HAS_IOMEM |
e1d5b659 RR |
752 | help |
753 | If you say yes to this option, support will be included for the | |
754 | Xilinx I2C controller. | |
755 | ||
756 | This driver can also be built as a module. If so, the module | |
757 | will be called xilinx_i2c. | |
758 | ||
401c3434 GR |
759 | config I2C_XLR |
760 | tristate "XLR I2C support" | |
761 | depends on CPU_XLR | |
762 | help | |
763 | This driver enables support for the on-chip I2C interface of | |
764 | the Netlogic XLR/XLS MIPS processors. | |
765 | ||
766 | This driver can also be built as a module. If so, the module | |
767 | will be called i2c-xlr. | |
768 | ||
6ccbe607 KM |
769 | config I2C_RCAR |
770 | tristate "Renesas R-Car I2C Controller" | |
771 | depends on ARCH_SHMOBILE && I2C | |
772 | help | |
773 | If you say yes to this option, support will be included for the | |
774 | R-Car I2C controller. | |
775 | ||
776 | This driver can also be built as a module. If so, the module | |
777 | will be called i2c-rcar. | |
778 | ||
f5b728a1 | 779 | comment "External I2C/SMBus adapter drivers" |
11de70bd | 780 | |
335d7c58 GR |
781 | config I2C_DIOLAN_U2C |
782 | tristate "Diolan U2C-12 USB adapter" | |
783 | depends on USB | |
784 | help | |
785 | If you say yes to this option, support will be included for Diolan | |
786 | U2C-12, a USB to I2C interface. | |
787 | ||
788 | This driver can also be built as a module. If so, the module | |
789 | will be called i2c-diolan-u2c. | |
790 | ||
f5b728a1 JD |
791 | config I2C_PARPORT |
792 | tristate "Parallel port adapter" | |
0244ad00 | 793 | depends on PARPORT |
f5b728a1 | 794 | select I2C_ALGOBIT |
35859254 | 795 | select I2C_SMBUS |
1da177e4 | 796 | help |
f5b728a1 JD |
797 | This supports parallel port I2C adapters such as the ones made by |
798 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
799 | Basically any adapter using the parallel port as an I2C bus with | |
800 | no extra chipset is supported by this driver, or could be. | |
1da177e4 | 801 | |
f5b728a1 JD |
802 | This driver is a replacement for (and was inspired by) an older |
803 | driver named i2c-philips-par. The new driver supports more devices, | |
804 | and makes it easier to add support for new devices. | |
1da177e4 | 805 | |
f5b728a1 JD |
806 | An adapter type parameter is now mandatory. Please read the file |
807 | Documentation/i2c/busses/i2c-parport for details. | |
1da177e4 | 808 | |
f5b728a1 JD |
809 | Another driver exists, named i2c-parport-light, which doesn't depend |
810 | on the parport driver. This is meant for embedded systems. Don't say | |
811 | Y here if you intend to say Y or M there. | |
1da177e4 | 812 | |
4c03f68f | 813 | This support is also available as a module. If so, the module |
f5b728a1 | 814 | will be called i2c-parport. |
1da177e4 | 815 | |
f5b728a1 JD |
816 | config I2C_PARPORT_LIGHT |
817 | tristate "Parallel port adapter (light)" | |
818 | select I2C_ALGOBIT | |
927ab2f8 | 819 | select I2C_SMBUS |
1da177e4 | 820 | help |
f5b728a1 JD |
821 | This supports parallel port I2C adapters such as the ones made by |
822 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
823 | Basically any adapter using the parallel port as an I2C bus with | |
824 | no extra chipset is supported by this driver, or could be. | |
1da177e4 | 825 | |
f5b728a1 JD |
826 | This driver is a light version of i2c-parport. It doesn't depend |
827 | on the parport driver, and uses direct I/O access instead. This | |
828 | might be preferred on embedded systems where wasting memory for | |
829 | the clean but heavy parport handling is not an option. The | |
830 | drawback is a reduced portability and the impossibility to | |
831 | daisy-chain other parallel port devices. | |
1da177e4 | 832 | |
f5b728a1 JD |
833 | Don't say Y here if you said Y or M to i2c-parport. Saying M to |
834 | both is possible but both modules should not be loaded at the same | |
835 | time. | |
1da177e4 | 836 | |
f5b728a1 JD |
837 | This support is also available as a module. If so, the module |
838 | will be called i2c-parport-light. | |
1da177e4 | 839 | |
b9cdad74 JD |
840 | config I2C_TAOS_EVM |
841 | tristate "TAOS evaluation module" | |
21eaab6d | 842 | depends on TTY |
b9cdad74 JD |
843 | select SERIO |
844 | select SERIO_SERPORT | |
845 | default n | |
846 | help | |
847 | This supports TAOS evaluation modules on serial port. In order to | |
848 | use this driver, you will need the inputattach tool, which is part | |
849 | of the input-utils package. | |
850 | ||
851 | If unsure, say N. | |
852 | ||
853 | This support is also available as a module. If so, the module | |
854 | will be called i2c-taos-evm. | |
855 | ||
e8c76eed | 856 | config I2C_TINY_USB |
f5b728a1 | 857 | tristate "Tiny-USB adapter" |
e8c76eed TH |
858 | depends on USB |
859 | help | |
860 | If you say yes to this option, support will be included for the | |
861 | i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See | |
862 | http://www.harbaum.org/till/i2c_tiny_usb for hardware details. | |
863 | ||
864 | This driver can also be built as a module. If so, the module | |
865 | will be called i2c-tiny-usb. | |
866 | ||
174a13aa LP |
867 | config I2C_VIPERBOARD |
868 | tristate "Viperboard I2C master support" | |
869 | depends on MFD_VIPERBOARD && USB | |
870 | help | |
871 | Say yes here to access the I2C part of the Nano River | |
872 | Technologies Viperboard as I2C master. | |
873 | See viperboard API specification and Nano | |
874 | River Tech's viperboard.h for detailed meaning | |
875 | of the module parameters. | |
876 | ||
f5b728a1 | 877 | comment "Other I2C/SMBus bus drivers" |
6b65cd74 | 878 | |
8d91cbad | 879 | config I2C_ACORN |
2a9915c8 | 880 | tristate "Acorn IOC/IOMD I2C bus support" |
16538e6b | 881 | depends on ARCH_ACORN |
8d91cbad RK |
882 | default y |
883 | select I2C_ALGOBIT | |
884 | help | |
885 | Say yes if you want to support the I2C bus on Acorn platforms. | |
886 | ||
887 | If you don't know, say Y. | |
888 | ||
f5b728a1 JD |
889 | config I2C_ELEKTOR |
890 | tristate "Elektor ISA card" | |
9519282a | 891 | depends on ISA && HAS_IOPORT && BROKEN_ON_SMP |
f5b728a1 | 892 | select I2C_ALGOPCF |
1da177e4 | 893 | help |
f5b728a1 JD |
894 | This supports the PCF8584 ISA bus I2C adapter. Say Y if you own |
895 | such an adapter. | |
1da177e4 | 896 | |
f5b728a1 JD |
897 | This support is also available as a module. If so, the module |
898 | will be called i2c-elektor. | |
1da177e4 LT |
899 | |
900 | config I2C_PCA_ISA | |
eff9ec95 | 901 | tristate "PCA9564/PCA9665 on an ISA bus" |
16538e6b | 902 | depends on ISA |
1da177e4 | 903 | select I2C_ALGOPCA |
aee62305 | 904 | default n |
1da177e4 | 905 | help |
eff9ec95 | 906 | This driver supports ISA boards using the Philips PCA9564/PCA9665 |
244fbbb8 | 907 | parallel bus to I2C bus controller. |
4c03f68f | 908 | |
1da177e4 LT |
909 | This driver can also be built as a module. If so, the module |
910 | will be called i2c-pca-isa. | |
911 | ||
aee62305 JD |
912 | This device is almost undetectable and using this driver on a |
913 | system which doesn't have this device will result in long | |
914 | delays when I2C/SMBus chip drivers are loaded (e.g. at boot | |
915 | time). If unsure, say N. | |
916 | ||
f5b728a1 JD |
917 | config I2C_SIBYTE |
918 | tristate "SiByte SMBus interface" | |
919 | depends on SIBYTE_SB1xxx_SOC | |
a26c20b1 | 920 | help |
f5b728a1 | 921 | Supports the SiByte SOC on-chip I2C interfaces (2 channels). |
a26c20b1 | 922 | |
f5b728a1 JD |
923 | config SCx200_I2C |
924 | tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)" | |
925 | depends on SCx200_GPIO | |
926 | select I2C_ALGOBIT | |
da672773 | 927 | help |
f5b728a1 | 928 | Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. |
da672773 | 929 | |
f5b728a1 JD |
930 | If you don't know what to do here, say N. |
931 | ||
932 | This support is also available as a module. If so, the module | |
933 | will be called scx200_i2c. | |
934 | ||
935 | This driver is deprecated and will be dropped soon. Use i2c-gpio | |
936 | (or scx200_acb) instead. | |
937 | ||
938 | config SCx200_I2C_SCL | |
939 | int "GPIO pin used for SCL" | |
940 | depends on SCx200_I2C | |
941 | default "12" | |
942 | help | |
943 | Enter the GPIO pin number used for the SCL signal. This value can | |
944 | also be specified with a module parameter. | |
945 | ||
946 | config SCx200_I2C_SDA | |
947 | int "GPIO pin used for SDA" | |
948 | depends on SCx200_I2C | |
949 | default "13" | |
950 | help | |
951 | Enter the GPIO pin number used for the SSA signal. This value can | |
952 | also be specified with a module parameter. | |
953 | ||
954 | config SCx200_ACB | |
955 | tristate "Geode ACCESS.bus support" | |
956 | depends on X86_32 && PCI | |
957 | help | |
958 | Enable the use of the ACCESS.bus controllers on the Geode SCx200 and | |
959 | SC1100 processors and the CS5535 and CS5536 Geode companion devices. | |
960 | ||
961 | If you don't know what to do here, say N. | |
962 | ||
963 | This support is also available as a module. If so, the module | |
964 | will be called scx200_acb. | |
da672773 | 965 | |
1da177e4 | 966 | endmenu |