2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
7 comment "PC SMBus host controller drivers"
14 If you say yes to this option, support will be included for the SMB
15 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
16 controller is part of the 7101 device, which is an ACPI-compliant
17 Power Management Unit (PMU).
19 This driver can also be built as a module. If so, the module
20 will be called i2c-ali1535.
24 depends on PCI && EXPERIMENTAL
26 If you say yes to this option, support will be included for the SMB
27 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
28 controller is part of the 7101 device, which is an ACPI-compliant
29 Power Management Unit (PMU).
31 This driver can also be built as a module. If so, the module
32 will be called i2c-ali1563.
38 If you say yes to this option, support will be included for the
39 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
41 This driver can also be built as a module. If so, the module
42 will be called i2c-ali15x3.
45 tristate "AMD 756/766/768/8111 and nVidia nForce"
48 If you say yes to this option, support will be included for the AMD
49 756/766/768 mainboard I2C interfaces. The driver also includes
50 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
51 the nVidia nForce I2C interface.
53 This driver can also be built as a module. If so, the module
54 will be called i2c-amd756.
56 config I2C_AMD756_S4882
57 tristate "SMBus multiplexing on the Tyan S4882"
58 depends on I2C_AMD756 && X86 && EXPERIMENTAL
60 Enabling this option will add specific SMBus support for the Tyan
61 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
62 over 8 different channels, where the various memory module EEPROMs
63 and temperature sensors live. Saying yes here will give you access
64 to these in addition to the trunk.
66 This driver can also be built as a module. If so, the module
67 will be called i2c-amd756-s4882.
73 If you say yes to this option, support will be included for the
74 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
76 This driver can also be built as a module. If so, the module
77 will be called i2c-amd8111.
80 tristate "Intel 82801 (ICH/PCH)"
83 If you say yes to this option, support will be included for the Intel
84 801 family of mainboard I2C interfaces. Specifically, the following
85 versions of the chipset are supported:
91 82801EB/ER (ICH5/ICH5R)
104 This driver can also be built as a module. If so, the module
105 will be called i2c-i801.
108 tristate "Intel SCH SMBus 1.0"
113 Say Y here if you want to use SMBus controller on the Intel SCH
116 This driver can also be built as a module. If so, the module
117 will be called i2c-isch.
120 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
123 If you say yes to this option, support will be included for the Intel
124 PIIX4 family of mainboard I2C interfaces. Specifically, the following
125 versions of the chipset are supported (note that Serverworks is part
143 This driver can also be built as a module. If so, the module
144 will be called i2c-piix4.
147 tristate "Nvidia nForce2, nForce3 and nForce4"
150 If you say yes to this option, support will be included for the Nvidia
151 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
153 This driver can also be built as a module. If so, the module
154 will be called i2c-nforce2.
156 config I2C_NFORCE2_S4985
157 tristate "SMBus multiplexing on the Tyan S4985"
158 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
160 Enabling this option will add specific SMBus support for the Tyan
161 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
162 over 4 different channels, where the various memory module EEPROMs
163 live. Saying yes here will give you access to these in addition
166 This driver can also be built as a module. If so, the module
167 will be called i2c-nforce2-s4985.
173 If you say yes to this option, support will be included for the
174 SiS5595 SMBus (a subset of I2C) interface.
176 This driver can also be built as a module. If so, the module
177 will be called i2c-sis5595.
180 tristate "SiS 630/730"
183 If you say yes to this option, support will be included for the
184 SiS630 and SiS730 SMBus (a subset of I2C) interface.
186 This driver can also be built as a module. If so, the module
187 will be called i2c-sis630.
193 If you say yes to this option, support will be included for the SiS
194 96x SMBus (a subset of I2C) interfaces. Specifically, the following
195 chipsets are supported:
204 This driver can also be built as a module. If so, the module
205 will be called i2c-sis96x.
208 tristate "VIA VT82C586B"
209 depends on PCI && EXPERIMENTAL
212 If you say yes to this option, support will be included for the VIA
213 82C586B I2C interface
215 This driver can also be built as a module. If so, the module
216 will be called i2c-via.
219 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
222 If you say yes to this option, support will be included for the VIA
223 VT82C596 and later SMBus interface. Specifically, the following
224 chipsets are supported:
236 This driver can also be built as a module. If so, the module
237 will be called i2c-viapro.
241 comment "ACPI drivers"
244 tristate "SMBus Control Method Interface"
246 This driver supports the SMBus Control Method Interface. It needs the
247 BIOS to declare ACPI control methods as described in the SMBus Control
248 Method Interface specification.
250 To compile this driver as a module, choose M here:
251 the module will be called i2c-scmi.
255 comment "Mac SMBus host controller drivers"
256 depends on PPC_CHRP || PPC_PMAC
259 tristate "CHRP Apple Hydra Mac I/O I2C interface"
260 depends on PCI && PPC_CHRP && EXPERIMENTAL
263 This supports the use of the I2C interface in the Apple Hydra Mac
264 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
267 This support is also available as a module. If so, the module
268 will be called i2c-hydra.
271 tristate "Powermac I2C interface"
275 This exposes the various PowerMac i2c interfaces to the linux i2c
276 layer and to userland. It is used by various drivers on the PowerMac
277 platform, and should generally be enabled.
279 This support is also available as a module. If so, the module
280 will be called i2c-powermac.
282 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
285 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
286 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
288 This supports the use of the I2C interface on Atmel AT91
291 This driver is BROKEN because the controller which it uses
292 will easily trigger RX overrun and TX underrun errors. Using
293 low I2C clock rates may partially work around those issues
294 on some systems. Another serious problem is that there is no
295 documented way to issue repeated START conditions, as needed
296 to support combined I2C messages. Use the i2c-gpio driver
297 unless your system can cope with those limitations.
300 tristate "Au1550/Au1200 SMBus interface"
301 depends on SOC_AU1550 || SOC_AU1200
303 If you say yes to this option, support will be included for the
304 Au1550 and Au1200 SMBus interface.
306 This driver can also be built as a module. If so, the module
307 will be called i2c-au1550.
309 config I2C_BLACKFIN_TWI
310 tristate "Blackfin TWI I2C support"
312 depends on !BF561 && !BF531 && !BF532 && !BF533
314 This is the I2C bus driver for Blackfin on-chip TWI interface.
316 This driver can also be built as a module. If so, the module
317 will be called i2c-bfin-twi.
319 config I2C_BLACKFIN_TWI_CLK_KHZ
320 int "Blackfin TWI I2C clock (kHz)"
321 depends on I2C_BLACKFIN_TWI
325 The unit of the TWI clock is kHz.
328 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
329 depends on (CPM1 || CPM2) && OF_I2C
331 This supports the use of the I2C interface on Freescale
332 processors with CPM1 or CPM2.
334 This driver can also be built as a module. If so, the module
335 will be called i2c-cpm.
338 tristate "DaVinci I2C driver"
339 depends on ARCH_DAVINCI
341 Support for TI DaVinci I2C controller driver.
343 This driver can also be built as a module. If so, the module
344 will be called i2c-davinci.
346 Please note that this driver might be needed to bring up other
347 devices such as DaVinci NIC.
348 For details please see http://www.ti.com/davinci
350 config I2C_DESIGNWARE
351 tristate "Synopsys DesignWare"
354 If you say yes to this option, support will be included for the
355 Synopsys DesignWare I2C adapter. Only master mode is supported.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-designware.
361 tristate "GPIO-based bitbanging I2C"
362 depends on GENERIC_GPIO
365 This is a very simple bitbanging I2C driver utilizing the
366 arch-neutral GPIO API to control the SCL and SDA lines.
368 config I2C_HIGHLANDER
369 tristate "Highlander FPGA SMBus interface"
370 depends on SH_HIGHLANDER
372 If you say yes to this option, support will be included for
373 the SMBus interface located in the FPGA on various Highlander
374 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
375 FPGAs. This is wholly unrelated to the SoC I2C.
377 This driver can also be built as a module. If so, the module
378 will be called i2c-highlander.
381 tristate "IBM PPC 4xx on-chip I2C interface"
384 Say Y here if you want to use IIC peripheral found on
385 embedded IBM PPC 4xx based systems.
387 This driver can also be built as a module. If so, the module
388 will be called i2c-ibm_iic.
391 tristate "IMX I2C interface"
394 Say Y here if you want to use the IIC bus controller on
395 the Freescale i.MX/MXC processors.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-imx.
401 tristate "Intel Moorestown/Medfield Platform I2C controller"
404 Say Y here if you have an Intel Moorestown/Medfield platform I2C
407 This support is also available as a module. If so, the module
408 will be called i2c-intel-mid.
411 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
412 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
414 Say Y here if you want to use the IIC bus controller on
415 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
417 This driver can also be built as a module. If so, the module
418 will be called i2c-iop3xx.
421 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
422 depends on ARCH_IXP2000
425 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
426 system and are using GPIO lines for an I2C bus.
428 This support is also available as a module. If so, the module
429 will be called i2c-ixp2000.
431 This driver is deprecated and will be dropped soon. Use i2c-gpio
435 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
438 If you say yes to this option, support will be included for the
439 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
440 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
442 This driver can also be built as a module. If so, the module
443 will be called i2c-mpc.
446 tristate "Marvell mv64xxx I2C Controller"
447 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
449 If you say yes to this option, support will be included for the
450 built-in I2C interface on the Marvell 64xxx line of host bridges.
452 This driver can also be built as a module. If so, the module
453 will be called i2c-mv64xxx.
456 tristate "Freescale i.MX28 I2C interface"
459 Say Y here if you want to use the I2C bus controller on
460 the Freescale i.MX28 processors.
462 This driver can also be built as a module. If so, the module
463 will be called i2c-mxs.
466 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
467 depends on PLAT_NOMADIK
469 If you say yes to this option, support will be included for the
470 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
473 tristate "NUC900 I2C Driver"
474 depends on ARCH_W90X900
476 Say Y here to include support for I2C controller in the
477 Winbond/Nuvoton NUC900 based System-on-Chip devices.
480 tristate "OpenCores I2C Controller"
481 depends on EXPERIMENTAL
483 If you say yes to this option, support will be included for the
484 OpenCores I2C controller. For details see
485 http://www.opencores.org/projects.cgi/web/i2c/overview
487 This driver can also be built as a module. If so, the module
488 will be called i2c-ocores.
491 tristate "OMAP I2C adapter"
493 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
495 If you say yes to this option, support will be included for the
496 I2C interface on the Texas Instruments OMAP1/2 family of processors.
497 Like OMAP1510/1610/1710/5912 and OMAP242x.
498 For details see http://www.ti.com/omap.
501 tristate "PA Semi SMBus interface"
502 depends on PPC_PASEMI && PCI
504 Supports the PA Semi PWRficient on-chip SMBus interfaces.
506 config I2C_PCA_PLATFORM
507 tristate "PCA9564/PCA9665 as platform device"
511 This driver supports a memory mapped Philips PCA9564/PCA9665
512 parallel bus to I2C bus controller.
514 This driver can also be built as a module. If so, the module
515 will be called i2c-pca-platform.
518 tristate "PMC MSP I2C TWI Controller"
521 This driver supports the PMC TWI controller on MSP devices.
523 This driver can also be built as module. If so, the module
524 will be called i2c-pmcmsp.
527 tristate "I2C bus support for Philips PNX and NXP LPC targets"
528 depends on ARCH_PNX4008 || ARCH_LPC32XX
530 This driver supports the Philips IP3204 I2C IP block master and/or
533 This driver can also be built as a module. If so, the module
534 will be called i2c-pnx.
537 tristate "PKUnity v3 I2C bus support"
538 depends on UNICORE32 && ARCH_PUV3
541 This driver supports the I2C IP inside the PKUnity-v3 SoC.
542 This I2C bus controller is under AMBA/AXI bus.
544 This driver can also be built as a module. If so, the module
545 will be called i2c-puv3.
548 tristate "Intel PXA2XX I2C adapter"
549 depends on ARCH_PXA || ARCH_MMP
551 If you have devices in the PXA I2C bus, say yes to this option.
552 This driver can also be built as a module. If so, the module
553 will be called i2c-pxa.
556 bool "Intel PXA2XX I2C Slave comms support"
559 Support I2C slave mode communications on the PXA I2C bus. This
560 is necessary for systems where the PXA may be a target on the
563 config HAVE_S3C2410_I2C
566 This will include I2C support for Samsung SoCs. If you want to
567 include I2C support for any machine, kindly select this in the
568 respective Kconfig file.
571 tristate "S3C2410 I2C Driver"
572 depends on HAVE_S3C2410_I2C
574 Say Y here to include support for I2C controller in the
578 tristate "S6000 I2C support"
579 depends on XTENSA_VARIANT_S6000
581 This driver supports the on chip I2C device on the
582 S6000 xtensa processor family.
584 To compile this driver as a module, choose M here. The module
585 will be called i2c-s6000.
588 tristate "Renesas SH7760 I2C Controller"
589 depends on CPU_SUBTYPE_SH7760
591 This driver supports the 2 I2C interfaces on the Renesas SH7760.
593 This driver can also be built as a module. If so, the module
594 will be called i2c-sh7760.
597 tristate "SuperH Mobile I2C Controller"
598 depends on SUPERH || ARCH_SHMOBILE
600 If you say yes to this option, support will be included for the
601 built-in I2C interface on the Renesas SH-Mobile processor.
603 This driver can also be built as a module. If so, the module
604 will be called i2c-sh_mobile.
607 tristate "Simtec Generic I2C interface"
610 If you say yes to this option, support will be included for
611 the Simtec Generic I2C interface. This driver is for the
612 simple I2C bus used on newer Simtec products for general
613 I2C, such as DDC on the Simtec BBD2016A.
615 This driver can also be built as a module. If so, the module
616 will be called i2c-simtec.
619 tristate "ST Microelectronics DDC I2C interface"
621 default y if MACH_U300
623 If you say yes to this option, support will be included for the
624 I2C interface from ST Microelectronics simply called "DDC I2C"
625 supporting both I2C and DDC, used in e.g. the U300 series
628 This driver can also be built as a module. If so, the module
629 will be called i2c-stu300.
632 tristate "NVIDIA Tegra internal I2C controller"
633 depends on ARCH_TEGRA
635 If you say yes to this option, support will be included for the
636 I2C controller embedded in NVIDIA Tegra SOCs
639 tristate "ARM Versatile/Realview I2C bus support"
640 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
643 Say yes if you want to support the I2C serial bus on ARMs Versatile
646 This driver can also be built as a module. If so, the module
647 will be called i2c-versatile.
650 tristate "Cavium OCTEON I2C bus support"
651 depends on CPU_CAVIUM_OCTEON
653 Say yes if you want to support the I2C serial bus on Cavium
656 This driver can also be built as a module. If so, the module
657 will be called i2c-octeon.
660 tristate "Xilinx I2C Controller"
661 depends on EXPERIMENTAL && HAS_IOMEM
663 If you say yes to this option, support will be included for the
664 Xilinx I2C controller.
666 This driver can also be built as a module. If so, the module
667 will be called xilinx_i2c.
670 tristate "PCH I2C of Intel EG20T"
673 This driver is for PCH(Platform controller Hub) I2C of EG20T which
674 is an IOH(Input/Output Hub) for x86 embedded processor.
675 This driver can access PCH I2C bus device.
677 comment "External I2C/SMBus adapter drivers"
680 tristate "Parallel port adapter"
685 This supports parallel port I2C adapters such as the ones made by
686 Philips or Velleman, Analog Devices evaluation boards, and more.
687 Basically any adapter using the parallel port as an I2C bus with
688 no extra chipset is supported by this driver, or could be.
690 This driver is a replacement for (and was inspired by) an older
691 driver named i2c-philips-par. The new driver supports more devices,
692 and makes it easier to add support for new devices.
694 An adapter type parameter is now mandatory. Please read the file
695 Documentation/i2c/busses/i2c-parport for details.
697 Another driver exists, named i2c-parport-light, which doesn't depend
698 on the parport driver. This is meant for embedded systems. Don't say
699 Y here if you intend to say Y or M there.
701 This support is also available as a module. If so, the module
702 will be called i2c-parport.
704 config I2C_PARPORT_LIGHT
705 tristate "Parallel port adapter (light)"
709 This supports parallel port I2C adapters such as the ones made by
710 Philips or Velleman, Analog Devices evaluation boards, and more.
711 Basically any adapter using the parallel port as an I2C bus with
712 no extra chipset is supported by this driver, or could be.
714 This driver is a light version of i2c-parport. It doesn't depend
715 on the parport driver, and uses direct I/O access instead. This
716 might be preferred on embedded systems where wasting memory for
717 the clean but heavy parport handling is not an option. The
718 drawback is a reduced portability and the impossibility to
719 daisy-chain other parallel port devices.
721 Don't say Y here if you said Y or M to i2c-parport. Saying M to
722 both is possible but both modules should not be loaded at the same
725 This support is also available as a module. If so, the module
726 will be called i2c-parport-light.
729 tristate "TAOS evaluation module"
730 depends on EXPERIMENTAL
735 This supports TAOS evaluation modules on serial port. In order to
736 use this driver, you will need the inputattach tool, which is part
737 of the input-utils package.
741 This support is also available as a module. If so, the module
742 will be called i2c-taos-evm.
745 tristate "Tiny-USB adapter"
748 If you say yes to this option, support will be included for the
749 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
750 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
752 This driver can also be built as a module. If so, the module
753 will be called i2c-tiny-usb.
755 comment "Other I2C/SMBus bus drivers"
758 tristate "Acorn IOC/IOMD I2C bus support"
759 depends on ARCH_ACORN
763 Say yes if you want to support the I2C bus on Acorn platforms.
765 If you don't know, say Y.
768 tristate "Elektor ISA card"
769 depends on ISA && BROKEN_ON_SMP
772 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
775 This support is also available as a module. If so, the module
776 will be called i2c-elektor.
779 tristate "PCA9564/PCA9665 on an ISA bus"
784 This driver supports ISA boards using the Philips PCA9564/PCA9665
785 parallel bus to I2C bus controller.
787 This driver can also be built as a module. If so, the module
788 will be called i2c-pca-isa.
790 This device is almost undetectable and using this driver on a
791 system which doesn't have this device will result in long
792 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
793 time). If unsure, say N.
796 tristate "SiByte SMBus interface"
797 depends on SIBYTE_SB1xxx_SOC
799 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
802 tristate "I2C/SMBus Test Stub"
803 depends on EXPERIMENTAL && m
806 This module may be useful to developers of SMBus client drivers,
807 especially for certain kinds of sensor chips.
809 If you do build this module, be sure to read the notes and warnings
810 in <file:Documentation/i2c/i2c-stub>.
812 If you don't know what to do here, definitely say N.
815 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
816 depends on SCx200_GPIO
819 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
821 If you don't know what to do here, say N.
823 This support is also available as a module. If so, the module
824 will be called scx200_i2c.
826 This driver is deprecated and will be dropped soon. Use i2c-gpio
827 (or scx200_acb) instead.
829 config SCx200_I2C_SCL
830 int "GPIO pin used for SCL"
831 depends on SCx200_I2C
834 Enter the GPIO pin number used for the SCL signal. This value can
835 also be specified with a module parameter.
837 config SCx200_I2C_SDA
838 int "GPIO pin used for SDA"
839 depends on SCx200_I2C
842 Enter the GPIO pin number used for the SSA signal. This value can
843 also be specified with a module parameter.
846 tristate "Geode ACCESS.bus support"
847 depends on X86_32 && PCI
849 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
850 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
852 If you don't know what to do here, say N.
854 This support is also available as a module. If so, the module
855 will be called scx200_acb.