2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
11 If you say yes to this option, support will be included for the SMB
12 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
13 controller is part of the 7101 device, which is an ACPI-compliant
14 Power Management Unit (PMU).
16 This driver can also be built as a module. If so, the module
17 will be called i2c-ali1535.
21 depends on PCI && EXPERIMENTAL
23 If you say yes to this option, support will be included for the SMB
24 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
25 controller is part of the 7101 device, which is an ACPI-compliant
26 Power Management Unit (PMU).
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1563.
35 If you say yes to this option, support will be included for the
36 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
38 This driver can also be built as a module. If so, the module
39 will be called i2c-ali15x3.
42 tristate "AMD 756/766/768/8111 and nVidia nForce"
45 If you say yes to this option, support will be included for the AMD
46 756/766/768 mainboard I2C interfaces. The driver also includes
47 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
48 the nVidia nForce I2C interface.
50 This driver can also be built as a module. If so, the module
51 will be called i2c-amd756.
53 config I2C_AMD756_S4882
54 tristate "SMBus multiplexing on the Tyan S4882"
55 depends on I2C_AMD756 && EXPERIMENTAL
57 Enabling this option will add specific SMBus support for the Tyan
58 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
59 over 8 different channels, where the various memory module EEPROMs
60 and temperature sensors live. Saying yes here will give you access
61 to these in addition to the trunk.
63 This driver can also be built as a module. If so, the module
64 will be called i2c-amd756-s4882.
70 If you say yes to this option, support will be included for the
71 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
73 This driver can also be built as a module. If so, the module
74 will be called i2c-amd8111.
77 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
78 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
80 This supports the use of the I2C interface on Atmel AT91
83 This driver is BROKEN because the controller which it uses
84 will easily trigger RX overrun and TX underrun errors. Using
85 low I2C clock rates may partially work around those issues
86 on some systems. Another serious problem is that there is no
87 documented way to issue repeated START conditions, as needed
88 to support combined I2C messages. Use the i2c-gpio driver
89 unless your system can cope with those limitations.
92 tristate "Au1550/Au1200 SMBus interface"
93 depends on SOC_AU1550 || SOC_AU1200
95 If you say yes to this option, support will be included for the
96 Au1550 and Au1200 SMBus interface.
98 This driver can also be built as a module. If so, the module
99 will be called i2c-au1550.
101 config I2C_BLACKFIN_TWI
102 tristate "Blackfin TWI I2C support"
103 depends on BF534 || BF536 || BF537
105 This is the TWI I2C device driver for Blackfin 534/536/537/54x.
106 This driver can also be built as a module. If so, the module
107 will be called i2c-bfin-twi.
109 config I2C_BLACKFIN_TWI_CLK_KHZ
110 int "Blackfin TWI I2C clock (kHz)"
111 depends on I2C_BLACKFIN_TWI
115 The unit of the TWI clock is kHz.
118 tristate "DaVinci I2C driver"
119 depends on ARCH_DAVINCI
121 Support for TI DaVinci I2C controller driver.
123 This driver can also be built as a module. If so, the module
124 will be called i2c-davinci.
126 Please note that this driver might be needed to bring up other
127 devices such as DaVinci NIC.
128 For details please see http://www.ti.com/davinci
131 tristate "Elektor ISA card"
132 depends on ISA && BROKEN_ON_SMP
135 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
138 This support is also available as a module. If so, the module
139 will be called i2c-elektor.
142 tristate "GPIO-based bitbanging I2C"
143 depends on GENERIC_GPIO
146 This is a very simple bitbanging I2C driver utilizing the
147 arch-neutral GPIO API to control the SCL and SDA lines.
150 tristate "CHRP Apple Hydra Mac I/O I2C interface"
151 depends on PCI && PPC_CHRP && EXPERIMENTAL
154 This supports the use of the I2C interface in the Apple Hydra Mac
155 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
158 This support is also available as a module. If so, the module
159 will be called i2c-hydra.
162 tristate "Intel 82801 (ICH)"
165 If you say yes to this option, support will be included for the Intel
166 801 family of mainboard I2C interfaces. Specifically, the following
167 versions of the chipset are supported:
173 82801EB/ER (ICH5/ICH5R)
183 This driver can also be built as a module. If so, the module
184 will be called i2c-i801.
187 tristate "Intel 810/815 (DEPRECATED)"
192 If you say yes to this option, support will be included for the Intel
193 810/815 family of mainboard I2C interfaces. Specifically, the
194 following versions of the chipset are supported:
201 This driver is deprecated in favor of the i810fb and intelfb drivers.
203 This driver can also be built as a module. If so, the module
204 will be called i2c-i810.
207 tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
208 depends on EXPERIMENTAL && ARCH_PXA
210 If you have devices in the PXA I2C bus, say yes to this option.
211 This driver can also be built as a module. If so, the module
212 will be called i2c-pxa.
215 bool "Intel PXA2XX I2C Slave comms support"
218 Support I2C slave mode communications on the PXA I2C bus. This
219 is necessary for systems where the PXA may be a target on the
223 tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
226 If you say yes to this option, support will be included for the Intel
227 PIIX4 family of mainboard I2C interfaces. Specifically, the following
228 versions of the chipset are supported (note that Serverworks is part
244 This driver can also be built as a module. If so, the module
245 will be called i2c-piix4.
248 tristate "IBM PPC 4xx on-chip I2C interface"
251 Say Y here if you want to use IIC peripheral found on
252 embedded IBM PPC 4xx based systems.
254 This driver can also be built as a module. If so, the module
255 will be called i2c-ibm_iic.
258 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
259 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
261 Say Y here if you want to use the IIC bus controller on
262 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
264 This driver can also be built as a module. If so, the module
265 will be called i2c-iop3xx.
268 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
269 depends on ARCH_IXP2000
272 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
273 system and are using GPIO lines for an I2C bus.
275 This support is also available as a module. If so, the module
276 will be called i2c-ixp2000.
278 This driver is deprecated and will be dropped soon. Use i2c-gpio
282 tristate "Powermac I2C interface"
286 This exposes the various PowerMac i2c interfaces to the linux i2c
287 layer and to userland. It is used by various drivers on the PowerMac
288 platform, and should generally be enabled.
290 This support is also available as a module. If so, the module
291 will be called i2c-powermac.
294 tristate "MPC107/824x/85xx/52xx/86xx"
297 If you say yes to this option, support will be included for the
298 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
299 MPC85xx/MPC8641 family processors. The driver may also work on 52xx
300 family processors, though interrupts are known not to work.
302 This driver can also be built as a module. If so, the module
303 will be called i2c-mpc.
306 tristate "Nvidia nForce2, nForce3 and nForce4"
309 If you say yes to this option, support will be included for the Nvidia
310 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
312 This driver can also be built as a module. If so, the module
313 will be called i2c-nforce2.
316 tristate "OpenCores I2C Controller"
317 depends on EXPERIMENTAL
319 If you say yes to this option, support will be included for the
320 OpenCores I2C controller. For details see
321 http://www.opencores.org/projects.cgi/web/i2c/overview
323 This driver can also be built as a module. If so, the module
324 will be called i2c-ocores.
327 tristate "OMAP I2C adapter"
329 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
331 If you say yes to this option, support will be included for the
332 I2C interface on the Texas Instruments OMAP1/2 family of processors.
333 Like OMAP1510/1610/1710/5912 and OMAP242x.
334 For details see http://www.ti.com/omap.
337 tristate "Parallel port adapter"
341 This supports parallel port I2C adapters such as the ones made by
342 Philips or Velleman, Analog Devices evaluation boards, and more.
343 Basically any adapter using the parallel port as an I2C bus with
344 no extra chipset is supported by this driver, or could be.
346 This driver is a replacement for (and was inspired by) an older
347 driver named i2c-philips-par. The new driver supports more devices,
348 and makes it easier to add support for new devices.
350 An adapter type parameter is now mandatory. Please read the file
351 Documentation/i2c/busses/i2c-parport for details.
353 Another driver exists, named i2c-parport-light, which doesn't depend
354 on the parport driver. This is meant for embedded systems. Don't say
355 Y here if you intend to say Y or M there.
357 This support is also available as a module. If so, the module
358 will be called i2c-parport.
360 config I2C_PARPORT_LIGHT
361 tristate "Parallel port adapter (light)"
364 This supports parallel port I2C adapters such as the ones made by
365 Philips or Velleman, Analog Devices evaluation boards, and more.
366 Basically any adapter using the parallel port as an I2C bus with
367 no extra chipset is supported by this driver, or could be.
369 This driver is a light version of i2c-parport. It doesn't depend
370 on the parport driver, and uses direct I/O access instead. This
371 might be preferred on embedded systems where wasting memory for
372 the clean but heavy parport handling is not an option. The
373 drawback is a reduced portability and the impossibility to
374 daisy-chain other parallel port devices.
376 Don't say Y here if you said Y or M to i2c-parport. Saying M to
377 both is possible but both modules should not be loaded at the same
380 This support is also available as a module. If so, the module
381 will be called i2c-parport-light.
384 tristate "PA Semi SMBus interface"
385 depends on PPC_PASEMI && PCI
387 Supports the PA Semi PWRficient on-chip SMBus interfaces.
390 tristate "S3/VIA (Pro)Savage (DEPRECATED)"
395 If you say yes to this option, support will be included for the
396 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
399 S3/VIA KM266/VT8375 aka ProSavage8
400 S3/VIA KM133/VT8365 aka Savage4
402 This driver is deprecated in favor of the savagefb driver.
404 This support is also available as a module. If so, the module
405 will be called i2c-prosavage.
408 tristate "S3C2410 I2C Driver"
409 depends on ARCH_S3C2410
411 Say Y here to include support for I2C controller in the
412 Samsung S3C2410 based System-on-Chip devices.
415 tristate "S3 Savage 4 (DEPRECATED)"
420 If you say yes to this option, support will be included for the
421 S3 Savage 4 I2C interface.
423 This driver is deprecated in favor of the savagefb driver.
425 This driver can also be built as a module. If so, the module
426 will be called i2c-savage4.
429 tristate "SiByte SMBus interface"
430 depends on SIBYTE_SB1xxx_SOC
432 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
435 tristate "Simtec Generic I2C interface"
438 If you say yes to this option, support will be included for
439 the Simtec Generic I2C interface. This driver is for the
440 simple I2C bus used on newer Simtec products for general
441 I2C, such as DDC on the Simtec BBD2016A.
443 This driver can also be built as a module. If so, the module
444 will be called i2c-simtec.
447 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
448 depends on SCx200_GPIO
451 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
453 If you don't know what to do here, say N.
455 This support is also available as a module. If so, the module
456 will be called scx200_i2c.
458 This driver is deprecated and will be dropped soon. Use i2c-gpio
459 (or scx200_acb) instead.
461 config SCx200_I2C_SCL
462 int "GPIO pin used for SCL"
463 depends on SCx200_I2C
466 Enter the GPIO pin number used for the SCL signal. This value can
467 also be specified with a module parameter.
469 config SCx200_I2C_SDA
470 int "GPIO pin used for SDA"
471 depends on SCx200_I2C
474 Enter the GPIO pin number used for the SSA signal. This value can
475 also be specified with a module parameter.
478 tristate "Geode ACCESS.bus support"
479 depends on X86_32 && PCI
481 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
482 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
484 If you don't know what to do here, say N.
486 This support is also available as a module. If so, the module
487 will be called scx200_acb.
493 If you say yes to this option, support will be included for the
494 SiS5595 SMBus (a subset of I2C) interface.
496 This driver can also be built as a module. If so, the module
497 will be called i2c-sis5595.
500 tristate "SiS 630/730"
503 If you say yes to this option, support will be included for the
504 SiS630 and SiS730 SMBus (a subset of I2C) interface.
506 This driver can also be built as a module. If so, the module
507 will be called i2c-sis630.
513 If you say yes to this option, support will be included for the SiS
514 96x SMBus (a subset of I2C) interfaces. Specifically, the following
515 chipsets are supported:
524 This driver can also be built as a module. If so, the module
525 will be called i2c-sis96x.
528 tristate "TAOS evaluation module"
529 depends on EXPERIMENTAL
534 This supports TAOS evaluation modules on serial port. In order to
535 use this driver, you will need the inputattach tool, which is part
536 of the input-utils package.
540 This support is also available as a module. If so, the module
541 will be called i2c-taos-evm.
544 tristate "I2C/SMBus Test Stub"
545 depends on EXPERIMENTAL && m
548 This module may be useful to developers of SMBus client drivers,
549 especially for certain kinds of sensor chips.
551 If you do build this module, be sure to read the notes and warnings
552 in <file:Documentation/i2c/i2c-stub>.
554 If you don't know what to do here, definitely say N.
557 tristate "I2C-Tiny-USB"
560 If you say yes to this option, support will be included for the
561 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
562 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
564 This driver can also be built as a module. If so, the module
565 will be called i2c-tiny-usb.
568 tristate "ARM Versatile/Realview I2C bus support"
569 depends on ARCH_VERSATILE || ARCH_REALVIEW
572 Say yes if you want to support the I2C serial bus on ARMs Versatile
575 This driver can also be built as a module. If so, the module
576 will be called i2c-versatile.
579 tristate "Acorn IOC/IOMD I2C bus support"
580 depends on ARCH_ACORN
584 Say yes if you want to support the I2C bus on Acorn platforms.
586 If you don't know, say Y.
589 tristate "VIA 82C586B"
590 depends on PCI && EXPERIMENTAL
593 If you say yes to this option, support will be included for the VIA
594 82C586B I2C interface
596 This driver can also be built as a module. If so, the module
597 will be called i2c-via.
600 tristate "VIA VT82C596/82C686/82xx and CX700"
603 If you say yes to this option, support will be included for the VIA
604 VT82C596 and later SMBus interface. Specifically, the following
605 chipsets are supported:
615 This driver can also be built as a module. If so, the module
616 will be called i2c-viapro.
623 If you say yes to this option, support will be included for the
624 Voodoo 3 I2C interface.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-voodoo3.
630 tristate "PCA9564 on an ISA bus"
635 This driver supports ISA boards using the Philips PCA9564
636 parallel bus to I2C bus controller.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-pca-isa.
641 This device is almost undetectable and using this driver on a
642 system which doesn't have this device will result in long
643 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
644 time). If unsure, say N.
646 config I2C_PCA_PLATFORM
647 tristate "PCA9564 as platform device"
651 This driver supports a memory mapped Philips PCA9564
652 parallel bus to I2C bus controller.
654 This driver can also be built as a module. If so, the module
655 will be called i2c-pca-platform.
658 tristate "Marvell mv64xxx I2C Controller"
659 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
661 If you say yes to this option, support will be included for the
662 built-in I2C interface on the Marvell 64xxx line of host bridges.
664 This driver can also be built as a module. If so, the module
665 will be called i2c-mv64xxx.
668 tristate "I2C bus support for Philips PNX targets"
669 depends on ARCH_PNX4008
671 This driver supports the Philips IP3204 I2C IP block master and/or
674 This driver can also be built as a module. If so, the module
675 will be called i2c-pnx.
678 tristate "PMC MSP I2C TWI Controller"
681 This driver supports the PMC TWI controller on MSP devices.
683 This driver can also be built as module. If so, the module
684 will be called i2c-pmcmsp.
687 tristate "Renesas SH7760 I2C Controller"
688 depends on CPU_SUBTYPE_SH7760
690 This driver supports the 2 I2C interfaces on the Renesas SH7760.
692 This driver can also be built as a module. If so, the module
693 will be called i2c-sh7760.