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 Wildcat Point-LP (PCH)
113 This driver can also be built as a module. If so, the module
114 will be called i2c-i801.
117 tristate "Intel SCH SMBus 1.0"
121 Say Y here if you want to use SMBus controller on the Intel SCH
124 This driver can also be built as a module. If so, the module
125 will be called i2c-isch.
128 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
131 If you say yes to this option, support will be included for the Intel
132 PIIX4 family of mainboard I2C interfaces. Specifically, the following
133 versions of the chipset are supported (note that Serverworks is part
153 This driver can also be built as a module. If so, the module
154 will be called i2c-piix4.
157 tristate "Nvidia nForce2, nForce3 and nForce4"
160 If you say yes to this option, support will be included for the Nvidia
161 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
163 This driver can also be built as a module. If so, the module
164 will be called i2c-nforce2.
166 config I2C_NFORCE2_S4985
167 tristate "SMBus multiplexing on the Tyan S4985"
168 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
170 Enabling this option will add specific SMBus support for the Tyan
171 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
172 over 4 different channels, where the various memory module EEPROMs
173 live. Saying yes here will give you access to these in addition
176 This driver can also be built as a module. If so, the module
177 will be called i2c-nforce2-s4985.
183 If you say yes to this option, support will be included for the
184 SiS5595 SMBus (a subset of I2C) interface.
186 This driver can also be built as a module. If so, the module
187 will be called i2c-sis5595.
190 tristate "SiS 630/730"
193 If you say yes to this option, support will be included for the
194 SiS630 and SiS730 SMBus (a subset of I2C) interface.
196 This driver can also be built as a module. If so, the module
197 will be called i2c-sis630.
203 If you say yes to this option, support will be included for the SiS
204 96x SMBus (a subset of I2C) interfaces. Specifically, the following
205 chipsets are supported:
214 This driver can also be built as a module. If so, the module
215 will be called i2c-sis96x.
218 tristate "VIA VT82C586B"
219 depends on PCI && EXPERIMENTAL
222 If you say yes to this option, support will be included for the VIA
223 82C586B I2C interface
225 This driver can also be built as a module. If so, the module
226 will be called i2c-via.
229 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
232 If you say yes to this option, support will be included for the VIA
233 VT82C596 and later SMBus interface. Specifically, the following
234 chipsets are supported:
246 This driver can also be built as a module. If so, the module
247 will be called i2c-viapro.
251 comment "ACPI drivers"
254 tristate "SMBus Control Method Interface"
256 This driver supports the SMBus Control Method Interface. It needs the
257 BIOS to declare ACPI control methods as described in the SMBus Control
258 Method Interface specification.
260 To compile this driver as a module, choose M here:
261 the module will be called i2c-scmi.
265 comment "Mac SMBus host controller drivers"
266 depends on PPC_CHRP || PPC_PMAC
269 tristate "CHRP Apple Hydra Mac I/O I2C interface"
270 depends on PCI && PPC_CHRP && EXPERIMENTAL
273 This supports the use of the I2C interface in the Apple Hydra Mac
274 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
277 This support is also available as a module. If so, the module
278 will be called i2c-hydra.
281 tristate "Powermac I2C interface"
285 This exposes the various PowerMac i2c interfaces to the linux i2c
286 layer and to userland. It is used by various drivers on the PowerMac
287 platform, and should generally be enabled.
289 This support is also available as a module. If so, the module
290 will be called i2c-powermac.
292 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
295 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
296 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
298 This supports the use of the I2C interface on Atmel AT91
301 This driver is BROKEN because the controller which it uses
302 will easily trigger RX overrun and TX underrun errors. Using
303 low I2C clock rates may partially work around those issues
304 on some systems. Another serious problem is that there is no
305 documented way to issue repeated START conditions, as needed
306 to support combined I2C messages. Use the i2c-gpio driver
307 unless your system can cope with those limitations.
310 tristate "Au1550/Au1200 SMBus interface"
311 depends on MIPS_ALCHEMY
313 If you say yes to this option, support will be included for the
314 Au1550 and Au1200 SMBus interface.
316 This driver can also be built as a module. If so, the module
317 will be called i2c-au1550.
319 config I2C_BLACKFIN_TWI
320 tristate "Blackfin TWI I2C support"
322 depends on !BF561 && !BF531 && !BF532 && !BF533
324 This is the I2C bus driver for Blackfin on-chip TWI interface.
326 This driver can also be built as a module. If so, the module
327 will be called i2c-bfin-twi.
329 config I2C_BLACKFIN_TWI_CLK_KHZ
330 int "Blackfin TWI I2C clock (kHz)"
331 depends on I2C_BLACKFIN_TWI
335 The unit of the TWI clock is kHz.
338 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
339 depends on (CPM1 || CPM2) && OF_I2C
341 This supports the use of the I2C interface on Freescale
342 processors with CPM1 or CPM2.
344 This driver can also be built as a module. If so, the module
345 will be called i2c-cpm.
348 tristate "DaVinci I2C driver"
349 depends on ARCH_DAVINCI
351 Support for TI DaVinci I2C controller driver.
353 This driver can also be built as a module. If so, the module
354 will be called i2c-davinci.
356 Please note that this driver might be needed to bring up other
357 devices such as DaVinci NIC.
358 For details please see http://www.ti.com/davinci
360 config I2C_DESIGNWARE_CORE
363 config I2C_DESIGNWARE_PLATFORM
364 tristate "Synopsys DesignWare Platfrom"
366 select I2C_DESIGNWARE_CORE
368 If you say yes to this option, support will be included for the
369 Synopsys DesignWare I2C adapter. Only master mode is supported.
371 This driver can also be built as a module. If so, the module
372 will be called i2c-designware-platform.
374 config I2C_DESIGNWARE_PCI
375 tristate "Synopsys DesignWare PCI"
377 select I2C_DESIGNWARE_CORE
379 If you say yes to this option, support will be included for the
380 Synopsys DesignWare I2C adapter. Only master mode is supported.
382 This driver can also be built as a module. If so, the module
383 will be called i2c-designware-pci.
386 tristate "GPIO-based bitbanging I2C"
387 depends on GENERIC_GPIO
390 This is a very simple bitbanging I2C driver utilizing the
391 arch-neutral GPIO API to control the SCL and SDA lines.
393 config I2C_HIGHLANDER
394 tristate "Highlander FPGA SMBus interface"
395 depends on SH_HIGHLANDER
397 If you say yes to this option, support will be included for
398 the SMBus interface located in the FPGA on various Highlander
399 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
400 FPGAs. This is wholly unrelated to the SoC I2C.
402 This driver can also be built as a module. If so, the module
403 will be called i2c-highlander.
406 tristate "IBM PPC 4xx on-chip I2C interface"
409 Say Y here if you want to use IIC peripheral found on
410 embedded IBM PPC 4xx based systems.
412 This driver can also be built as a module. If so, the module
413 will be called i2c-ibm_iic.
416 tristate "IMX I2C interface"
419 Say Y here if you want to use the IIC bus controller on
420 the Freescale i.MX/MXC processors.
422 This driver can also be built as a module. If so, the module
423 will be called i2c-imx.
426 tristate "Intel Moorestown/Medfield Platform I2C controller"
429 Say Y here if you have an Intel Moorestown/Medfield platform I2C
432 This support is also available as a module. If so, the module
433 will be called i2c-intel-mid.
436 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
437 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
439 Say Y here if you want to use the IIC bus controller on
440 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
442 This driver can also be built as a module. If so, the module
443 will be called i2c-iop3xx.
446 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
447 depends on ARCH_IXP2000
450 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
451 system and are using GPIO lines for an I2C bus.
453 This support is also available as a module. If so, the module
454 will be called i2c-ixp2000.
456 This driver is deprecated and will be dropped soon. Use i2c-gpio
460 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
463 If you say yes to this option, support will be included for the
464 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
465 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
467 This driver can also be built as a module. If so, the module
468 will be called i2c-mpc.
471 tristate "Marvell mv64xxx I2C Controller"
472 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
474 If you say yes to this option, support will be included for the
475 built-in I2C interface on the Marvell 64xxx line of host bridges.
477 This driver can also be built as a module. If so, the module
478 will be called i2c-mv64xxx.
481 tristate "Freescale i.MX28 I2C interface"
484 Say Y here if you want to use the I2C bus controller on
485 the Freescale i.MX28 processors.
487 This driver can also be built as a module. If so, the module
488 will be called i2c-mxs.
491 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
492 depends on PLAT_NOMADIK
494 If you say yes to this option, support will be included for the
495 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
498 tristate "NUC900 I2C Driver"
499 depends on ARCH_W90X900
501 Say Y here to include support for I2C controller in the
502 Winbond/Nuvoton NUC900 based System-on-Chip devices.
505 tristate "OpenCores I2C Controller"
506 depends on EXPERIMENTAL
508 If you say yes to this option, support will be included for the
509 OpenCores I2C controller. For details see
510 http://www.opencores.org/projects.cgi/web/i2c/overview
512 This driver can also be built as a module. If so, the module
513 will be called i2c-ocores.
516 tristate "OMAP I2C adapter"
518 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
520 If you say yes to this option, support will be included for the
521 I2C interface on the Texas Instruments OMAP1/2 family of processors.
522 Like OMAP1510/1610/1710/5912 and OMAP242x.
523 For details see http://www.ti.com/omap.
526 tristate "PA Semi SMBus interface"
527 depends on PPC_PASEMI && PCI
529 Supports the PA Semi PWRficient on-chip SMBus interfaces.
531 config I2C_PCA_PLATFORM
532 tristate "PCA9564/PCA9665 as platform device"
536 This driver supports a memory mapped Philips PCA9564/PCA9665
537 parallel bus to I2C bus controller.
539 This driver can also be built as a module. If so, the module
540 will be called i2c-pca-platform.
543 tristate "PMC MSP I2C TWI Controller"
546 This driver supports the PMC TWI controller on MSP devices.
548 This driver can also be built as module. If so, the module
549 will be called i2c-pmcmsp.
552 tristate "I2C bus support for Philips PNX and NXP LPC targets"
553 depends on ARCH_PNX4008 || ARCH_LPC32XX
555 This driver supports the Philips IP3204 I2C IP block master and/or
558 This driver can also be built as a module. If so, the module
559 will be called i2c-pnx.
562 tristate "PKUnity v3 I2C bus support"
563 depends on UNICORE32 && ARCH_PUV3
566 This driver supports the I2C IP inside the PKUnity-v3 SoC.
567 This I2C bus controller is under AMBA/AXI bus.
569 This driver can also be built as a module. If so, the module
570 will be called i2c-puv3.
573 tristate "Intel PXA2XX I2C adapter"
574 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
576 If you have devices in the PXA I2C bus, say yes to this option.
577 This driver can also be built as a module. If so, the module
578 will be called i2c-pxa.
581 def_bool I2C_PXA && X86_32 && PCI && OF
584 bool "Intel PXA2XX I2C Slave comms support"
585 depends on I2C_PXA && !X86_32
587 Support I2C slave mode communications on the PXA I2C bus. This
588 is necessary for systems where the PXA may be a target on the
591 config HAVE_S3C2410_I2C
594 This will include I2C support for Samsung SoCs. If you want to
595 include I2C support for any machine, kindly select this in the
596 respective Kconfig file.
599 tristate "S3C2410 I2C Driver"
600 depends on HAVE_S3C2410_I2C
602 Say Y here to include support for I2C controller in the
606 tristate "S6000 I2C support"
607 depends on XTENSA_VARIANT_S6000
609 This driver supports the on chip I2C device on the
610 S6000 xtensa processor family.
612 To compile this driver as a module, choose M here. The module
613 will be called i2c-s6000.
616 tristate "Renesas SH7760 I2C Controller"
617 depends on CPU_SUBTYPE_SH7760
619 This driver supports the 2 I2C interfaces on the Renesas SH7760.
621 This driver can also be built as a module. If so, the module
622 will be called i2c-sh7760.
625 tristate "SuperH Mobile I2C Controller"
626 depends on SUPERH || ARCH_SHMOBILE
628 If you say yes to this option, support will be included for the
629 built-in I2C interface on the Renesas SH-Mobile processor.
631 This driver can also be built as a module. If so, the module
632 will be called i2c-sh_mobile.
635 tristate "Simtec Generic I2C interface"
638 If you say yes to this option, support will be included for
639 the Simtec Generic I2C interface. This driver is for the
640 simple I2C bus used on newer Simtec products for general
641 I2C, such as DDC on the Simtec BBD2016A.
643 This driver can also be built as a module. If so, the module
644 will be called i2c-simtec.
647 tristate "ST Microelectronics DDC I2C interface"
649 default y if MACH_U300
651 If you say yes to this option, support will be included for the
652 I2C interface from ST Microelectronics simply called "DDC I2C"
653 supporting both I2C and DDC, used in e.g. the U300 series
656 This driver can also be built as a module. If so, the module
657 will be called i2c-stu300.
660 tristate "NVIDIA Tegra internal I2C controller"
661 depends on ARCH_TEGRA
663 If you say yes to this option, support will be included for the
664 I2C controller embedded in NVIDIA Tegra SOCs
667 tristate "ARM Versatile/Realview I2C bus support"
668 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
671 Say yes if you want to support the I2C serial bus on ARMs Versatile
674 This driver can also be built as a module. If so, the module
675 will be called i2c-versatile.
678 tristate "Cavium OCTEON I2C bus support"
679 depends on CPU_CAVIUM_OCTEON
681 Say yes if you want to support the I2C serial bus on Cavium
684 This driver can also be built as a module. If so, the module
685 will be called i2c-octeon.
688 tristate "Xilinx I2C Controller"
689 depends on EXPERIMENTAL && HAS_IOMEM
691 If you say yes to this option, support will be included for the
692 Xilinx I2C controller.
694 This driver can also be built as a module. If so, the module
695 will be called xilinx_i2c.
698 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
701 This driver is for PCH(Platform controller Hub) I2C of EG20T which
702 is an IOH(Input/Output Hub) for x86 embedded processor.
703 This driver can access PCH I2C bus device.
705 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
706 Output Hub), ML7213 and ML7223.
707 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
708 for MP(Media Phone) use.
709 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
710 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
712 comment "External I2C/SMBus adapter drivers"
714 config I2C_DIOLAN_U2C
715 tristate "Diolan U2C-12 USB adapter"
718 If you say yes to this option, support will be included for Diolan
719 U2C-12, a USB to I2C interface.
721 This driver can also be built as a module. If so, the module
722 will be called i2c-diolan-u2c.
725 tristate "Parallel port adapter"
730 This supports parallel port I2C adapters such as the ones made by
731 Philips or Velleman, Analog Devices evaluation boards, and more.
732 Basically any adapter using the parallel port as an I2C bus with
733 no extra chipset is supported by this driver, or could be.
735 This driver is a replacement for (and was inspired by) an older
736 driver named i2c-philips-par. The new driver supports more devices,
737 and makes it easier to add support for new devices.
739 An adapter type parameter is now mandatory. Please read the file
740 Documentation/i2c/busses/i2c-parport for details.
742 Another driver exists, named i2c-parport-light, which doesn't depend
743 on the parport driver. This is meant for embedded systems. Don't say
744 Y here if you intend to say Y or M there.
746 This support is also available as a module. If so, the module
747 will be called i2c-parport.
749 config I2C_PARPORT_LIGHT
750 tristate "Parallel port adapter (light)"
754 This supports parallel port I2C adapters such as the ones made by
755 Philips or Velleman, Analog Devices evaluation boards, and more.
756 Basically any adapter using the parallel port as an I2C bus with
757 no extra chipset is supported by this driver, or could be.
759 This driver is a light version of i2c-parport. It doesn't depend
760 on the parport driver, and uses direct I/O access instead. This
761 might be preferred on embedded systems where wasting memory for
762 the clean but heavy parport handling is not an option. The
763 drawback is a reduced portability and the impossibility to
764 daisy-chain other parallel port devices.
766 Don't say Y here if you said Y or M to i2c-parport. Saying M to
767 both is possible but both modules should not be loaded at the same
770 This support is also available as a module. If so, the module
771 will be called i2c-parport-light.
774 tristate "TAOS evaluation module"
775 depends on EXPERIMENTAL
780 This supports TAOS evaluation modules on serial port. In order to
781 use this driver, you will need the inputattach tool, which is part
782 of the input-utils package.
786 This support is also available as a module. If so, the module
787 will be called i2c-taos-evm.
790 tristate "Tiny-USB adapter"
793 If you say yes to this option, support will be included for the
794 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
795 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
797 This driver can also be built as a module. If so, the module
798 will be called i2c-tiny-usb.
800 comment "Other I2C/SMBus bus drivers"
803 tristate "Acorn IOC/IOMD I2C bus support"
804 depends on ARCH_ACORN
808 Say yes if you want to support the I2C bus on Acorn platforms.
810 If you don't know, say Y.
813 tristate "Elektor ISA card"
814 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
817 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
820 This support is also available as a module. If so, the module
821 will be called i2c-elektor.
824 tristate "PCA9564/PCA9665 on an ISA bus"
829 This driver supports ISA boards using the Philips PCA9564/PCA9665
830 parallel bus to I2C bus controller.
832 This driver can also be built as a module. If so, the module
833 will be called i2c-pca-isa.
835 This device is almost undetectable and using this driver on a
836 system which doesn't have this device will result in long
837 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
838 time). If unsure, say N.
841 tristate "SiByte SMBus interface"
842 depends on SIBYTE_SB1xxx_SOC
844 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
847 tristate "I2C/SMBus Test Stub"
848 depends on EXPERIMENTAL && m
851 This module may be useful to developers of SMBus client drivers,
852 especially for certain kinds of sensor chips.
854 If you do build this module, be sure to read the notes and warnings
855 in <file:Documentation/i2c/i2c-stub>.
857 If you don't know what to do here, definitely say N.
860 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
861 depends on SCx200_GPIO
864 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
866 If you don't know what to do here, say N.
868 This support is also available as a module. If so, the module
869 will be called scx200_i2c.
871 This driver is deprecated and will be dropped soon. Use i2c-gpio
872 (or scx200_acb) instead.
874 config SCx200_I2C_SCL
875 int "GPIO pin used for SCL"
876 depends on SCx200_I2C
879 Enter the GPIO pin number used for the SCL signal. This value can
880 also be specified with a module parameter.
882 config SCx200_I2C_SDA
883 int "GPIO pin used for SDA"
884 depends on SCx200_I2C
887 Enter the GPIO pin number used for the SSA signal. This value can
888 also be specified with a module parameter.
891 tristate "Geode ACCESS.bus support"
892 depends on X86_32 && PCI
894 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
895 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
897 If you don't know what to do here, say N.
899 This support is also available as a module. If so, the module
900 will be called scx200_acb.