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)
114 Sunrise Point-H (PCH)
116 This driver can also be built as a module. If so, the module
117 will be called i2c-i801.
120 tristate "Intel SCH SMBus 1.0"
124 Say Y here if you want to use SMBus controller on the Intel SCH
127 This driver can also be built as a module. If so, the module
128 will be called i2c-isch.
131 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
134 If you say yes to this option, support will be included for the Intel
135 PIIX4 family of mainboard I2C interfaces. Specifically, the following
136 versions of the chipset are supported (note that Serverworks is part
156 This driver can also be built as a module. If so, the module
157 will be called i2c-piix4.
160 tristate "Nvidia nForce2, nForce3 and nForce4"
163 If you say yes to this option, support will be included for the Nvidia
164 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
166 This driver can also be built as a module. If so, the module
167 will be called i2c-nforce2.
169 config I2C_NFORCE2_S4985
170 tristate "SMBus multiplexing on the Tyan S4985"
171 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
173 Enabling this option will add specific SMBus support for the Tyan
174 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
175 over 4 different channels, where the various memory module EEPROMs
176 live. Saying yes here will give you access to these in addition
179 This driver can also be built as a module. If so, the module
180 will be called i2c-nforce2-s4985.
186 If you say yes to this option, support will be included for the
187 SiS5595 SMBus (a subset of I2C) interface.
189 This driver can also be built as a module. If so, the module
190 will be called i2c-sis5595.
193 tristate "SiS 630/730"
196 If you say yes to this option, support will be included for the
197 SiS630 and SiS730 SMBus (a subset of I2C) interface.
199 This driver can also be built as a module. If so, the module
200 will be called i2c-sis630.
206 If you say yes to this option, support will be included for the SiS
207 96x SMBus (a subset of I2C) interfaces. Specifically, the following
208 chipsets are supported:
217 This driver can also be built as a module. If so, the module
218 will be called i2c-sis96x.
221 tristate "VIA VT82C586B"
222 depends on PCI && EXPERIMENTAL
225 If you say yes to this option, support will be included for the VIA
226 82C586B I2C interface
228 This driver can also be built as a module. If so, the module
229 will be called i2c-via.
232 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
235 If you say yes to this option, support will be included for the VIA
236 VT82C596 and later SMBus interface. Specifically, the following
237 chipsets are supported:
249 This driver can also be built as a module. If so, the module
250 will be called i2c-viapro.
254 comment "ACPI drivers"
257 tristate "SMBus Control Method Interface"
259 This driver supports the SMBus Control Method Interface. It needs the
260 BIOS to declare ACPI control methods as described in the SMBus Control
261 Method Interface specification.
263 To compile this driver as a module, choose M here:
264 the module will be called i2c-scmi.
268 comment "Mac SMBus host controller drivers"
269 depends on PPC_CHRP || PPC_PMAC
272 tristate "CHRP Apple Hydra Mac I/O I2C interface"
273 depends on PCI && PPC_CHRP && EXPERIMENTAL
276 This supports the use of the I2C interface in the Apple Hydra Mac
277 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
280 This support is also available as a module. If so, the module
281 will be called i2c-hydra.
284 tristate "Powermac I2C interface"
288 This exposes the various PowerMac i2c interfaces to the linux i2c
289 layer and to userland. It is used by various drivers on the PowerMac
290 platform, and should generally be enabled.
292 This support is also available as a module. If so, the module
293 will be called i2c-powermac.
295 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
298 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
299 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
301 This supports the use of the I2C interface on Atmel AT91
304 This driver is BROKEN because the controller which it uses
305 will easily trigger RX overrun and TX underrun errors. Using
306 low I2C clock rates may partially work around those issues
307 on some systems. Another serious problem is that there is no
308 documented way to issue repeated START conditions, as needed
309 to support combined I2C messages. Use the i2c-gpio driver
310 unless your system can cope with those limitations.
313 tristate "Au1550/Au1200 SMBus interface"
314 depends on MIPS_ALCHEMY
316 If you say yes to this option, support will be included for the
317 Au1550 and Au1200 SMBus interface.
319 This driver can also be built as a module. If so, the module
320 will be called i2c-au1550.
322 config I2C_BLACKFIN_TWI
323 tristate "Blackfin TWI I2C support"
325 depends on !BF561 && !BF531 && !BF532 && !BF533
327 This is the I2C bus driver for Blackfin on-chip TWI interface.
329 This driver can also be built as a module. If so, the module
330 will be called i2c-bfin-twi.
332 config I2C_BLACKFIN_TWI_CLK_KHZ
333 int "Blackfin TWI I2C clock (kHz)"
334 depends on I2C_BLACKFIN_TWI
338 The unit of the TWI clock is kHz.
341 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
342 depends on (CPM1 || CPM2) && OF_I2C
344 This supports the use of the I2C interface on Freescale
345 processors with CPM1 or CPM2.
347 This driver can also be built as a module. If so, the module
348 will be called i2c-cpm.
351 tristate "DaVinci I2C driver"
352 depends on ARCH_DAVINCI
354 Support for TI DaVinci I2C controller driver.
356 This driver can also be built as a module. If so, the module
357 will be called i2c-davinci.
359 Please note that this driver might be needed to bring up other
360 devices such as DaVinci NIC.
361 For details please see http://www.ti.com/davinci
363 config I2C_DESIGNWARE_CORE
366 config I2C_DESIGNWARE_PLATFORM
367 tristate "Synopsys DesignWare Platfrom"
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-platform.
377 config I2C_DESIGNWARE_PCI
378 tristate "Synopsys DesignWare PCI"
380 select I2C_DESIGNWARE_CORE
382 If you say yes to this option, support will be included for the
383 Synopsys DesignWare I2C adapter. Only master mode is supported.
385 This driver can also be built as a module. If so, the module
386 will be called i2c-designware-pci.
389 tristate "GPIO-based bitbanging I2C"
390 depends on GENERIC_GPIO
393 This is a very simple bitbanging I2C driver utilizing the
394 arch-neutral GPIO API to control the SCL and SDA lines.
396 config I2C_HIGHLANDER
397 tristate "Highlander FPGA SMBus interface"
398 depends on SH_HIGHLANDER
400 If you say yes to this option, support will be included for
401 the SMBus interface located in the FPGA on various Highlander
402 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
403 FPGAs. This is wholly unrelated to the SoC I2C.
405 This driver can also be built as a module. If so, the module
406 will be called i2c-highlander.
409 tristate "IBM PPC 4xx on-chip I2C interface"
412 Say Y here if you want to use IIC peripheral found on
413 embedded IBM PPC 4xx based systems.
415 This driver can also be built as a module. If so, the module
416 will be called i2c-ibm_iic.
419 tristate "IMX I2C interface"
422 Say Y here if you want to use the IIC bus controller on
423 the Freescale i.MX/MXC processors.
425 This driver can also be built as a module. If so, the module
426 will be called i2c-imx.
429 tristate "Intel Moorestown/Medfield Platform I2C controller"
432 Say Y here if you have an Intel Moorestown/Medfield platform I2C
435 This support is also available as a module. If so, the module
436 will be called i2c-intel-mid.
439 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
440 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
442 Say Y here if you want to use the IIC bus controller on
443 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
445 This driver can also be built as a module. If so, the module
446 will be called i2c-iop3xx.
449 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
450 depends on ARCH_IXP2000
453 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
454 system and are using GPIO lines for an I2C bus.
456 This support is also available as a module. If so, the module
457 will be called i2c-ixp2000.
459 This driver is deprecated and will be dropped soon. Use i2c-gpio
463 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
466 If you say yes to this option, support will be included for the
467 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
468 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
470 This driver can also be built as a module. If so, the module
471 will be called i2c-mpc.
474 tristate "Marvell mv64xxx I2C Controller"
475 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
477 If you say yes to this option, support will be included for the
478 built-in I2C interface on the Marvell 64xxx line of host bridges.
480 This driver can also be built as a module. If so, the module
481 will be called i2c-mv64xxx.
484 tristate "Freescale i.MX28 I2C interface"
487 Say Y here if you want to use the I2C bus controller on
488 the Freescale i.MX28 processors.
490 This driver can also be built as a module. If so, the module
491 will be called i2c-mxs.
494 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
495 depends on PLAT_NOMADIK
497 If you say yes to this option, support will be included for the
498 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
501 tristate "NUC900 I2C Driver"
502 depends on ARCH_W90X900
504 Say Y here to include support for I2C controller in the
505 Winbond/Nuvoton NUC900 based System-on-Chip devices.
508 tristate "OpenCores I2C Controller"
509 depends on EXPERIMENTAL
511 If you say yes to this option, support will be included for the
512 OpenCores I2C controller. For details see
513 http://www.opencores.org/projects.cgi/web/i2c/overview
515 This driver can also be built as a module. If so, the module
516 will be called i2c-ocores.
519 tristate "OMAP I2C adapter"
521 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
523 If you say yes to this option, support will be included for the
524 I2C interface on the Texas Instruments OMAP1/2 family of processors.
525 Like OMAP1510/1610/1710/5912 and OMAP242x.
526 For details see http://www.ti.com/omap.
529 tristate "PA Semi SMBus interface"
530 depends on PPC_PASEMI && PCI
532 Supports the PA Semi PWRficient on-chip SMBus interfaces.
534 config I2C_PCA_PLATFORM
535 tristate "PCA9564/PCA9665 as platform device"
539 This driver supports a memory mapped Philips PCA9564/PCA9665
540 parallel bus to I2C bus controller.
542 This driver can also be built as a module. If so, the module
543 will be called i2c-pca-platform.
546 tristate "PMC MSP I2C TWI Controller"
549 This driver supports the PMC TWI controller on MSP devices.
551 This driver can also be built as module. If so, the module
552 will be called i2c-pmcmsp.
555 tristate "I2C bus support for Philips PNX and NXP LPC targets"
556 depends on ARCH_PNX4008 || ARCH_LPC32XX
558 This driver supports the Philips IP3204 I2C IP block master and/or
561 This driver can also be built as a module. If so, the module
562 will be called i2c-pnx.
565 tristate "PKUnity v3 I2C bus support"
566 depends on UNICORE32 && ARCH_PUV3
569 This driver supports the I2C IP inside the PKUnity-v3 SoC.
570 This I2C bus controller is under AMBA/AXI bus.
572 This driver can also be built as a module. If so, the module
573 will be called i2c-puv3.
576 tristate "Intel PXA2XX I2C adapter"
577 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
579 If you have devices in the PXA I2C bus, say yes to this option.
580 This driver can also be built as a module. If so, the module
581 will be called i2c-pxa.
584 def_bool I2C_PXA && X86_32 && PCI && OF
587 bool "Intel PXA2XX I2C Slave comms support"
588 depends on I2C_PXA && !X86_32
590 Support I2C slave mode communications on the PXA I2C bus. This
591 is necessary for systems where the PXA may be a target on the
594 config HAVE_S3C2410_I2C
597 This will include I2C support for Samsung SoCs. If you want to
598 include I2C support for any machine, kindly select this in the
599 respective Kconfig file.
602 tristate "S3C2410 I2C Driver"
603 depends on HAVE_S3C2410_I2C
605 Say Y here to include support for I2C controller in the
609 tristate "S6000 I2C support"
610 depends on XTENSA_VARIANT_S6000
612 This driver supports the on chip I2C device on the
613 S6000 xtensa processor family.
615 To compile this driver as a module, choose M here. The module
616 will be called i2c-s6000.
619 tristate "Renesas SH7760 I2C Controller"
620 depends on CPU_SUBTYPE_SH7760
622 This driver supports the 2 I2C interfaces on the Renesas SH7760.
624 This driver can also be built as a module. If so, the module
625 will be called i2c-sh7760.
628 tristate "SuperH Mobile I2C Controller"
629 depends on SUPERH || ARCH_SHMOBILE
631 If you say yes to this option, support will be included for the
632 built-in I2C interface on the Renesas SH-Mobile processor.
634 This driver can also be built as a module. If so, the module
635 will be called i2c-sh_mobile.
638 tristate "Simtec Generic I2C interface"
641 If you say yes to this option, support will be included for
642 the Simtec Generic I2C interface. This driver is for the
643 simple I2C bus used on newer Simtec products for general
644 I2C, such as DDC on the Simtec BBD2016A.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-simtec.
650 tristate "ST Microelectronics DDC I2C interface"
652 default y if MACH_U300
654 If you say yes to this option, support will be included for the
655 I2C interface from ST Microelectronics simply called "DDC I2C"
656 supporting both I2C and DDC, used in e.g. the U300 series
659 This driver can also be built as a module. If so, the module
660 will be called i2c-stu300.
663 tristate "NVIDIA Tegra internal I2C controller"
664 depends on ARCH_TEGRA
666 If you say yes to this option, support will be included for the
667 I2C controller embedded in NVIDIA Tegra SOCs
670 tristate "ARM Versatile/Realview I2C bus support"
671 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
674 Say yes if you want to support the I2C serial bus on ARMs Versatile
677 This driver can also be built as a module. If so, the module
678 will be called i2c-versatile.
681 tristate "Cavium OCTEON I2C bus support"
682 depends on CPU_CAVIUM_OCTEON
684 Say yes if you want to support the I2C serial bus on Cavium
687 This driver can also be built as a module. If so, the module
688 will be called i2c-octeon.
691 tristate "Xilinx I2C Controller"
692 depends on EXPERIMENTAL && HAS_IOMEM
694 If you say yes to this option, support will be included for the
695 Xilinx I2C controller.
697 This driver can also be built as a module. If so, the module
698 will be called xilinx_i2c.
701 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
704 This driver is for PCH(Platform controller Hub) I2C of EG20T which
705 is an IOH(Input/Output Hub) for x86 embedded processor.
706 This driver can access PCH I2C bus device.
708 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
709 Output Hub), ML7213 and ML7223.
710 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
711 for MP(Media Phone) use.
712 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
713 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
715 comment "External I2C/SMBus adapter drivers"
717 config I2C_DIOLAN_U2C
718 tristate "Diolan U2C-12 USB adapter"
721 If you say yes to this option, support will be included for Diolan
722 U2C-12, a USB to I2C interface.
724 This driver can also be built as a module. If so, the module
725 will be called i2c-diolan-u2c.
728 tristate "Parallel port adapter"
733 This supports parallel port I2C adapters such as the ones made by
734 Philips or Velleman, Analog Devices evaluation boards, and more.
735 Basically any adapter using the parallel port as an I2C bus with
736 no extra chipset is supported by this driver, or could be.
738 This driver is a replacement for (and was inspired by) an older
739 driver named i2c-philips-par. The new driver supports more devices,
740 and makes it easier to add support for new devices.
742 An adapter type parameter is now mandatory. Please read the file
743 Documentation/i2c/busses/i2c-parport for details.
745 Another driver exists, named i2c-parport-light, which doesn't depend
746 on the parport driver. This is meant for embedded systems. Don't say
747 Y here if you intend to say Y or M there.
749 This support is also available as a module. If so, the module
750 will be called i2c-parport.
752 config I2C_PARPORT_LIGHT
753 tristate "Parallel port adapter (light)"
757 This supports parallel port I2C adapters such as the ones made by
758 Philips or Velleman, Analog Devices evaluation boards, and more.
759 Basically any adapter using the parallel port as an I2C bus with
760 no extra chipset is supported by this driver, or could be.
762 This driver is a light version of i2c-parport. It doesn't depend
763 on the parport driver, and uses direct I/O access instead. This
764 might be preferred on embedded systems where wasting memory for
765 the clean but heavy parport handling is not an option. The
766 drawback is a reduced portability and the impossibility to
767 daisy-chain other parallel port devices.
769 Don't say Y here if you said Y or M to i2c-parport. Saying M to
770 both is possible but both modules should not be loaded at the same
773 This support is also available as a module. If so, the module
774 will be called i2c-parport-light.
777 tristate "TAOS evaluation module"
778 depends on EXPERIMENTAL
783 This supports TAOS evaluation modules on serial port. In order to
784 use this driver, you will need the inputattach tool, which is part
785 of the input-utils package.
789 This support is also available as a module. If so, the module
790 will be called i2c-taos-evm.
793 tristate "Tiny-USB adapter"
796 If you say yes to this option, support will be included for the
797 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
798 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
800 This driver can also be built as a module. If so, the module
801 will be called i2c-tiny-usb.
803 comment "Other I2C/SMBus bus drivers"
806 tristate "Acorn IOC/IOMD I2C bus support"
807 depends on ARCH_ACORN
811 Say yes if you want to support the I2C bus on Acorn platforms.
813 If you don't know, say Y.
816 tristate "Elektor ISA card"
817 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
820 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
823 This support is also available as a module. If so, the module
824 will be called i2c-elektor.
827 tristate "PCA9564/PCA9665 on an ISA bus"
832 This driver supports ISA boards using the Philips PCA9564/PCA9665
833 parallel bus to I2C bus controller.
835 This driver can also be built as a module. If so, the module
836 will be called i2c-pca-isa.
838 This device is almost undetectable and using this driver on a
839 system which doesn't have this device will result in long
840 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
841 time). If unsure, say N.
844 tristate "SiByte SMBus interface"
845 depends on SIBYTE_SB1xxx_SOC
847 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
850 tristate "I2C/SMBus Test Stub"
851 depends on EXPERIMENTAL && m
854 This module may be useful to developers of SMBus client drivers,
855 especially for certain kinds of sensor chips.
857 If you do build this module, be sure to read the notes and warnings
858 in <file:Documentation/i2c/i2c-stub>.
860 If you don't know what to do here, definitely say N.
863 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
864 depends on SCx200_GPIO
867 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
869 If you don't know what to do here, say N.
871 This support is also available as a module. If so, the module
872 will be called scx200_i2c.
874 This driver is deprecated and will be dropped soon. Use i2c-gpio
875 (or scx200_acb) instead.
877 config SCx200_I2C_SCL
878 int "GPIO pin used for SCL"
879 depends on SCx200_I2C
882 Enter the GPIO pin number used for the SCL signal. This value can
883 also be specified with a module parameter.
885 config SCx200_I2C_SDA
886 int "GPIO pin used for SDA"
887 depends on SCx200_I2C
890 Enter the GPIO pin number used for the SSA signal. This value can
891 also be specified with a module parameter.
894 tristate "Geode ACCESS.bus support"
895 depends on X86_32 && PCI
897 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
898 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
900 If you don't know what to do here, say N.
902 This support is also available as a module. If so, the module
903 will be called scx200_acb.