2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
7 comment "PC SMBus host controller drivers"
14 If you say yes to this option, support will be included for the SMB
15 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
16 controller is part of the 7101 device, which is an ACPI-compliant
17 Power Management Unit (PMU).
19 This driver can also be built as a module. If so, the module
20 will be called i2c-ali1535.
24 depends on PCI && EXPERIMENTAL
26 If you say yes to this option, support will be included for the SMB
27 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
28 controller is part of the 7101 device, which is an ACPI-compliant
29 Power Management Unit (PMU).
31 This driver can also be built as a module. If so, the module
32 will be called i2c-ali1563.
38 If you say yes to this option, support will be included for the
39 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
41 This driver can also be built as a module. If so, the module
42 will be called i2c-ali15x3.
45 tristate "AMD 756/766/768/8111 and nVidia nForce"
48 If you say yes to this option, support will be included for the AMD
49 756/766/768 mainboard I2C interfaces. The driver also includes
50 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
51 the nVidia nForce I2C interface.
53 This driver can also be built as a module. If so, the module
54 will be called i2c-amd756.
56 config I2C_AMD756_S4882
57 tristate "SMBus multiplexing on the Tyan S4882"
58 depends on I2C_AMD756 && X86 && EXPERIMENTAL
60 Enabling this option will add specific SMBus support for the Tyan
61 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
62 over 8 different channels, where the various memory module EEPROMs
63 and temperature sensors live. Saying yes here will give you access
64 to these in addition to the trunk.
66 This driver can also be built as a module. If so, the module
67 will be called i2c-amd756-s4882.
73 If you say yes to this option, support will be included for the
74 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
76 This driver can also be built as a module. If so, the module
77 will be called i2c-amd8111.
80 tristate "Intel 82801 (ICH/PCH)"
82 select CHECK_SIGNATURE if X86 && DMI
84 If you say yes to this option, support will be included for the Intel
85 801 family of mainboard I2C interfaces. Specifically, the following
86 versions of the chipset are supported:
92 82801EB/ER (ICH5/ICH5R)
112 Wildcat Point-LP (PCH)
114 Sunrise Point-H (PCH)
115 Sunrise Point-LP (PCH)
120 This driver can also be built as a module. If so, the module
121 will be called i2c-i801.
124 tristate "Intel SCH SMBus 1.0"
128 Say Y here if you want to use SMBus controller on the Intel SCH
131 This driver can also be built as a module. If so, the module
132 will be called i2c-isch.
135 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
138 If you say yes to this option, support will be included for the Intel
139 PIIX4 family of mainboard I2C interfaces. Specifically, the following
140 versions of the chipset are supported (note that Serverworks is part
160 This driver can also be built as a module. If so, the module
161 will be called i2c-piix4.
164 tristate "Nvidia nForce2, nForce3 and nForce4"
167 If you say yes to this option, support will be included for the Nvidia
168 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
170 This driver can also be built as a module. If so, the module
171 will be called i2c-nforce2.
173 config I2C_NFORCE2_S4985
174 tristate "SMBus multiplexing on the Tyan S4985"
175 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
177 Enabling this option will add specific SMBus support for the Tyan
178 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
179 over 4 different channels, where the various memory module EEPROMs
180 live. Saying yes here will give you access to these in addition
183 This driver can also be built as a module. If so, the module
184 will be called i2c-nforce2-s4985.
190 If you say yes to this option, support will be included for the
191 SiS5595 SMBus (a subset of I2C) interface.
193 This driver can also be built as a module. If so, the module
194 will be called i2c-sis5595.
197 tristate "SiS 630/730"
200 If you say yes to this option, support will be included for the
201 SiS630 and SiS730 SMBus (a subset of I2C) interface.
203 This driver can also be built as a module. If so, the module
204 will be called i2c-sis630.
210 If you say yes to this option, support will be included for the SiS
211 96x SMBus (a subset of I2C) interfaces. Specifically, the following
212 chipsets are supported:
221 This driver can also be built as a module. If so, the module
222 will be called i2c-sis96x.
225 tristate "VIA VT82C586B"
226 depends on PCI && EXPERIMENTAL
229 If you say yes to this option, support will be included for the VIA
230 82C586B I2C interface
232 This driver can also be built as a module. If so, the module
233 will be called i2c-via.
236 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
239 If you say yes to this option, support will be included for the VIA
240 VT82C596 and later SMBus interface. Specifically, the following
241 chipsets are supported:
253 This driver can also be built as a module. If so, the module
254 will be called i2c-viapro.
258 comment "ACPI drivers"
261 tristate "SMBus Control Method Interface"
263 This driver supports the SMBus Control Method Interface. It needs the
264 BIOS to declare ACPI control methods as described in the SMBus Control
265 Method Interface specification.
267 To compile this driver as a module, choose M here:
268 the module will be called i2c-scmi.
272 comment "Mac SMBus host controller drivers"
273 depends on PPC_CHRP || PPC_PMAC
276 tristate "CHRP Apple Hydra Mac I/O I2C interface"
277 depends on PCI && PPC_CHRP && EXPERIMENTAL
280 This supports the use of the I2C interface in the Apple Hydra Mac
281 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
284 This support is also available as a module. If so, the module
285 will be called i2c-hydra.
288 tristate "Powermac I2C interface"
292 This exposes the various PowerMac i2c interfaces to the linux i2c
293 layer and to userland. It is used by various drivers on the PowerMac
294 platform, and should generally be enabled.
296 This support is also available as a module. If so, the module
297 will be called i2c-powermac.
299 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
302 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
303 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
305 This supports the use of the I2C interface on Atmel AT91
308 This driver is BROKEN because the controller which it uses
309 will easily trigger RX overrun and TX underrun errors. Using
310 low I2C clock rates may partially work around those issues
311 on some systems. Another serious problem is that there is no
312 documented way to issue repeated START conditions, as needed
313 to support combined I2C messages. Use the i2c-gpio driver
314 unless your system can cope with those limitations.
317 tristate "Au1550/Au1200 SMBus interface"
318 depends on MIPS_ALCHEMY
320 If you say yes to this option, support will be included for the
321 Au1550 and Au1200 SMBus interface.
323 This driver can also be built as a module. If so, the module
324 will be called i2c-au1550.
326 config I2C_BLACKFIN_TWI
327 tristate "Blackfin TWI I2C support"
329 depends on !BF561 && !BF531 && !BF532 && !BF533
331 This is the I2C bus driver for Blackfin on-chip TWI interface.
333 This driver can also be built as a module. If so, the module
334 will be called i2c-bfin-twi.
336 config I2C_BLACKFIN_TWI_CLK_KHZ
337 int "Blackfin TWI I2C clock (kHz)"
338 depends on I2C_BLACKFIN_TWI
342 The unit of the TWI clock is kHz.
345 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
346 depends on (CPM1 || CPM2) && OF_I2C
348 This supports the use of the I2C interface on Freescale
349 processors with CPM1 or CPM2.
351 This driver can also be built as a module. If so, the module
352 will be called i2c-cpm.
355 tristate "DaVinci I2C driver"
356 depends on ARCH_DAVINCI
358 Support for TI DaVinci I2C controller driver.
360 This driver can also be built as a module. If so, the module
361 will be called i2c-davinci.
363 Please note that this driver might be needed to bring up other
364 devices such as DaVinci NIC.
365 For details please see http://www.ti.com/davinci
367 config I2C_DESIGNWARE_CORE
370 config I2C_DESIGNWARE_PLATFORM
371 tristate "Synopsys DesignWare Platfrom"
373 select I2C_DESIGNWARE_CORE
375 If you say yes to this option, support will be included for the
376 Synopsys DesignWare I2C adapter. Only master mode is supported.
378 This driver can also be built as a module. If so, the module
379 will be called i2c-designware-platform.
381 config I2C_DESIGNWARE_PCI
382 tristate "Synopsys DesignWare PCI"
384 select I2C_DESIGNWARE_CORE
386 If you say yes to this option, support will be included for the
387 Synopsys DesignWare I2C adapter. Only master mode is supported.
389 This driver can also be built as a module. If so, the module
390 will be called i2c-designware-pci.
393 tristate "GPIO-based bitbanging I2C"
394 depends on GENERIC_GPIO
397 This is a very simple bitbanging I2C driver utilizing the
398 arch-neutral GPIO API to control the SCL and SDA lines.
400 config I2C_HIGHLANDER
401 tristate "Highlander FPGA SMBus interface"
402 depends on SH_HIGHLANDER
404 If you say yes to this option, support will be included for
405 the SMBus interface located in the FPGA on various Highlander
406 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
407 FPGAs. This is wholly unrelated to the SoC I2C.
409 This driver can also be built as a module. If so, the module
410 will be called i2c-highlander.
413 tristate "IBM PPC 4xx on-chip I2C interface"
416 Say Y here if you want to use IIC peripheral found on
417 embedded IBM PPC 4xx based systems.
419 This driver can also be built as a module. If so, the module
420 will be called i2c-ibm_iic.
423 tristate "IMX I2C interface"
426 Say Y here if you want to use the IIC bus controller on
427 the Freescale i.MX/MXC processors.
429 This driver can also be built as a module. If so, the module
430 will be called i2c-imx.
433 tristate "Intel Moorestown/Medfield Platform I2C controller"
436 Say Y here if you have an Intel Moorestown/Medfield platform I2C
439 This support is also available as a module. If so, the module
440 will be called i2c-intel-mid.
443 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
444 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
446 Say Y here if you want to use the IIC bus controller on
447 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
449 This driver can also be built as a module. If so, the module
450 will be called i2c-iop3xx.
453 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
454 depends on ARCH_IXP2000
457 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
458 system and are using GPIO lines for an I2C bus.
460 This support is also available as a module. If so, the module
461 will be called i2c-ixp2000.
463 This driver is deprecated and will be dropped soon. Use i2c-gpio
467 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
470 If you say yes to this option, support will be included for the
471 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
472 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
474 This driver can also be built as a module. If so, the module
475 will be called i2c-mpc.
478 tristate "Marvell mv64xxx I2C Controller"
479 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
481 If you say yes to this option, support will be included for the
482 built-in I2C interface on the Marvell 64xxx line of host bridges.
484 This driver can also be built as a module. If so, the module
485 will be called i2c-mv64xxx.
488 tristate "Freescale i.MX28 I2C interface"
491 Say Y here if you want to use the I2C bus controller on
492 the Freescale i.MX28 processors.
494 This driver can also be built as a module. If so, the module
495 will be called i2c-mxs.
498 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
499 depends on PLAT_NOMADIK
501 If you say yes to this option, support will be included for the
502 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
505 tristate "NUC900 I2C Driver"
506 depends on ARCH_W90X900
508 Say Y here to include support for I2C controller in the
509 Winbond/Nuvoton NUC900 based System-on-Chip devices.
512 tristate "OpenCores I2C Controller"
513 depends on EXPERIMENTAL
515 If you say yes to this option, support will be included for the
516 OpenCores I2C controller. For details see
517 http://www.opencores.org/projects.cgi/web/i2c/overview
519 This driver can also be built as a module. If so, the module
520 will be called i2c-ocores.
523 tristate "OMAP I2C adapter"
525 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
527 If you say yes to this option, support will be included for the
528 I2C interface on the Texas Instruments OMAP1/2 family of processors.
529 Like OMAP1510/1610/1710/5912 and OMAP242x.
530 For details see http://www.ti.com/omap.
533 tristate "PA Semi SMBus interface"
534 depends on PPC_PASEMI && PCI
536 Supports the PA Semi PWRficient on-chip SMBus interfaces.
538 config I2C_PCA_PLATFORM
539 tristate "PCA9564/PCA9665 as platform device"
543 This driver supports a memory mapped Philips PCA9564/PCA9665
544 parallel bus to I2C bus controller.
546 This driver can also be built as a module. If so, the module
547 will be called i2c-pca-platform.
550 tristate "PMC MSP I2C TWI Controller"
553 This driver supports the PMC TWI controller on MSP devices.
555 This driver can also be built as module. If so, the module
556 will be called i2c-pmcmsp.
559 tristate "I2C bus support for Philips PNX and NXP LPC targets"
560 depends on ARCH_PNX4008 || ARCH_LPC32XX
562 This driver supports the Philips IP3204 I2C IP block master and/or
565 This driver can also be built as a module. If so, the module
566 will be called i2c-pnx.
569 tristate "PKUnity v3 I2C bus support"
570 depends on UNICORE32 && ARCH_PUV3
573 This driver supports the I2C IP inside the PKUnity-v3 SoC.
574 This I2C bus controller is under AMBA/AXI bus.
576 This driver can also be built as a module. If so, the module
577 will be called i2c-puv3.
580 tristate "Intel PXA2XX I2C adapter"
581 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
583 If you have devices in the PXA I2C bus, say yes to this option.
584 This driver can also be built as a module. If so, the module
585 will be called i2c-pxa.
588 def_bool I2C_PXA && X86_32 && PCI && OF
591 bool "Intel PXA2XX I2C Slave comms support"
592 depends on I2C_PXA && !X86_32
594 Support I2C slave mode communications on the PXA I2C bus. This
595 is necessary for systems where the PXA may be a target on the
598 config HAVE_S3C2410_I2C
601 This will include I2C support for Samsung SoCs. If you want to
602 include I2C support for any machine, kindly select this in the
603 respective Kconfig file.
606 tristate "S3C2410 I2C Driver"
607 depends on HAVE_S3C2410_I2C
609 Say Y here to include support for I2C controller in the
613 tristate "S6000 I2C support"
614 depends on XTENSA_VARIANT_S6000
616 This driver supports the on chip I2C device on the
617 S6000 xtensa processor family.
619 To compile this driver as a module, choose M here. The module
620 will be called i2c-s6000.
623 tristate "Renesas SH7760 I2C Controller"
624 depends on CPU_SUBTYPE_SH7760
626 This driver supports the 2 I2C interfaces on the Renesas SH7760.
628 This driver can also be built as a module. If so, the module
629 will be called i2c-sh7760.
632 tristate "SuperH Mobile I2C Controller"
633 depends on SUPERH || ARCH_SHMOBILE
635 If you say yes to this option, support will be included for the
636 built-in I2C interface on the Renesas SH-Mobile processor.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-sh_mobile.
642 tristate "Simtec Generic I2C interface"
645 If you say yes to this option, support will be included for
646 the Simtec Generic I2C interface. This driver is for the
647 simple I2C bus used on newer Simtec products for general
648 I2C, such as DDC on the Simtec BBD2016A.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-simtec.
654 tristate "ST Microelectronics DDC I2C interface"
656 default y if MACH_U300
658 If you say yes to this option, support will be included for the
659 I2C interface from ST Microelectronics simply called "DDC I2C"
660 supporting both I2C and DDC, used in e.g. the U300 series
663 This driver can also be built as a module. If so, the module
664 will be called i2c-stu300.
667 tristate "NVIDIA Tegra internal I2C controller"
668 depends on ARCH_TEGRA
670 If you say yes to this option, support will be included for the
671 I2C controller embedded in NVIDIA Tegra SOCs
674 tristate "ARM Versatile/Realview I2C bus support"
675 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
678 Say yes if you want to support the I2C serial bus on ARMs Versatile
681 This driver can also be built as a module. If so, the module
682 will be called i2c-versatile.
685 tristate "Cavium OCTEON I2C bus support"
686 depends on CPU_CAVIUM_OCTEON
688 Say yes if you want to support the I2C serial bus on Cavium
691 This driver can also be built as a module. If so, the module
692 will be called i2c-octeon.
695 tristate "Xilinx I2C Controller"
696 depends on EXPERIMENTAL && HAS_IOMEM
698 If you say yes to this option, support will be included for the
699 Xilinx I2C controller.
701 This driver can also be built as a module. If so, the module
702 will be called xilinx_i2c.
705 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
708 This driver is for PCH(Platform controller Hub) I2C of EG20T which
709 is an IOH(Input/Output Hub) for x86 embedded processor.
710 This driver can access PCH I2C bus device.
712 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
713 Output Hub), ML7213 and ML7223.
714 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
715 for MP(Media Phone) use.
716 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
717 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
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 "I2C/SMBus Test Stub"
855 depends on EXPERIMENTAL && m
858 This module may be useful to developers of SMBus client drivers,
859 especially for certain kinds of sensor chips.
861 If you do build this module, be sure to read the notes and warnings
862 in <file:Documentation/i2c/i2c-stub>.
864 If you don't know what to do here, definitely say N.
867 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
868 depends on SCx200_GPIO
871 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
873 If you don't know what to do here, say N.
875 This support is also available as a module. If so, the module
876 will be called scx200_i2c.
878 This driver is deprecated and will be dropped soon. Use i2c-gpio
879 (or scx200_acb) instead.
881 config SCx200_I2C_SCL
882 int "GPIO pin used for SCL"
883 depends on SCx200_I2C
886 Enter the GPIO pin number used for the SCL signal. This value can
887 also be specified with a module parameter.
889 config SCx200_I2C_SDA
890 int "GPIO pin used for SDA"
891 depends on SCx200_I2C
894 Enter the GPIO pin number used for the SSA signal. This value can
895 also be specified with a module parameter.
898 tristate "Geode ACCESS.bus support"
899 depends on X86_32 && PCI
901 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
902 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
904 If you don't know what to do here, say N.
906 This support is also available as a module. If so, the module
907 will be called scx200_acb.