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