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"
115 Say Y here if you want to use SMBus controller on the Intel SCH
118 This driver can also be built as a module. If so, the module
119 will be called i2c-isch.
122 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
125 If you say yes to this option, support will be included for the Intel
126 PIIX4 family of mainboard I2C interfaces. Specifically, the following
127 versions of the chipset are supported (note that Serverworks is part
145 This driver can also be built as a module. If so, the module
146 will be called i2c-piix4.
149 tristate "Nvidia nForce2, nForce3 and nForce4"
152 If you say yes to this option, support will be included for the Nvidia
153 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
155 This driver can also be built as a module. If so, the module
156 will be called i2c-nforce2.
158 config I2C_NFORCE2_S4985
159 tristate "SMBus multiplexing on the Tyan S4985"
160 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
162 Enabling this option will add specific SMBus support for the Tyan
163 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
164 over 4 different channels, where the various memory module EEPROMs
165 live. Saying yes here will give you access to these in addition
168 This driver can also be built as a module. If so, the module
169 will be called i2c-nforce2-s4985.
175 If you say yes to this option, support will be included for the
176 SiS5595 SMBus (a subset of I2C) interface.
178 This driver can also be built as a module. If so, the module
179 will be called i2c-sis5595.
182 tristate "SiS 630/730"
185 If you say yes to this option, support will be included for the
186 SiS630 and SiS730 SMBus (a subset of I2C) interface.
188 This driver can also be built as a module. If so, the module
189 will be called i2c-sis630.
195 If you say yes to this option, support will be included for the SiS
196 96x SMBus (a subset of I2C) interfaces. Specifically, the following
197 chipsets are supported:
206 This driver can also be built as a module. If so, the module
207 will be called i2c-sis96x.
210 tristate "VIA VT82C586B"
211 depends on PCI && EXPERIMENTAL
214 If you say yes to this option, support will be included for the VIA
215 82C586B I2C interface
217 This driver can also be built as a module. If so, the module
218 will be called i2c-via.
221 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
224 If you say yes to this option, support will be included for the VIA
225 VT82C596 and later SMBus interface. Specifically, the following
226 chipsets are supported:
238 This driver can also be built as a module. If so, the module
239 will be called i2c-viapro.
243 comment "ACPI drivers"
246 tristate "SMBus Control Method Interface"
248 This driver supports the SMBus Control Method Interface. It needs the
249 BIOS to declare ACPI control methods as described in the SMBus Control
250 Method Interface specification.
252 To compile this driver as a module, choose M here:
253 the module will be called i2c-scmi.
257 comment "Mac SMBus host controller drivers"
258 depends on PPC_CHRP || PPC_PMAC
261 tristate "CHRP Apple Hydra Mac I/O I2C interface"
262 depends on PCI && PPC_CHRP && EXPERIMENTAL
265 This supports the use of the I2C interface in the Apple Hydra Mac
266 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
269 This support is also available as a module. If so, the module
270 will be called i2c-hydra.
273 tristate "Powermac I2C interface"
277 This exposes the various PowerMac i2c interfaces to the linux i2c
278 layer and to userland. It is used by various drivers on the PowerMac
279 platform, and should generally be enabled.
281 This support is also available as a module. If so, the module
282 will be called i2c-powermac.
284 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
287 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
288 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
290 This supports the use of the I2C interface on Atmel AT91
293 This driver is BROKEN because the controller which it uses
294 will easily trigger RX overrun and TX underrun errors. Using
295 low I2C clock rates may partially work around those issues
296 on some systems. Another serious problem is that there is no
297 documented way to issue repeated START conditions, as needed
298 to support combined I2C messages. Use the i2c-gpio driver
299 unless your system can cope with those limitations.
302 tristate "Au1550/Au1200 SMBus interface"
303 depends on MIPS_ALCHEMY
305 If you say yes to this option, support will be included for the
306 Au1550 and Au1200 SMBus interface.
308 This driver can also be built as a module. If so, the module
309 will be called i2c-au1550.
311 config I2C_BLACKFIN_TWI
312 tristate "Blackfin TWI I2C support"
314 depends on !BF561 && !BF531 && !BF532 && !BF533
316 This is the I2C bus driver for Blackfin on-chip TWI interface.
318 This driver can also be built as a module. If so, the module
319 will be called i2c-bfin-twi.
321 config I2C_BLACKFIN_TWI_CLK_KHZ
322 int "Blackfin TWI I2C clock (kHz)"
323 depends on I2C_BLACKFIN_TWI
327 The unit of the TWI clock is kHz.
330 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
331 depends on (CPM1 || CPM2) && OF_I2C
333 This supports the use of the I2C interface on Freescale
334 processors with CPM1 or CPM2.
336 This driver can also be built as a module. If so, the module
337 will be called i2c-cpm.
340 tristate "DaVinci I2C driver"
341 depends on ARCH_DAVINCI
343 Support for TI DaVinci I2C controller driver.
345 This driver can also be built as a module. If so, the module
346 will be called i2c-davinci.
348 Please note that this driver might be needed to bring up other
349 devices such as DaVinci NIC.
350 For details please see http://www.ti.com/davinci
352 config I2C_DESIGNWARE_CORE
355 config I2C_DESIGNWARE_PLATFORM
356 tristate "Synopsys DesignWare Platfrom"
358 select I2C_DESIGNWARE_CORE
360 If you say yes to this option, support will be included for the
361 Synopsys DesignWare I2C adapter. Only master mode is supported.
363 This driver can also be built as a module. If so, the module
364 will be called i2c-designware-platform.
366 config I2C_DESIGNWARE_PCI
367 tristate "Synopsys DesignWare PCI"
369 select I2C_DESIGNWARE_CORE
371 If you say yes to this option, support will be included for the
372 Synopsys DesignWare I2C adapter. Only master mode is supported.
374 This driver can also be built as a module. If so, the module
375 will be called i2c-designware-pci.
378 tristate "GPIO-based bitbanging I2C"
379 depends on GENERIC_GPIO
382 This is a very simple bitbanging I2C driver utilizing the
383 arch-neutral GPIO API to control the SCL and SDA lines.
385 config I2C_HIGHLANDER
386 tristate "Highlander FPGA SMBus interface"
387 depends on SH_HIGHLANDER
389 If you say yes to this option, support will be included for
390 the SMBus interface located in the FPGA on various Highlander
391 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
392 FPGAs. This is wholly unrelated to the SoC I2C.
394 This driver can also be built as a module. If so, the module
395 will be called i2c-highlander.
398 tristate "IBM PPC 4xx on-chip I2C interface"
401 Say Y here if you want to use IIC peripheral found on
402 embedded IBM PPC 4xx based systems.
404 This driver can also be built as a module. If so, the module
405 will be called i2c-ibm_iic.
408 tristate "IMX I2C interface"
411 Say Y here if you want to use the IIC bus controller on
412 the Freescale i.MX/MXC processors.
414 This driver can also be built as a module. If so, the module
415 will be called i2c-imx.
418 tristate "Intel Moorestown/Medfield Platform I2C controller"
421 Say Y here if you have an Intel Moorestown/Medfield platform I2C
424 This support is also available as a module. If so, the module
425 will be called i2c-intel-mid.
428 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
429 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
431 Say Y here if you want to use the IIC bus controller on
432 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
434 This driver can also be built as a module. If so, the module
435 will be called i2c-iop3xx.
438 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
439 depends on ARCH_IXP2000
442 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
443 system and are using GPIO lines for an I2C bus.
445 This support is also available as a module. If so, the module
446 will be called i2c-ixp2000.
448 This driver is deprecated and will be dropped soon. Use i2c-gpio
452 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
455 If you say yes to this option, support will be included for the
456 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
457 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
459 This driver can also be built as a module. If so, the module
460 will be called i2c-mpc.
463 tristate "Marvell mv64xxx I2C Controller"
464 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
466 If you say yes to this option, support will be included for the
467 built-in I2C interface on the Marvell 64xxx line of host bridges.
469 This driver can also be built as a module. If so, the module
470 will be called i2c-mv64xxx.
473 tristate "Freescale i.MX28 I2C interface"
476 Say Y here if you want to use the I2C bus controller on
477 the Freescale i.MX28 processors.
479 This driver can also be built as a module. If so, the module
480 will be called i2c-mxs.
483 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
484 depends on PLAT_NOMADIK
486 If you say yes to this option, support will be included for the
487 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
490 tristate "NUC900 I2C Driver"
491 depends on ARCH_W90X900
493 Say Y here to include support for I2C controller in the
494 Winbond/Nuvoton NUC900 based System-on-Chip devices.
497 tristate "OpenCores I2C Controller"
498 depends on EXPERIMENTAL
500 If you say yes to this option, support will be included for the
501 OpenCores I2C controller. For details see
502 http://www.opencores.org/projects.cgi/web/i2c/overview
504 This driver can also be built as a module. If so, the module
505 will be called i2c-ocores.
508 tristate "OMAP I2C adapter"
510 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
512 If you say yes to this option, support will be included for the
513 I2C interface on the Texas Instruments OMAP1/2 family of processors.
514 Like OMAP1510/1610/1710/5912 and OMAP242x.
515 For details see http://www.ti.com/omap.
518 tristate "PA Semi SMBus interface"
519 depends on PPC_PASEMI && PCI
521 Supports the PA Semi PWRficient on-chip SMBus interfaces.
523 config I2C_PCA_PLATFORM
524 tristate "PCA9564/PCA9665 as platform device"
528 This driver supports a memory mapped Philips PCA9564/PCA9665
529 parallel bus to I2C bus controller.
531 This driver can also be built as a module. If so, the module
532 will be called i2c-pca-platform.
535 tristate "PMC MSP I2C TWI Controller"
538 This driver supports the PMC TWI controller on MSP devices.
540 This driver can also be built as module. If so, the module
541 will be called i2c-pmcmsp.
544 tristate "I2C bus support for Philips PNX and NXP LPC targets"
545 depends on ARCH_PNX4008 || ARCH_LPC32XX
547 This driver supports the Philips IP3204 I2C IP block master and/or
550 This driver can also be built as a module. If so, the module
551 will be called i2c-pnx.
554 tristate "PKUnity v3 I2C bus support"
555 depends on UNICORE32 && ARCH_PUV3
558 This driver supports the I2C IP inside the PKUnity-v3 SoC.
559 This I2C bus controller is under AMBA/AXI bus.
561 This driver can also be built as a module. If so, the module
562 will be called i2c-puv3.
565 tristate "Intel PXA2XX I2C adapter"
566 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
568 If you have devices in the PXA I2C bus, say yes to this option.
569 This driver can also be built as a module. If so, the module
570 will be called i2c-pxa.
573 def_bool I2C_PXA && X86_32 && PCI && OF
576 bool "Intel PXA2XX I2C Slave comms support"
577 depends on I2C_PXA && !X86_32
579 Support I2C slave mode communications on the PXA I2C bus. This
580 is necessary for systems where the PXA may be a target on the
583 config HAVE_S3C2410_I2C
586 This will include I2C support for Samsung SoCs. If you want to
587 include I2C support for any machine, kindly select this in the
588 respective Kconfig file.
591 tristate "S3C2410 I2C Driver"
592 depends on HAVE_S3C2410_I2C
594 Say Y here to include support for I2C controller in the
598 tristate "S6000 I2C support"
599 depends on XTENSA_VARIANT_S6000
601 This driver supports the on chip I2C device on the
602 S6000 xtensa processor family.
604 To compile this driver as a module, choose M here. The module
605 will be called i2c-s6000.
608 tristate "Renesas SH7760 I2C Controller"
609 depends on CPU_SUBTYPE_SH7760
611 This driver supports the 2 I2C interfaces on the Renesas SH7760.
613 This driver can also be built as a module. If so, the module
614 will be called i2c-sh7760.
617 tristate "SuperH Mobile I2C Controller"
618 depends on SUPERH || ARCH_SHMOBILE
620 If you say yes to this option, support will be included for the
621 built-in I2C interface on the Renesas SH-Mobile processor.
623 This driver can also be built as a module. If so, the module
624 will be called i2c-sh_mobile.
627 tristate "Simtec Generic I2C interface"
630 If you say yes to this option, support will be included for
631 the Simtec Generic I2C interface. This driver is for the
632 simple I2C bus used on newer Simtec products for general
633 I2C, such as DDC on the Simtec BBD2016A.
635 This driver can also be built as a module. If so, the module
636 will be called i2c-simtec.
639 tristate "ST Microelectronics DDC I2C interface"
641 default y if MACH_U300
643 If you say yes to this option, support will be included for the
644 I2C interface from ST Microelectronics simply called "DDC I2C"
645 supporting both I2C and DDC, used in e.g. the U300 series
648 This driver can also be built as a module. If so, the module
649 will be called i2c-stu300.
652 tristate "NVIDIA Tegra internal I2C controller"
653 depends on ARCH_TEGRA
655 If you say yes to this option, support will be included for the
656 I2C controller embedded in NVIDIA Tegra SOCs
659 tristate "ARM Versatile/Realview I2C bus support"
660 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
663 Say yes if you want to support the I2C serial bus on ARMs Versatile
666 This driver can also be built as a module. If so, the module
667 will be called i2c-versatile.
670 tristate "Cavium OCTEON I2C bus support"
671 depends on CPU_CAVIUM_OCTEON
673 Say yes if you want to support the I2C serial bus on Cavium
676 This driver can also be built as a module. If so, the module
677 will be called i2c-octeon.
680 tristate "Xilinx I2C Controller"
681 depends on EXPERIMENTAL && HAS_IOMEM
683 If you say yes to this option, support will be included for the
684 Xilinx I2C controller.
686 This driver can also be built as a module. If so, the module
687 will be called xilinx_i2c.
690 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
693 This driver is for PCH(Platform controller Hub) I2C of EG20T which
694 is an IOH(Input/Output Hub) for x86 embedded processor.
695 This driver can access PCH I2C bus device.
697 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
698 Output Hub), ML7213 and ML7223.
699 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
700 for MP(Media Phone) use.
701 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
702 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
704 comment "External I2C/SMBus adapter drivers"
706 config I2C_DIOLAN_U2C
707 tristate "Diolan U2C-12 USB adapter"
710 If you say yes to this option, support will be included for Diolan
711 U2C-12, a USB to I2C interface.
713 This driver can also be built as a module. If so, the module
714 will be called i2c-diolan-u2c.
717 tristate "Parallel port adapter"
722 This supports parallel port I2C adapters such as the ones made by
723 Philips or Velleman, Analog Devices evaluation boards, and more.
724 Basically any adapter using the parallel port as an I2C bus with
725 no extra chipset is supported by this driver, or could be.
727 This driver is a replacement for (and was inspired by) an older
728 driver named i2c-philips-par. The new driver supports more devices,
729 and makes it easier to add support for new devices.
731 An adapter type parameter is now mandatory. Please read the file
732 Documentation/i2c/busses/i2c-parport for details.
734 Another driver exists, named i2c-parport-light, which doesn't depend
735 on the parport driver. This is meant for embedded systems. Don't say
736 Y here if you intend to say Y or M there.
738 This support is also available as a module. If so, the module
739 will be called i2c-parport.
741 config I2C_PARPORT_LIGHT
742 tristate "Parallel port adapter (light)"
746 This supports parallel port I2C adapters such as the ones made by
747 Philips or Velleman, Analog Devices evaluation boards, and more.
748 Basically any adapter using the parallel port as an I2C bus with
749 no extra chipset is supported by this driver, or could be.
751 This driver is a light version of i2c-parport. It doesn't depend
752 on the parport driver, and uses direct I/O access instead. This
753 might be preferred on embedded systems where wasting memory for
754 the clean but heavy parport handling is not an option. The
755 drawback is a reduced portability and the impossibility to
756 daisy-chain other parallel port devices.
758 Don't say Y here if you said Y or M to i2c-parport. Saying M to
759 both is possible but both modules should not be loaded at the same
762 This support is also available as a module. If so, the module
763 will be called i2c-parport-light.
766 tristate "TAOS evaluation module"
767 depends on EXPERIMENTAL
772 This supports TAOS evaluation modules on serial port. In order to
773 use this driver, you will need the inputattach tool, which is part
774 of the input-utils package.
778 This support is also available as a module. If so, the module
779 will be called i2c-taos-evm.
782 tristate "Tiny-USB adapter"
785 If you say yes to this option, support will be included for the
786 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
787 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
789 This driver can also be built as a module. If so, the module
790 will be called i2c-tiny-usb.
792 comment "Other I2C/SMBus bus drivers"
795 tristate "Acorn IOC/IOMD I2C bus support"
796 depends on ARCH_ACORN
800 Say yes if you want to support the I2C bus on Acorn platforms.
802 If you don't know, say Y.
805 tristate "Elektor ISA card"
806 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
809 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
812 This support is also available as a module. If so, the module
813 will be called i2c-elektor.
816 tristate "PCA9564/PCA9665 on an ISA bus"
821 This driver supports ISA boards using the Philips PCA9564/PCA9665
822 parallel bus to I2C bus controller.
824 This driver can also be built as a module. If so, the module
825 will be called i2c-pca-isa.
827 This device is almost undetectable and using this driver on a
828 system which doesn't have this device will result in long
829 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
830 time). If unsure, say N.
833 tristate "SiByte SMBus interface"
834 depends on SIBYTE_SB1xxx_SOC
836 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
839 tristate "I2C/SMBus Test Stub"
840 depends on EXPERIMENTAL && m
843 This module may be useful to developers of SMBus client drivers,
844 especially for certain kinds of sensor chips.
846 If you do build this module, be sure to read the notes and warnings
847 in <file:Documentation/i2c/i2c-stub>.
849 If you don't know what to do here, definitely say N.
852 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
853 depends on SCx200_GPIO
856 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
858 If you don't know what to do here, say N.
860 This support is also available as a module. If so, the module
861 will be called scx200_i2c.
863 This driver is deprecated and will be dropped soon. Use i2c-gpio
864 (or scx200_acb) instead.
866 config SCx200_I2C_SCL
867 int "GPIO pin used for SCL"
868 depends on SCx200_I2C
871 Enter the GPIO pin number used for the SCL signal. This value can
872 also be specified with a module parameter.
874 config SCx200_I2C_SDA
875 int "GPIO pin used for SDA"
876 depends on SCx200_I2C
879 Enter the GPIO pin number used for the SSA signal. This value can
880 also be specified with a module parameter.
883 tristate "Geode ACCESS.bus support"
884 depends on X86_32 && PCI
886 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
887 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
889 If you don't know what to do here, say N.
891 This support is also available as a module. If so, the module
892 will be called scx200_acb.