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)
114 This driver can also be built as a module. If so, the module
115 will be called i2c-i801.
118 tristate "Intel SCH SMBus 1.0"
122 Say Y here if you want to use SMBus controller on the Intel SCH
125 This driver can also be built as a module. If so, the module
126 will be called i2c-isch.
129 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
132 If you say yes to this option, support will be included for the Intel
133 PIIX4 family of mainboard I2C interfaces. Specifically, the following
134 versions of the chipset are supported (note that Serverworks is part
154 This driver can also be built as a module. If so, the module
155 will be called i2c-piix4.
158 tristate "Nvidia nForce2, nForce3 and nForce4"
161 If you say yes to this option, support will be included for the Nvidia
162 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
164 This driver can also be built as a module. If so, the module
165 will be called i2c-nforce2.
167 config I2C_NFORCE2_S4985
168 tristate "SMBus multiplexing on the Tyan S4985"
169 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
171 Enabling this option will add specific SMBus support for the Tyan
172 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
173 over 4 different channels, where the various memory module EEPROMs
174 live. Saying yes here will give you access to these in addition
177 This driver can also be built as a module. If so, the module
178 will be called i2c-nforce2-s4985.
184 If you say yes to this option, support will be included for the
185 SiS5595 SMBus (a subset of I2C) interface.
187 This driver can also be built as a module. If so, the module
188 will be called i2c-sis5595.
191 tristate "SiS 630/730"
194 If you say yes to this option, support will be included for the
195 SiS630 and SiS730 SMBus (a subset of I2C) interface.
197 This driver can also be built as a module. If so, the module
198 will be called i2c-sis630.
204 If you say yes to this option, support will be included for the SiS
205 96x SMBus (a subset of I2C) interfaces. Specifically, the following
206 chipsets are supported:
215 This driver can also be built as a module. If so, the module
216 will be called i2c-sis96x.
219 tristate "VIA VT82C586B"
220 depends on PCI && EXPERIMENTAL
223 If you say yes to this option, support will be included for the VIA
224 82C586B I2C interface
226 This driver can also be built as a module. If so, the module
227 will be called i2c-via.
230 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
233 If you say yes to this option, support will be included for the VIA
234 VT82C596 and later SMBus interface. Specifically, the following
235 chipsets are supported:
247 This driver can also be built as a module. If so, the module
248 will be called i2c-viapro.
252 comment "ACPI drivers"
255 tristate "SMBus Control Method Interface"
257 This driver supports the SMBus Control Method Interface. It needs the
258 BIOS to declare ACPI control methods as described in the SMBus Control
259 Method Interface specification.
261 To compile this driver as a module, choose M here:
262 the module will be called i2c-scmi.
266 comment "Mac SMBus host controller drivers"
267 depends on PPC_CHRP || PPC_PMAC
270 tristate "CHRP Apple Hydra Mac I/O I2C interface"
271 depends on PCI && PPC_CHRP && EXPERIMENTAL
274 This supports the use of the I2C interface in the Apple Hydra Mac
275 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
278 This support is also available as a module. If so, the module
279 will be called i2c-hydra.
282 tristate "Powermac I2C interface"
286 This exposes the various PowerMac i2c interfaces to the linux i2c
287 layer and to userland. It is used by various drivers on the PowerMac
288 platform, and should generally be enabled.
290 This support is also available as a module. If so, the module
291 will be called i2c-powermac.
293 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
296 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
297 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
299 This supports the use of the I2C interface on Atmel AT91
302 This driver is BROKEN because the controller which it uses
303 will easily trigger RX overrun and TX underrun errors. Using
304 low I2C clock rates may partially work around those issues
305 on some systems. Another serious problem is that there is no
306 documented way to issue repeated START conditions, as needed
307 to support combined I2C messages. Use the i2c-gpio driver
308 unless your system can cope with those limitations.
311 tristate "Au1550/Au1200 SMBus interface"
312 depends on MIPS_ALCHEMY
314 If you say yes to this option, support will be included for the
315 Au1550 and Au1200 SMBus interface.
317 This driver can also be built as a module. If so, the module
318 will be called i2c-au1550.
320 config I2C_BLACKFIN_TWI
321 tristate "Blackfin TWI I2C support"
323 depends on !BF561 && !BF531 && !BF532 && !BF533
325 This is the I2C bus driver for Blackfin on-chip TWI interface.
327 This driver can also be built as a module. If so, the module
328 will be called i2c-bfin-twi.
330 config I2C_BLACKFIN_TWI_CLK_KHZ
331 int "Blackfin TWI I2C clock (kHz)"
332 depends on I2C_BLACKFIN_TWI
336 The unit of the TWI clock is kHz.
339 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
340 depends on (CPM1 || CPM2) && OF_I2C
342 This supports the use of the I2C interface on Freescale
343 processors with CPM1 or CPM2.
345 This driver can also be built as a module. If so, the module
346 will be called i2c-cpm.
349 tristate "DaVinci I2C driver"
350 depends on ARCH_DAVINCI
352 Support for TI DaVinci I2C controller driver.
354 This driver can also be built as a module. If so, the module
355 will be called i2c-davinci.
357 Please note that this driver might be needed to bring up other
358 devices such as DaVinci NIC.
359 For details please see http://www.ti.com/davinci
361 config I2C_DESIGNWARE_CORE
364 config I2C_DESIGNWARE_PLATFORM
365 tristate "Synopsys DesignWare Platfrom"
367 select I2C_DESIGNWARE_CORE
369 If you say yes to this option, support will be included for the
370 Synopsys DesignWare I2C adapter. Only master mode is supported.
372 This driver can also be built as a module. If so, the module
373 will be called i2c-designware-platform.
375 config I2C_DESIGNWARE_PCI
376 tristate "Synopsys DesignWare PCI"
378 select I2C_DESIGNWARE_CORE
380 If you say yes to this option, support will be included for the
381 Synopsys DesignWare I2C adapter. Only master mode is supported.
383 This driver can also be built as a module. If so, the module
384 will be called i2c-designware-pci.
387 tristate "GPIO-based bitbanging I2C"
388 depends on GENERIC_GPIO
391 This is a very simple bitbanging I2C driver utilizing the
392 arch-neutral GPIO API to control the SCL and SDA lines.
394 config I2C_HIGHLANDER
395 tristate "Highlander FPGA SMBus interface"
396 depends on SH_HIGHLANDER
398 If you say yes to this option, support will be included for
399 the SMBus interface located in the FPGA on various Highlander
400 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
401 FPGAs. This is wholly unrelated to the SoC I2C.
403 This driver can also be built as a module. If so, the module
404 will be called i2c-highlander.
407 tristate "IBM PPC 4xx on-chip I2C interface"
410 Say Y here if you want to use IIC peripheral found on
411 embedded IBM PPC 4xx based systems.
413 This driver can also be built as a module. If so, the module
414 will be called i2c-ibm_iic.
417 tristate "IMX I2C interface"
420 Say Y here if you want to use the IIC bus controller on
421 the Freescale i.MX/MXC processors.
423 This driver can also be built as a module. If so, the module
424 will be called i2c-imx.
427 tristate "Intel Moorestown/Medfield Platform I2C controller"
430 Say Y here if you have an Intel Moorestown/Medfield platform I2C
433 This support is also available as a module. If so, the module
434 will be called i2c-intel-mid.
437 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
438 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
440 Say Y here if you want to use the IIC bus controller on
441 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
443 This driver can also be built as a module. If so, the module
444 will be called i2c-iop3xx.
447 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
448 depends on ARCH_IXP2000
451 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
452 system and are using GPIO lines for an I2C bus.
454 This support is also available as a module. If so, the module
455 will be called i2c-ixp2000.
457 This driver is deprecated and will be dropped soon. Use i2c-gpio
461 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
464 If you say yes to this option, support will be included for the
465 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
466 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
468 This driver can also be built as a module. If so, the module
469 will be called i2c-mpc.
472 tristate "Marvell mv64xxx I2C Controller"
473 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
475 If you say yes to this option, support will be included for the
476 built-in I2C interface on the Marvell 64xxx line of host bridges.
478 This driver can also be built as a module. If so, the module
479 will be called i2c-mv64xxx.
482 tristate "Freescale i.MX28 I2C interface"
485 Say Y here if you want to use the I2C bus controller on
486 the Freescale i.MX28 processors.
488 This driver can also be built as a module. If so, the module
489 will be called i2c-mxs.
492 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
493 depends on PLAT_NOMADIK
495 If you say yes to this option, support will be included for the
496 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
499 tristate "NUC900 I2C Driver"
500 depends on ARCH_W90X900
502 Say Y here to include support for I2C controller in the
503 Winbond/Nuvoton NUC900 based System-on-Chip devices.
506 tristate "OpenCores I2C Controller"
507 depends on EXPERIMENTAL
509 If you say yes to this option, support will be included for the
510 OpenCores I2C controller. For details see
511 http://www.opencores.org/projects.cgi/web/i2c/overview
513 This driver can also be built as a module. If so, the module
514 will be called i2c-ocores.
517 tristate "OMAP I2C adapter"
519 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
521 If you say yes to this option, support will be included for the
522 I2C interface on the Texas Instruments OMAP1/2 family of processors.
523 Like OMAP1510/1610/1710/5912 and OMAP242x.
524 For details see http://www.ti.com/omap.
527 tristate "PA Semi SMBus interface"
528 depends on PPC_PASEMI && PCI
530 Supports the PA Semi PWRficient on-chip SMBus interfaces.
532 config I2C_PCA_PLATFORM
533 tristate "PCA9564/PCA9665 as platform device"
537 This driver supports a memory mapped Philips PCA9564/PCA9665
538 parallel bus to I2C bus controller.
540 This driver can also be built as a module. If so, the module
541 will be called i2c-pca-platform.
544 tristate "PMC MSP I2C TWI Controller"
547 This driver supports the PMC TWI controller on MSP devices.
549 This driver can also be built as module. If so, the module
550 will be called i2c-pmcmsp.
553 tristate "I2C bus support for Philips PNX and NXP LPC targets"
554 depends on ARCH_PNX4008 || ARCH_LPC32XX
556 This driver supports the Philips IP3204 I2C IP block master and/or
559 This driver can also be built as a module. If so, the module
560 will be called i2c-pnx.
563 tristate "PKUnity v3 I2C bus support"
564 depends on UNICORE32 && ARCH_PUV3
567 This driver supports the I2C IP inside the PKUnity-v3 SoC.
568 This I2C bus controller is under AMBA/AXI bus.
570 This driver can also be built as a module. If so, the module
571 will be called i2c-puv3.
574 tristate "Intel PXA2XX I2C adapter"
575 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
577 If you have devices in the PXA I2C bus, say yes to this option.
578 This driver can also be built as a module. If so, the module
579 will be called i2c-pxa.
582 def_bool I2C_PXA && X86_32 && PCI && OF
585 bool "Intel PXA2XX I2C Slave comms support"
586 depends on I2C_PXA && !X86_32
588 Support I2C slave mode communications on the PXA I2C bus. This
589 is necessary for systems where the PXA may be a target on the
592 config HAVE_S3C2410_I2C
595 This will include I2C support for Samsung SoCs. If you want to
596 include I2C support for any machine, kindly select this in the
597 respective Kconfig file.
600 tristate "S3C2410 I2C Driver"
601 depends on HAVE_S3C2410_I2C
603 Say Y here to include support for I2C controller in the
607 tristate "S6000 I2C support"
608 depends on XTENSA_VARIANT_S6000
610 This driver supports the on chip I2C device on the
611 S6000 xtensa processor family.
613 To compile this driver as a module, choose M here. The module
614 will be called i2c-s6000.
617 tristate "Renesas SH7760 I2C Controller"
618 depends on CPU_SUBTYPE_SH7760
620 This driver supports the 2 I2C interfaces on the Renesas SH7760.
622 This driver can also be built as a module. If so, the module
623 will be called i2c-sh7760.
626 tristate "SuperH Mobile I2C Controller"
627 depends on SUPERH || ARCH_SHMOBILE
629 If you say yes to this option, support will be included for the
630 built-in I2C interface on the Renesas SH-Mobile processor.
632 This driver can also be built as a module. If so, the module
633 will be called i2c-sh_mobile.
636 tristate "Simtec Generic I2C interface"
639 If you say yes to this option, support will be included for
640 the Simtec Generic I2C interface. This driver is for the
641 simple I2C bus used on newer Simtec products for general
642 I2C, such as DDC on the Simtec BBD2016A.
644 This driver can also be built as a module. If so, the module
645 will be called i2c-simtec.
648 tristate "ST Microelectronics DDC I2C interface"
650 default y if MACH_U300
652 If you say yes to this option, support will be included for the
653 I2C interface from ST Microelectronics simply called "DDC I2C"
654 supporting both I2C and DDC, used in e.g. the U300 series
657 This driver can also be built as a module. If so, the module
658 will be called i2c-stu300.
661 tristate "NVIDIA Tegra internal I2C controller"
662 depends on ARCH_TEGRA
664 If you say yes to this option, support will be included for the
665 I2C controller embedded in NVIDIA Tegra SOCs
668 tristate "ARM Versatile/Realview I2C bus support"
669 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
672 Say yes if you want to support the I2C serial bus on ARMs Versatile
675 This driver can also be built as a module. If so, the module
676 will be called i2c-versatile.
679 tristate "Cavium OCTEON I2C bus support"
680 depends on CPU_CAVIUM_OCTEON
682 Say yes if you want to support the I2C serial bus on Cavium
685 This driver can also be built as a module. If so, the module
686 will be called i2c-octeon.
689 tristate "Xilinx I2C Controller"
690 depends on EXPERIMENTAL && HAS_IOMEM
692 If you say yes to this option, support will be included for the
693 Xilinx I2C controller.
695 This driver can also be built as a module. If so, the module
696 will be called xilinx_i2c.
699 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
702 This driver is for PCH(Platform controller Hub) I2C of EG20T which
703 is an IOH(Input/Output Hub) for x86 embedded processor.
704 This driver can access PCH I2C bus device.
706 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
707 Output Hub), ML7213 and ML7223.
708 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
709 for MP(Media Phone) use.
710 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
711 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
713 comment "External I2C/SMBus adapter drivers"
715 config I2C_DIOLAN_U2C
716 tristate "Diolan U2C-12 USB adapter"
719 If you say yes to this option, support will be included for Diolan
720 U2C-12, a USB to I2C interface.
722 This driver can also be built as a module. If so, the module
723 will be called i2c-diolan-u2c.
726 tristate "Parallel port adapter"
731 This supports parallel port I2C adapters such as the ones made by
732 Philips or Velleman, Analog Devices evaluation boards, and more.
733 Basically any adapter using the parallel port as an I2C bus with
734 no extra chipset is supported by this driver, or could be.
736 This driver is a replacement for (and was inspired by) an older
737 driver named i2c-philips-par. The new driver supports more devices,
738 and makes it easier to add support for new devices.
740 An adapter type parameter is now mandatory. Please read the file
741 Documentation/i2c/busses/i2c-parport for details.
743 Another driver exists, named i2c-parport-light, which doesn't depend
744 on the parport driver. This is meant for embedded systems. Don't say
745 Y here if you intend to say Y or M there.
747 This support is also available as a module. If so, the module
748 will be called i2c-parport.
750 config I2C_PARPORT_LIGHT
751 tristate "Parallel port adapter (light)"
755 This supports parallel port I2C adapters such as the ones made by
756 Philips or Velleman, Analog Devices evaluation boards, and more.
757 Basically any adapter using the parallel port as an I2C bus with
758 no extra chipset is supported by this driver, or could be.
760 This driver is a light version of i2c-parport. It doesn't depend
761 on the parport driver, and uses direct I/O access instead. This
762 might be preferred on embedded systems where wasting memory for
763 the clean but heavy parport handling is not an option. The
764 drawback is a reduced portability and the impossibility to
765 daisy-chain other parallel port devices.
767 Don't say Y here if you said Y or M to i2c-parport. Saying M to
768 both is possible but both modules should not be loaded at the same
771 This support is also available as a module. If so, the module
772 will be called i2c-parport-light.
775 tristate "TAOS evaluation module"
776 depends on EXPERIMENTAL
781 This supports TAOS evaluation modules on serial port. In order to
782 use this driver, you will need the inputattach tool, which is part
783 of the input-utils package.
787 This support is also available as a module. If so, the module
788 will be called i2c-taos-evm.
791 tristate "Tiny-USB adapter"
794 If you say yes to this option, support will be included for the
795 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
796 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
798 This driver can also be built as a module. If so, the module
799 will be called i2c-tiny-usb.
801 comment "Other I2C/SMBus bus drivers"
804 tristate "Acorn IOC/IOMD I2C bus support"
805 depends on ARCH_ACORN
809 Say yes if you want to support the I2C bus on Acorn platforms.
811 If you don't know, say Y.
814 tristate "Elektor ISA card"
815 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
818 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
821 This support is also available as a module. If so, the module
822 will be called i2c-elektor.
825 tristate "PCA9564/PCA9665 on an ISA bus"
830 This driver supports ISA boards using the Philips PCA9564/PCA9665
831 parallel bus to I2C bus controller.
833 This driver can also be built as a module. If so, the module
834 will be called i2c-pca-isa.
836 This device is almost undetectable and using this driver on a
837 system which doesn't have this device will result in long
838 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
839 time). If unsure, say N.
842 tristate "SiByte SMBus interface"
843 depends on SIBYTE_SB1xxx_SOC
845 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
848 tristate "I2C/SMBus Test Stub"
849 depends on EXPERIMENTAL && m
852 This module may be useful to developers of SMBus client drivers,
853 especially for certain kinds of sensor chips.
855 If you do build this module, be sure to read the notes and warnings
856 in <file:Documentation/i2c/i2c-stub>.
858 If you don't know what to do here, definitely say N.
861 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
862 depends on SCx200_GPIO
865 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
867 If you don't know what to do here, say N.
869 This support is also available as a module. If so, the module
870 will be called scx200_i2c.
872 This driver is deprecated and will be dropped soon. Use i2c-gpio
873 (or scx200_acb) instead.
875 config SCx200_I2C_SCL
876 int "GPIO pin used for SCL"
877 depends on SCx200_I2C
880 Enter the GPIO pin number used for the SCL signal. This value can
881 also be specified with a module parameter.
883 config SCx200_I2C_SDA
884 int "GPIO pin used for SDA"
885 depends on SCx200_I2C
888 Enter the GPIO pin number used for the SSA signal. This value can
889 also be specified with a module parameter.
892 tristate "Geode ACCESS.bus support"
893 depends on X86_32 && PCI
895 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
896 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
898 If you don't know what to do here, say N.
900 This support is also available as a module. If so, the module
901 will be called scx200_acb.