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