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)
109 This driver can also be built as a module. If so, the module
110 will be called i2c-i801.
113 tristate "Intel SCH SMBus 1.0"
117 Say Y here if you want to use SMBus controller on the Intel SCH
120 This driver can also be built as a module. If so, the module
121 will be called i2c-isch.
124 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
127 If you say yes to this option, support will be included for the Intel
128 PIIX4 family of mainboard I2C interfaces. Specifically, the following
129 versions of the chipset are supported (note that Serverworks is part
147 This driver can also be built as a module. If so, the module
148 will be called i2c-piix4.
151 tristate "Nvidia nForce2, nForce3 and nForce4"
154 If you say yes to this option, support will be included for the Nvidia
155 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
157 This driver can also be built as a module. If so, the module
158 will be called i2c-nforce2.
160 config I2C_NFORCE2_S4985
161 tristate "SMBus multiplexing on the Tyan S4985"
162 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
164 Enabling this option will add specific SMBus support for the Tyan
165 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
166 over 4 different channels, where the various memory module EEPROMs
167 live. Saying yes here will give you access to these in addition
170 This driver can also be built as a module. If so, the module
171 will be called i2c-nforce2-s4985.
177 If you say yes to this option, support will be included for the
178 SiS5595 SMBus (a subset of I2C) interface.
180 This driver can also be built as a module. If so, the module
181 will be called i2c-sis5595.
184 tristate "SiS 630/730"
187 If you say yes to this option, support will be included for the
188 SiS630 and SiS730 SMBus (a subset of I2C) interface.
190 This driver can also be built as a module. If so, the module
191 will be called i2c-sis630.
197 If you say yes to this option, support will be included for the SiS
198 96x SMBus (a subset of I2C) interfaces. Specifically, the following
199 chipsets are supported:
208 This driver can also be built as a module. If so, the module
209 will be called i2c-sis96x.
212 tristate "VIA VT82C586B"
213 depends on PCI && EXPERIMENTAL
216 If you say yes to this option, support will be included for the VIA
217 82C586B I2C interface
219 This driver can also be built as a module. If so, the module
220 will be called i2c-via.
223 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
226 If you say yes to this option, support will be included for the VIA
227 VT82C596 and later SMBus interface. Specifically, the following
228 chipsets are supported:
240 This driver can also be built as a module. If so, the module
241 will be called i2c-viapro.
245 comment "ACPI drivers"
248 tristate "SMBus Control Method Interface"
250 This driver supports the SMBus Control Method Interface. It needs the
251 BIOS to declare ACPI control methods as described in the SMBus Control
252 Method Interface specification.
254 To compile this driver as a module, choose M here:
255 the module will be called i2c-scmi.
259 comment "Mac SMBus host controller drivers"
260 depends on PPC_CHRP || PPC_PMAC
263 tristate "CHRP Apple Hydra Mac I/O I2C interface"
264 depends on PCI && PPC_CHRP && EXPERIMENTAL
267 This supports the use of the I2C interface in the Apple Hydra Mac
268 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
271 This support is also available as a module. If so, the module
272 will be called i2c-hydra.
275 tristate "Powermac I2C interface"
279 This exposes the various PowerMac i2c interfaces to the linux i2c
280 layer and to userland. It is used by various drivers on the PowerMac
281 platform, and should generally be enabled.
283 This support is also available as a module. If so, the module
284 will be called i2c-powermac.
286 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
289 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
290 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
292 This supports the use of the I2C interface on Atmel AT91
295 This driver is BROKEN because the controller which it uses
296 will easily trigger RX overrun and TX underrun errors. Using
297 low I2C clock rates may partially work around those issues
298 on some systems. Another serious problem is that there is no
299 documented way to issue repeated START conditions, as needed
300 to support combined I2C messages. Use the i2c-gpio driver
301 unless your system can cope with those limitations.
304 tristate "Au1550/Au1200 SMBus interface"
305 depends on MIPS_ALCHEMY
307 If you say yes to this option, support will be included for the
308 Au1550 and Au1200 SMBus interface.
310 This driver can also be built as a module. If so, the module
311 will be called i2c-au1550.
313 config I2C_BLACKFIN_TWI
314 tristate "Blackfin TWI I2C support"
316 depends on !BF561 && !BF531 && !BF532 && !BF533
318 This is the I2C bus driver for Blackfin on-chip TWI interface.
320 This driver can also be built as a module. If so, the module
321 will be called i2c-bfin-twi.
323 config I2C_BLACKFIN_TWI_CLK_KHZ
324 int "Blackfin TWI I2C clock (kHz)"
325 depends on I2C_BLACKFIN_TWI
329 The unit of the TWI clock is kHz.
332 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
333 depends on (CPM1 || CPM2) && OF_I2C
335 This supports the use of the I2C interface on Freescale
336 processors with CPM1 or CPM2.
338 This driver can also be built as a module. If so, the module
339 will be called i2c-cpm.
342 tristate "DaVinci I2C driver"
343 depends on ARCH_DAVINCI
345 Support for TI DaVinci I2C controller driver.
347 This driver can also be built as a module. If so, the module
348 will be called i2c-davinci.
350 Please note that this driver might be needed to bring up other
351 devices such as DaVinci NIC.
352 For details please see http://www.ti.com/davinci
354 config I2C_DESIGNWARE_CORE
357 config I2C_DESIGNWARE_PLATFORM
358 tristate "Synopsys DesignWare Platfrom"
360 select I2C_DESIGNWARE_CORE
362 If you say yes to this option, support will be included for the
363 Synopsys DesignWare I2C adapter. Only master mode is supported.
365 This driver can also be built as a module. If so, the module
366 will be called i2c-designware-platform.
368 config I2C_DESIGNWARE_PCI
369 tristate "Synopsys DesignWare PCI"
371 select I2C_DESIGNWARE_CORE
373 If you say yes to this option, support will be included for the
374 Synopsys DesignWare I2C adapter. Only master mode is supported.
376 This driver can also be built as a module. If so, the module
377 will be called i2c-designware-pci.
380 tristate "GPIO-based bitbanging I2C"
381 depends on GENERIC_GPIO
384 This is a very simple bitbanging I2C driver utilizing the
385 arch-neutral GPIO API to control the SCL and SDA lines.
387 config I2C_HIGHLANDER
388 tristate "Highlander FPGA SMBus interface"
389 depends on SH_HIGHLANDER
391 If you say yes to this option, support will be included for
392 the SMBus interface located in the FPGA on various Highlander
393 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
394 FPGAs. This is wholly unrelated to the SoC I2C.
396 This driver can also be built as a module. If so, the module
397 will be called i2c-highlander.
400 tristate "IBM PPC 4xx on-chip I2C interface"
403 Say Y here if you want to use IIC peripheral found on
404 embedded IBM PPC 4xx based systems.
406 This driver can also be built as a module. If so, the module
407 will be called i2c-ibm_iic.
410 tristate "IMX I2C interface"
413 Say Y here if you want to use the IIC bus controller on
414 the Freescale i.MX/MXC processors.
416 This driver can also be built as a module. If so, the module
417 will be called i2c-imx.
420 tristate "Intel Moorestown/Medfield Platform I2C controller"
423 Say Y here if you have an Intel Moorestown/Medfield platform I2C
426 This support is also available as a module. If so, the module
427 will be called i2c-intel-mid.
430 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
431 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
433 Say Y here if you want to use the IIC bus controller on
434 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
436 This driver can also be built as a module. If so, the module
437 will be called i2c-iop3xx.
440 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
441 depends on ARCH_IXP2000
444 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
445 system and are using GPIO lines for an I2C bus.
447 This support is also available as a module. If so, the module
448 will be called i2c-ixp2000.
450 This driver is deprecated and will be dropped soon. Use i2c-gpio
454 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
457 If you say yes to this option, support will be included for the
458 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
459 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
461 This driver can also be built as a module. If so, the module
462 will be called i2c-mpc.
465 tristate "Marvell mv64xxx I2C Controller"
466 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
468 If you say yes to this option, support will be included for the
469 built-in I2C interface on the Marvell 64xxx line of host bridges.
471 This driver can also be built as a module. If so, the module
472 will be called i2c-mv64xxx.
475 tristate "Freescale i.MX28 I2C interface"
478 Say Y here if you want to use the I2C bus controller on
479 the Freescale i.MX28 processors.
481 This driver can also be built as a module. If so, the module
482 will be called i2c-mxs.
485 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
486 depends on PLAT_NOMADIK
488 If you say yes to this option, support will be included for the
489 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
492 tristate "NUC900 I2C Driver"
493 depends on ARCH_W90X900
495 Say Y here to include support for I2C controller in the
496 Winbond/Nuvoton NUC900 based System-on-Chip devices.
499 tristate "OpenCores I2C Controller"
500 depends on EXPERIMENTAL
502 If you say yes to this option, support will be included for the
503 OpenCores I2C controller. For details see
504 http://www.opencores.org/projects.cgi/web/i2c/overview
506 This driver can also be built as a module. If so, the module
507 will be called i2c-ocores.
510 tristate "OMAP I2C adapter"
512 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
514 If you say yes to this option, support will be included for the
515 I2C interface on the Texas Instruments OMAP1/2 family of processors.
516 Like OMAP1510/1610/1710/5912 and OMAP242x.
517 For details see http://www.ti.com/omap.
520 tristate "PA Semi SMBus interface"
521 depends on PPC_PASEMI && PCI
523 Supports the PA Semi PWRficient on-chip SMBus interfaces.
525 config I2C_PCA_PLATFORM
526 tristate "PCA9564/PCA9665 as platform device"
530 This driver supports a memory mapped Philips PCA9564/PCA9665
531 parallel bus to I2C bus controller.
533 This driver can also be built as a module. If so, the module
534 will be called i2c-pca-platform.
537 tristate "PMC MSP I2C TWI Controller"
540 This driver supports the PMC TWI controller on MSP devices.
542 This driver can also be built as module. If so, the module
543 will be called i2c-pmcmsp.
546 tristate "I2C bus support for Philips PNX and NXP LPC targets"
547 depends on ARCH_PNX4008 || ARCH_LPC32XX
549 This driver supports the Philips IP3204 I2C IP block master and/or
552 This driver can also be built as a module. If so, the module
553 will be called i2c-pnx.
556 tristate "PKUnity v3 I2C bus support"
557 depends on UNICORE32 && ARCH_PUV3
560 This driver supports the I2C IP inside the PKUnity-v3 SoC.
561 This I2C bus controller is under AMBA/AXI bus.
563 This driver can also be built as a module. If so, the module
564 will be called i2c-puv3.
567 tristate "Intel PXA2XX I2C adapter"
568 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
570 If you have devices in the PXA I2C bus, say yes to this option.
571 This driver can also be built as a module. If so, the module
572 will be called i2c-pxa.
575 def_bool I2C_PXA && X86_32 && PCI && OF
578 bool "Intel PXA2XX I2C Slave comms support"
579 depends on I2C_PXA && !X86_32
581 Support I2C slave mode communications on the PXA I2C bus. This
582 is necessary for systems where the PXA may be a target on the
585 config HAVE_S3C2410_I2C
588 This will include I2C support for Samsung SoCs. If you want to
589 include I2C support for any machine, kindly select this in the
590 respective Kconfig file.
593 tristate "S3C2410 I2C Driver"
594 depends on HAVE_S3C2410_I2C
596 Say Y here to include support for I2C controller in the
600 tristate "S6000 I2C support"
601 depends on XTENSA_VARIANT_S6000
603 This driver supports the on chip I2C device on the
604 S6000 xtensa processor family.
606 To compile this driver as a module, choose M here. The module
607 will be called i2c-s6000.
610 tristate "Renesas SH7760 I2C Controller"
611 depends on CPU_SUBTYPE_SH7760
613 This driver supports the 2 I2C interfaces on the Renesas SH7760.
615 This driver can also be built as a module. If so, the module
616 will be called i2c-sh7760.
619 tristate "SuperH Mobile I2C Controller"
620 depends on SUPERH || ARCH_SHMOBILE
622 If you say yes to this option, support will be included for the
623 built-in I2C interface on the Renesas SH-Mobile processor.
625 This driver can also be built as a module. If so, the module
626 will be called i2c-sh_mobile.
629 tristate "Simtec Generic I2C interface"
632 If you say yes to this option, support will be included for
633 the Simtec Generic I2C interface. This driver is for the
634 simple I2C bus used on newer Simtec products for general
635 I2C, such as DDC on the Simtec BBD2016A.
637 This driver can also be built as a module. If so, the module
638 will be called i2c-simtec.
641 tristate "ST Microelectronics DDC I2C interface"
643 default y if MACH_U300
645 If you say yes to this option, support will be included for the
646 I2C interface from ST Microelectronics simply called "DDC I2C"
647 supporting both I2C and DDC, used in e.g. the U300 series
650 This driver can also be built as a module. If so, the module
651 will be called i2c-stu300.
654 tristate "NVIDIA Tegra internal I2C controller"
655 depends on ARCH_TEGRA
657 If you say yes to this option, support will be included for the
658 I2C controller embedded in NVIDIA Tegra SOCs
661 tristate "ARM Versatile/Realview I2C bus support"
662 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
665 Say yes if you want to support the I2C serial bus on ARMs Versatile
668 This driver can also be built as a module. If so, the module
669 will be called i2c-versatile.
672 tristate "Cavium OCTEON I2C bus support"
673 depends on CPU_CAVIUM_OCTEON
675 Say yes if you want to support the I2C serial bus on Cavium
678 This driver can also be built as a module. If so, the module
679 will be called i2c-octeon.
682 tristate "Xilinx I2C Controller"
683 depends on EXPERIMENTAL && HAS_IOMEM
685 If you say yes to this option, support will be included for the
686 Xilinx I2C controller.
688 This driver can also be built as a module. If so, the module
689 will be called xilinx_i2c.
692 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
695 This driver is for PCH(Platform controller Hub) I2C of EG20T which
696 is an IOH(Input/Output Hub) for x86 embedded processor.
697 This driver can access PCH I2C bus device.
699 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
700 Output Hub), ML7213 and ML7223.
701 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
702 for MP(Media Phone) use.
703 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
704 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
706 comment "External I2C/SMBus adapter drivers"
708 config I2C_DIOLAN_U2C
709 tristate "Diolan U2C-12 USB adapter"
712 If you say yes to this option, support will be included for Diolan
713 U2C-12, a USB to I2C interface.
715 This driver can also be built as a module. If so, the module
716 will be called i2c-diolan-u2c.
719 tristate "Parallel port adapter"
724 This supports parallel port I2C adapters such as the ones made by
725 Philips or Velleman, Analog Devices evaluation boards, and more.
726 Basically any adapter using the parallel port as an I2C bus with
727 no extra chipset is supported by this driver, or could be.
729 This driver is a replacement for (and was inspired by) an older
730 driver named i2c-philips-par. The new driver supports more devices,
731 and makes it easier to add support for new devices.
733 An adapter type parameter is now mandatory. Please read the file
734 Documentation/i2c/busses/i2c-parport for details.
736 Another driver exists, named i2c-parport-light, which doesn't depend
737 on the parport driver. This is meant for embedded systems. Don't say
738 Y here if you intend to say Y or M there.
740 This support is also available as a module. If so, the module
741 will be called i2c-parport.
743 config I2C_PARPORT_LIGHT
744 tristate "Parallel port adapter (light)"
748 This supports parallel port I2C adapters such as the ones made by
749 Philips or Velleman, Analog Devices evaluation boards, and more.
750 Basically any adapter using the parallel port as an I2C bus with
751 no extra chipset is supported by this driver, or could be.
753 This driver is a light version of i2c-parport. It doesn't depend
754 on the parport driver, and uses direct I/O access instead. This
755 might be preferred on embedded systems where wasting memory for
756 the clean but heavy parport handling is not an option. The
757 drawback is a reduced portability and the impossibility to
758 daisy-chain other parallel port devices.
760 Don't say Y here if you said Y or M to i2c-parport. Saying M to
761 both is possible but both modules should not be loaded at the same
764 This support is also available as a module. If so, the module
765 will be called i2c-parport-light.
768 tristate "TAOS evaluation module"
769 depends on EXPERIMENTAL
774 This supports TAOS evaluation modules on serial port. In order to
775 use this driver, you will need the inputattach tool, which is part
776 of the input-utils package.
780 This support is also available as a module. If so, the module
781 will be called i2c-taos-evm.
784 tristate "Tiny-USB adapter"
787 If you say yes to this option, support will be included for the
788 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
789 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
791 This driver can also be built as a module. If so, the module
792 will be called i2c-tiny-usb.
794 comment "Other I2C/SMBus bus drivers"
797 tristate "Acorn IOC/IOMD I2C bus support"
798 depends on ARCH_ACORN
802 Say yes if you want to support the I2C bus on Acorn platforms.
804 If you don't know, say Y.
807 tristate "Elektor ISA card"
808 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
811 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
814 This support is also available as a module. If so, the module
815 will be called i2c-elektor.
818 tristate "PCA9564/PCA9665 on an ISA bus"
823 This driver supports ISA boards using the Philips PCA9564/PCA9665
824 parallel bus to I2C bus controller.
826 This driver can also be built as a module. If so, the module
827 will be called i2c-pca-isa.
829 This device is almost undetectable and using this driver on a
830 system which doesn't have this device will result in long
831 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
832 time). If unsure, say N.
835 tristate "SiByte SMBus interface"
836 depends on SIBYTE_SB1xxx_SOC
838 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
841 tristate "I2C/SMBus Test Stub"
842 depends on EXPERIMENTAL && m
845 This module may be useful to developers of SMBus client drivers,
846 especially for certain kinds of sensor chips.
848 If you do build this module, be sure to read the notes and warnings
849 in <file:Documentation/i2c/i2c-stub>.
851 If you don't know what to do here, definitely say N.
854 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
855 depends on SCx200_GPIO
858 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
860 If you don't know what to do here, say N.
862 This support is also available as a module. If so, the module
863 will be called scx200_i2c.
865 This driver is deprecated and will be dropped soon. Use i2c-gpio
866 (or scx200_acb) instead.
868 config SCx200_I2C_SCL
869 int "GPIO pin used for SCL"
870 depends on SCx200_I2C
873 Enter the GPIO pin number used for the SCL signal. This value can
874 also be specified with a module parameter.
876 config SCx200_I2C_SDA
877 int "GPIO pin used for SDA"
878 depends on SCx200_I2C
881 Enter the GPIO pin number used for the SSA signal. This value can
882 also be specified with a module parameter.
885 tristate "Geode ACCESS.bus support"
886 depends on X86_32 && PCI
888 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
889 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
891 If you don't know what to do here, say N.
893 This support is also available as a module. If so, the module
894 will be called scx200_acb.