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