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)
109 This driver can also be built as a module. If so, the module
110 will be called i2c-i801.
113 tristate "Intel SCH SMBus 1.0"
117 Say Y here if you want to use SMBus controller on the Intel SCH
120 This driver can also be built as a module. If so, the module
121 will be called i2c-isch.
124 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
127 If you say yes to this option, support will be included for the Intel
128 PIIX4 family of mainboard I2C interfaces. Specifically, the following
129 versions of the chipset are supported (note that Serverworks is part
148 This driver can also be built as a module. If so, the module
149 will be called i2c-piix4.
152 tristate "Nvidia nForce2, nForce3 and nForce4"
155 If you say yes to this option, support will be included for the Nvidia
156 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
158 This driver can also be built as a module. If so, the module
159 will be called i2c-nforce2.
161 config I2C_NFORCE2_S4985
162 tristate "SMBus multiplexing on the Tyan S4985"
163 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
165 Enabling this option will add specific SMBus support for the Tyan
166 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
167 over 4 different channels, where the various memory module EEPROMs
168 live. Saying yes here will give you access to these in addition
171 This driver can also be built as a module. If so, the module
172 will be called i2c-nforce2-s4985.
178 If you say yes to this option, support will be included for the
179 SiS5595 SMBus (a subset of I2C) interface.
181 This driver can also be built as a module. If so, the module
182 will be called i2c-sis5595.
185 tristate "SiS 630/730"
188 If you say yes to this option, support will be included for the
189 SiS630 and SiS730 SMBus (a subset of I2C) interface.
191 This driver can also be built as a module. If so, the module
192 will be called i2c-sis630.
198 If you say yes to this option, support will be included for the SiS
199 96x SMBus (a subset of I2C) interfaces. Specifically, the following
200 chipsets are supported:
209 This driver can also be built as a module. If so, the module
210 will be called i2c-sis96x.
213 tristate "VIA VT82C586B"
214 depends on PCI && EXPERIMENTAL
217 If you say yes to this option, support will be included for the VIA
218 82C586B I2C interface
220 This driver can also be built as a module. If so, the module
221 will be called i2c-via.
224 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
227 If you say yes to this option, support will be included for the VIA
228 VT82C596 and later SMBus interface. Specifically, the following
229 chipsets are supported:
241 This driver can also be built as a module. If so, the module
242 will be called i2c-viapro.
246 comment "ACPI drivers"
249 tristate "SMBus Control Method Interface"
251 This driver supports the SMBus Control Method Interface. It needs the
252 BIOS to declare ACPI control methods as described in the SMBus Control
253 Method Interface specification.
255 To compile this driver as a module, choose M here:
256 the module will be called i2c-scmi.
260 comment "Mac SMBus host controller drivers"
261 depends on PPC_CHRP || PPC_PMAC
264 tristate "CHRP Apple Hydra Mac I/O I2C interface"
265 depends on PCI && PPC_CHRP && EXPERIMENTAL
268 This supports the use of the I2C interface in the Apple Hydra Mac
269 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
272 This support is also available as a module. If so, the module
273 will be called i2c-hydra.
276 tristate "Powermac I2C interface"
280 This exposes the various PowerMac i2c interfaces to the linux i2c
281 layer and to userland. It is used by various drivers on the PowerMac
282 platform, and should generally be enabled.
284 This support is also available as a module. If so, the module
285 will be called i2c-powermac.
287 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
290 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
291 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
293 This supports the use of the I2C interface on Atmel AT91
296 This driver is BROKEN because the controller which it uses
297 will easily trigger RX overrun and TX underrun errors. Using
298 low I2C clock rates may partially work around those issues
299 on some systems. Another serious problem is that there is no
300 documented way to issue repeated START conditions, as needed
301 to support combined I2C messages. Use the i2c-gpio driver
302 unless your system can cope with those limitations.
305 tristate "Au1550/Au1200 SMBus interface"
306 depends on MIPS_ALCHEMY
308 If you say yes to this option, support will be included for the
309 Au1550 and Au1200 SMBus interface.
311 This driver can also be built as a module. If so, the module
312 will be called i2c-au1550.
314 config I2C_BLACKFIN_TWI
315 tristate "Blackfin TWI I2C support"
317 depends on !BF561 && !BF531 && !BF532 && !BF533
319 This is the I2C bus driver for Blackfin on-chip TWI interface.
321 This driver can also be built as a module. If so, the module
322 will be called i2c-bfin-twi.
324 config I2C_BLACKFIN_TWI_CLK_KHZ
325 int "Blackfin TWI I2C clock (kHz)"
326 depends on I2C_BLACKFIN_TWI
330 The unit of the TWI clock is kHz.
333 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
334 depends on (CPM1 || CPM2) && OF_I2C
336 This supports the use of the I2C interface on Freescale
337 processors with CPM1 or CPM2.
339 This driver can also be built as a module. If so, the module
340 will be called i2c-cpm.
343 tristate "DaVinci I2C driver"
344 depends on ARCH_DAVINCI
346 Support for TI DaVinci I2C controller driver.
348 This driver can also be built as a module. If so, the module
349 will be called i2c-davinci.
351 Please note that this driver might be needed to bring up other
352 devices such as DaVinci NIC.
353 For details please see http://www.ti.com/davinci
355 config I2C_DESIGNWARE_CORE
358 config I2C_DESIGNWARE_PLATFORM
359 tristate "Synopsys DesignWare Platfrom"
361 select I2C_DESIGNWARE_CORE
363 If you say yes to this option, support will be included for the
364 Synopsys DesignWare I2C adapter. Only master mode is supported.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-designware-platform.
369 config I2C_DESIGNWARE_PCI
370 tristate "Synopsys DesignWare PCI"
372 select I2C_DESIGNWARE_CORE
374 If you say yes to this option, support will be included for the
375 Synopsys DesignWare I2C adapter. Only master mode is supported.
377 This driver can also be built as a module. If so, the module
378 will be called i2c-designware-pci.
381 tristate "GPIO-based bitbanging I2C"
382 depends on GENERIC_GPIO
385 This is a very simple bitbanging I2C driver utilizing the
386 arch-neutral GPIO API to control the SCL and SDA lines.
388 config I2C_HIGHLANDER
389 tristate "Highlander FPGA SMBus interface"
390 depends on SH_HIGHLANDER
392 If you say yes to this option, support will be included for
393 the SMBus interface located in the FPGA on various Highlander
394 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
395 FPGAs. This is wholly unrelated to the SoC I2C.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-highlander.
401 tristate "IBM PPC 4xx on-chip I2C interface"
404 Say Y here if you want to use IIC peripheral found on
405 embedded IBM PPC 4xx based systems.
407 This driver can also be built as a module. If so, the module
408 will be called i2c-ibm_iic.
411 tristate "IMX I2C interface"
414 Say Y here if you want to use the IIC bus controller on
415 the Freescale i.MX/MXC processors.
417 This driver can also be built as a module. If so, the module
418 will be called i2c-imx.
421 tristate "Intel Moorestown/Medfield Platform I2C controller"
424 Say Y here if you have an Intel Moorestown/Medfield platform I2C
427 This support is also available as a module. If so, the module
428 will be called i2c-intel-mid.
431 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
432 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
434 Say Y here if you want to use the IIC bus controller on
435 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
437 This driver can also be built as a module. If so, the module
438 will be called i2c-iop3xx.
441 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
442 depends on ARCH_IXP2000
445 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
446 system and are using GPIO lines for an I2C bus.
448 This support is also available as a module. If so, the module
449 will be called i2c-ixp2000.
451 This driver is deprecated and will be dropped soon. Use i2c-gpio
455 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
458 If you say yes to this option, support will be included for the
459 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
460 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
462 This driver can also be built as a module. If so, the module
463 will be called i2c-mpc.
466 tristate "Marvell mv64xxx I2C Controller"
467 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
469 If you say yes to this option, support will be included for the
470 built-in I2C interface on the Marvell 64xxx line of host bridges.
472 This driver can also be built as a module. If so, the module
473 will be called i2c-mv64xxx.
476 tristate "Freescale i.MX28 I2C interface"
479 Say Y here if you want to use the I2C bus controller on
480 the Freescale i.MX28 processors.
482 This driver can also be built as a module. If so, the module
483 will be called i2c-mxs.
486 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
487 depends on PLAT_NOMADIK
489 If you say yes to this option, support will be included for the
490 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
493 tristate "NUC900 I2C Driver"
494 depends on ARCH_W90X900
496 Say Y here to include support for I2C controller in the
497 Winbond/Nuvoton NUC900 based System-on-Chip devices.
500 tristate "OpenCores I2C Controller"
501 depends on EXPERIMENTAL
503 If you say yes to this option, support will be included for the
504 OpenCores I2C controller. For details see
505 http://www.opencores.org/projects.cgi/web/i2c/overview
507 This driver can also be built as a module. If so, the module
508 will be called i2c-ocores.
511 tristate "OMAP I2C adapter"
513 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
515 If you say yes to this option, support will be included for the
516 I2C interface on the Texas Instruments OMAP1/2 family of processors.
517 Like OMAP1510/1610/1710/5912 and OMAP242x.
518 For details see http://www.ti.com/omap.
521 tristate "PA Semi SMBus interface"
522 depends on PPC_PASEMI && PCI
524 Supports the PA Semi PWRficient on-chip SMBus interfaces.
526 config I2C_PCA_PLATFORM
527 tristate "PCA9564/PCA9665 as platform device"
531 This driver supports a memory mapped Philips PCA9564/PCA9665
532 parallel bus to I2C bus controller.
534 This driver can also be built as a module. If so, the module
535 will be called i2c-pca-platform.
538 tristate "PMC MSP I2C TWI Controller"
541 This driver supports the PMC TWI controller on MSP devices.
543 This driver can also be built as module. If so, the module
544 will be called i2c-pmcmsp.
547 tristate "I2C bus support for Philips PNX and NXP LPC targets"
548 depends on ARCH_PNX4008 || ARCH_LPC32XX
550 This driver supports the Philips IP3204 I2C IP block master and/or
553 This driver can also be built as a module. If so, the module
554 will be called i2c-pnx.
557 tristate "PKUnity v3 I2C bus support"
558 depends on UNICORE32 && ARCH_PUV3
561 This driver supports the I2C IP inside the PKUnity-v3 SoC.
562 This I2C bus controller is under AMBA/AXI bus.
564 This driver can also be built as a module. If so, the module
565 will be called i2c-puv3.
568 tristate "Intel PXA2XX I2C adapter"
569 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
571 If you have devices in the PXA I2C bus, say yes to this option.
572 This driver can also be built as a module. If so, the module
573 will be called i2c-pxa.
576 def_bool I2C_PXA && X86_32 && PCI && OF
579 bool "Intel PXA2XX I2C Slave comms support"
580 depends on I2C_PXA && !X86_32
582 Support I2C slave mode communications on the PXA I2C bus. This
583 is necessary for systems where the PXA may be a target on the
586 config HAVE_S3C2410_I2C
589 This will include I2C support for Samsung SoCs. If you want to
590 include I2C support for any machine, kindly select this in the
591 respective Kconfig file.
594 tristate "S3C2410 I2C Driver"
595 depends on HAVE_S3C2410_I2C
597 Say Y here to include support for I2C controller in the
601 tristate "S6000 I2C support"
602 depends on XTENSA_VARIANT_S6000
604 This driver supports the on chip I2C device on the
605 S6000 xtensa processor family.
607 To compile this driver as a module, choose M here. The module
608 will be called i2c-s6000.
611 tristate "Renesas SH7760 I2C Controller"
612 depends on CPU_SUBTYPE_SH7760
614 This driver supports the 2 I2C interfaces on the Renesas SH7760.
616 This driver can also be built as a module. If so, the module
617 will be called i2c-sh7760.
620 tristate "SuperH Mobile I2C Controller"
621 depends on SUPERH || ARCH_SHMOBILE
623 If you say yes to this option, support will be included for the
624 built-in I2C interface on the Renesas SH-Mobile processor.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-sh_mobile.
630 tristate "Simtec Generic I2C interface"
633 If you say yes to this option, support will be included for
634 the Simtec Generic I2C interface. This driver is for the
635 simple I2C bus used on newer Simtec products for general
636 I2C, such as DDC on the Simtec BBD2016A.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-simtec.
642 tristate "ST Microelectronics DDC I2C interface"
644 default y if MACH_U300
646 If you say yes to this option, support will be included for the
647 I2C interface from ST Microelectronics simply called "DDC I2C"
648 supporting both I2C and DDC, used in e.g. the U300 series
651 This driver can also be built as a module. If so, the module
652 will be called i2c-stu300.
655 tristate "NVIDIA Tegra internal I2C controller"
656 depends on ARCH_TEGRA
658 If you say yes to this option, support will be included for the
659 I2C controller embedded in NVIDIA Tegra SOCs
662 tristate "ARM Versatile/Realview I2C bus support"
663 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
666 Say yes if you want to support the I2C serial bus on ARMs Versatile
669 This driver can also be built as a module. If so, the module
670 will be called i2c-versatile.
673 tristate "Cavium OCTEON I2C bus support"
674 depends on CPU_CAVIUM_OCTEON
676 Say yes if you want to support the I2C serial bus on Cavium
679 This driver can also be built as a module. If so, the module
680 will be called i2c-octeon.
683 tristate "Xilinx I2C Controller"
684 depends on EXPERIMENTAL && HAS_IOMEM
686 If you say yes to this option, support will be included for the
687 Xilinx I2C controller.
689 This driver can also be built as a module. If so, the module
690 will be called xilinx_i2c.
693 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
696 This driver is for PCH(Platform controller Hub) I2C of EG20T which
697 is an IOH(Input/Output Hub) for x86 embedded processor.
698 This driver can access PCH I2C bus device.
700 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
701 Output Hub), ML7213 and ML7223.
702 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
703 for MP(Media Phone) use.
704 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
705 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
707 comment "External I2C/SMBus adapter drivers"
709 config I2C_DIOLAN_U2C
710 tristate "Diolan U2C-12 USB adapter"
713 If you say yes to this option, support will be included for Diolan
714 U2C-12, a USB to I2C interface.
716 This driver can also be built as a module. If so, the module
717 will be called i2c-diolan-u2c.
720 tristate "Parallel port adapter"
725 This supports parallel port I2C adapters such as the ones made by
726 Philips or Velleman, Analog Devices evaluation boards, and more.
727 Basically any adapter using the parallel port as an I2C bus with
728 no extra chipset is supported by this driver, or could be.
730 This driver is a replacement for (and was inspired by) an older
731 driver named i2c-philips-par. The new driver supports more devices,
732 and makes it easier to add support for new devices.
734 An adapter type parameter is now mandatory. Please read the file
735 Documentation/i2c/busses/i2c-parport for details.
737 Another driver exists, named i2c-parport-light, which doesn't depend
738 on the parport driver. This is meant for embedded systems. Don't say
739 Y here if you intend to say Y or M there.
741 This support is also available as a module. If so, the module
742 will be called i2c-parport.
744 config I2C_PARPORT_LIGHT
745 tristate "Parallel port adapter (light)"
749 This supports parallel port I2C adapters such as the ones made by
750 Philips or Velleman, Analog Devices evaluation boards, and more.
751 Basically any adapter using the parallel port as an I2C bus with
752 no extra chipset is supported by this driver, or could be.
754 This driver is a light version of i2c-parport. It doesn't depend
755 on the parport driver, and uses direct I/O access instead. This
756 might be preferred on embedded systems where wasting memory for
757 the clean but heavy parport handling is not an option. The
758 drawback is a reduced portability and the impossibility to
759 daisy-chain other parallel port devices.
761 Don't say Y here if you said Y or M to i2c-parport. Saying M to
762 both is possible but both modules should not be loaded at the same
765 This support is also available as a module. If so, the module
766 will be called i2c-parport-light.
769 tristate "TAOS evaluation module"
770 depends on EXPERIMENTAL
775 This supports TAOS evaluation modules on serial port. In order to
776 use this driver, you will need the inputattach tool, which is part
777 of the input-utils package.
781 This support is also available as a module. If so, the module
782 will be called i2c-taos-evm.
785 tristate "Tiny-USB adapter"
788 If you say yes to this option, support will be included for the
789 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
790 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
792 This driver can also be built as a module. If so, the module
793 will be called i2c-tiny-usb.
795 comment "Other I2C/SMBus bus drivers"
798 tristate "Acorn IOC/IOMD I2C bus support"
799 depends on ARCH_ACORN
803 Say yes if you want to support the I2C bus on Acorn platforms.
805 If you don't know, say Y.
808 tristate "Elektor ISA card"
809 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
812 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
815 This support is also available as a module. If so, the module
816 will be called i2c-elektor.
819 tristate "PCA9564/PCA9665 on an ISA bus"
824 This driver supports ISA boards using the Philips PCA9564/PCA9665
825 parallel bus to I2C bus controller.
827 This driver can also be built as a module. If so, the module
828 will be called i2c-pca-isa.
830 This device is almost undetectable and using this driver on a
831 system which doesn't have this device will result in long
832 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
833 time). If unsure, say N.
836 tristate "SiByte SMBus interface"
837 depends on SIBYTE_SB1xxx_SOC
839 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
842 tristate "I2C/SMBus Test Stub"
843 depends on EXPERIMENTAL && m
846 This module may be useful to developers of SMBus client drivers,
847 especially for certain kinds of sensor chips.
849 If you do build this module, be sure to read the notes and warnings
850 in <file:Documentation/i2c/i2c-stub>.
852 If you don't know what to do here, definitely say N.
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.