2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
8 comment "PC SMBus host controller drivers"
15 If you say yes to this option, support will be included for the SMB
16 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
17 controller is part of the 7101 device, which is an ACPI-compliant
18 Power Management Unit (PMU).
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
25 depends on PCI && EXPERIMENTAL
27 If you say yes to this option, support will be included for the SMB
28 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
29 controller is part of the 7101 device, which is an ACPI-compliant
30 Power Management Unit (PMU).
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
39 If you say yes to this option, support will be included for the
40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
46 tristate "AMD 756/766/768/8111 and nVidia nForce"
49 If you say yes to this option, support will be included for the AMD
50 756/766/768 mainboard I2C interfaces. The driver also includes
51 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
52 the nVidia nForce I2C interface.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
57 config I2C_AMD756_S4882
58 tristate "SMBus multiplexing on the Tyan S4882"
59 depends on I2C_AMD756 && X86 && EXPERIMENTAL
61 Enabling this option will add specific SMBus support for the Tyan
62 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
63 over 8 different channels, where the various memory module EEPROMs
64 and temperature sensors live. Saying yes here will give you access
65 to these in addition to the trunk.
67 This driver can also be built as a module. If so, the module
68 will be called i2c-amd756-s4882.
74 If you say yes to this option, support will be included for the
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
77 This driver can also be built as a module. If so, the module
78 will be called i2c-amd8111.
81 tristate "Intel 82801 (ICH/PCH)"
83 select CHECK_SIGNATURE if X86 && DMI
85 If you say yes to this option, support will be included for the Intel
86 801 family of mainboard I2C interfaces. Specifically, the following
87 versions of the chipset are supported:
93 82801EB/ER (ICH5/ICH5R)
110 This driver can also be built as a module. If so, the module
111 will be called i2c-i801.
114 tristate "Intel SCH SMBus 1.0"
118 Say Y here if you want to use SMBus controller on the Intel SCH
121 This driver can also be built as a module. If so, the module
122 will be called i2c-isch.
125 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
128 If you say yes to this option, support will be included for the Intel
129 PIIX4 family of mainboard I2C interfaces. Specifically, the following
130 versions of the chipset are supported (note that Serverworks is part
148 Some AMD chipsets contain two PIIX4-compatible SMBus
149 controllers. This driver will attempt to use both controllers
150 on the SB700/SP5100, if they have been initialized by the BIOS.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-piix4.
156 tristate "Nvidia nForce2, nForce3 and nForce4"
159 If you say yes to this option, support will be included for the Nvidia
160 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
162 This driver can also be built as a module. If so, the module
163 will be called i2c-nforce2.
165 config I2C_NFORCE2_S4985
166 tristate "SMBus multiplexing on the Tyan S4985"
167 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
169 Enabling this option will add specific SMBus support for the Tyan
170 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
171 over 4 different channels, where the various memory module EEPROMs
172 live. Saying yes here will give you access to these in addition
175 This driver can also be built as a module. If so, the module
176 will be called i2c-nforce2-s4985.
182 If you say yes to this option, support will be included for the
183 SiS5595 SMBus (a subset of I2C) interface.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-sis5595.
189 tristate "SiS 630/730"
192 If you say yes to this option, support will be included for the
193 SiS630 and SiS730 SMBus (a subset of I2C) interface.
195 This driver can also be built as a module. If so, the module
196 will be called i2c-sis630.
202 If you say yes to this option, support will be included for the SiS
203 96x SMBus (a subset of I2C) interfaces. Specifically, the following
204 chipsets are supported:
213 This driver can also be built as a module. If so, the module
214 will be called i2c-sis96x.
217 tristate "VIA VT82C586B"
218 depends on PCI && EXPERIMENTAL
221 If you say yes to this option, support will be included for the VIA
222 82C586B I2C interface
224 This driver can also be built as a module. If so, the module
225 will be called i2c-via.
228 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
231 If you say yes to this option, support will be included for the VIA
232 VT82C596 and later SMBus interface. Specifically, the following
233 chipsets are supported:
245 This driver can also be built as a module. If so, the module
246 will be called i2c-viapro.
250 comment "ACPI drivers"
253 tristate "SMBus Control Method Interface"
255 This driver supports the SMBus Control Method Interface. It needs the
256 BIOS to declare ACPI control methods as described in the SMBus Control
257 Method Interface specification.
259 To compile this driver as a module, choose M here:
260 the module will be called i2c-scmi.
264 comment "Mac SMBus host controller drivers"
265 depends on PPC_CHRP || PPC_PMAC
268 tristate "CHRP Apple Hydra Mac I/O I2C interface"
269 depends on PCI && PPC_CHRP && EXPERIMENTAL
272 This supports the use of the I2C interface in the Apple Hydra Mac
273 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
276 This support is also available as a module. If so, the module
277 will be called i2c-hydra.
280 tristate "Powermac I2C interface"
284 This exposes the various PowerMac i2c interfaces to the linux i2c
285 layer and to userland. It is used by various drivers on the PowerMac
286 platform, and should generally be enabled.
288 This support is also available as a module. If so, the module
289 will be called i2c-powermac.
291 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
294 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
295 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
297 This supports the use of the I2C interface on Atmel AT91
300 This driver is BROKEN because the controller which it uses
301 will easily trigger RX overrun and TX underrun errors. Using
302 low I2C clock rates may partially work around those issues
303 on some systems. Another serious problem is that there is no
304 documented way to issue repeated START conditions, as needed
305 to support combined I2C messages. Use the i2c-gpio driver
306 unless your system can cope with those limitations.
309 tristate "Au1550/Au1200/Au1300 SMBus interface"
310 depends on MIPS_ALCHEMY
312 If you say yes to this option, support will be included for the
313 Au1550/Au1200/Au1300 SMBus interface.
315 This driver can also be built as a module. If so, the module
316 will be called i2c-au1550.
318 config I2C_BLACKFIN_TWI
319 tristate "Blackfin TWI I2C support"
321 depends on !BF561 && !BF531 && !BF532 && !BF533
323 This is the I2C bus driver for Blackfin on-chip TWI interface.
325 This driver can also be built as a module. If so, the module
326 will be called i2c-bfin-twi.
328 config I2C_BLACKFIN_TWI_CLK_KHZ
329 int "Blackfin TWI I2C clock (kHz)"
330 depends on I2C_BLACKFIN_TWI
334 The unit of the TWI clock is kHz.
337 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
338 depends on (CPM1 || CPM2) && OF_I2C
340 This supports the use of the I2C interface on Freescale
341 processors with CPM1 or CPM2.
343 This driver can also be built as a module. If so, the module
344 will be called i2c-cpm.
347 tristate "DaVinci I2C driver"
348 depends on ARCH_DAVINCI
350 Support for TI DaVinci I2C controller driver.
352 This driver can also be built as a module. If so, the module
353 will be called i2c-davinci.
355 Please note that this driver might be needed to bring up other
356 devices such as DaVinci NIC.
357 For details please see http://www.ti.com/davinci
359 config I2C_DESIGNWARE_CORE
362 config I2C_DESIGNWARE_PLATFORM
363 tristate "Synopsys DesignWare Platform"
365 select I2C_DESIGNWARE_CORE
367 If you say yes to this option, support will be included for the
368 Synopsys DesignWare I2C adapter. Only master mode is supported.
370 This driver can also be built as a module. If so, the module
371 will be called i2c-designware-platform.
373 config I2C_DESIGNWARE_PCI
374 tristate "Synopsys DesignWare PCI"
376 select I2C_DESIGNWARE_CORE
378 If you say yes to this option, support will be included for the
379 Synopsys DesignWare I2C adapter. Only master mode is supported.
381 This driver can also be built as a module. If so, the module
382 will be called i2c-designware-pci.
385 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
388 This driver is for PCH(Platform controller Hub) I2C of EG20T which
389 is an IOH(Input/Output Hub) for x86 embedded processor.
390 This driver can access PCH I2C bus device.
392 This driver also can be used for LAPIS Semiconductor IOH(Input/
393 Output Hub), ML7213, ML7223 and ML7831.
394 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
395 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
396 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
397 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
400 tristate "GPIO-based bitbanging I2C"
401 depends on GENERIC_GPIO
404 This is a very simple bitbanging I2C driver utilizing the
405 arch-neutral GPIO API to control the SCL and SDA lines.
407 config I2C_HIGHLANDER
408 tristate "Highlander FPGA SMBus interface"
409 depends on SH_HIGHLANDER
411 If you say yes to this option, support will be included for
412 the SMBus interface located in the FPGA on various Highlander
413 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
414 FPGAs. This is wholly unrelated to the SoC I2C.
416 This driver can also be built as a module. If so, the module
417 will be called i2c-highlander.
420 tristate "IBM PPC 4xx on-chip I2C interface"
423 Say Y here if you want to use IIC peripheral found on
424 embedded IBM PPC 4xx based systems.
426 This driver can also be built as a module. If so, the module
427 will be called i2c-ibm_iic.
430 tristate "IMX I2C interface"
433 Say Y here if you want to use the IIC bus controller on
434 the Freescale i.MX/MXC processors.
436 This driver can also be built as a module. If so, the module
437 will be called i2c-imx.
440 tristate "Intel Moorestown/Medfield Platform I2C controller"
443 Say Y here if you have an Intel Moorestown/Medfield platform I2C
446 This support is also available as a module. If so, the module
447 will be called i2c-intel-mid.
450 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
451 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
453 Say Y here if you want to use the IIC bus controller on
454 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
456 This driver can also be built as a module. If so, the module
457 will be called i2c-iop3xx.
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)
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"
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"
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,
497 as well as the STA2X11 PCIe I/O HUB.
500 tristate "NUC900 I2C Driver"
501 depends on ARCH_W90X900
503 Say Y here to include support for I2C controller in the
504 Winbond/Nuvoton NUC900 based System-on-Chip devices.
507 tristate "OpenCores I2C Controller"
508 depends on EXPERIMENTAL
510 If you say yes to this option, support will be included for the
511 OpenCores I2C controller. For details see
512 http://www.opencores.org/projects.cgi/web/i2c/overview
514 This driver can also be built as a module. If so, the module
515 will be called i2c-ocores.
518 tristate "OMAP I2C adapter"
520 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
522 If you say yes to this option, support will be included for the
523 I2C interface on the Texas Instruments OMAP1/2 family of processors.
524 Like OMAP1510/1610/1710/5912 and OMAP242x.
525 For details see http://www.ti.com/omap.
528 tristate "PA Semi SMBus interface"
529 depends on PPC_PASEMI && PCI
531 Supports the PA Semi PWRficient on-chip SMBus interfaces.
533 config I2C_PCA_PLATFORM
534 tristate "PCA9564/PCA9665 as platform device"
538 This driver supports a memory mapped Philips PCA9564/PCA9665
539 parallel bus to I2C bus controller.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-pca-platform.
545 tristate "PMC MSP I2C TWI Controller"
548 This driver supports the PMC TWI controller on MSP devices.
550 This driver can also be built as module. If so, the module
551 will be called i2c-pmcmsp.
554 tristate "I2C bus support for Philips PNX and NXP LPC targets"
555 depends on ARCH_LPC32XX
557 This driver supports the Philips IP3204 I2C IP block master and/or
560 This driver can also be built as a module. If so, the module
561 will be called i2c-pnx.
564 tristate "PKUnity v3 I2C bus support"
565 depends on UNICORE32 && ARCH_PUV3
568 This driver supports the I2C IP inside the PKUnity-v3 SoC.
569 This I2C bus controller is under AMBA/AXI bus.
571 This driver can also be built as a module. If so, the module
572 will be called i2c-puv3.
575 tristate "Intel PXA2XX I2C adapter"
576 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
578 If you have devices in the PXA I2C bus, say yes to this option.
579 This driver can also be built as a module. If so, the module
580 will be called i2c-pxa.
583 def_bool I2C_PXA && X86_32 && PCI && OF
586 bool "Intel PXA2XX I2C Slave comms support"
587 depends on I2C_PXA && !X86_32
589 Support I2C slave mode communications on the PXA I2C bus. This
590 is necessary for systems where the PXA may be a target on the
593 config HAVE_S3C2410_I2C
596 This will include I2C support for Samsung SoCs. If you want to
597 include I2C support for any machine, kindly select this in the
598 respective Kconfig file.
601 tristate "S3C2410 I2C Driver"
602 depends on HAVE_S3C2410_I2C
604 Say Y here to include support for I2C controller in the
608 tristate "S6000 I2C support"
609 depends on XTENSA_VARIANT_S6000
611 This driver supports the on chip I2C device on the
612 S6000 xtensa processor family.
614 To compile this driver as a module, choose M here. The module
615 will be called i2c-s6000.
618 tristate "Renesas SH7760 I2C Controller"
619 depends on CPU_SUBTYPE_SH7760
621 This driver supports the 2 I2C interfaces on the Renesas SH7760.
623 This driver can also be built as a module. If so, the module
624 will be called i2c-sh7760.
627 tristate "SuperH Mobile I2C Controller"
628 depends on SUPERH || ARCH_SHMOBILE
630 If you say yes to this option, support will be included for the
631 built-in I2C interface on the Renesas SH-Mobile processor.
633 This driver can also be built as a module. If so, the module
634 will be called i2c-sh_mobile.
637 tristate "Simtec Generic I2C interface"
640 If you say yes to this option, support will be included for
641 the Simtec Generic I2C interface. This driver is for the
642 simple I2C bus used on newer Simtec products for general
643 I2C, such as DDC on the Simtec BBD2016A.
645 This driver can also be built as a module. If so, the module
646 will be called i2c-simtec.
649 tristate "CSR SiRFprimaII I2C interface"
650 depends on ARCH_PRIMA2
652 If you say yes to this option, support will be included for the
653 CSR SiRFprimaII I2C interface.
655 This driver can also be built as a module. If so, the module
656 will be called i2c-sirf.
659 tristate "ST Microelectronics DDC I2C interface"
661 default y if MACH_U300
663 If you say yes to this option, support will be included for the
664 I2C interface from ST Microelectronics simply called "DDC I2C"
665 supporting both I2C and DDC, used in e.g. the U300 series
668 This driver can also be built as a module. If so, the module
669 will be called i2c-stu300.
672 tristate "NVIDIA Tegra internal I2C controller"
673 depends on ARCH_TEGRA
675 If you say yes to this option, support will be included for the
676 I2C controller embedded in NVIDIA Tegra SOCs
679 tristate "ARM Versatile/Realview I2C bus support"
680 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
683 Say yes if you want to support the I2C serial bus on ARMs Versatile
686 This driver can also be built as a module. If so, the module
687 will be called i2c-versatile.
690 tristate "Cavium OCTEON I2C bus support"
691 depends on CPU_CAVIUM_OCTEON
693 Say yes if you want to support the I2C serial bus on Cavium
696 This driver can also be built as a module. If so, the module
697 will be called i2c-octeon.
700 tristate "Xilinx I2C Controller"
701 depends on EXPERIMENTAL && HAS_IOMEM
703 If you say yes to this option, support will be included for the
704 Xilinx I2C controller.
706 This driver can also be built as a module. If so, the module
707 will be called xilinx_i2c.
710 tristate "XLR I2C support"
713 This driver enables support for the on-chip I2C interface of
714 the Netlogic XLR/XLS MIPS processors.
716 This driver can also be built as a module. If so, the module
717 will be called i2c-xlr.
719 comment "External I2C/SMBus adapter drivers"
721 config I2C_DIOLAN_U2C
722 tristate "Diolan U2C-12 USB adapter"
725 If you say yes to this option, support will be included for Diolan
726 U2C-12, a USB to I2C interface.
728 This driver can also be built as a module. If so, the module
729 will be called i2c-diolan-u2c.
732 tristate "Parallel port adapter"
737 This supports parallel port I2C adapters such as the ones made by
738 Philips or Velleman, Analog Devices evaluation boards, and more.
739 Basically any adapter using the parallel port as an I2C bus with
740 no extra chipset is supported by this driver, or could be.
742 This driver is a replacement for (and was inspired by) an older
743 driver named i2c-philips-par. The new driver supports more devices,
744 and makes it easier to add support for new devices.
746 An adapter type parameter is now mandatory. Please read the file
747 Documentation/i2c/busses/i2c-parport for details.
749 Another driver exists, named i2c-parport-light, which doesn't depend
750 on the parport driver. This is meant for embedded systems. Don't say
751 Y here if you intend to say Y or M there.
753 This support is also available as a module. If so, the module
754 will be called i2c-parport.
756 config I2C_PARPORT_LIGHT
757 tristate "Parallel port adapter (light)"
761 This supports parallel port I2C adapters such as the ones made by
762 Philips or Velleman, Analog Devices evaluation boards, and more.
763 Basically any adapter using the parallel port as an I2C bus with
764 no extra chipset is supported by this driver, or could be.
766 This driver is a light version of i2c-parport. It doesn't depend
767 on the parport driver, and uses direct I/O access instead. This
768 might be preferred on embedded systems where wasting memory for
769 the clean but heavy parport handling is not an option. The
770 drawback is a reduced portability and the impossibility to
771 daisy-chain other parallel port devices.
773 Don't say Y here if you said Y or M to i2c-parport. Saying M to
774 both is possible but both modules should not be loaded at the same
777 This support is also available as a module. If so, the module
778 will be called i2c-parport-light.
781 tristate "TAOS evaluation module"
782 depends on EXPERIMENTAL
787 This supports TAOS evaluation modules on serial port. In order to
788 use this driver, you will need the inputattach tool, which is part
789 of the input-utils package.
793 This support is also available as a module. If so, the module
794 will be called i2c-taos-evm.
797 tristate "Tiny-USB adapter"
800 If you say yes to this option, support will be included for the
801 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
802 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
804 This driver can also be built as a module. If so, the module
805 will be called i2c-tiny-usb.
807 comment "Other I2C/SMBus bus drivers"
810 tristate "Acorn IOC/IOMD I2C bus support"
811 depends on ARCH_ACORN
815 Say yes if you want to support the I2C bus on Acorn platforms.
817 If you don't know, say Y.
820 tristate "Elektor ISA card"
821 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
824 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
827 This support is also available as a module. If so, the module
828 will be called i2c-elektor.
831 tristate "PCA9564/PCA9665 on an ISA bus"
836 This driver supports ISA boards using the Philips PCA9564/PCA9665
837 parallel bus to I2C bus controller.
839 This driver can also be built as a module. If so, the module
840 will be called i2c-pca-isa.
842 This device is almost undetectable and using this driver on a
843 system which doesn't have this device will result in long
844 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
845 time). If unsure, say N.
848 tristate "SiByte SMBus interface"
849 depends on SIBYTE_SB1xxx_SOC
851 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
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.