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