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)
112 Wildcat Point-LP (PCH)
115 This driver can also be built as a module. If so, the module
116 will be called i2c-i801.
119 tristate "Intel SCH SMBus 1.0"
123 Say Y here if you want to use SMBus controller on the Intel SCH
126 This driver can also be built as a module. If so, the module
127 will be called i2c-isch.
130 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
133 If you say yes to this option, support will be included for the Intel
134 PIIX4 family of mainboard I2C interfaces. Specifically, the following
135 versions of the chipset are supported (note that Serverworks is part
155 This driver can also be built as a module. If so, the module
156 will be called i2c-piix4.
159 tristate "Nvidia nForce2, nForce3 and nForce4"
162 If you say yes to this option, support will be included for the Nvidia
163 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
165 This driver can also be built as a module. If so, the module
166 will be called i2c-nforce2.
168 config I2C_NFORCE2_S4985
169 tristate "SMBus multiplexing on the Tyan S4985"
170 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
172 Enabling this option will add specific SMBus support for the Tyan
173 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
174 over 4 different channels, where the various memory module EEPROMs
175 live. Saying yes here will give you access to these in addition
178 This driver can also be built as a module. If so, the module
179 will be called i2c-nforce2-s4985.
185 If you say yes to this option, support will be included for the
186 SiS5595 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-sis5595.
192 tristate "SiS 630/730"
195 If you say yes to this option, support will be included for the
196 SiS630 and SiS730 SMBus (a subset of I2C) interface.
198 This driver can also be built as a module. If so, the module
199 will be called i2c-sis630.
205 If you say yes to this option, support will be included for the SiS
206 96x SMBus (a subset of I2C) interfaces. Specifically, the following
207 chipsets are supported:
216 This driver can also be built as a module. If so, the module
217 will be called i2c-sis96x.
220 tristate "VIA VT82C586B"
221 depends on PCI && EXPERIMENTAL
224 If you say yes to this option, support will be included for the VIA
225 82C586B I2C interface
227 This driver can also be built as a module. If so, the module
228 will be called i2c-via.
231 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
234 If you say yes to this option, support will be included for the VIA
235 VT82C596 and later SMBus interface. Specifically, the following
236 chipsets are supported:
248 This driver can also be built as a module. If so, the module
249 will be called i2c-viapro.
253 comment "ACPI drivers"
256 tristate "SMBus Control Method Interface"
258 This driver supports the SMBus Control Method Interface. It needs the
259 BIOS to declare ACPI control methods as described in the SMBus Control
260 Method Interface specification.
262 To compile this driver as a module, choose M here:
263 the module will be called i2c-scmi.
267 comment "Mac SMBus host controller drivers"
268 depends on PPC_CHRP || PPC_PMAC
271 tristate "CHRP Apple Hydra Mac I/O I2C interface"
272 depends on PCI && PPC_CHRP && EXPERIMENTAL
275 This supports the use of the I2C interface in the Apple Hydra Mac
276 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
279 This support is also available as a module. If so, the module
280 will be called i2c-hydra.
283 tristate "Powermac I2C interface"
287 This exposes the various PowerMac i2c interfaces to the linux i2c
288 layer and to userland. It is used by various drivers on the PowerMac
289 platform, and should generally be enabled.
291 This support is also available as a module. If so, the module
292 will be called i2c-powermac.
294 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
297 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
298 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
300 This supports the use of the I2C interface on Atmel AT91
303 This driver is BROKEN because the controller which it uses
304 will easily trigger RX overrun and TX underrun errors. Using
305 low I2C clock rates may partially work around those issues
306 on some systems. Another serious problem is that there is no
307 documented way to issue repeated START conditions, as needed
308 to support combined I2C messages. Use the i2c-gpio driver
309 unless your system can cope with those limitations.
312 tristate "Au1550/Au1200 SMBus interface"
313 depends on MIPS_ALCHEMY
315 If you say yes to this option, support will be included for the
316 Au1550 and Au1200 SMBus interface.
318 This driver can also be built as a module. If so, the module
319 will be called i2c-au1550.
321 config I2C_BLACKFIN_TWI
322 tristate "Blackfin TWI I2C support"
324 depends on !BF561 && !BF531 && !BF532 && !BF533
326 This is the I2C bus driver for Blackfin on-chip TWI interface.
328 This driver can also be built as a module. If so, the module
329 will be called i2c-bfin-twi.
331 config I2C_BLACKFIN_TWI_CLK_KHZ
332 int "Blackfin TWI I2C clock (kHz)"
333 depends on I2C_BLACKFIN_TWI
337 The unit of the TWI clock is kHz.
340 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
341 depends on (CPM1 || CPM2) && OF_I2C
343 This supports the use of the I2C interface on Freescale
344 processors with CPM1 or CPM2.
346 This driver can also be built as a module. If so, the module
347 will be called i2c-cpm.
350 tristate "DaVinci I2C driver"
351 depends on ARCH_DAVINCI
353 Support for TI DaVinci I2C controller driver.
355 This driver can also be built as a module. If so, the module
356 will be called i2c-davinci.
358 Please note that this driver might be needed to bring up other
359 devices such as DaVinci NIC.
360 For details please see http://www.ti.com/davinci
362 config I2C_DESIGNWARE_CORE
365 config I2C_DESIGNWARE_PLATFORM
366 tristate "Synopsys DesignWare Platfrom"
368 select I2C_DESIGNWARE_CORE
370 If you say yes to this option, support will be included for the
371 Synopsys DesignWare I2C adapter. Only master mode is supported.
373 This driver can also be built as a module. If so, the module
374 will be called i2c-designware-platform.
376 config I2C_DESIGNWARE_PCI
377 tristate "Synopsys DesignWare PCI"
379 select I2C_DESIGNWARE_CORE
381 If you say yes to this option, support will be included for the
382 Synopsys DesignWare I2C adapter. Only master mode is supported.
384 This driver can also be built as a module. If so, the module
385 will be called i2c-designware-pci.
388 tristate "GPIO-based bitbanging I2C"
389 depends on GENERIC_GPIO
392 This is a very simple bitbanging I2C driver utilizing the
393 arch-neutral GPIO API to control the SCL and SDA lines.
395 config I2C_HIGHLANDER
396 tristate "Highlander FPGA SMBus interface"
397 depends on SH_HIGHLANDER
399 If you say yes to this option, support will be included for
400 the SMBus interface located in the FPGA on various Highlander
401 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
402 FPGAs. This is wholly unrelated to the SoC I2C.
404 This driver can also be built as a module. If so, the module
405 will be called i2c-highlander.
408 tristate "IBM PPC 4xx on-chip I2C interface"
411 Say Y here if you want to use IIC peripheral found on
412 embedded IBM PPC 4xx based systems.
414 This driver can also be built as a module. If so, the module
415 will be called i2c-ibm_iic.
418 tristate "IMX I2C interface"
421 Say Y here if you want to use the IIC bus controller on
422 the Freescale i.MX/MXC processors.
424 This driver can also be built as a module. If so, the module
425 will be called i2c-imx.
428 tristate "Intel Moorestown/Medfield Platform I2C controller"
431 Say Y here if you have an Intel Moorestown/Medfield platform I2C
434 This support is also available as a module. If so, the module
435 will be called i2c-intel-mid.
438 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
439 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
441 Say Y here if you want to use the IIC bus controller on
442 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
444 This driver can also be built as a module. If so, the module
445 will be called i2c-iop3xx.
448 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
449 depends on ARCH_IXP2000
452 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
453 system and are using GPIO lines for an I2C bus.
455 This support is also available as a module. If so, the module
456 will be called i2c-ixp2000.
458 This driver is deprecated and will be dropped soon. Use i2c-gpio
462 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
465 If you say yes to this option, support will be included for the
466 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
467 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
469 This driver can also be built as a module. If so, the module
470 will be called i2c-mpc.
473 tristate "Marvell mv64xxx I2C Controller"
474 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
476 If you say yes to this option, support will be included for the
477 built-in I2C interface on the Marvell 64xxx line of host bridges.
479 This driver can also be built as a module. If so, the module
480 will be called i2c-mv64xxx.
483 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"
494 depends on PLAT_NOMADIK
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.
500 tristate "NUC900 I2C Driver"
501 depends on ARCH_W90X900
503 Say Y here to include support for I2C controller in the
504 Winbond/Nuvoton NUC900 based System-on-Chip devices.
507 tristate "OpenCores I2C Controller"
508 depends on EXPERIMENTAL
510 If you say yes to this option, support will be included for the
511 OpenCores I2C controller. For details see
512 http://www.opencores.org/projects.cgi/web/i2c/overview
514 This driver can also be built as a module. If so, the module
515 will be called i2c-ocores.
518 tristate "OMAP I2C adapter"
520 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
522 If you say yes to this option, support will be included for the
523 I2C interface on the Texas Instruments OMAP1/2 family of processors.
524 Like OMAP1510/1610/1710/5912 and OMAP242x.
525 For details see http://www.ti.com/omap.
528 tristate "PA Semi SMBus interface"
529 depends on PPC_PASEMI && PCI
531 Supports the PA Semi PWRficient on-chip SMBus interfaces.
533 config I2C_PCA_PLATFORM
534 tristate "PCA9564/PCA9665 as platform device"
538 This driver supports a memory mapped Philips PCA9564/PCA9665
539 parallel bus to I2C bus controller.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-pca-platform.
545 tristate "PMC MSP I2C TWI Controller"
548 This driver supports the PMC TWI controller on MSP devices.
550 This driver can also be built as module. If so, the module
551 will be called i2c-pmcmsp.
554 tristate "I2C bus support for Philips PNX and NXP LPC targets"
555 depends on ARCH_PNX4008 || ARCH_LPC32XX
557 This driver supports the Philips IP3204 I2C IP block master and/or
560 This driver can also be built as a module. If so, the module
561 will be called i2c-pnx.
564 tristate "PKUnity v3 I2C bus support"
565 depends on UNICORE32 && ARCH_PUV3
568 This driver supports the I2C IP inside the PKUnity-v3 SoC.
569 This I2C bus controller is under AMBA/AXI bus.
571 This driver can also be built as a module. If so, the module
572 will be called i2c-puv3.
575 tristate "Intel PXA2XX I2C adapter"
576 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
578 If you have devices in the PXA I2C bus, say yes to this option.
579 This driver can also be built as a module. If so, the module
580 will be called i2c-pxa.
583 def_bool I2C_PXA && X86_32 && PCI && OF
586 bool "Intel PXA2XX I2C Slave comms support"
587 depends on I2C_PXA && !X86_32
589 Support I2C slave mode communications on the PXA I2C bus. This
590 is necessary for systems where the PXA may be a target on the
593 config HAVE_S3C2410_I2C
596 This will include I2C support for Samsung SoCs. If you want to
597 include I2C support for any machine, kindly select this in the
598 respective Kconfig file.
601 tristate "S3C2410 I2C Driver"
602 depends on HAVE_S3C2410_I2C
604 Say Y here to include support for I2C controller in the
608 tristate "S6000 I2C support"
609 depends on XTENSA_VARIANT_S6000
611 This driver supports the on chip I2C device on the
612 S6000 xtensa processor family.
614 To compile this driver as a module, choose M here. The module
615 will be called i2c-s6000.
618 tristate "Renesas SH7760 I2C Controller"
619 depends on CPU_SUBTYPE_SH7760
621 This driver supports the 2 I2C interfaces on the Renesas SH7760.
623 This driver can also be built as a module. If so, the module
624 will be called i2c-sh7760.
627 tristate "SuperH Mobile I2C Controller"
628 depends on SUPERH || ARCH_SHMOBILE
630 If you say yes to this option, support will be included for the
631 built-in I2C interface on the Renesas SH-Mobile processor.
633 This driver can also be built as a module. If so, the module
634 will be called i2c-sh_mobile.
637 tristate "Simtec Generic I2C interface"
640 If you say yes to this option, support will be included for
641 the Simtec Generic I2C interface. This driver is for the
642 simple I2C bus used on newer Simtec products for general
643 I2C, such as DDC on the Simtec BBD2016A.
645 This driver can also be built as a module. If so, the module
646 will be called i2c-simtec.
649 tristate "ST Microelectronics DDC I2C interface"
651 default y if MACH_U300
653 If you say yes to this option, support will be included for the
654 I2C interface from ST Microelectronics simply called "DDC I2C"
655 supporting both I2C and DDC, used in e.g. the U300 series
658 This driver can also be built as a module. If so, the module
659 will be called i2c-stu300.
662 tristate "NVIDIA Tegra internal I2C controller"
663 depends on ARCH_TEGRA
665 If you say yes to this option, support will be included for the
666 I2C controller embedded in NVIDIA Tegra SOCs
669 tristate "ARM Versatile/Realview I2C bus support"
670 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
673 Say yes if you want to support the I2C serial bus on ARMs Versatile
676 This driver can also be built as a module. If so, the module
677 will be called i2c-versatile.
680 tristate "Cavium OCTEON I2C bus support"
681 depends on CPU_CAVIUM_OCTEON
683 Say yes if you want to support the I2C serial bus on Cavium
686 This driver can also be built as a module. If so, the module
687 will be called i2c-octeon.
690 tristate "Xilinx I2C Controller"
691 depends on EXPERIMENTAL && HAS_IOMEM
693 If you say yes to this option, support will be included for the
694 Xilinx I2C controller.
696 This driver can also be built as a module. If so, the module
697 will be called xilinx_i2c.
700 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
703 This driver is for PCH(Platform controller Hub) I2C of EG20T which
704 is an IOH(Input/Output Hub) for x86 embedded processor.
705 This driver can access PCH I2C bus device.
707 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
708 Output Hub), ML7213 and ML7223.
709 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
710 for MP(Media Phone) use.
711 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
712 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
714 comment "External I2C/SMBus adapter drivers"
716 config I2C_DIOLAN_U2C
717 tristate "Diolan U2C-12 USB adapter"
720 If you say yes to this option, support will be included for Diolan
721 U2C-12, a USB to I2C interface.
723 This driver can also be built as a module. If so, the module
724 will be called i2c-diolan-u2c.
727 tristate "Parallel port adapter"
732 This supports parallel port I2C adapters such as the ones made by
733 Philips or Velleman, Analog Devices evaluation boards, and more.
734 Basically any adapter using the parallel port as an I2C bus with
735 no extra chipset is supported by this driver, or could be.
737 This driver is a replacement for (and was inspired by) an older
738 driver named i2c-philips-par. The new driver supports more devices,
739 and makes it easier to add support for new devices.
741 An adapter type parameter is now mandatory. Please read the file
742 Documentation/i2c/busses/i2c-parport for details.
744 Another driver exists, named i2c-parport-light, which doesn't depend
745 on the parport driver. This is meant for embedded systems. Don't say
746 Y here if you intend to say Y or M there.
748 This support is also available as a module. If so, the module
749 will be called i2c-parport.
751 config I2C_PARPORT_LIGHT
752 tristate "Parallel port adapter (light)"
756 This supports parallel port I2C adapters such as the ones made by
757 Philips or Velleman, Analog Devices evaluation boards, and more.
758 Basically any adapter using the parallel port as an I2C bus with
759 no extra chipset is supported by this driver, or could be.
761 This driver is a light version of i2c-parport. It doesn't depend
762 on the parport driver, and uses direct I/O access instead. This
763 might be preferred on embedded systems where wasting memory for
764 the clean but heavy parport handling is not an option. The
765 drawback is a reduced portability and the impossibility to
766 daisy-chain other parallel port devices.
768 Don't say Y here if you said Y or M to i2c-parport. Saying M to
769 both is possible but both modules should not be loaded at the same
772 This support is also available as a module. If so, the module
773 will be called i2c-parport-light.
776 tristate "TAOS evaluation module"
777 depends on EXPERIMENTAL
782 This supports TAOS evaluation modules on serial port. In order to
783 use this driver, you will need the inputattach tool, which is part
784 of the input-utils package.
788 This support is also available as a module. If so, the module
789 will be called i2c-taos-evm.
792 tristate "Tiny-USB adapter"
795 If you say yes to this option, support will be included for the
796 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
797 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
799 This driver can also be built as a module. If so, the module
800 will be called i2c-tiny-usb.
802 comment "Other I2C/SMBus bus drivers"
805 tristate "Acorn IOC/IOMD I2C bus support"
806 depends on ARCH_ACORN
810 Say yes if you want to support the I2C bus on Acorn platforms.
812 If you don't know, say Y.
815 tristate "Elektor ISA card"
816 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
819 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
822 This support is also available as a module. If so, the module
823 will be called i2c-elektor.
826 tristate "PCA9564/PCA9665 on an ISA bus"
831 This driver supports ISA boards using the Philips PCA9564/PCA9665
832 parallel bus to I2C bus controller.
834 This driver can also be built as a module. If so, the module
835 will be called i2c-pca-isa.
837 This device is almost undetectable and using this driver on a
838 system which doesn't have this device will result in long
839 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
840 time). If unsure, say N.
843 tristate "SiByte SMBus interface"
844 depends on SIBYTE_SB1xxx_SOC
846 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
849 tristate "I2C/SMBus Test Stub"
850 depends on EXPERIMENTAL && m
853 This module may be useful to developers of SMBus client drivers,
854 especially for certain kinds of sensor chips.
856 If you do build this module, be sure to read the notes and warnings
857 in <file:Documentation/i2c/i2c-stub>.
859 If you don't know what to do here, definitely say N.
862 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
863 depends on SCx200_GPIO
866 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
868 If you don't know what to do here, say N.
870 This support is also available as a module. If so, the module
871 will be called scx200_i2c.
873 This driver is deprecated and will be dropped soon. Use i2c-gpio
874 (or scx200_acb) instead.
876 config SCx200_I2C_SCL
877 int "GPIO pin used for SCL"
878 depends on SCx200_I2C
881 Enter the GPIO pin number used for the SCL signal. This value can
882 also be specified with a module parameter.
884 config SCx200_I2C_SDA
885 int "GPIO pin used for SDA"
886 depends on SCx200_I2C
889 Enter the GPIO pin number used for the SSA signal. This value can
890 also be specified with a module parameter.
893 tristate "Geode ACCESS.bus support"
894 depends on X86_32 && PCI
896 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
897 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
899 If you don't know what to do here, say N.
901 This support is also available as a module. If so, the module
902 will be called scx200_acb.