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