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