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