2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
8 comment "PC SMBus host controller drivers"
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).
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
25 depends on PCI && EXPERIMENTAL
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).
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
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.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
46 tristate "AMD 756/766/768/8111 and nVidia nForce"
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.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
57 config I2C_AMD756_S4882
58 tristate "SMBus multiplexing on the Tyan S4882"
59 depends on I2C_AMD756 && X86 && EXPERIMENTAL
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.
67 This driver can also be built as a module. If so, the module
68 will be called i2c-amd756-s4882.
74 If you say yes to this option, support will be included for the
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
77 This driver can also be built as a module. If so, the module
78 will be called i2c-amd8111.
81 tristate "Intel 82801 (ICH/PCH)"
83 select CHECK_SIGNATURE if X86 && DMI
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:
93 82801EB/ER (ICH5/ICH5R)
110 This driver can also be built as a module. If so, the module
111 will be called i2c-i801.
114 tristate "Intel SCH SMBus 1.0"
118 Say Y here if you want to use SMBus controller on the Intel SCH
121 This driver can also be built as a module. If so, the module
122 will be called i2c-isch.
125 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
128 If you say yes to this option, support will be included for the Intel
129 PIIX4 family of mainboard I2C interfaces. Specifically, the following
130 versions of the chipset are supported (note that Serverworks is part
148 Some AMD chipsets contain two PIIX4-compatible SMBus
149 controllers. This driver will attempt to use both controllers
150 on the SB700/SP5100, if they have been initialized by the BIOS.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-piix4.
156 tristate "Nvidia nForce2, nForce3 and nForce4"
159 If you say yes to this option, support will be included for the Nvidia
160 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
162 This driver can also be built as a module. If so, the module
163 will be called i2c-nforce2.
165 config I2C_NFORCE2_S4985
166 tristate "SMBus multiplexing on the Tyan S4985"
167 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
169 Enabling this option will add specific SMBus support for the Tyan
170 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
171 over 4 different channels, where the various memory module EEPROMs
172 live. Saying yes here will give you access to these in addition
175 This driver can also be built as a module. If so, the module
176 will be called i2c-nforce2-s4985.
182 If you say yes to this option, support will be included for the
183 SiS5595 SMBus (a subset of I2C) interface.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-sis5595.
189 tristate "SiS 630/730"
192 If you say yes to this option, support will be included for the
193 SiS630 and SiS730 SMBus (a subset of I2C) interface.
195 This driver can also be built as a module. If so, the module
196 will be called i2c-sis630.
202 If you say yes to this option, support will be included for the SiS
203 96x SMBus (a subset of I2C) interfaces. Specifically, the following
204 chipsets are supported:
213 This driver can also be built as a module. If so, the module
214 will be called i2c-sis96x.
217 tristate "VIA VT82C586B"
218 depends on PCI && EXPERIMENTAL
221 If you say yes to this option, support will be included for the VIA
222 82C586B I2C interface
224 This driver can also be built as a module. If so, the module
225 will be called i2c-via.
228 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
231 If you say yes to this option, support will be included for the VIA
232 VT82C596 and later SMBus interface. Specifically, the following
233 chipsets are supported:
246 This driver can also be built as a module. If so, the module
247 will be called i2c-viapro.
251 comment "ACPI drivers"
254 tristate "SMBus Control Method Interface"
256 This driver supports the SMBus Control Method Interface. It needs the
257 BIOS to declare ACPI control methods as described in the SMBus Control
258 Method Interface specification.
260 To compile this driver as a module, choose M here:
261 the module will be called i2c-scmi.
265 comment "Mac SMBus host controller drivers"
266 depends on PPC_CHRP || PPC_PMAC
269 tristate "CHRP Apple Hydra Mac I/O I2C interface"
270 depends on PCI && PPC_CHRP && EXPERIMENTAL
273 This supports the use of the I2C interface in the Apple Hydra Mac
274 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
277 This support is also available as a module. If so, the module
278 will be called i2c-hydra.
281 tristate "Powermac I2C interface"
285 This exposes the various PowerMac i2c interfaces to the linux i2c
286 layer and to userland. It is used by various drivers on the PowerMac
287 platform, and should generally be enabled.
289 This support is also available as a module. If so, the module
290 will be called i2c-powermac.
292 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
295 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
296 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
298 This supports the use of the I2C interface on Atmel AT91
301 This driver is BROKEN because the controller which it uses
302 will easily trigger RX overrun and TX underrun errors. Using
303 low I2C clock rates may partially work around those issues
304 on some systems. Another serious problem is that there is no
305 documented way to issue repeated START conditions, as needed
306 to support combined I2C messages. Use the i2c-gpio driver
307 unless your system can cope with those limitations.
310 tristate "Au1550/Au1200/Au1300 SMBus interface"
311 depends on MIPS_ALCHEMY
313 If you say yes to this option, support will be included for the
314 Au1550/Au1200/Au1300 SMBus interface.
316 This driver can also be built as a module. If so, the module
317 will be called i2c-au1550.
319 config I2C_BLACKFIN_TWI
320 tristate "Blackfin TWI I2C support"
322 depends on !BF561 && !BF531 && !BF532 && !BF533
324 This is the I2C bus driver for Blackfin on-chip TWI interface.
326 This driver can also be built as a module. If so, the module
327 will be called i2c-bfin-twi.
329 config I2C_BLACKFIN_TWI_CLK_KHZ
330 int "Blackfin TWI I2C clock (kHz)"
331 depends on I2C_BLACKFIN_TWI
335 The unit of the TWI clock is kHz.
338 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
339 depends on (CPM1 || CPM2) && OF_I2C
341 This supports the use of the I2C interface on Freescale
342 processors with CPM1 or CPM2.
344 This driver can also be built as a module. If so, the module
345 will be called i2c-cpm.
348 tristate "DaVinci I2C driver"
349 depends on ARCH_DAVINCI
351 Support for TI DaVinci I2C controller driver.
353 This driver can also be built as a module. If so, the module
354 will be called i2c-davinci.
356 Please note that this driver might be needed to bring up other
357 devices such as DaVinci NIC.
358 For details please see http://www.ti.com/davinci
360 config I2C_DESIGNWARE_CORE
363 config I2C_DESIGNWARE_PLATFORM
364 tristate "Synopsys DesignWare Platform"
366 select I2C_DESIGNWARE_CORE
368 If you say yes to this option, support will be included for the
369 Synopsys DesignWare I2C adapter. Only master mode is supported.
371 This driver can also be built as a module. If so, the module
372 will be called i2c-designware-platform.
374 config I2C_DESIGNWARE_PCI
375 tristate "Synopsys DesignWare PCI"
377 select I2C_DESIGNWARE_CORE
379 If you say yes to this option, support will be included for the
380 Synopsys DesignWare I2C adapter. Only master mode is supported.
382 This driver can also be built as a module. If so, the module
383 will be called i2c-designware-pci.
386 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
389 This driver is for PCH(Platform controller Hub) I2C of EG20T which
390 is an IOH(Input/Output Hub) for x86 embedded processor.
391 This driver can access PCH I2C bus device.
393 This driver also can be used for LAPIS Semiconductor IOH(Input/
394 Output Hub), ML7213, ML7223 and ML7831.
395 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
396 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
397 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
398 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
401 tristate "GPIO-based bitbanging I2C"
402 depends on GENERIC_GPIO
405 This is a very simple bitbanging I2C driver utilizing the
406 arch-neutral GPIO API to control the SCL and SDA lines.
408 config I2C_HIGHLANDER
409 tristate "Highlander FPGA SMBus interface"
410 depends on SH_HIGHLANDER
412 If you say yes to this option, support will be included for
413 the SMBus interface located in the FPGA on various Highlander
414 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
415 FPGAs. This is wholly unrelated to the SoC I2C.
417 This driver can also be built as a module. If so, the module
418 will be called i2c-highlander.
421 tristate "IBM PPC 4xx on-chip I2C interface"
424 Say Y here if you want to use IIC peripheral found on
425 embedded IBM PPC 4xx based systems.
427 This driver can also be built as a module. If so, the module
428 will be called i2c-ibm_iic.
431 tristate "IMX I2C interface"
434 Say Y here if you want to use the IIC bus controller on
435 the Freescale i.MX/MXC processors.
437 This driver can also be built as a module. If so, the module
438 will be called i2c-imx.
441 tristate "Intel Moorestown/Medfield Platform I2C controller"
444 Say Y here if you have an Intel Moorestown/Medfield platform I2C
447 This support is also available as a module. If so, the module
448 will be called i2c-intel-mid.
451 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
452 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
454 Say Y here if you want to use the IIC bus controller on
455 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
457 This driver can also be built as a module. If so, the module
458 will be called i2c-iop3xx.
461 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
464 If you say yes to this option, support will be included for the
465 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
466 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
468 This driver can also be built as a module. If so, the module
469 will be called i2c-mpc.
472 tristate "Marvell mv64xxx I2C Controller"
473 depends on (MV64X60 || PLAT_ORION)
475 If you say yes to this option, support will be included for the
476 built-in I2C interface on the Marvell 64xxx line of host bridges.
478 This driver can also be built as a module. If so, the module
479 will be called i2c-mv64xxx.
482 tristate "Freescale i.MX28 I2C interface"
486 Say Y here if you want to use the I2C bus controller on
487 the Freescale i.MX28 processors.
489 This driver can also be built as a module. If so, the module
490 will be called i2c-mxs.
493 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
496 If you say yes to this option, support will be included for the
497 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
498 as well as the STA2X11 PCIe I/O HUB.
501 tristate "NUC900 I2C Driver"
502 depends on ARCH_W90X900
504 Say Y here to include support for I2C controller in the
505 Winbond/Nuvoton NUC900 based System-on-Chip devices.
508 tristate "OpenCores I2C Controller"
509 depends on EXPERIMENTAL
511 If you say yes to this option, support will be included for the
512 OpenCores I2C controller. For details see
513 http://www.opencores.org/projects.cgi/web/i2c/overview
515 This driver can also be built as a module. If so, the module
516 will be called i2c-ocores.
519 tristate "OMAP I2C adapter"
521 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
523 If you say yes to this option, support will be included for the
524 I2C interface on the Texas Instruments OMAP1/2 family of processors.
525 Like OMAP1510/1610/1710/5912 and OMAP242x.
526 For details see http://www.ti.com/omap.
529 tristate "PA Semi SMBus interface"
530 depends on PPC_PASEMI && PCI
532 Supports the PA Semi PWRficient on-chip SMBus interfaces.
534 config I2C_PCA_PLATFORM
535 tristate "PCA9564/PCA9665 as platform device"
539 This driver supports a memory mapped Philips PCA9564/PCA9665
540 parallel bus to I2C bus controller.
542 This driver can also be built as a module. If so, the module
543 will be called i2c-pca-platform.
546 tristate "PMC MSP I2C TWI Controller"
549 This driver supports the PMC TWI controller on MSP devices.
551 This driver can also be built as module. If so, the module
552 will be called i2c-pmcmsp.
555 tristate "I2C bus support for Philips PNX and NXP LPC targets"
556 depends on ARCH_LPC32XX
558 This driver supports the Philips IP3204 I2C IP block master and/or
561 This driver can also be built as a module. If so, the module
562 will be called i2c-pnx.
565 tristate "PKUnity v3 I2C bus support"
566 depends on UNICORE32 && ARCH_PUV3
569 This driver supports the I2C IP inside the PKUnity-v3 SoC.
570 This I2C bus controller is under AMBA/AXI bus.
572 This driver can also be built as a module. If so, the module
573 will be called i2c-puv3.
576 tristate "Intel PXA2XX I2C adapter"
577 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
579 If you have devices in the PXA I2C bus, say yes to this option.
580 This driver can also be built as a module. If so, the module
581 will be called i2c-pxa.
584 def_bool I2C_PXA && X86_32 && PCI && OF
587 bool "Intel PXA2XX I2C Slave comms support"
588 depends on I2C_PXA && !X86_32
590 Support I2C slave mode communications on the PXA I2C bus. This
591 is necessary for systems where the PXA may be a target on the
594 config HAVE_S3C2410_I2C
597 This will include I2C support for Samsung SoCs. If you want to
598 include I2C support for any machine, kindly select this in the
599 respective Kconfig file.
602 tristate "S3C2410 I2C Driver"
603 depends on HAVE_S3C2410_I2C
605 Say Y here to include support for I2C controller in the
609 tristate "S6000 I2C support"
610 depends on XTENSA_VARIANT_S6000
612 This driver supports the on chip I2C device on the
613 S6000 xtensa processor family.
615 To compile this driver as a module, choose M here. The module
616 will be called i2c-s6000.
619 tristate "Renesas SH7760 I2C Controller"
620 depends on CPU_SUBTYPE_SH7760
622 This driver supports the 2 I2C interfaces on the Renesas SH7760.
624 This driver can also be built as a module. If so, the module
625 will be called i2c-sh7760.
628 tristate "SuperH Mobile I2C Controller"
629 depends on SUPERH || ARCH_SHMOBILE
631 If you say yes to this option, support will be included for the
632 built-in I2C interface on the Renesas SH-Mobile processor.
634 This driver can also be built as a module. If so, the module
635 will be called i2c-sh_mobile.
638 tristate "Simtec Generic I2C interface"
641 If you say yes to this option, support will be included for
642 the Simtec Generic I2C interface. This driver is for the
643 simple I2C bus used on newer Simtec products for general
644 I2C, such as DDC on the Simtec BBD2016A.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-simtec.
650 tristate "CSR SiRFprimaII I2C interface"
651 depends on ARCH_PRIMA2
653 If you say yes to this option, support will be included for the
654 CSR SiRFprimaII I2C interface.
656 This driver can also be built as a module. If so, the module
657 will be called i2c-sirf.
660 tristate "ST Microelectronics DDC I2C interface"
662 default y if MACH_U300
664 If you say yes to this option, support will be included for the
665 I2C interface from ST Microelectronics simply called "DDC I2C"
666 supporting both I2C and DDC, used in e.g. the U300 series
669 This driver can also be built as a module. If so, the module
670 will be called i2c-stu300.
673 tristate "NVIDIA Tegra internal I2C controller"
674 depends on ARCH_TEGRA
676 If you say yes to this option, support will be included for the
677 I2C controller embedded in NVIDIA Tegra SOCs
680 tristate "ARM Versatile/Realview I2C bus support"
681 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
684 Say yes if you want to support the I2C serial bus on ARMs Versatile
687 This driver can also be built as a module. If so, the module
688 will be called i2c-versatile.
691 tristate "Cavium OCTEON I2C bus support"
692 depends on CPU_CAVIUM_OCTEON
694 Say yes if you want to support the I2C serial bus on Cavium
697 This driver can also be built as a module. If so, the module
698 will be called i2c-octeon.
701 tristate "Xilinx I2C Controller"
702 depends on EXPERIMENTAL && HAS_IOMEM
704 If you say yes to this option, support will be included for the
705 Xilinx I2C controller.
707 This driver can also be built as a module. If so, the module
708 will be called xilinx_i2c.
711 tristate "XLR I2C support"
714 This driver enables support for the on-chip I2C interface of
715 the Netlogic XLR/XLS MIPS processors.
717 This driver can also be built as a module. If so, the module
718 will be called i2c-xlr.
720 comment "External I2C/SMBus adapter drivers"
722 config I2C_DIOLAN_U2C
723 tristate "Diolan U2C-12 USB adapter"
726 If you say yes to this option, support will be included for Diolan
727 U2C-12, a USB to I2C interface.
729 This driver can also be built as a module. If so, the module
730 will be called i2c-diolan-u2c.
733 tristate "Parallel port adapter"
738 This supports parallel port I2C adapters such as the ones made by
739 Philips or Velleman, Analog Devices evaluation boards, and more.
740 Basically any adapter using the parallel port as an I2C bus with
741 no extra chipset is supported by this driver, or could be.
743 This driver is a replacement for (and was inspired by) an older
744 driver named i2c-philips-par. The new driver supports more devices,
745 and makes it easier to add support for new devices.
747 An adapter type parameter is now mandatory. Please read the file
748 Documentation/i2c/busses/i2c-parport for details.
750 Another driver exists, named i2c-parport-light, which doesn't depend
751 on the parport driver. This is meant for embedded systems. Don't say
752 Y here if you intend to say Y or M there.
754 This support is also available as a module. If so, the module
755 will be called i2c-parport.
757 config I2C_PARPORT_LIGHT
758 tristate "Parallel port adapter (light)"
762 This supports parallel port I2C adapters such as the ones made by
763 Philips or Velleman, Analog Devices evaluation boards, and more.
764 Basically any adapter using the parallel port as an I2C bus with
765 no extra chipset is supported by this driver, or could be.
767 This driver is a light version of i2c-parport. It doesn't depend
768 on the parport driver, and uses direct I/O access instead. This
769 might be preferred on embedded systems where wasting memory for
770 the clean but heavy parport handling is not an option. The
771 drawback is a reduced portability and the impossibility to
772 daisy-chain other parallel port devices.
774 Don't say Y here if you said Y or M to i2c-parport. Saying M to
775 both is possible but both modules should not be loaded at the same
778 This support is also available as a module. If so, the module
779 will be called i2c-parport-light.
782 tristate "TAOS evaluation module"
783 depends on EXPERIMENTAL
788 This supports TAOS evaluation modules on serial port. In order to
789 use this driver, you will need the inputattach tool, which is part
790 of the input-utils package.
794 This support is also available as a module. If so, the module
795 will be called i2c-taos-evm.
798 tristate "Tiny-USB adapter"
801 If you say yes to this option, support will be included for the
802 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
803 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
805 This driver can also be built as a module. If so, the module
806 will be called i2c-tiny-usb.
808 comment "Other I2C/SMBus bus drivers"
811 tristate "Acorn IOC/IOMD I2C bus support"
812 depends on ARCH_ACORN
816 Say yes if you want to support the I2C bus on Acorn platforms.
818 If you don't know, say Y.
821 tristate "Elektor ISA card"
822 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
825 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
828 This support is also available as a module. If so, the module
829 will be called i2c-elektor.
832 tristate "PCA9564/PCA9665 on an ISA bus"
837 This driver supports ISA boards using the Philips PCA9564/PCA9665
838 parallel bus to I2C bus controller.
840 This driver can also be built as a module. If so, the module
841 will be called i2c-pca-isa.
843 This device is almost undetectable and using this driver on a
844 system which doesn't have this device will result in long
845 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
846 time). If unsure, say N.
849 tristate "SiByte SMBus interface"
850 depends on SIBYTE_SB1xxx_SOC
852 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
855 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
856 depends on SCx200_GPIO
859 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
861 If you don't know what to do here, say N.
863 This support is also available as a module. If so, the module
864 will be called scx200_i2c.
866 This driver is deprecated and will be dropped soon. Use i2c-gpio
867 (or scx200_acb) instead.
869 config SCx200_I2C_SCL
870 int "GPIO pin used for SCL"
871 depends on SCx200_I2C
874 Enter the GPIO pin number used for the SCL signal. This value can
875 also be specified with a module parameter.
877 config SCx200_I2C_SDA
878 int "GPIO pin used for SDA"
879 depends on SCx200_I2C
882 Enter the GPIO pin number used for the SSA signal. This value can
883 also be specified with a module parameter.
886 tristate "Geode ACCESS.bus support"
887 depends on X86_32 && PCI
889 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
890 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
892 If you don't know what to do here, say N.
894 This support is also available as a module. If so, the module
895 will be called scx200_acb.