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 | ||
15ef2775 WY |
80 | config I2C_HIX5HD2 |
81 | tristate "Hix5hd2 high-speed I2C driver" | |
181d9a07 | 82 | depends on ARCH_HIX5HD2 || COMPILE_TEST |
15ef2775 WY |
83 | help |
84 | Say Y here to include support for high-speed I2C controller in the | |
85 | Hisilicon based hix5hd2 SoCs. | |
86 | ||
87 | This driver can also be built as a module. If so, the module | |
88 | will be called i2c-hix5hd2. | |
89 | ||
1da177e4 | 90 | config I2C_I801 |
39376434 | 91 | tristate "Intel 82801 (ICH/PCH)" |
16538e6b | 92 | depends on PCI |
8eacfceb | 93 | select CHECK_SIGNATURE if X86 && DMI |
1da177e4 LT |
94 | help |
95 | If you say yes to this option, support will be included for the Intel | |
96 | 801 family of mainboard I2C interfaces. Specifically, the following | |
97 | versions of the chipset are supported: | |
98 | 82801AA | |
99 | 82801AB | |
100 | 82801BA | |
101 | 82801CA/CAM | |
102 | 82801DB | |
103 | 82801EB/ER (ICH5/ICH5R) | |
104 | 6300ESB | |
105 | ICH6 | |
106 | ICH7 | |
b0a70b57 | 107 | ESB2 |
8254fc4a | 108 | ICH8 |
adbc2a10 | 109 | ICH9 |
cb04e95b | 110 | EP80579 (Tolapai) |
d28dc711 | 111 | ICH10 |
cb04e95b | 112 | 5/3400 Series (PCH) |
662cda8a | 113 | 6 Series (PCH) |
e30d9859 | 114 | Patsburg (PCH) |
662cda8a | 115 | DH89xxCC (PCH) |
6e2a851e | 116 | Panther Point (PCH) |
062737fb | 117 | Lynx Point (PCH) |
4a8f1ddd | 118 | Lynx Point-LP (PCH) |
c2db409c | 119 | Avoton (SOC) |
a3fc0ff0 | 120 | Wellsburg (PCH) |
f39901c1 | 121 | Coleto Creek (PCH) |
b299de83 | 122 | Wildcat Point (PCH) |
afc65924 | 123 | Wildcat Point-LP (PCH) |
1b31e9b7 | 124 | BayTrail (SOC) |
3e27a844 | 125 | Sunrise Point-H (PCH) |
3eee1799 | 126 | Sunrise Point-LP (PCH) |
1da177e4 LT |
127 | |
128 | This driver can also be built as a module. If so, the module | |
129 | will be called i2c-i801. | |
130 | ||
5bc12008 AD |
131 | config I2C_ISCH |
132 | tristate "Intel SCH SMBus 1.0" | |
0244ad00 | 133 | depends on PCI |
fd46a006 | 134 | select LPC_SCH |
5bc12008 AD |
135 | help |
136 | Say Y here if you want to use SMBus controller on the Intel SCH | |
137 | based systems. | |
138 | ||
139 | This driver can also be built as a module. If so, the module | |
140 | will be called i2c-isch. | |
141 | ||
13f35ac1 NH |
142 | config I2C_ISMT |
143 | tristate "Intel iSMT SMBus Controller" | |
144 | depends on PCI && X86 | |
145 | help | |
146 | If you say yes to this option, support will be included for the Intel | |
147 | iSMT SMBus host controller interface. | |
148 | ||
149 | This driver can also be built as a module. If so, the module will be | |
150 | called i2c-ismt. | |
151 | ||
1da177e4 | 152 | config I2C_PIIX4 |
76b3e28f | 153 | tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" |
16538e6b | 154 | depends on PCI |
1da177e4 LT |
155 | help |
156 | If you say yes to this option, support will be included for the Intel | |
157 | PIIX4 family of mainboard I2C interfaces. Specifically, the following | |
5f7ea3c5 MD |
158 | versions of the chipset are supported (note that Serverworks is part |
159 | of Broadcom): | |
1da177e4 LT |
160 | Intel PIIX4 |
161 | Intel 440MX | |
02e0c5d5 RM |
162 | ATI IXP200 |
163 | ATI IXP300 | |
164 | ATI IXP400 | |
4e6697fc | 165 | ATI SB600 |
2a2f7404 | 166 | ATI SB700/SP5100 |
60693e5a | 167 | ATI SB800 |
3806e94b | 168 | AMD Hudson-2 |
032f708b | 169 | AMD ML |
b996ac90 | 170 | AMD CZ |
1da177e4 LT |
171 | Serverworks OSB4 |
172 | Serverworks CSB5 | |
173 | Serverworks CSB6 | |
5f7ea3c5 | 174 | Serverworks HT-1000 |
506a8b6c | 175 | Serverworks HT-1100 |
1da177e4 LT |
176 | SMSC Victory66 |
177 | ||
2a2f7404 AA |
178 | Some AMD chipsets contain two PIIX4-compatible SMBus |
179 | controllers. This driver will attempt to use both controllers | |
180 | on the SB700/SP5100, if they have been initialized by the BIOS. | |
181 | ||
1da177e4 LT |
182 | This driver can also be built as a module. If so, the module |
183 | will be called i2c-piix4. | |
184 | ||
1da177e4 | 185 | config I2C_NFORCE2 |
5d740fe9 | 186 | tristate "Nvidia nForce2, nForce3 and nForce4" |
16538e6b | 187 | depends on PCI |
1da177e4 LT |
188 | help |
189 | If you say yes to this option, support will be included for the Nvidia | |
5d740fe9 | 190 | nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. |
1da177e4 LT |
191 | |
192 | This driver can also be built as a module. If so, the module | |
193 | will be called i2c-nforce2. | |
194 | ||
279e9024 JD |
195 | config I2C_NFORCE2_S4985 |
196 | tristate "SMBus multiplexing on the Tyan S4985" | |
417e86ce | 197 | depends on I2C_NFORCE2 && X86 |
279e9024 JD |
198 | help |
199 | Enabling this option will add specific SMBus support for the Tyan | |
200 | S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed | |
201 | over 4 different channels, where the various memory module EEPROMs | |
202 | live. Saying yes here will give you access to these in addition | |
203 | to the trunk. | |
204 | ||
205 | This driver can also be built as a module. If so, the module | |
206 | will be called i2c-nforce2-s4985. | |
207 | ||
f5b728a1 JD |
208 | config I2C_SIS5595 |
209 | tristate "SiS 5595" | |
210 | depends on PCI | |
18f98b1e PK |
211 | help |
212 | If you say yes to this option, support will be included for the | |
f5b728a1 | 213 | SiS5595 SMBus (a subset of I2C) interface. |
18f98b1e PK |
214 | |
215 | This driver can also be built as a module. If so, the module | |
f5b728a1 | 216 | will be called i2c-sis5595. |
18f98b1e | 217 | |
f5b728a1 | 218 | config I2C_SIS630 |
974d6a37 | 219 | tristate "SiS 630/730/964" |
f5b728a1 | 220 | depends on PCI |
010d442c KS |
221 | help |
222 | If you say yes to this option, support will be included for the | |
974d6a37 | 223 | SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface. |
010d442c | 224 | |
f5b728a1 JD |
225 | This driver can also be built as a module. If so, the module |
226 | will be called i2c-sis630. | |
227 | ||
228 | config I2C_SIS96X | |
229 | tristate "SiS 96x" | |
230 | depends on PCI | |
231 | help | |
232 | If you say yes to this option, support will be included for the SiS | |
233 | 96x SMBus (a subset of I2C) interfaces. Specifically, the following | |
234 | chipsets are supported: | |
235 | 645/961 | |
236 | 645DX/961 | |
237 | 645DX/962 | |
238 | 648/961 | |
239 | 650/961 | |
240 | 735 | |
241 | 745 | |
242 | ||
243 | This driver can also be built as a module. If so, the module | |
244 | will be called i2c-sis96x. | |
245 | ||
246 | config I2C_VIA | |
247 | tristate "VIA VT82C586B" | |
417e86ce | 248 | depends on PCI |
1da177e4 LT |
249 | select I2C_ALGOBIT |
250 | help | |
f5b728a1 JD |
251 | If you say yes to this option, support will be included for the VIA |
252 | 82C586B I2C interface | |
1da177e4 | 253 | |
f5b728a1 JD |
254 | This driver can also be built as a module. If so, the module |
255 | will be called i2c-via. | |
e97b81dd | 256 | |
f5b728a1 | 257 | config I2C_VIAPRO |
01d56a6a | 258 | tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900" |
f5b728a1 JD |
259 | depends on PCI |
260 | help | |
261 | If you say yes to this option, support will be included for the VIA | |
262 | VT82C596 and later SMBus interface. Specifically, the following | |
263 | chipsets are supported: | |
264 | VT82C596A/B | |
265 | VT82C686A/B | |
266 | VT8231 | |
267 | VT8233/A | |
268 | VT8235 | |
269 | VT8237R/A/S | |
270 | VT8251 | |
271 | CX700 | |
a231591f HW |
272 | VX800/VX820 |
273 | VX855/VX875 | |
01d56a6a | 274 | VX900 |
e97b81dd | 275 | |
f5b728a1 JD |
276 | This driver can also be built as a module. If so, the module |
277 | will be called i2c-viapro. | |
1da177e4 | 278 | |
cfd550ed JD |
279 | if ACPI |
280 | ||
281 | comment "ACPI drivers" | |
282 | ||
283 | config I2C_SCMI | |
284 | tristate "SMBus Control Method Interface" | |
285 | help | |
286 | This driver supports the SMBus Control Method Interface. It needs the | |
287 | BIOS to declare ACPI control methods as described in the SMBus Control | |
288 | Method Interface specification. | |
289 | ||
290 | To compile this driver as a module, choose M here: | |
291 | the module will be called i2c-scmi. | |
292 | ||
293 | endif # ACPI | |
294 | ||
f5b728a1 JD |
295 | comment "Mac SMBus host controller drivers" |
296 | depends on PPC_CHRP || PPC_PMAC | |
1da177e4 | 297 | |
f5b728a1 JD |
298 | config I2C_HYDRA |
299 | tristate "CHRP Apple Hydra Mac I/O I2C interface" | |
417e86ce | 300 | depends on PCI && PPC_CHRP |
1da177e4 LT |
301 | select I2C_ALGOBIT |
302 | help | |
f5b728a1 JD |
303 | This supports the use of the I2C interface in the Apple Hydra Mac |
304 | I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you | |
305 | have such a machine. | |
4c03f68f | 306 | |
f5b728a1 JD |
307 | This support is also available as a module. If so, the module |
308 | will be called i2c-hydra. | |
309 | ||
310 | config I2C_POWERMAC | |
311 | tristate "Powermac I2C interface" | |
312 | depends on PPC_PMAC | |
313 | default y | |
314 | help | |
315 | This exposes the various PowerMac i2c interfaces to the linux i2c | |
316 | layer and to userland. It is used by various drivers on the PowerMac | |
317 | platform, and should generally be enabled. | |
1da177e4 | 318 | |
4c03f68f | 319 | This support is also available as a module. If so, the module |
f5b728a1 JD |
320 | will be called i2c-powermac. |
321 | ||
322 | comment "I2C system bus drivers (mostly embedded / system-on-chip)" | |
323 | ||
324 | config I2C_AT91 | |
325 | tristate "Atmel AT91 I2C Two-Wire interface (TWI)" | |
417e86ce | 326 | depends on ARCH_AT91 |
f5b728a1 JD |
327 | help |
328 | This supports the use of the I2C interface on Atmel AT91 | |
329 | processors. | |
330 | ||
fac368a0 NV |
331 | A serious problem is that there is no documented way to issue |
332 | repeated START conditions for more than two messages, as needed | |
f5b728a1 | 333 | to support combined I2C messages. Use the i2c-gpio driver |
fac368a0 NV |
334 | unless your system can cope with this limitation. |
335 | ||
336 | Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices | |
337 | don't have clock stretching in transmission mode. For that reason, | |
338 | you can encounter underrun issues causing premature stop sendings if | |
339 | the latency to fill the transmission register is too long. If you | |
340 | are facing this situation, use the i2c-gpio driver. | |
f5b728a1 JD |
341 | |
342 | config I2C_AU1550 | |
809f36c6 | 343 | tristate "Au1550/Au1200/Au1300 SMBus interface" |
37663860 | 344 | depends on MIPS_ALCHEMY |
f5b728a1 JD |
345 | help |
346 | If you say yes to this option, support will be included for the | |
809f36c6 | 347 | Au1550/Au1200/Au1300 SMBus interface. |
f5b728a1 JD |
348 | |
349 | This driver can also be built as a module. If so, the module | |
350 | will be called i2c-au1550. | |
351 | ||
08678b85 AB |
352 | config I2C_AXXIA |
353 | tristate "Axxia I2C controller" | |
354 | depends on ARCH_AXXIA || COMPILE_TEST | |
355 | default ARCH_AXXIA | |
356 | help | |
357 | Say yes if you want to support the I2C bus on Axxia platforms. | |
358 | ||
359 | Please note that this controller is limited to transfers of maximum | |
360 | 255 bytes in length. Any attempt to to a larger transfer will return | |
361 | an error. | |
362 | ||
f3b54b9a SW |
363 | config I2C_BCM2835 |
364 | tristate "Broadcom BCM2835 I2C controller" | |
365 | depends on ARCH_BCM2835 | |
366 | help | |
367 | If you say yes to this option, support will be included for the | |
368 | BCM2835 I2C controller. | |
369 | ||
370 | If you don't know what to do here, say N. | |
371 | ||
372 | This support is also available as a module. If so, the module | |
373 | will be called i2c-bcm2835. | |
374 | ||
e6e5dd35 RJ |
375 | config I2C_BCM_IPROC |
376 | tristate "Broadcom iProc I2C controller" | |
377 | depends on ARCH_BCM_IPROC || COMPILE_TEST | |
378 | default ARCH_BCM_IPROC | |
379 | help | |
380 | If you say yes to this option, support will be included for the | |
381 | Broadcom iProc I2C controller. | |
382 | ||
383 | If you don't know what to do here, say N. | |
384 | ||
93d17247 TK |
385 | config I2C_BCM_KONA |
386 | tristate "BCM Kona I2C adapter" | |
387 | depends on ARCH_BCM_MOBILE | |
388 | default y | |
389 | help | |
390 | If you say yes to this option, support will be included for the | |
391 | I2C interface on the Broadcom Kona family of processors. | |
392 | ||
f54619f2 | 393 | If you do not need KONA I2C interface, say N. |
93d17247 | 394 | |
f5b728a1 JD |
395 | config I2C_BLACKFIN_TWI |
396 | tristate "Blackfin TWI I2C support" | |
397 | depends on BLACKFIN | |
398 | depends on !BF561 && !BF531 && !BF532 && !BF533 | |
399 | help | |
400 | This is the I2C bus driver for Blackfin on-chip TWI interface. | |
401 | ||
402 | This driver can also be built as a module. If so, the module | |
403 | will be called i2c-bfin-twi. | |
404 | ||
405 | config I2C_BLACKFIN_TWI_CLK_KHZ | |
406 | int "Blackfin TWI I2C clock (kHz)" | |
407 | depends on I2C_BLACKFIN_TWI | |
9528d1c7 | 408 | range 21 400 |
f5b728a1 JD |
409 | default 50 |
410 | help | |
411 | The unit of the TWI clock is kHz. | |
412 | ||
df8eb569 SB |
413 | config I2C_CADENCE |
414 | tristate "Cadence I2C Controller" | |
1fbeab0b | 415 | depends on ARCH_ZYNQ |
df8eb569 SB |
416 | help |
417 | Say yes here to select Cadence I2C Host Controller. This controller is | |
418 | e.g. used by Xilinx Zynq. | |
419 | ||
0857ba3c AK |
420 | config I2C_CBUS_GPIO |
421 | tristate "CBUS I2C driver" | |
76ec9d18 | 422 | depends on GPIOLIB |
0857ba3c AK |
423 | help |
424 | Support for CBUS access using I2C API. Mostly relevant for Nokia | |
425 | Internet Tablets (770, N800 and N810). | |
426 | ||
427 | This driver can also be built as a module. If so, the module | |
428 | will be called i2c-cbus-gpio. | |
429 | ||
61045dbe JF |
430 | config I2C_CPM |
431 | tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" | |
62c19c9d | 432 | depends on CPM1 || CPM2 |
61045dbe JF |
433 | help |
434 | This supports the use of the I2C interface on Freescale | |
435 | processors with CPM1 or CPM2. | |
436 | ||
437 | This driver can also be built as a module. If so, the module | |
438 | will be called i2c-cpm. | |
439 | ||
f5b728a1 JD |
440 | config I2C_DAVINCI |
441 | tristate "DaVinci I2C driver" | |
d654b548 | 442 | depends on ARCH_DAVINCI || ARCH_KEYSTONE |
f5b728a1 JD |
443 | help |
444 | Support for TI DaVinci I2C controller driver. | |
445 | ||
446 | This driver can also be built as a module. If so, the module | |
447 | will be called i2c-davinci. | |
448 | ||
449 | Please note that this driver might be needed to bring up other | |
450 | devices such as DaVinci NIC. | |
451 | For details please see http://www.ti.com/davinci | |
452 | ||
e68bb91b AL |
453 | config I2C_DESIGNWARE_CORE |
454 | tristate | |
455 | ||
2373f6b9 | 456 | config I2C_DESIGNWARE_PLATFORM |
6b2aac42 | 457 | tristate "Synopsys DesignWare Platform" |
e68bb91b | 458 | select I2C_DESIGNWARE_CORE |
a445900c | 459 | depends on (ACPI && COMMON_CLK) || !ACPI |
1ab52cf9 BS |
460 | help |
461 | If you say yes to this option, support will be included for the | |
462 | Synopsys DesignWare I2C adapter. Only master mode is supported. | |
463 | ||
464 | This driver can also be built as a module. If so, the module | |
2373f6b9 | 465 | will be called i2c-designware-platform. |
1ab52cf9 | 466 | |
fe20ff5c DB |
467 | config I2C_DESIGNWARE_PCI |
468 | tristate "Synopsys DesignWare PCI" | |
469 | depends on PCI | |
e68bb91b | 470 | select I2C_DESIGNWARE_CORE |
fe20ff5c DB |
471 | help |
472 | If you say yes to this option, support will be included for the | |
473 | Synopsys DesignWare I2C adapter. Only master mode is supported. | |
474 | ||
475 | This driver can also be built as a module. If so, the module | |
476 | will be called i2c-designware-pci. | |
1ab52cf9 | 477 | |
894acb2f DB |
478 | config I2C_DESIGNWARE_BAYTRAIL |
479 | bool "Intel Baytrail I2C semaphore support" | |
b4ad0510 | 480 | depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI |
894acb2f DB |
481 | help |
482 | This driver enables managed host access to the PMIC I2C bus on select | |
483 | Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows | |
484 | the host to request uninterrupted access to the PMIC's I2C bus from | |
485 | the platform firmware controlling it. You should say Y if running on | |
486 | a BayTrail system using the AXP288. | |
487 | ||
4a7a0822 BS |
488 | config I2C_DIGICOLOR |
489 | tristate "Conexant Digicolor I2C driver" | |
490 | depends on ARCH_DIGICOLOR | |
491 | help | |
492 | Support for Conexant Digicolor SoCs (CX92755) I2C controller driver. | |
493 | ||
494 | This driver can also be built as a module. If so, the module | |
495 | will be called i2c-digicolor. | |
496 | ||
1b5b2371 UKK |
497 | config I2C_EFM32 |
498 | tristate "EFM32 I2C controller" | |
499 | depends on ARCH_EFM32 || COMPILE_TEST | |
500 | help | |
501 | This driver supports the i2c block found in Energy Micro's EFM32 | |
502 | SoCs. | |
503 | ||
3e1b76be J |
504 | config I2C_EG20T |
505 | tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" | |
fa96faaa | 506 | depends on PCI && (X86_32 || COMPILE_TEST) |
3e1b76be J |
507 | help |
508 | This driver is for PCH(Platform controller Hub) I2C of EG20T which | |
509 | is an IOH(Input/Output Hub) for x86 embedded processor. | |
510 | This driver can access PCH I2C bus device. | |
511 | ||
512 | This driver also can be used for LAPIS Semiconductor IOH(Input/ | |
513 | Output Hub), ML7213, ML7223 and ML7831. | |
514 | ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is | |
515 | for MP(Media Phone) use and ML7831 IOH is for general purpose use. | |
516 | ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. | |
517 | ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. | |
518 | ||
8a73cd4c NKC |
519 | config I2C_EXYNOS5 |
520 | tristate "Exynos5 high-speed I2C driver" | |
2374a539 | 521 | depends on ARCH_EXYNOS && OF |
741d3589 | 522 | default y |
8a73cd4c | 523 | help |
741d3589 | 524 | High-speed I2C controller on Exynos5 based Samsung SoCs. |
8a73cd4c | 525 | |
f5b728a1 JD |
526 | config I2C_GPIO |
527 | tristate "GPIO-based bitbanging I2C" | |
76ec9d18 | 528 | depends on GPIOLIB |
f5b728a1 JD |
529 | select I2C_ALGOBIT |
530 | help | |
531 | This is a very simple bitbanging I2C driver utilizing the | |
532 | arch-neutral GPIO API to control the SCL and SDA lines. | |
533 | ||
4ad48e6a PM |
534 | config I2C_HIGHLANDER |
535 | tristate "Highlander FPGA SMBus interface" | |
536 | depends on SH_HIGHLANDER | |
537 | help | |
538 | If you say yes to this option, support will be included for | |
539 | the SMBus interface located in the FPGA on various Highlander | |
540 | boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL | |
541 | FPGAs. This is wholly unrelated to the SoC I2C. | |
542 | ||
543 | This driver can also be built as a module. If so, the module | |
544 | will be called i2c-highlander. | |
545 | ||
f5b728a1 JD |
546 | config I2C_IBM_IIC |
547 | tristate "IBM PPC 4xx on-chip I2C interface" | |
548 | depends on 4xx | |
549 | help | |
550 | Say Y here if you want to use IIC peripheral found on | |
551 | embedded IBM PPC 4xx based systems. | |
552 | ||
553 | This driver can also be built as a module. If so, the module | |
554 | will be called i2c-ibm_iic. | |
555 | ||
27bce457 JH |
556 | config I2C_IMG |
557 | tristate "Imagination Technologies I2C SCB Controller" | |
06205206 | 558 | depends on MIPS || METAG || COMPILE_TEST |
27bce457 JH |
559 | help |
560 | Say Y here if you want to use the IMG I2C SCB controller, | |
06205206 | 561 | available on the TZ1090 and other IMG SoCs. |
27bce457 JH |
562 | |
563 | This driver can also be built as a module. If so, the module | |
564 | will be called i2c-img-scb. | |
565 | ||
aa11e38c DA |
566 | config I2C_IMX |
567 | tristate "IMX I2C interface" | |
568 | depends on ARCH_MXC | |
569 | help | |
570 | Say Y here if you want to use the IIC bus controller on | |
571 | the Freescale i.MX/MXC processors. | |
572 | ||
573 | This driver can also be built as a module. If so, the module | |
574 | will be called i2c-imx. | |
575 | ||
f5b728a1 JD |
576 | config I2C_IOP3XX |
577 | tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" | |
578 | depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX | |
579 | help | |
580 | Say Y here if you want to use the IIC bus controller on | |
581 | the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. | |
582 | ||
583 | This driver can also be built as a module. If so, the module | |
584 | will be called i2c-iop3xx. | |
585 | ||
ba92222e ZLK |
586 | config I2C_JZ4780 |
587 | tristate "JZ4780 I2C controller interface support" | |
588 | depends on MACH_JZ4780 || COMPILE_TEST | |
589 | help | |
590 | If you say yes to this option, support will be included for the | |
591 | Ingenic JZ4780 I2C controller. | |
592 | ||
593 | If you don't know what to do here, say N. | |
594 | ||
e0b9b7b0 KS |
595 | config I2C_KEMPLD |
596 | tristate "Kontron COM I2C Controller" | |
597 | depends on MFD_KEMPLD | |
598 | help | |
599 | This enables support for the I2C bus interface on some Kontron ETX | |
600 | and COMexpress (ETXexpress) modules. | |
601 | ||
602 | This driver can also be built as a module. If so, the module | |
603 | will be called i2c-kempld. | |
604 | ||
30021e37 BG |
605 | config I2C_MESON |
606 | tristate "Amlogic Meson I2C controller" | |
607 | depends on ARCH_MESON | |
608 | help | |
609 | If you say yes to this option, support will be included for the | |
610 | I2C interface on the Amlogic Meson family of SoCs. | |
611 | ||
f5b728a1 | 612 | config I2C_MPC |
f00d738f | 613 | tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" |
0724d464 | 614 | depends on PPC |
f5b728a1 JD |
615 | help |
616 | If you say yes to this option, support will be included for the | |
f00d738f WG |
617 | built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, |
618 | MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. | |
f5b728a1 JD |
619 | |
620 | This driver can also be built as a module. If so, the module | |
621 | will be called i2c-mpc. | |
622 | ||
623 | config I2C_MV64XXX | |
624 | tristate "Marvell mv64xxx I2C Controller" | |
80c69915 | 625 | depends on MV64X60 || PLAT_ORION || ARCH_SUNXI |
f5b728a1 JD |
626 | help |
627 | If you say yes to this option, support will be included for the | |
628 | built-in I2C interface on the Marvell 64xxx line of host bridges. | |
3d66ac7d | 629 | This driver is also used for Allwinner SoCs I2C controllers. |
f5b728a1 JD |
630 | |
631 | This driver can also be built as a module. If so, the module | |
632 | will be called i2c-mv64xxx. | |
633 | ||
a8da7fec WS |
634 | config I2C_MXS |
635 | tristate "Freescale i.MX28 I2C interface" | |
636 | depends on SOC_IMX28 | |
6b866c15 | 637 | select STMP_DEVICE |
a8da7fec WS |
638 | help |
639 | Say Y here if you want to use the I2C bus controller on | |
640 | the Freescale i.MX28 processors. | |
641 | ||
642 | This driver can also be built as a module. If so, the module | |
643 | will be called i2c-mxs. | |
644 | ||
3f9900f1 | 645 | config I2C_NOMADIK |
646 | tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" | |
419408ed | 647 | depends on ARM_AMBA |
3f9900f1 | 648 | help |
649 | If you say yes to this option, support will be included for the | |
419408ed AR |
650 | I2C interface from ST-Ericsson's Nomadik and Ux500 architectures, |
651 | as well as the STA2X11 PCIe I/O HUB. | |
3f9900f1 | 652 | |
f5b728a1 JD |
653 | config I2C_OCORES |
654 | tristate "OpenCores I2C Controller" | |
f5b728a1 JD |
655 | help |
656 | If you say yes to this option, support will be included for the | |
657 | OpenCores I2C controller. For details see | |
658 | http://www.opencores.org/projects.cgi/web/i2c/overview | |
659 | ||
660 | This driver can also be built as a module. If so, the module | |
661 | will be called i2c-ocores. | |
662 | ||
663 | config I2C_OMAP | |
664 | tristate "OMAP I2C adapter" | |
665 | depends on ARCH_OMAP | |
666 | default y if MACH_OMAP_H3 || MACH_OMAP_OSK | |
667 | help | |
668 | If you say yes to this option, support will be included for the | |
669 | I2C interface on the Texas Instruments OMAP1/2 family of processors. | |
670 | Like OMAP1510/1610/1710/5912 and OMAP242x. | |
671 | For details see http://www.ti.com/omap. | |
1da177e4 | 672 | |
beb58aa3 OJ |
673 | config I2C_PASEMI |
674 | tristate "PA Semi SMBus interface" | |
16538e6b | 675 | depends on PPC_PASEMI && PCI |
beb58aa3 OJ |
676 | help |
677 | Supports the PA Semi PWRficient on-chip SMBus interfaces. | |
678 | ||
35bfc353 WS |
679 | config I2C_PCA_PLATFORM |
680 | tristate "PCA9564/PCA9665 as platform device" | |
681 | select I2C_ALGOPCA | |
682 | default n | |
683 | help | |
684 | This driver supports a memory mapped Philips PCA9564/PCA9665 | |
685 | parallel bus to I2C bus controller. | |
686 | ||
687 | This driver can also be built as a module. If so, the module | |
688 | will be called i2c-pca-platform. | |
689 | ||
690 | config I2C_PMCMSP | |
691 | tristate "PMC MSP I2C TWI Controller" | |
692 | depends on PMC_MSP | |
693 | help | |
694 | This driver supports the PMC TWI controller on MSP devices. | |
695 | ||
696 | This driver can also be built as module. If so, the module | |
697 | will be called i2c-pmcmsp. | |
698 | ||
f5b728a1 | 699 | config I2C_PNX |
c115167a | 700 | tristate "I2C bus support for Philips PNX and NXP LPC targets" |
d684f05f | 701 | depends on ARCH_LPC32XX |
f5b728a1 JD |
702 | help |
703 | This driver supports the Philips IP3204 I2C IP block master and/or | |
704 | slave controller | |
705 | ||
706 | This driver can also be built as a module. If so, the module | |
707 | will be called i2c-pnx. | |
708 | ||
d10e4a66 G |
709 | config I2C_PUV3 |
710 | tristate "PKUnity v3 I2C bus support" | |
711 | depends on UNICORE32 && ARCH_PUV3 | |
712 | select I2C_ALGOBIT | |
713 | help | |
714 | This driver supports the I2C IP inside the PKUnity-v3 SoC. | |
715 | This I2C bus controller is under AMBA/AXI bus. | |
716 | ||
717 | This driver can also be built as a module. If so, the module | |
718 | will be called i2c-puv3. | |
719 | ||
f5b728a1 | 720 | config I2C_PXA |
d7c46ddd | 721 | tristate "Intel PXA2XX I2C adapter" |
7e94dd15 | 722 | depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF) |
f5b728a1 JD |
723 | help |
724 | If you have devices in the PXA I2C bus, say yes to this option. | |
725 | This driver can also be built as a module. If so, the module | |
726 | will be called i2c-pxa. | |
727 | ||
7e94dd15 SAS |
728 | config I2C_PXA_PCI |
729 | def_bool I2C_PXA && X86_32 && PCI && OF | |
730 | ||
f5b728a1 JD |
731 | config I2C_PXA_SLAVE |
732 | bool "Intel PXA2XX I2C Slave comms support" | |
7e94dd15 | 733 | depends on I2C_PXA && !X86_32 |
f5b728a1 JD |
734 | help |
735 | Support I2C slave mode communications on the PXA I2C bus. This | |
736 | is necessary for systems where the PXA may be a target on the | |
737 | I2C bus. | |
738 | ||
10c5a842 BA |
739 | config I2C_QUP |
740 | tristate "Qualcomm QUP based I2C controller" | |
741 | depends on ARCH_QCOM | |
742 | help | |
743 | If you say yes to this option, support will be included for the | |
744 | built-in I2C interface on the Qualcomm SoCs. | |
745 | ||
746 | This driver can also be built as a module. If so, the module | |
747 | will be called i2c-qup. | |
748 | ||
310c18a4 WS |
749 | config I2C_RIIC |
750 | tristate "Renesas RIIC adapter" | |
751 | depends on ARCH_SHMOBILE || COMPILE_TEST | |
752 | help | |
753 | If you say yes to this option, support will be included for the | |
754 | Renesas RIIC I2C interface. | |
755 | ||
756 | This driver can also be built as a module. If so, the module | |
757 | will be called i2c-riic. | |
758 | ||
c41aa3ce MS |
759 | config I2C_RK3X |
760 | tristate "Rockchip RK3xxx I2C adapter" | |
80f1774f | 761 | depends on OF && COMMON_CLK |
c41aa3ce MS |
762 | help |
763 | Say Y here to include support for the I2C adapter in Rockchip RK3xxx | |
764 | SoCs. | |
765 | ||
766 | This driver can also be built as a module. If so, the module will | |
767 | be called i2c-rk3x. | |
768 | ||
4b623926 NKC |
769 | config HAVE_S3C2410_I2C |
770 | bool | |
771 | help | |
772 | This will include I2C support for Samsung SoCs. If you want to | |
773 | include I2C support for any machine, kindly select this in the | |
774 | respective Kconfig file. | |
775 | ||
1da177e4 LT |
776 | config I2C_S3C2410 |
777 | tristate "S3C2410 I2C Driver" | |
4b623926 | 778 | depends on HAVE_S3C2410_I2C |
1da177e4 LT |
779 | help |
780 | Say Y here to include support for I2C controller in the | |
4b623926 | 781 | Samsung SoCs. |
1da177e4 | 782 | |
f5b728a1 JD |
783 | config I2C_SH7760 |
784 | tristate "Renesas SH7760 I2C Controller" | |
785 | depends on CPU_SUBTYPE_SH7760 | |
1da177e4 | 786 | help |
f5b728a1 JD |
787 | This driver supports the 2 I2C interfaces on the Renesas SH7760. |
788 | ||
789 | This driver can also be built as a module. If so, the module | |
790 | will be called i2c-sh7760. | |
791 | ||
792 | config I2C_SH_MOBILE | |
793 | tristate "SuperH Mobile I2C Controller" | |
f16ea4f0 | 794 | depends on HAS_DMA |
46a4e737 | 795 | depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST |
f5b728a1 JD |
796 | help |
797 | If you say yes to this option, support will be included for the | |
798 | built-in I2C interface on the Renesas SH-Mobile processor. | |
799 | ||
800 | This driver can also be built as a module. If so, the module | |
801 | will be called i2c-sh_mobile. | |
1da177e4 | 802 | |
bcda9f1e BD |
803 | config I2C_SIMTEC |
804 | tristate "Simtec Generic I2C interface" | |
805 | select I2C_ALGOBIT | |
806 | help | |
01dd2fbf | 807 | If you say yes to this option, support will be included for |
bcda9f1e BD |
808 | the Simtec Generic I2C interface. This driver is for the |
809 | simple I2C bus used on newer Simtec products for general | |
810 | I2C, such as DDC on the Simtec BBD2016A. | |
811 | ||
01dd2fbf | 812 | This driver can also be built as a module. If so, the module |
bcda9f1e BD |
813 | will be called i2c-simtec. |
814 | ||
979b907f ZS |
815 | config I2C_SIRF |
816 | tristate "CSR SiRFprimaII I2C interface" | |
c5dece37 | 817 | depends on ARCH_SIRF |
979b907f ZS |
818 | help |
819 | If you say yes to this option, support will be included for the | |
820 | CSR SiRFprimaII I2C interface. | |
821 | ||
822 | This driver can also be built as a module. If so, the module | |
823 | will be called i2c-sirf. | |
824 | ||
85b4fab2 MC |
825 | config I2C_ST |
826 | tristate "STMicroelectronics SSC I2C support" | |
827 | depends on ARCH_STI | |
828 | help | |
829 | Enable this option to add support for STMicroelectronics SoCs | |
830 | hardware SSC (Synchronous Serial Controller) as an I2C controller. | |
831 | ||
832 | This driver can also be built as module. If so, the module | |
833 | will be called i2c-st. | |
834 | ||
18904c0e LW |
835 | config I2C_STU300 |
836 | tristate "ST Microelectronics DDC I2C interface" | |
4eaad8ad | 837 | depends on MACH_U300 |
18904c0e LW |
838 | default y if MACH_U300 |
839 | help | |
840 | If you say yes to this option, support will be included for the | |
841 | I2C interface from ST Microelectronics simply called "DDC I2C" | |
842 | supporting both I2C and DDC, used in e.g. the U300 series | |
843 | mobile platforms. | |
844 | ||
845 | This driver can also be built as a module. If so, the module | |
846 | will be called i2c-stu300. | |
847 | ||
3e833490 BB |
848 | config I2C_SUN6I_P2WI |
849 | tristate "Allwinner sun6i internal P2WI controller" | |
850 | depends on RESET_CONTROLLER | |
851 | depends on MACH_SUN6I || COMPILE_TEST | |
852 | help | |
853 | If you say yes to this option, support will be included for the | |
854 | P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi | |
855 | SOCs. | |
856 | The P2WI looks like an SMBus controller (which supports only byte | |
857 | accesses), except that it only supports one slave device. | |
858 | This interface is used to connect to specific PMIC devices (like the | |
859 | AXP221). | |
860 | ||
db811ca0 CC |
861 | config I2C_TEGRA |
862 | tristate "NVIDIA Tegra internal I2C controller" | |
863 | depends on ARCH_TEGRA | |
864 | help | |
865 | If you say yes to this option, support will be included for the | |
866 | I2C controller embedded in NVIDIA Tegra SOCs | |
867 | ||
f5b728a1 JD |
868 | config I2C_VERSATILE |
869 | tristate "ARM Versatile/Realview I2C bus support" | |
ceade897 | 870 | depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS |
1da177e4 LT |
871 | select I2C_ALGOBIT |
872 | help | |
f5b728a1 JD |
873 | Say yes if you want to support the I2C serial bus on ARMs Versatile |
874 | range of platforms. | |
1da177e4 | 875 | |
f5b728a1 JD |
876 | This driver can also be built as a module. If so, the module |
877 | will be called i2c-versatile. | |
1da177e4 | 878 | |
560746eb TP |
879 | config I2C_WMT |
880 | tristate "Wondermedia WM8xxx SoC I2C bus support" | |
881 | depends on ARCH_VT8500 | |
882 | help | |
883 | Say yes if you want to support the I2C bus on Wondermedia 8xxx-series | |
884 | SoCs. | |
885 | ||
886 | This driver can also be built as a module. If so, the module will be | |
887 | called i2c-wmt. | |
888 | ||
85660f43 RB |
889 | config I2C_OCTEON |
890 | tristate "Cavium OCTEON I2C bus support" | |
9ddebc46 | 891 | depends on CAVIUM_OCTEON_SOC |
85660f43 RB |
892 | help |
893 | Say yes if you want to support the I2C serial bus on Cavium | |
894 | OCTEON SOC. | |
895 | ||
896 | This driver can also be built as a module. If so, the module | |
897 | will be called i2c-octeon. | |
898 | ||
e1d5b659 RR |
899 | config I2C_XILINX |
900 | tristate "Xilinx I2C Controller" | |
417e86ce | 901 | depends on HAS_IOMEM |
e1d5b659 RR |
902 | help |
903 | If you say yes to this option, support will be included for the | |
904 | Xilinx I2C controller. | |
905 | ||
906 | This driver can also be built as a module. If so, the module | |
907 | will be called xilinx_i2c. | |
908 | ||
401c3434 GR |
909 | config I2C_XLR |
910 | tristate "XLR I2C support" | |
911 | depends on CPU_XLR | |
912 | help | |
913 | This driver enables support for the on-chip I2C interface of | |
914 | the Netlogic XLR/XLS MIPS processors. | |
915 | ||
916 | This driver can also be built as a module. If so, the module | |
917 | will be called i2c-xlr. | |
918 | ||
2bbd681b SSB |
919 | config I2C_XLP9XX |
920 | tristate "XLP9XX I2C support" | |
921 | depends on CPU_XLP || COMPILE_TEST | |
922 | help | |
923 | This driver enables support for the on-chip I2C interface of | |
924 | the Broadcom XLP9xx/XLP5xx MIPS processors. | |
925 | ||
926 | This driver can also be built as a module. If so, the module will | |
927 | be called i2c-xlp9xx. | |
928 | ||
6ccbe607 KM |
929 | config I2C_RCAR |
930 | tristate "Renesas R-Car I2C Controller" | |
46a4e737 | 931 | depends on ARCH_SHMOBILE || COMPILE_TEST |
d5fd120e | 932 | select I2C_SLAVE |
6ccbe607 KM |
933 | help |
934 | If you say yes to this option, support will be included for the | |
935 | R-Car I2C controller. | |
936 | ||
937 | This driver can also be built as a module. If so, the module | |
938 | will be called i2c-rcar. | |
939 | ||
f5b728a1 | 940 | comment "External I2C/SMBus adapter drivers" |
11de70bd | 941 | |
335d7c58 GR |
942 | config I2C_DIOLAN_U2C |
943 | tristate "Diolan U2C-12 USB adapter" | |
944 | depends on USB | |
945 | help | |
946 | If you say yes to this option, support will be included for Diolan | |
947 | U2C-12, a USB to I2C interface. | |
948 | ||
949 | This driver can also be built as a module. If so, the module | |
950 | will be called i2c-diolan-u2c. | |
951 | ||
db23e500 LP |
952 | config I2C_DLN2 |
953 | tristate "Diolan DLN-2 USB I2C adapter" | |
954 | depends on MFD_DLN2 | |
955 | help | |
956 | If you say yes to this option, support will be included for Diolan | |
957 | DLN2, a USB to I2C interface. | |
958 | ||
959 | This driver can also be built as a module. If so, the module | |
960 | will be called i2c-dln2. | |
961 | ||
f5b728a1 JD |
962 | config I2C_PARPORT |
963 | tristate "Parallel port adapter" | |
0244ad00 | 964 | depends on PARPORT |
f5b728a1 | 965 | select I2C_ALGOBIT |
35859254 | 966 | select I2C_SMBUS |
1da177e4 | 967 | help |
f5b728a1 JD |
968 | This supports parallel port I2C adapters such as the ones made by |
969 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
970 | Basically any adapter using the parallel port as an I2C bus with | |
971 | no extra chipset is supported by this driver, or could be. | |
1da177e4 | 972 | |
f5b728a1 JD |
973 | This driver is a replacement for (and was inspired by) an older |
974 | driver named i2c-philips-par. The new driver supports more devices, | |
975 | and makes it easier to add support for new devices. | |
1da177e4 | 976 | |
f5b728a1 JD |
977 | An adapter type parameter is now mandatory. Please read the file |
978 | Documentation/i2c/busses/i2c-parport for details. | |
1da177e4 | 979 | |
f5b728a1 JD |
980 | Another driver exists, named i2c-parport-light, which doesn't depend |
981 | on the parport driver. This is meant for embedded systems. Don't say | |
982 | Y here if you intend to say Y or M there. | |
1da177e4 | 983 | |
4c03f68f | 984 | This support is also available as a module. If so, the module |
f5b728a1 | 985 | will be called i2c-parport. |
1da177e4 | 986 | |
f5b728a1 JD |
987 | config I2C_PARPORT_LIGHT |
988 | tristate "Parallel port adapter (light)" | |
989 | select I2C_ALGOBIT | |
927ab2f8 | 990 | select I2C_SMBUS |
1da177e4 | 991 | help |
f5b728a1 JD |
992 | This supports parallel port I2C adapters such as the ones made by |
993 | Philips or Velleman, Analog Devices evaluation boards, and more. | |
994 | Basically any adapter using the parallel port as an I2C bus with | |
995 | no extra chipset is supported by this driver, or could be. | |
1da177e4 | 996 | |
f5b728a1 JD |
997 | This driver is a light version of i2c-parport. It doesn't depend |
998 | on the parport driver, and uses direct I/O access instead. This | |
999 | might be preferred on embedded systems where wasting memory for | |
1000 | the clean but heavy parport handling is not an option. The | |
1001 | drawback is a reduced portability and the impossibility to | |
1002 | daisy-chain other parallel port devices. | |
1da177e4 | 1003 | |
f5b728a1 JD |
1004 | Don't say Y here if you said Y or M to i2c-parport. Saying M to |
1005 | both is possible but both modules should not be loaded at the same | |
1006 | time. | |
1da177e4 | 1007 | |
f5b728a1 JD |
1008 | This support is also available as a module. If so, the module |
1009 | will be called i2c-parport-light. | |
1da177e4 | 1010 | |
83e53a8f AL |
1011 | config I2C_ROBOTFUZZ_OSIF |
1012 | tristate "RobotFuzz Open Source InterFace USB adapter" | |
1013 | depends on USB | |
1014 | help | |
1015 | If you say yes to this option, support will be included for the | |
1016 | RobotFuzz Open Source InterFace USB to I2C interface. | |
1017 | ||
1018 | This driver can also be built as a module. If so, the module | |
1019 | will be called i2c-osif. | |
1020 | ||
b9cdad74 JD |
1021 | config I2C_TAOS_EVM |
1022 | tristate "TAOS evaluation module" | |
21eaab6d | 1023 | depends on TTY |
b9cdad74 JD |
1024 | select SERIO |
1025 | select SERIO_SERPORT | |
1026 | default n | |
1027 | help | |
1028 | This supports TAOS evaluation modules on serial port. In order to | |
1029 | use this driver, you will need the inputattach tool, which is part | |
1030 | of the input-utils package. | |
1031 | ||
1032 | If unsure, say N. | |
1033 | ||
1034 | This support is also available as a module. If so, the module | |
1035 | will be called i2c-taos-evm. | |
1036 | ||
e8c76eed | 1037 | config I2C_TINY_USB |
f5b728a1 | 1038 | tristate "Tiny-USB adapter" |
e8c76eed TH |
1039 | depends on USB |
1040 | help | |
1041 | If you say yes to this option, support will be included for the | |
1042 | i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See | |
1043 | http://www.harbaum.org/till/i2c_tiny_usb for hardware details. | |
1044 | ||
1045 | This driver can also be built as a module. If so, the module | |
1046 | will be called i2c-tiny-usb. | |
1047 | ||
174a13aa LP |
1048 | config I2C_VIPERBOARD |
1049 | tristate "Viperboard I2C master support" | |
1050 | depends on MFD_VIPERBOARD && USB | |
1051 | help | |
1052 | Say yes here to access the I2C part of the Nano River | |
1053 | Technologies Viperboard as I2C master. | |
1054 | See viperboard API specification and Nano | |
1055 | River Tech's viperboard.h for detailed meaning | |
1056 | of the module parameters. | |
1057 | ||
f5b728a1 | 1058 | comment "Other I2C/SMBus bus drivers" |
6b65cd74 | 1059 | |
8d91cbad | 1060 | config I2C_ACORN |
2a9915c8 | 1061 | tristate "Acorn IOC/IOMD I2C bus support" |
16538e6b | 1062 | depends on ARCH_ACORN |
8d91cbad RK |
1063 | default y |
1064 | select I2C_ALGOBIT | |
1065 | help | |
1066 | Say yes if you want to support the I2C bus on Acorn platforms. | |
1067 | ||
1068 | If you don't know, say Y. | |
1069 | ||
f5b728a1 JD |
1070 | config I2C_ELEKTOR |
1071 | tristate "Elektor ISA card" | |
ce816fa8 | 1072 | depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP |
f5b728a1 | 1073 | select I2C_ALGOPCF |
1da177e4 | 1074 | help |
f5b728a1 JD |
1075 | This supports the PCF8584 ISA bus I2C adapter. Say Y if you own |
1076 | such an adapter. | |
1da177e4 | 1077 | |
f5b728a1 JD |
1078 | This support is also available as a module. If so, the module |
1079 | will be called i2c-elektor. | |
1da177e4 LT |
1080 | |
1081 | config I2C_PCA_ISA | |
eff9ec95 | 1082 | tristate "PCA9564/PCA9665 on an ISA bus" |
16538e6b | 1083 | depends on ISA |
1da177e4 | 1084 | select I2C_ALGOPCA |
aee62305 | 1085 | default n |
1da177e4 | 1086 | help |
eff9ec95 | 1087 | This driver supports ISA boards using the Philips PCA9564/PCA9665 |
244fbbb8 | 1088 | parallel bus to I2C bus controller. |
4c03f68f | 1089 | |
1da177e4 LT |
1090 | This driver can also be built as a module. If so, the module |
1091 | will be called i2c-pca-isa. | |
1092 | ||
aee62305 JD |
1093 | This device is almost undetectable and using this driver on a |
1094 | system which doesn't have this device will result in long | |
1095 | delays when I2C/SMBus chip drivers are loaded (e.g. at boot | |
1096 | time). If unsure, say N. | |
1097 | ||
f5b728a1 JD |
1098 | config I2C_SIBYTE |
1099 | tristate "SiByte SMBus interface" | |
1100 | depends on SIBYTE_SB1xxx_SOC | |
a26c20b1 | 1101 | help |
f5b728a1 | 1102 | Supports the SiByte SOC on-chip I2C interfaces (2 channels). |
a26c20b1 | 1103 | |
9d230c9e DA |
1104 | config I2C_CROS_EC_TUNNEL |
1105 | tristate "ChromeOS EC tunnel I2C bus" | |
1106 | depends on MFD_CROS_EC | |
1107 | help | |
1108 | If you say yes here you get an I2C bus that will tunnel i2c commands | |
1109 | through to the other side of the ChromeOS EC to the i2c bus | |
1110 | connected there. This will work whatever the interface used to | |
1111 | talk to the EC (SPI, I2C or LPC). | |
1112 | ||
f5b728a1 JD |
1113 | config SCx200_ACB |
1114 | tristate "Geode ACCESS.bus support" | |
1115 | depends on X86_32 && PCI | |
1116 | help | |
1117 | Enable the use of the ACCESS.bus controllers on the Geode SCx200 and | |
1118 | SC1100 processors and the CS5535 and CS5536 Geode companion devices. | |
1119 | ||
1120 | If you don't know what to do here, say N. | |
1121 | ||
1122 | This support is also available as a module. If so, the module | |
1123 | will be called scx200_acb. | |
da672773 | 1124 | |
47083450 NG |
1125 | config I2C_OPAL |
1126 | tristate "IBM OPAL I2C driver" | |
1127 | depends on PPC_POWERNV | |
1128 | default y | |
1129 | help | |
1130 | This exposes the PowerNV platform i2c busses to the linux i2c layer, | |
1131 | the driver is based on the OPAL interfaces. | |
1132 | ||
1133 | This driver can also be built as a module. If so, the module will be | |
1134 | called as i2c-opal. | |
1135 | ||
1da177e4 | 1136 | endmenu |