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)
111 This driver can also be built as a module. If so, the module
112 will be called i2c-i801.
115 tristate "Intel SCH SMBus 1.0"
119 Say Y here if you want to use SMBus controller on the Intel SCH
122 This driver can also be built as a module. If so, the module
123 will be called i2c-isch.
126 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
129 If you say yes to this option, support will be included for the Intel
130 PIIX4 family of mainboard I2C interfaces. Specifically, the following
131 versions of the chipset are supported (note that Serverworks is part
151 This driver can also be built as a module. If so, the module
152 will be called i2c-piix4.
155 tristate "Nvidia nForce2, nForce3 and nForce4"
158 If you say yes to this option, support will be included for the Nvidia
159 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
161 This driver can also be built as a module. If so, the module
162 will be called i2c-nforce2.
164 config I2C_NFORCE2_S4985
165 tristate "SMBus multiplexing on the Tyan S4985"
166 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
168 Enabling this option will add specific SMBus support for the Tyan
169 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
170 over 4 different channels, where the various memory module EEPROMs
171 live. Saying yes here will give you access to these in addition
174 This driver can also be built as a module. If so, the module
175 will be called i2c-nforce2-s4985.
181 If you say yes to this option, support will be included for the
182 SiS5595 SMBus (a subset of I2C) interface.
184 This driver can also be built as a module. If so, the module
185 will be called i2c-sis5595.
188 tristate "SiS 630/730"
191 If you say yes to this option, support will be included for the
192 SiS630 and SiS730 SMBus (a subset of I2C) interface.
194 This driver can also be built as a module. If so, the module
195 will be called i2c-sis630.
201 If you say yes to this option, support will be included for the SiS
202 96x SMBus (a subset of I2C) interfaces. Specifically, the following
203 chipsets are supported:
212 This driver can also be built as a module. If so, the module
213 will be called i2c-sis96x.
216 tristate "VIA VT82C586B"
217 depends on PCI && EXPERIMENTAL
220 If you say yes to this option, support will be included for the VIA
221 82C586B I2C interface
223 This driver can also be built as a module. If so, the module
224 will be called i2c-via.
227 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
230 If you say yes to this option, support will be included for the VIA
231 VT82C596 and later SMBus interface. Specifically, the following
232 chipsets are supported:
244 This driver can also be built as a module. If so, the module
245 will be called i2c-viapro.
249 comment "ACPI drivers"
252 tristate "SMBus Control Method Interface"
254 This driver supports the SMBus Control Method Interface. It needs the
255 BIOS to declare ACPI control methods as described in the SMBus Control
256 Method Interface specification.
258 To compile this driver as a module, choose M here:
259 the module will be called i2c-scmi.
263 comment "Mac SMBus host controller drivers"
264 depends on PPC_CHRP || PPC_PMAC
267 tristate "CHRP Apple Hydra Mac I/O I2C interface"
268 depends on PCI && PPC_CHRP && EXPERIMENTAL
271 This supports the use of the I2C interface in the Apple Hydra Mac
272 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
275 This support is also available as a module. If so, the module
276 will be called i2c-hydra.
279 tristate "Powermac I2C interface"
283 This exposes the various PowerMac i2c interfaces to the linux i2c
284 layer and to userland. It is used by various drivers on the PowerMac
285 platform, and should generally be enabled.
287 This support is also available as a module. If so, the module
288 will be called i2c-powermac.
290 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
293 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
294 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
296 This supports the use of the I2C interface on Atmel AT91
299 This driver is BROKEN because the controller which it uses
300 will easily trigger RX overrun and TX underrun errors. Using
301 low I2C clock rates may partially work around those issues
302 on some systems. Another serious problem is that there is no
303 documented way to issue repeated START conditions, as needed
304 to support combined I2C messages. Use the i2c-gpio driver
305 unless your system can cope with those limitations.
308 tristate "Au1550/Au1200 SMBus interface"
309 depends on MIPS_ALCHEMY
311 If you say yes to this option, support will be included for the
312 Au1550 and Au1200 SMBus interface.
314 This driver can also be built as a module. If so, the module
315 will be called i2c-au1550.
317 config I2C_BLACKFIN_TWI
318 tristate "Blackfin TWI I2C support"
320 depends on !BF561 && !BF531 && !BF532 && !BF533
322 This is the I2C bus driver for Blackfin on-chip TWI interface.
324 This driver can also be built as a module. If so, the module
325 will be called i2c-bfin-twi.
327 config I2C_BLACKFIN_TWI_CLK_KHZ
328 int "Blackfin TWI I2C clock (kHz)"
329 depends on I2C_BLACKFIN_TWI
333 The unit of the TWI clock is kHz.
336 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
337 depends on (CPM1 || CPM2) && OF_I2C
339 This supports the use of the I2C interface on Freescale
340 processors with CPM1 or CPM2.
342 This driver can also be built as a module. If so, the module
343 will be called i2c-cpm.
346 tristate "DaVinci I2C driver"
347 depends on ARCH_DAVINCI
349 Support for TI DaVinci I2C controller driver.
351 This driver can also be built as a module. If so, the module
352 will be called i2c-davinci.
354 Please note that this driver might be needed to bring up other
355 devices such as DaVinci NIC.
356 For details please see http://www.ti.com/davinci
358 config I2C_DESIGNWARE_CORE
361 config I2C_DESIGNWARE_PLATFORM
362 tristate "Synopsys DesignWare Platfrom"
364 select I2C_DESIGNWARE_CORE
366 If you say yes to this option, support will be included for the
367 Synopsys DesignWare I2C adapter. Only master mode is supported.
369 This driver can also be built as a module. If so, the module
370 will be called i2c-designware-platform.
372 config I2C_DESIGNWARE_PCI
373 tristate "Synopsys DesignWare PCI"
375 select I2C_DESIGNWARE_CORE
377 If you say yes to this option, support will be included for the
378 Synopsys DesignWare I2C adapter. Only master mode is supported.
380 This driver can also be built as a module. If so, the module
381 will be called i2c-designware-pci.
384 tristate "GPIO-based bitbanging I2C"
385 depends on GENERIC_GPIO
388 This is a very simple bitbanging I2C driver utilizing the
389 arch-neutral GPIO API to control the SCL and SDA lines.
391 config I2C_HIGHLANDER
392 tristate "Highlander FPGA SMBus interface"
393 depends on SH_HIGHLANDER
395 If you say yes to this option, support will be included for
396 the SMBus interface located in the FPGA on various Highlander
397 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
398 FPGAs. This is wholly unrelated to the SoC I2C.
400 This driver can also be built as a module. If so, the module
401 will be called i2c-highlander.
404 tristate "IBM PPC 4xx on-chip I2C interface"
407 Say Y here if you want to use IIC peripheral found on
408 embedded IBM PPC 4xx based systems.
410 This driver can also be built as a module. If so, the module
411 will be called i2c-ibm_iic.
414 tristate "IMX I2C interface"
417 Say Y here if you want to use the IIC bus controller on
418 the Freescale i.MX/MXC processors.
420 This driver can also be built as a module. If so, the module
421 will be called i2c-imx.
424 tristate "Intel Moorestown/Medfield Platform I2C controller"
427 Say Y here if you have an Intel Moorestown/Medfield platform I2C
430 This support is also available as a module. If so, the module
431 will be called i2c-intel-mid.
434 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
435 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
437 Say Y here if you want to use the IIC bus controller on
438 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
440 This driver can also be built as a module. If so, the module
441 will be called i2c-iop3xx.
444 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
445 depends on ARCH_IXP2000
448 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
449 system and are using GPIO lines for an I2C bus.
451 This support is also available as a module. If so, the module
452 will be called i2c-ixp2000.
454 This driver is deprecated and will be dropped soon. Use i2c-gpio
458 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
461 If you say yes to this option, support will be included for the
462 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
463 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
465 This driver can also be built as a module. If so, the module
466 will be called i2c-mpc.
469 tristate "Marvell mv64xxx I2C Controller"
470 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
472 If you say yes to this option, support will be included for the
473 built-in I2C interface on the Marvell 64xxx line of host bridges.
475 This driver can also be built as a module. If so, the module
476 will be called i2c-mv64xxx.
479 tristate "Freescale i.MX28 I2C interface"
482 Say Y here if you want to use the I2C bus controller on
483 the Freescale i.MX28 processors.
485 This driver can also be built as a module. If so, the module
486 will be called i2c-mxs.
489 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
490 depends on PLAT_NOMADIK
492 If you say yes to this option, support will be included for the
493 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
496 tristate "NUC900 I2C Driver"
497 depends on ARCH_W90X900
499 Say Y here to include support for I2C controller in the
500 Winbond/Nuvoton NUC900 based System-on-Chip devices.
503 tristate "OpenCores I2C Controller"
504 depends on EXPERIMENTAL
506 If you say yes to this option, support will be included for the
507 OpenCores I2C controller. For details see
508 http://www.opencores.org/projects.cgi/web/i2c/overview
510 This driver can also be built as a module. If so, the module
511 will be called i2c-ocores.
514 tristate "OMAP I2C adapter"
516 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
518 If you say yes to this option, support will be included for the
519 I2C interface on the Texas Instruments OMAP1/2 family of processors.
520 Like OMAP1510/1610/1710/5912 and OMAP242x.
521 For details see http://www.ti.com/omap.
524 tristate "PA Semi SMBus interface"
525 depends on PPC_PASEMI && PCI
527 Supports the PA Semi PWRficient on-chip SMBus interfaces.
529 config I2C_PCA_PLATFORM
530 tristate "PCA9564/PCA9665 as platform device"
534 This driver supports a memory mapped Philips PCA9564/PCA9665
535 parallel bus to I2C bus controller.
537 This driver can also be built as a module. If so, the module
538 will be called i2c-pca-platform.
541 tristate "PMC MSP I2C TWI Controller"
544 This driver supports the PMC TWI controller on MSP devices.
546 This driver can also be built as module. If so, the module
547 will be called i2c-pmcmsp.
550 tristate "I2C bus support for Philips PNX and NXP LPC targets"
551 depends on ARCH_PNX4008 || ARCH_LPC32XX
553 This driver supports the Philips IP3204 I2C IP block master and/or
556 This driver can also be built as a module. If so, the module
557 will be called i2c-pnx.
560 tristate "PKUnity v3 I2C bus support"
561 depends on UNICORE32 && ARCH_PUV3
564 This driver supports the I2C IP inside the PKUnity-v3 SoC.
565 This I2C bus controller is under AMBA/AXI bus.
567 This driver can also be built as a module. If so, the module
568 will be called i2c-puv3.
571 tristate "Intel PXA2XX I2C adapter"
572 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
574 If you have devices in the PXA I2C bus, say yes to this option.
575 This driver can also be built as a module. If so, the module
576 will be called i2c-pxa.
579 def_bool I2C_PXA && X86_32 && PCI && OF
582 bool "Intel PXA2XX I2C Slave comms support"
583 depends on I2C_PXA && !X86_32
585 Support I2C slave mode communications on the PXA I2C bus. This
586 is necessary for systems where the PXA may be a target on the
589 config HAVE_S3C2410_I2C
592 This will include I2C support for Samsung SoCs. If you want to
593 include I2C support for any machine, kindly select this in the
594 respective Kconfig file.
597 tristate "S3C2410 I2C Driver"
598 depends on HAVE_S3C2410_I2C
600 Say Y here to include support for I2C controller in the
604 tristate "S6000 I2C support"
605 depends on XTENSA_VARIANT_S6000
607 This driver supports the on chip I2C device on the
608 S6000 xtensa processor family.
610 To compile this driver as a module, choose M here. The module
611 will be called i2c-s6000.
614 tristate "Renesas SH7760 I2C Controller"
615 depends on CPU_SUBTYPE_SH7760
617 This driver supports the 2 I2C interfaces on the Renesas SH7760.
619 This driver can also be built as a module. If so, the module
620 will be called i2c-sh7760.
623 tristate "SuperH Mobile I2C Controller"
624 depends on SUPERH || ARCH_SHMOBILE
626 If you say yes to this option, support will be included for the
627 built-in I2C interface on the Renesas SH-Mobile processor.
629 This driver can also be built as a module. If so, the module
630 will be called i2c-sh_mobile.
633 tristate "Simtec Generic I2C interface"
636 If you say yes to this option, support will be included for
637 the Simtec Generic I2C interface. This driver is for the
638 simple I2C bus used on newer Simtec products for general
639 I2C, such as DDC on the Simtec BBD2016A.
641 This driver can also be built as a module. If so, the module
642 will be called i2c-simtec.
645 tristate "ST Microelectronics DDC I2C interface"
647 default y if MACH_U300
649 If you say yes to this option, support will be included for the
650 I2C interface from ST Microelectronics simply called "DDC I2C"
651 supporting both I2C and DDC, used in e.g. the U300 series
654 This driver can also be built as a module. If so, the module
655 will be called i2c-stu300.
658 tristate "NVIDIA Tegra internal I2C controller"
659 depends on ARCH_TEGRA
661 If you say yes to this option, support will be included for the
662 I2C controller embedded in NVIDIA Tegra SOCs
665 tristate "ARM Versatile/Realview I2C bus support"
666 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
669 Say yes if you want to support the I2C serial bus on ARMs Versatile
672 This driver can also be built as a module. If so, the module
673 will be called i2c-versatile.
676 tristate "Cavium OCTEON I2C bus support"
677 depends on CPU_CAVIUM_OCTEON
679 Say yes if you want to support the I2C serial bus on Cavium
682 This driver can also be built as a module. If so, the module
683 will be called i2c-octeon.
686 tristate "Xilinx I2C Controller"
687 depends on EXPERIMENTAL && HAS_IOMEM
689 If you say yes to this option, support will be included for the
690 Xilinx I2C controller.
692 This driver can also be built as a module. If so, the module
693 will be called xilinx_i2c.
696 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
699 This driver is for PCH(Platform controller Hub) I2C of EG20T which
700 is an IOH(Input/Output Hub) for x86 embedded processor.
701 This driver can access PCH I2C bus device.
703 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
704 Output Hub), ML7213 and ML7223.
705 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
706 for MP(Media Phone) use.
707 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
708 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
710 comment "External I2C/SMBus adapter drivers"
712 config I2C_DIOLAN_U2C
713 tristate "Diolan U2C-12 USB adapter"
716 If you say yes to this option, support will be included for Diolan
717 U2C-12, a USB to I2C interface.
719 This driver can also be built as a module. If so, the module
720 will be called i2c-diolan-u2c.
723 tristate "Parallel port adapter"
728 This supports parallel port I2C adapters such as the ones made by
729 Philips or Velleman, Analog Devices evaluation boards, and more.
730 Basically any adapter using the parallel port as an I2C bus with
731 no extra chipset is supported by this driver, or could be.
733 This driver is a replacement for (and was inspired by) an older
734 driver named i2c-philips-par. The new driver supports more devices,
735 and makes it easier to add support for new devices.
737 An adapter type parameter is now mandatory. Please read the file
738 Documentation/i2c/busses/i2c-parport for details.
740 Another driver exists, named i2c-parport-light, which doesn't depend
741 on the parport driver. This is meant for embedded systems. Don't say
742 Y here if you intend to say Y or M there.
744 This support is also available as a module. If so, the module
745 will be called i2c-parport.
747 config I2C_PARPORT_LIGHT
748 tristate "Parallel port adapter (light)"
752 This supports parallel port I2C adapters such as the ones made by
753 Philips or Velleman, Analog Devices evaluation boards, and more.
754 Basically any adapter using the parallel port as an I2C bus with
755 no extra chipset is supported by this driver, or could be.
757 This driver is a light version of i2c-parport. It doesn't depend
758 on the parport driver, and uses direct I/O access instead. This
759 might be preferred on embedded systems where wasting memory for
760 the clean but heavy parport handling is not an option. The
761 drawback is a reduced portability and the impossibility to
762 daisy-chain other parallel port devices.
764 Don't say Y here if you said Y or M to i2c-parport. Saying M to
765 both is possible but both modules should not be loaded at the same
768 This support is also available as a module. If so, the module
769 will be called i2c-parport-light.
772 tristate "TAOS evaluation module"
773 depends on EXPERIMENTAL
778 This supports TAOS evaluation modules on serial port. In order to
779 use this driver, you will need the inputattach tool, which is part
780 of the input-utils package.
784 This support is also available as a module. If so, the module
785 will be called i2c-taos-evm.
788 tristate "Tiny-USB adapter"
791 If you say yes to this option, support will be included for the
792 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
793 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
795 This driver can also be built as a module. If so, the module
796 will be called i2c-tiny-usb.
798 comment "Other I2C/SMBus bus drivers"
801 tristate "Acorn IOC/IOMD I2C bus support"
802 depends on ARCH_ACORN
806 Say yes if you want to support the I2C bus on Acorn platforms.
808 If you don't know, say Y.
811 tristate "Elektor ISA card"
812 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
815 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
818 This support is also available as a module. If so, the module
819 will be called i2c-elektor.
822 tristate "PCA9564/PCA9665 on an ISA bus"
827 This driver supports ISA boards using the Philips PCA9564/PCA9665
828 parallel bus to I2C bus controller.
830 This driver can also be built as a module. If so, the module
831 will be called i2c-pca-isa.
833 This device is almost undetectable and using this driver on a
834 system which doesn't have this device will result in long
835 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
836 time). If unsure, say N.
839 tristate "SiByte SMBus interface"
840 depends on SIBYTE_SB1xxx_SOC
842 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
845 tristate "I2C/SMBus Test Stub"
846 depends on EXPERIMENTAL && m
849 This module may be useful to developers of SMBus client drivers,
850 especially for certain kinds of sensor chips.
852 If you do build this module, be sure to read the notes and warnings
853 in <file:Documentation/i2c/i2c-stub>.
855 If you don't know what to do here, definitely say N.
858 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
859 depends on SCx200_GPIO
862 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
864 If you don't know what to do here, say N.
866 This support is also available as a module. If so, the module
867 will be called scx200_i2c.
869 This driver is deprecated and will be dropped soon. Use i2c-gpio
870 (or scx200_acb) instead.
872 config SCx200_I2C_SCL
873 int "GPIO pin used for SCL"
874 depends on SCx200_I2C
877 Enter the GPIO pin number used for the SCL signal. This value can
878 also be specified with a module parameter.
880 config SCx200_I2C_SDA
881 int "GPIO pin used for SDA"
882 depends on SCx200_I2C
885 Enter the GPIO pin number used for the SSA signal. This value can
886 also be specified with a module parameter.
889 tristate "Geode ACCESS.bus support"
890 depends on X86_32 && PCI
892 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
893 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
895 If you don't know what to do here, say N.
897 This support is also available as a module. If so, the module
898 will be called scx200_acb.