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)"
82 select CHECK_SIGNATURE if X86 && DMI
84 If you say yes to this option, support will be included for the Intel
85 801 family of mainboard I2C interfaces. Specifically, the following
86 versions of the chipset are supported:
92 82801EB/ER (ICH5/ICH5R)
107 This driver can also be built as a module. If so, the module
108 will be called i2c-i801.
111 tristate "Intel SCH SMBus 1.0"
116 Say Y here if you want to use SMBus controller on the Intel SCH
119 This driver can also be built as a module. If so, the module
120 will be called i2c-isch.
123 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
126 If you say yes to this option, support will be included for the Intel
127 PIIX4 family of mainboard I2C interfaces. Specifically, the following
128 versions of the chipset are supported (note that Serverworks is part
146 This driver can also be built as a module. If so, the module
147 will be called i2c-piix4.
150 tristate "Nvidia nForce2, nForce3 and nForce4"
153 If you say yes to this option, support will be included for the Nvidia
154 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
156 This driver can also be built as a module. If so, the module
157 will be called i2c-nforce2.
159 config I2C_NFORCE2_S4985
160 tristate "SMBus multiplexing on the Tyan S4985"
161 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
163 Enabling this option will add specific SMBus support for the Tyan
164 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
165 over 4 different channels, where the various memory module EEPROMs
166 live. Saying yes here will give you access to these in addition
169 This driver can also be built as a module. If so, the module
170 will be called i2c-nforce2-s4985.
176 If you say yes to this option, support will be included for the
177 SiS5595 SMBus (a subset of I2C) interface.
179 This driver can also be built as a module. If so, the module
180 will be called i2c-sis5595.
183 tristate "SiS 630/730"
186 If you say yes to this option, support will be included for the
187 SiS630 and SiS730 SMBus (a subset of I2C) interface.
189 This driver can also be built as a module. If so, the module
190 will be called i2c-sis630.
196 If you say yes to this option, support will be included for the SiS
197 96x SMBus (a subset of I2C) interfaces. Specifically, the following
198 chipsets are supported:
207 This driver can also be built as a module. If so, the module
208 will be called i2c-sis96x.
211 tristate "VIA VT82C586B"
212 depends on PCI && EXPERIMENTAL
215 If you say yes to this option, support will be included for the VIA
216 82C586B I2C interface
218 This driver can also be built as a module. If so, the module
219 will be called i2c-via.
222 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
225 If you say yes to this option, support will be included for the VIA
226 VT82C596 and later SMBus interface. Specifically, the following
227 chipsets are supported:
239 This driver can also be built as a module. If so, the module
240 will be called i2c-viapro.
244 comment "ACPI drivers"
247 tristate "SMBus Control Method Interface"
249 This driver supports the SMBus Control Method Interface. It needs the
250 BIOS to declare ACPI control methods as described in the SMBus Control
251 Method Interface specification.
253 To compile this driver as a module, choose M here:
254 the module will be called i2c-scmi.
258 comment "Mac SMBus host controller drivers"
259 depends on PPC_CHRP || PPC_PMAC
262 tristate "CHRP Apple Hydra Mac I/O I2C interface"
263 depends on PCI && PPC_CHRP && EXPERIMENTAL
266 This supports the use of the I2C interface in the Apple Hydra Mac
267 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
270 This support is also available as a module. If so, the module
271 will be called i2c-hydra.
274 tristate "Powermac I2C interface"
278 This exposes the various PowerMac i2c interfaces to the linux i2c
279 layer and to userland. It is used by various drivers on the PowerMac
280 platform, and should generally be enabled.
282 This support is also available as a module. If so, the module
283 will be called i2c-powermac.
285 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
288 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
289 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
291 This supports the use of the I2C interface on Atmel AT91
294 This driver is BROKEN because the controller which it uses
295 will easily trigger RX overrun and TX underrun errors. Using
296 low I2C clock rates may partially work around those issues
297 on some systems. Another serious problem is that there is no
298 documented way to issue repeated START conditions, as needed
299 to support combined I2C messages. Use the i2c-gpio driver
300 unless your system can cope with those limitations.
303 tristate "Au1550/Au1200 SMBus interface"
304 depends on SOC_AU1550 || SOC_AU1200
306 If you say yes to this option, support will be included for the
307 Au1550 and Au1200 SMBus interface.
309 This driver can also be built as a module. If so, the module
310 will be called i2c-au1550.
312 config I2C_BLACKFIN_TWI
313 tristate "Blackfin TWI I2C support"
315 depends on !BF561 && !BF531 && !BF532 && !BF533
317 This is the I2C bus driver for Blackfin on-chip TWI interface.
319 This driver can also be built as a module. If so, the module
320 will be called i2c-bfin-twi.
322 config I2C_BLACKFIN_TWI_CLK_KHZ
323 int "Blackfin TWI I2C clock (kHz)"
324 depends on I2C_BLACKFIN_TWI
328 The unit of the TWI clock is kHz.
331 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
332 depends on (CPM1 || CPM2) && OF_I2C
334 This supports the use of the I2C interface on Freescale
335 processors with CPM1 or CPM2.
337 This driver can also be built as a module. If so, the module
338 will be called i2c-cpm.
341 tristate "DaVinci I2C driver"
342 depends on ARCH_DAVINCI
344 Support for TI DaVinci I2C controller driver.
346 This driver can also be built as a module. If so, the module
347 will be called i2c-davinci.
349 Please note that this driver might be needed to bring up other
350 devices such as DaVinci NIC.
351 For details please see http://www.ti.com/davinci
353 config I2C_DESIGNWARE_PLATFORM
354 tristate "Synopsys DesignWare Platfrom"
357 If you say yes to this option, support will be included for the
358 Synopsys DesignWare I2C adapter. Only master mode is supported.
360 This driver can also be built as a module. If so, the module
361 will be called i2c-designware-platform.
363 config I2C_DESIGNWARE_PCI
364 tristate "Synopsys DesignWare PCI"
367 If you say yes to this option, support will be included for the
368 Synopsys DesignWare I2C adapter. Only master mode is supported.
370 This driver can also be built as a module. If so, the module
371 will be called i2c-designware-pci.
374 tristate "GPIO-based bitbanging I2C"
375 depends on GENERIC_GPIO
378 This is a very simple bitbanging I2C driver utilizing the
379 arch-neutral GPIO API to control the SCL and SDA lines.
381 config I2C_HIGHLANDER
382 tristate "Highlander FPGA SMBus interface"
383 depends on SH_HIGHLANDER
385 If you say yes to this option, support will be included for
386 the SMBus interface located in the FPGA on various Highlander
387 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
388 FPGAs. This is wholly unrelated to the SoC I2C.
390 This driver can also be built as a module. If so, the module
391 will be called i2c-highlander.
394 tristate "IBM PPC 4xx on-chip I2C interface"
397 Say Y here if you want to use IIC peripheral found on
398 embedded IBM PPC 4xx based systems.
400 This driver can also be built as a module. If so, the module
401 will be called i2c-ibm_iic.
404 tristate "IMX I2C interface"
407 Say Y here if you want to use the IIC bus controller on
408 the Freescale i.MX/MXC processors.
410 This driver can also be built as a module. If so, the module
411 will be called i2c-imx.
414 tristate "Intel Moorestown/Medfield Platform I2C controller"
417 Say Y here if you have an Intel Moorestown/Medfield platform I2C
420 This support is also available as a module. If so, the module
421 will be called i2c-intel-mid.
424 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
425 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
427 Say Y here if you want to use the IIC bus controller on
428 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
430 This driver can also be built as a module. If so, the module
431 will be called i2c-iop3xx.
434 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
435 depends on ARCH_IXP2000
438 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
439 system and are using GPIO lines for an I2C bus.
441 This support is also available as a module. If so, the module
442 will be called i2c-ixp2000.
444 This driver is deprecated and will be dropped soon. Use i2c-gpio
448 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
451 If you say yes to this option, support will be included for the
452 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
453 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
455 This driver can also be built as a module. If so, the module
456 will be called i2c-mpc.
459 tristate "Marvell mv64xxx I2C Controller"
460 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
462 If you say yes to this option, support will be included for the
463 built-in I2C interface on the Marvell 64xxx line of host bridges.
465 This driver can also be built as a module. If so, the module
466 will be called i2c-mv64xxx.
469 tristate "Freescale i.MX28 I2C interface"
472 Say Y here if you want to use the I2C bus controller on
473 the Freescale i.MX28 processors.
475 This driver can also be built as a module. If so, the module
476 will be called i2c-mxs.
479 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
480 depends on PLAT_NOMADIK
482 If you say yes to this option, support will be included for the
483 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
486 tristate "NUC900 I2C Driver"
487 depends on ARCH_W90X900
489 Say Y here to include support for I2C controller in the
490 Winbond/Nuvoton NUC900 based System-on-Chip devices.
493 tristate "OpenCores I2C Controller"
494 depends on EXPERIMENTAL
496 If you say yes to this option, support will be included for the
497 OpenCores I2C controller. For details see
498 http://www.opencores.org/projects.cgi/web/i2c/overview
500 This driver can also be built as a module. If so, the module
501 will be called i2c-ocores.
504 tristate "OMAP I2C adapter"
506 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
508 If you say yes to this option, support will be included for the
509 I2C interface on the Texas Instruments OMAP1/2 family of processors.
510 Like OMAP1510/1610/1710/5912 and OMAP242x.
511 For details see http://www.ti.com/omap.
514 tristate "PA Semi SMBus interface"
515 depends on PPC_PASEMI && PCI
517 Supports the PA Semi PWRficient on-chip SMBus interfaces.
519 config I2C_PCA_PLATFORM
520 tristate "PCA9564/PCA9665 as platform device"
524 This driver supports a memory mapped Philips PCA9564/PCA9665
525 parallel bus to I2C bus controller.
527 This driver can also be built as a module. If so, the module
528 will be called i2c-pca-platform.
531 tristate "PMC MSP I2C TWI Controller"
534 This driver supports the PMC TWI controller on MSP devices.
536 This driver can also be built as module. If so, the module
537 will be called i2c-pmcmsp.
540 tristate "I2C bus support for Philips PNX and NXP LPC targets"
541 depends on ARCH_PNX4008 || ARCH_LPC32XX
543 This driver supports the Philips IP3204 I2C IP block master and/or
546 This driver can also be built as a module. If so, the module
547 will be called i2c-pnx.
550 tristate "PKUnity v3 I2C bus support"
551 depends on UNICORE32 && ARCH_PUV3
554 This driver supports the I2C IP inside the PKUnity-v3 SoC.
555 This I2C bus controller is under AMBA/AXI bus.
557 This driver can also be built as a module. If so, the module
558 will be called i2c-puv3.
561 tristate "Intel PXA2XX I2C adapter"
562 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
564 If you have devices in the PXA I2C bus, say yes to this option.
565 This driver can also be built as a module. If so, the module
566 will be called i2c-pxa.
569 def_bool I2C_PXA && X86_32 && PCI && OF
572 bool "Intel PXA2XX I2C Slave comms support"
573 depends on I2C_PXA && !X86_32
575 Support I2C slave mode communications on the PXA I2C bus. This
576 is necessary for systems where the PXA may be a target on the
579 config HAVE_S3C2410_I2C
582 This will include I2C support for Samsung SoCs. If you want to
583 include I2C support for any machine, kindly select this in the
584 respective Kconfig file.
587 tristate "S3C2410 I2C Driver"
588 depends on HAVE_S3C2410_I2C
590 Say Y here to include support for I2C controller in the
594 tristate "S6000 I2C support"
595 depends on XTENSA_VARIANT_S6000
597 This driver supports the on chip I2C device on the
598 S6000 xtensa processor family.
600 To compile this driver as a module, choose M here. The module
601 will be called i2c-s6000.
604 tristate "Renesas SH7760 I2C Controller"
605 depends on CPU_SUBTYPE_SH7760
607 This driver supports the 2 I2C interfaces on the Renesas SH7760.
609 This driver can also be built as a module. If so, the module
610 will be called i2c-sh7760.
613 tristate "SuperH Mobile I2C Controller"
614 depends on SUPERH || ARCH_SHMOBILE
616 If you say yes to this option, support will be included for the
617 built-in I2C interface on the Renesas SH-Mobile processor.
619 This driver can also be built as a module. If so, the module
620 will be called i2c-sh_mobile.
623 tristate "Simtec Generic I2C interface"
626 If you say yes to this option, support will be included for
627 the Simtec Generic I2C interface. This driver is for the
628 simple I2C bus used on newer Simtec products for general
629 I2C, such as DDC on the Simtec BBD2016A.
631 This driver can also be built as a module. If so, the module
632 will be called i2c-simtec.
635 tristate "ST Microelectronics DDC I2C interface"
637 default y if MACH_U300
639 If you say yes to this option, support will be included for the
640 I2C interface from ST Microelectronics simply called "DDC I2C"
641 supporting both I2C and DDC, used in e.g. the U300 series
644 This driver can also be built as a module. If so, the module
645 will be called i2c-stu300.
648 tristate "NVIDIA Tegra internal I2C controller"
649 depends on ARCH_TEGRA
651 If you say yes to this option, support will be included for the
652 I2C controller embedded in NVIDIA Tegra SOCs
655 tristate "ARM Versatile/Realview I2C bus support"
656 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
659 Say yes if you want to support the I2C serial bus on ARMs Versatile
662 This driver can also be built as a module. If so, the module
663 will be called i2c-versatile.
666 tristate "Cavium OCTEON I2C bus support"
667 depends on CPU_CAVIUM_OCTEON
669 Say yes if you want to support the I2C serial bus on Cavium
672 This driver can also be built as a module. If so, the module
673 will be called i2c-octeon.
676 tristate "Xilinx I2C Controller"
677 depends on EXPERIMENTAL && HAS_IOMEM
679 If you say yes to this option, support will be included for the
680 Xilinx I2C controller.
682 This driver can also be built as a module. If so, the module
683 will be called xilinx_i2c.
686 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
689 This driver is for PCH(Platform controller Hub) I2C of EG20T which
690 is an IOH(Input/Output Hub) for x86 embedded processor.
691 This driver can access PCH I2C bus device.
693 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
694 Output Hub), ML7213 and ML7223.
695 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
696 for MP(Media Phone) use.
697 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
698 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
700 comment "External I2C/SMBus adapter drivers"
702 config I2C_DIOLAN_U2C
703 tristate "Diolan U2C-12 USB adapter"
706 If you say yes to this option, support will be included for Diolan
707 U2C-12, a USB to I2C interface.
709 This driver can also be built as a module. If so, the module
710 will be called i2c-diolan-u2c.
713 tristate "Parallel port adapter"
718 This supports parallel port I2C adapters such as the ones made by
719 Philips or Velleman, Analog Devices evaluation boards, and more.
720 Basically any adapter using the parallel port as an I2C bus with
721 no extra chipset is supported by this driver, or could be.
723 This driver is a replacement for (and was inspired by) an older
724 driver named i2c-philips-par. The new driver supports more devices,
725 and makes it easier to add support for new devices.
727 An adapter type parameter is now mandatory. Please read the file
728 Documentation/i2c/busses/i2c-parport for details.
730 Another driver exists, named i2c-parport-light, which doesn't depend
731 on the parport driver. This is meant for embedded systems. Don't say
732 Y here if you intend to say Y or M there.
734 This support is also available as a module. If so, the module
735 will be called i2c-parport.
737 config I2C_PARPORT_LIGHT
738 tristate "Parallel port adapter (light)"
742 This supports parallel port I2C adapters such as the ones made by
743 Philips or Velleman, Analog Devices evaluation boards, and more.
744 Basically any adapter using the parallel port as an I2C bus with
745 no extra chipset is supported by this driver, or could be.
747 This driver is a light version of i2c-parport. It doesn't depend
748 on the parport driver, and uses direct I/O access instead. This
749 might be preferred on embedded systems where wasting memory for
750 the clean but heavy parport handling is not an option. The
751 drawback is a reduced portability and the impossibility to
752 daisy-chain other parallel port devices.
754 Don't say Y here if you said Y or M to i2c-parport. Saying M to
755 both is possible but both modules should not be loaded at the same
758 This support is also available as a module. If so, the module
759 will be called i2c-parport-light.
762 tristate "TAOS evaluation module"
763 depends on EXPERIMENTAL
768 This supports TAOS evaluation modules on serial port. In order to
769 use this driver, you will need the inputattach tool, which is part
770 of the input-utils package.
774 This support is also available as a module. If so, the module
775 will be called i2c-taos-evm.
778 tristate "Tiny-USB adapter"
781 If you say yes to this option, support will be included for the
782 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
783 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
785 This driver can also be built as a module. If so, the module
786 will be called i2c-tiny-usb.
788 comment "Other I2C/SMBus bus drivers"
791 tristate "Acorn IOC/IOMD I2C bus support"
792 depends on ARCH_ACORN
796 Say yes if you want to support the I2C bus on Acorn platforms.
798 If you don't know, say Y.
801 tristate "Elektor ISA card"
802 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
805 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
808 This support is also available as a module. If so, the module
809 will be called i2c-elektor.
812 tristate "PCA9564/PCA9665 on an ISA bus"
817 This driver supports ISA boards using the Philips PCA9564/PCA9665
818 parallel bus to I2C bus controller.
820 This driver can also be built as a module. If so, the module
821 will be called i2c-pca-isa.
823 This device is almost undetectable and using this driver on a
824 system which doesn't have this device will result in long
825 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
826 time). If unsure, say N.
829 tristate "SiByte SMBus interface"
830 depends on SIBYTE_SB1xxx_SOC
832 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
835 tristate "I2C/SMBus Test Stub"
836 depends on EXPERIMENTAL && m
839 This module may be useful to developers of SMBus client drivers,
840 especially for certain kinds of sensor chips.
842 If you do build this module, be sure to read the notes and warnings
843 in <file:Documentation/i2c/i2c-stub>.
845 If you don't know what to do here, definitely say N.
848 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
849 depends on SCx200_GPIO
852 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
854 If you don't know what to do here, say N.
856 This support is also available as a module. If so, the module
857 will be called scx200_i2c.
859 This driver is deprecated and will be dropped soon. Use i2c-gpio
860 (or scx200_acb) instead.
862 config SCx200_I2C_SCL
863 int "GPIO pin used for SCL"
864 depends on SCx200_I2C
867 Enter the GPIO pin number used for the SCL signal. This value can
868 also be specified with a module parameter.
870 config SCx200_I2C_SDA
871 int "GPIO pin used for SDA"
872 depends on SCx200_I2C
875 Enter the GPIO pin number used for the SSA signal. This value can
876 also be specified with a module parameter.
879 tristate "Geode ACCESS.bus support"
880 depends on X86_32 && PCI
882 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
883 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
885 If you don't know what to do here, say N.
887 This support is also available as a module. If so, the module
888 will be called scx200_acb.