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)
108 This driver can also be built as a module. If so, the module
109 will be called i2c-i801.
112 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 MIPS_ALCHEMY
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_CORE
356 config I2C_DESIGNWARE_PLATFORM
357 tristate "Synopsys DesignWare Platfrom"
359 select I2C_DESIGNWARE_CORE
361 If you say yes to this option, support will be included for the
362 Synopsys DesignWare I2C adapter. Only master mode is supported.
364 This driver can also be built as a module. If so, the module
365 will be called i2c-designware-platform.
367 config I2C_DESIGNWARE_PCI
368 tristate "Synopsys DesignWare PCI"
370 select I2C_DESIGNWARE_CORE
372 If you say yes to this option, support will be included for the
373 Synopsys DesignWare I2C adapter. Only master mode is supported.
375 This driver can also be built as a module. If so, the module
376 will be called i2c-designware-pci.
379 tristate "GPIO-based bitbanging I2C"
380 depends on GENERIC_GPIO
383 This is a very simple bitbanging I2C driver utilizing the
384 arch-neutral GPIO API to control the SCL and SDA lines.
386 config I2C_HIGHLANDER
387 tristate "Highlander FPGA SMBus interface"
388 depends on SH_HIGHLANDER
390 If you say yes to this option, support will be included for
391 the SMBus interface located in the FPGA on various Highlander
392 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
393 FPGAs. This is wholly unrelated to the SoC I2C.
395 This driver can also be built as a module. If so, the module
396 will be called i2c-highlander.
399 tristate "IBM PPC 4xx on-chip I2C interface"
402 Say Y here if you want to use IIC peripheral found on
403 embedded IBM PPC 4xx based systems.
405 This driver can also be built as a module. If so, the module
406 will be called i2c-ibm_iic.
409 tristate "IMX I2C interface"
412 Say Y here if you want to use the IIC bus controller on
413 the Freescale i.MX/MXC processors.
415 This driver can also be built as a module. If so, the module
416 will be called i2c-imx.
419 tristate "Intel Moorestown/Medfield Platform I2C controller"
422 Say Y here if you have an Intel Moorestown/Medfield platform I2C
425 This support is also available as a module. If so, the module
426 will be called i2c-intel-mid.
429 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
430 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
432 Say Y here if you want to use the IIC bus controller on
433 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
435 This driver can also be built as a module. If so, the module
436 will be called i2c-iop3xx.
439 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
440 depends on ARCH_IXP2000
443 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
444 system and are using GPIO lines for an I2C bus.
446 This support is also available as a module. If so, the module
447 will be called i2c-ixp2000.
449 This driver is deprecated and will be dropped soon. Use i2c-gpio
453 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
456 If you say yes to this option, support will be included for the
457 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
458 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
460 This driver can also be built as a module. If so, the module
461 will be called i2c-mpc.
464 tristate "Marvell mv64xxx I2C Controller"
465 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
467 If you say yes to this option, support will be included for the
468 built-in I2C interface on the Marvell 64xxx line of host bridges.
470 This driver can also be built as a module. If so, the module
471 will be called i2c-mv64xxx.
474 tristate "Freescale i.MX28 I2C interface"
477 Say Y here if you want to use the I2C bus controller on
478 the Freescale i.MX28 processors.
480 This driver can also be built as a module. If so, the module
481 will be called i2c-mxs.
484 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
485 depends on PLAT_NOMADIK
487 If you say yes to this option, support will be included for the
488 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
491 tristate "NUC900 I2C Driver"
492 depends on ARCH_W90X900
494 Say Y here to include support for I2C controller in the
495 Winbond/Nuvoton NUC900 based System-on-Chip devices.
498 tristate "OpenCores I2C Controller"
499 depends on EXPERIMENTAL
501 If you say yes to this option, support will be included for the
502 OpenCores I2C controller. For details see
503 http://www.opencores.org/projects.cgi/web/i2c/overview
505 This driver can also be built as a module. If so, the module
506 will be called i2c-ocores.
509 tristate "OMAP I2C adapter"
511 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
513 If you say yes to this option, support will be included for the
514 I2C interface on the Texas Instruments OMAP1/2 family of processors.
515 Like OMAP1510/1610/1710/5912 and OMAP242x.
516 For details see http://www.ti.com/omap.
519 tristate "PA Semi SMBus interface"
520 depends on PPC_PASEMI && PCI
522 Supports the PA Semi PWRficient on-chip SMBus interfaces.
524 config I2C_PCA_PLATFORM
525 tristate "PCA9564/PCA9665 as platform device"
529 This driver supports a memory mapped Philips PCA9564/PCA9665
530 parallel bus to I2C bus controller.
532 This driver can also be built as a module. If so, the module
533 will be called i2c-pca-platform.
536 tristate "PMC MSP I2C TWI Controller"
539 This driver supports the PMC TWI controller on MSP devices.
541 This driver can also be built as module. If so, the module
542 will be called i2c-pmcmsp.
545 tristate "I2C bus support for Philips PNX and NXP LPC targets"
546 depends on ARCH_PNX4008 || ARCH_LPC32XX
548 This driver supports the Philips IP3204 I2C IP block master and/or
551 This driver can also be built as a module. If so, the module
552 will be called i2c-pnx.
555 tristate "PKUnity v3 I2C bus support"
556 depends on UNICORE32 && ARCH_PUV3
559 This driver supports the I2C IP inside the PKUnity-v3 SoC.
560 This I2C bus controller is under AMBA/AXI bus.
562 This driver can also be built as a module. If so, the module
563 will be called i2c-puv3.
566 tristate "Intel PXA2XX I2C adapter"
567 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
569 If you have devices in the PXA I2C bus, say yes to this option.
570 This driver can also be built as a module. If so, the module
571 will be called i2c-pxa.
574 def_bool I2C_PXA && X86_32 && PCI && OF
577 bool "Intel PXA2XX I2C Slave comms support"
578 depends on I2C_PXA && !X86_32
580 Support I2C slave mode communications on the PXA I2C bus. This
581 is necessary for systems where the PXA may be a target on the
584 config HAVE_S3C2410_I2C
587 This will include I2C support for Samsung SoCs. If you want to
588 include I2C support for any machine, kindly select this in the
589 respective Kconfig file.
592 tristate "S3C2410 I2C Driver"
593 depends on HAVE_S3C2410_I2C
595 Say Y here to include support for I2C controller in the
599 tristate "S6000 I2C support"
600 depends on XTENSA_VARIANT_S6000
602 This driver supports the on chip I2C device on the
603 S6000 xtensa processor family.
605 To compile this driver as a module, choose M here. The module
606 will be called i2c-s6000.
609 tristate "Renesas SH7760 I2C Controller"
610 depends on CPU_SUBTYPE_SH7760
612 This driver supports the 2 I2C interfaces on the Renesas SH7760.
614 This driver can also be built as a module. If so, the module
615 will be called i2c-sh7760.
618 tristate "SuperH Mobile I2C Controller"
619 depends on SUPERH || ARCH_SHMOBILE
621 If you say yes to this option, support will be included for the
622 built-in I2C interface on the Renesas SH-Mobile processor.
624 This driver can also be built as a module. If so, the module
625 will be called i2c-sh_mobile.
628 tristate "Simtec Generic I2C interface"
631 If you say yes to this option, support will be included for
632 the Simtec Generic I2C interface. This driver is for the
633 simple I2C bus used on newer Simtec products for general
634 I2C, such as DDC on the Simtec BBD2016A.
636 This driver can also be built as a module. If so, the module
637 will be called i2c-simtec.
640 tristate "ST Microelectronics DDC I2C interface"
642 default y if MACH_U300
644 If you say yes to this option, support will be included for the
645 I2C interface from ST Microelectronics simply called "DDC I2C"
646 supporting both I2C and DDC, used in e.g. the U300 series
649 This driver can also be built as a module. If so, the module
650 will be called i2c-stu300.
653 tristate "NVIDIA Tegra internal I2C controller"
654 depends on ARCH_TEGRA
656 If you say yes to this option, support will be included for the
657 I2C controller embedded in NVIDIA Tegra SOCs
660 tristate "ARM Versatile/Realview I2C bus support"
661 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
664 Say yes if you want to support the I2C serial bus on ARMs Versatile
667 This driver can also be built as a module. If so, the module
668 will be called i2c-versatile.
671 tristate "Cavium OCTEON I2C bus support"
672 depends on CPU_CAVIUM_OCTEON
674 Say yes if you want to support the I2C serial bus on Cavium
677 This driver can also be built as a module. If so, the module
678 will be called i2c-octeon.
681 tristate "Xilinx I2C Controller"
682 depends on EXPERIMENTAL && HAS_IOMEM
684 If you say yes to this option, support will be included for the
685 Xilinx I2C controller.
687 This driver can also be built as a module. If so, the module
688 will be called xilinx_i2c.
691 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
694 This driver is for PCH(Platform controller Hub) I2C of EG20T which
695 is an IOH(Input/Output Hub) for x86 embedded processor.
696 This driver can access PCH I2C bus device.
698 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
699 Output Hub), ML7213 and ML7223.
700 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
701 for MP(Media Phone) use.
702 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
703 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
705 comment "External I2C/SMBus adapter drivers"
707 config I2C_DIOLAN_U2C
708 tristate "Diolan U2C-12 USB adapter"
711 If you say yes to this option, support will be included for Diolan
712 U2C-12, a USB to I2C interface.
714 This driver can also be built as a module. If so, the module
715 will be called i2c-diolan-u2c.
718 tristate "Parallel port adapter"
723 This supports parallel port I2C adapters such as the ones made by
724 Philips or Velleman, Analog Devices evaluation boards, and more.
725 Basically any adapter using the parallel port as an I2C bus with
726 no extra chipset is supported by this driver, or could be.
728 This driver is a replacement for (and was inspired by) an older
729 driver named i2c-philips-par. The new driver supports more devices,
730 and makes it easier to add support for new devices.
732 An adapter type parameter is now mandatory. Please read the file
733 Documentation/i2c/busses/i2c-parport for details.
735 Another driver exists, named i2c-parport-light, which doesn't depend
736 on the parport driver. This is meant for embedded systems. Don't say
737 Y here if you intend to say Y or M there.
739 This support is also available as a module. If so, the module
740 will be called i2c-parport.
742 config I2C_PARPORT_LIGHT
743 tristate "Parallel port adapter (light)"
747 This supports parallel port I2C adapters such as the ones made by
748 Philips or Velleman, Analog Devices evaluation boards, and more.
749 Basically any adapter using the parallel port as an I2C bus with
750 no extra chipset is supported by this driver, or could be.
752 This driver is a light version of i2c-parport. It doesn't depend
753 on the parport driver, and uses direct I/O access instead. This
754 might be preferred on embedded systems where wasting memory for
755 the clean but heavy parport handling is not an option. The
756 drawback is a reduced portability and the impossibility to
757 daisy-chain other parallel port devices.
759 Don't say Y here if you said Y or M to i2c-parport. Saying M to
760 both is possible but both modules should not be loaded at the same
763 This support is also available as a module. If so, the module
764 will be called i2c-parport-light.
767 tristate "TAOS evaluation module"
768 depends on EXPERIMENTAL
773 This supports TAOS evaluation modules on serial port. In order to
774 use this driver, you will need the inputattach tool, which is part
775 of the input-utils package.
779 This support is also available as a module. If so, the module
780 will be called i2c-taos-evm.
783 tristate "Tiny-USB adapter"
786 If you say yes to this option, support will be included for the
787 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
788 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
790 This driver can also be built as a module. If so, the module
791 will be called i2c-tiny-usb.
793 comment "Other I2C/SMBus bus drivers"
796 tristate "Acorn IOC/IOMD I2C bus support"
797 depends on ARCH_ACORN
801 Say yes if you want to support the I2C bus on Acorn platforms.
803 If you don't know, say Y.
806 tristate "Elektor ISA card"
807 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
810 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
813 This support is also available as a module. If so, the module
814 will be called i2c-elektor.
817 tristate "PCA9564/PCA9665 on an ISA bus"
822 This driver supports ISA boards using the Philips PCA9564/PCA9665
823 parallel bus to I2C bus controller.
825 This driver can also be built as a module. If so, the module
826 will be called i2c-pca-isa.
828 This device is almost undetectable and using this driver on a
829 system which doesn't have this device will result in long
830 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
831 time). If unsure, say N.
834 tristate "SiByte SMBus interface"
835 depends on SIBYTE_SB1xxx_SOC
837 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
840 tristate "I2C/SMBus Test Stub"
841 depends on EXPERIMENTAL && m
844 This module may be useful to developers of SMBus client drivers,
845 especially for certain kinds of sensor chips.
847 If you do build this module, be sure to read the notes and warnings
848 in <file:Documentation/i2c/i2c-stub>.
850 If you don't know what to do here, definitely say N.
853 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
854 depends on SCx200_GPIO
857 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
859 If you don't know what to do here, say N.
861 This support is also available as a module. If so, the module
862 will be called scx200_i2c.
864 This driver is deprecated and will be dropped soon. Use i2c-gpio
865 (or scx200_acb) instead.
867 config SCx200_I2C_SCL
868 int "GPIO pin used for SCL"
869 depends on SCx200_I2C
872 Enter the GPIO pin number used for the SCL signal. This value can
873 also be specified with a module parameter.
875 config SCx200_I2C_SDA
876 int "GPIO pin used for SDA"
877 depends on SCx200_I2C
880 Enter the GPIO pin number used for the SSA signal. This value can
881 also be specified with a module parameter.
884 tristate "Geode ACCESS.bus support"
885 depends on X86_32 && PCI
887 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
888 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
890 If you don't know what to do here, say N.
892 This support is also available as a module. If so, the module
893 will be called scx200_acb.