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