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)
117 This driver can also be built as a module. If so, the module
118 will be called i2c-i801.
121 tristate "Intel SCH SMBus 1.0"
125 Say Y here if you want to use SMBus controller on the Intel SCH
128 This driver can also be built as a module. If so, the module
129 will be called i2c-isch.
132 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
135 If you say yes to this option, support will be included for the Intel
136 PIIX4 family of mainboard I2C interfaces. Specifically, the following
137 versions of the chipset are supported (note that Serverworks is part
157 This driver can also be built as a module. If so, the module
158 will be called i2c-piix4.
161 tristate "Nvidia nForce2, nForce3 and nForce4"
164 If you say yes to this option, support will be included for the Nvidia
165 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
167 This driver can also be built as a module. If so, the module
168 will be called i2c-nforce2.
170 config I2C_NFORCE2_S4985
171 tristate "SMBus multiplexing on the Tyan S4985"
172 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
174 Enabling this option will add specific SMBus support for the Tyan
175 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
176 over 4 different channels, where the various memory module EEPROMs
177 live. Saying yes here will give you access to these in addition
180 This driver can also be built as a module. If so, the module
181 will be called i2c-nforce2-s4985.
187 If you say yes to this option, support will be included for the
188 SiS5595 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-sis5595.
194 tristate "SiS 630/730"
197 If you say yes to this option, support will be included for the
198 SiS630 and SiS730 SMBus (a subset of I2C) interface.
200 This driver can also be built as a module. If so, the module
201 will be called i2c-sis630.
207 If you say yes to this option, support will be included for the SiS
208 96x SMBus (a subset of I2C) interfaces. Specifically, the following
209 chipsets are supported:
218 This driver can also be built as a module. If so, the module
219 will be called i2c-sis96x.
222 tristate "VIA VT82C586B"
223 depends on PCI && EXPERIMENTAL
226 If you say yes to this option, support will be included for the VIA
227 82C586B I2C interface
229 This driver can also be built as a module. If so, the module
230 will be called i2c-via.
233 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
236 If you say yes to this option, support will be included for the VIA
237 VT82C596 and later SMBus interface. Specifically, the following
238 chipsets are supported:
250 This driver can also be built as a module. If so, the module
251 will be called i2c-viapro.
255 comment "ACPI drivers"
258 tristate "SMBus Control Method Interface"
260 This driver supports the SMBus Control Method Interface. It needs the
261 BIOS to declare ACPI control methods as described in the SMBus Control
262 Method Interface specification.
264 To compile this driver as a module, choose M here:
265 the module will be called i2c-scmi.
269 comment "Mac SMBus host controller drivers"
270 depends on PPC_CHRP || PPC_PMAC
273 tristate "CHRP Apple Hydra Mac I/O I2C interface"
274 depends on PCI && PPC_CHRP && EXPERIMENTAL
277 This supports the use of the I2C interface in the Apple Hydra Mac
278 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
281 This support is also available as a module. If so, the module
282 will be called i2c-hydra.
285 tristate "Powermac I2C interface"
289 This exposes the various PowerMac i2c interfaces to the linux i2c
290 layer and to userland. It is used by various drivers on the PowerMac
291 platform, and should generally be enabled.
293 This support is also available as a module. If so, the module
294 will be called i2c-powermac.
296 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
299 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
300 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
302 This supports the use of the I2C interface on Atmel AT91
305 This driver is BROKEN because the controller which it uses
306 will easily trigger RX overrun and TX underrun errors. Using
307 low I2C clock rates may partially work around those issues
308 on some systems. Another serious problem is that there is no
309 documented way to issue repeated START conditions, as needed
310 to support combined I2C messages. Use the i2c-gpio driver
311 unless your system can cope with those limitations.
314 tristate "Au1550/Au1200 SMBus interface"
315 depends on MIPS_ALCHEMY
317 If you say yes to this option, support will be included for the
318 Au1550 and Au1200 SMBus interface.
320 This driver can also be built as a module. If so, the module
321 will be called i2c-au1550.
323 config I2C_BLACKFIN_TWI
324 tristate "Blackfin TWI I2C support"
326 depends on !BF561 && !BF531 && !BF532 && !BF533
328 This is the I2C bus driver for Blackfin on-chip TWI interface.
330 This driver can also be built as a module. If so, the module
331 will be called i2c-bfin-twi.
333 config I2C_BLACKFIN_TWI_CLK_KHZ
334 int "Blackfin TWI I2C clock (kHz)"
335 depends on I2C_BLACKFIN_TWI
339 The unit of the TWI clock is kHz.
342 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
343 depends on (CPM1 || CPM2) && OF_I2C
345 This supports the use of the I2C interface on Freescale
346 processors with CPM1 or CPM2.
348 This driver can also be built as a module. If so, the module
349 will be called i2c-cpm.
352 tristate "DaVinci I2C driver"
353 depends on ARCH_DAVINCI
355 Support for TI DaVinci I2C controller driver.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-davinci.
360 Please note that this driver might be needed to bring up other
361 devices such as DaVinci NIC.
362 For details please see http://www.ti.com/davinci
364 config I2C_DESIGNWARE_CORE
367 config I2C_DESIGNWARE_PLATFORM
368 tristate "Synopsys DesignWare Platfrom"
370 select I2C_DESIGNWARE_CORE
372 If you say yes to this option, support will be included for the
373 Synopsys DesignWare I2C adapter. Only master mode is supported.
375 This driver can also be built as a module. If so, the module
376 will be called i2c-designware-platform.
378 config I2C_DESIGNWARE_PCI
379 tristate "Synopsys DesignWare PCI"
381 select I2C_DESIGNWARE_CORE
383 If you say yes to this option, support will be included for the
384 Synopsys DesignWare I2C adapter. Only master mode is supported.
386 This driver can also be built as a module. If so, the module
387 will be called i2c-designware-pci.
390 tristate "GPIO-based bitbanging I2C"
391 depends on GENERIC_GPIO
394 This is a very simple bitbanging I2C driver utilizing the
395 arch-neutral GPIO API to control the SCL and SDA lines.
397 config I2C_HIGHLANDER
398 tristate "Highlander FPGA SMBus interface"
399 depends on SH_HIGHLANDER
401 If you say yes to this option, support will be included for
402 the SMBus interface located in the FPGA on various Highlander
403 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
404 FPGAs. This is wholly unrelated to the SoC I2C.
406 This driver can also be built as a module. If so, the module
407 will be called i2c-highlander.
410 tristate "IBM PPC 4xx on-chip I2C interface"
413 Say Y here if you want to use IIC peripheral found on
414 embedded IBM PPC 4xx based systems.
416 This driver can also be built as a module. If so, the module
417 will be called i2c-ibm_iic.
420 tristate "IMX I2C interface"
423 Say Y here if you want to use the IIC bus controller on
424 the Freescale i.MX/MXC processors.
426 This driver can also be built as a module. If so, the module
427 will be called i2c-imx.
430 tristate "Intel Moorestown/Medfield Platform I2C controller"
433 Say Y here if you have an Intel Moorestown/Medfield platform I2C
436 This support is also available as a module. If so, the module
437 will be called i2c-intel-mid.
440 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
441 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
443 Say Y here if you want to use the IIC bus controller on
444 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
446 This driver can also be built as a module. If so, the module
447 will be called i2c-iop3xx.
450 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
451 depends on ARCH_IXP2000
454 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
455 system and are using GPIO lines for an I2C bus.
457 This support is also available as a module. If so, the module
458 will be called i2c-ixp2000.
460 This driver is deprecated and will be dropped soon. Use i2c-gpio
464 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
467 If you say yes to this option, support will be included for the
468 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
469 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
471 This driver can also be built as a module. If so, the module
472 will be called i2c-mpc.
475 tristate "Marvell mv64xxx I2C Controller"
476 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
478 If you say yes to this option, support will be included for the
479 built-in I2C interface on the Marvell 64xxx line of host bridges.
481 This driver can also be built as a module. If so, the module
482 will be called i2c-mv64xxx.
485 tristate "Freescale i.MX28 I2C interface"
488 Say Y here if you want to use the I2C bus controller on
489 the Freescale i.MX28 processors.
491 This driver can also be built as a module. If so, the module
492 will be called i2c-mxs.
495 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
496 depends on PLAT_NOMADIK
498 If you say yes to this option, support will be included for the
499 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
502 tristate "NUC900 I2C Driver"
503 depends on ARCH_W90X900
505 Say Y here to include support for I2C controller in the
506 Winbond/Nuvoton NUC900 based System-on-Chip devices.
509 tristate "OpenCores I2C Controller"
510 depends on EXPERIMENTAL
512 If you say yes to this option, support will be included for the
513 OpenCores I2C controller. For details see
514 http://www.opencores.org/projects.cgi/web/i2c/overview
516 This driver can also be built as a module. If so, the module
517 will be called i2c-ocores.
520 tristate "OMAP I2C adapter"
522 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
524 If you say yes to this option, support will be included for the
525 I2C interface on the Texas Instruments OMAP1/2 family of processors.
526 Like OMAP1510/1610/1710/5912 and OMAP242x.
527 For details see http://www.ti.com/omap.
530 tristate "PA Semi SMBus interface"
531 depends on PPC_PASEMI && PCI
533 Supports the PA Semi PWRficient on-chip SMBus interfaces.
535 config I2C_PCA_PLATFORM
536 tristate "PCA9564/PCA9665 as platform device"
540 This driver supports a memory mapped Philips PCA9564/PCA9665
541 parallel bus to I2C bus controller.
543 This driver can also be built as a module. If so, the module
544 will be called i2c-pca-platform.
547 tristate "PMC MSP I2C TWI Controller"
550 This driver supports the PMC TWI controller on MSP devices.
552 This driver can also be built as module. If so, the module
553 will be called i2c-pmcmsp.
556 tristate "I2C bus support for Philips PNX and NXP LPC targets"
557 depends on ARCH_PNX4008 || ARCH_LPC32XX
559 This driver supports the Philips IP3204 I2C IP block master and/or
562 This driver can also be built as a module. If so, the module
563 will be called i2c-pnx.
566 tristate "PKUnity v3 I2C bus support"
567 depends on UNICORE32 && ARCH_PUV3
570 This driver supports the I2C IP inside the PKUnity-v3 SoC.
571 This I2C bus controller is under AMBA/AXI bus.
573 This driver can also be built as a module. If so, the module
574 will be called i2c-puv3.
577 tristate "Intel PXA2XX I2C adapter"
578 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
580 If you have devices in the PXA I2C bus, say yes to this option.
581 This driver can also be built as a module. If so, the module
582 will be called i2c-pxa.
585 def_bool I2C_PXA && X86_32 && PCI && OF
588 bool "Intel PXA2XX I2C Slave comms support"
589 depends on I2C_PXA && !X86_32
591 Support I2C slave mode communications on the PXA I2C bus. This
592 is necessary for systems where the PXA may be a target on the
595 config HAVE_S3C2410_I2C
598 This will include I2C support for Samsung SoCs. If you want to
599 include I2C support for any machine, kindly select this in the
600 respective Kconfig file.
603 tristate "S3C2410 I2C Driver"
604 depends on HAVE_S3C2410_I2C
606 Say Y here to include support for I2C controller in the
610 tristate "S6000 I2C support"
611 depends on XTENSA_VARIANT_S6000
613 This driver supports the on chip I2C device on the
614 S6000 xtensa processor family.
616 To compile this driver as a module, choose M here. The module
617 will be called i2c-s6000.
620 tristate "Renesas SH7760 I2C Controller"
621 depends on CPU_SUBTYPE_SH7760
623 This driver supports the 2 I2C interfaces on the Renesas SH7760.
625 This driver can also be built as a module. If so, the module
626 will be called i2c-sh7760.
629 tristate "SuperH Mobile I2C Controller"
630 depends on SUPERH || ARCH_SHMOBILE
632 If you say yes to this option, support will be included for the
633 built-in I2C interface on the Renesas SH-Mobile processor.
635 This driver can also be built as a module. If so, the module
636 will be called i2c-sh_mobile.
639 tristate "Simtec Generic I2C interface"
642 If you say yes to this option, support will be included for
643 the Simtec Generic I2C interface. This driver is for the
644 simple I2C bus used on newer Simtec products for general
645 I2C, such as DDC on the Simtec BBD2016A.
647 This driver can also be built as a module. If so, the module
648 will be called i2c-simtec.
651 tristate "ST Microelectronics DDC I2C interface"
653 default y if MACH_U300
655 If you say yes to this option, support will be included for the
656 I2C interface from ST Microelectronics simply called "DDC I2C"
657 supporting both I2C and DDC, used in e.g. the U300 series
660 This driver can also be built as a module. If so, the module
661 will be called i2c-stu300.
664 tristate "NVIDIA Tegra internal I2C controller"
665 depends on ARCH_TEGRA
667 If you say yes to this option, support will be included for the
668 I2C controller embedded in NVIDIA Tegra SOCs
671 tristate "ARM Versatile/Realview I2C bus support"
672 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
675 Say yes if you want to support the I2C serial bus on ARMs Versatile
678 This driver can also be built as a module. If so, the module
679 will be called i2c-versatile.
682 tristate "Cavium OCTEON I2C bus support"
683 depends on CPU_CAVIUM_OCTEON
685 Say yes if you want to support the I2C serial bus on Cavium
688 This driver can also be built as a module. If so, the module
689 will be called i2c-octeon.
692 tristate "Xilinx I2C Controller"
693 depends on EXPERIMENTAL && HAS_IOMEM
695 If you say yes to this option, support will be included for the
696 Xilinx I2C controller.
698 This driver can also be built as a module. If so, the module
699 will be called xilinx_i2c.
702 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
705 This driver is for PCH(Platform controller Hub) I2C of EG20T which
706 is an IOH(Input/Output Hub) for x86 embedded processor.
707 This driver can access PCH I2C bus device.
709 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
710 Output Hub), ML7213 and ML7223.
711 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
712 for MP(Media Phone) use.
713 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
714 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
716 comment "External I2C/SMBus adapter drivers"
718 config I2C_DIOLAN_U2C
719 tristate "Diolan U2C-12 USB adapter"
722 If you say yes to this option, support will be included for Diolan
723 U2C-12, a USB to I2C interface.
725 This driver can also be built as a module. If so, the module
726 will be called i2c-diolan-u2c.
729 tristate "Parallel port adapter"
734 This supports parallel port I2C adapters such as the ones made by
735 Philips or Velleman, Analog Devices evaluation boards, and more.
736 Basically any adapter using the parallel port as an I2C bus with
737 no extra chipset is supported by this driver, or could be.
739 This driver is a replacement for (and was inspired by) an older
740 driver named i2c-philips-par. The new driver supports more devices,
741 and makes it easier to add support for new devices.
743 An adapter type parameter is now mandatory. Please read the file
744 Documentation/i2c/busses/i2c-parport for details.
746 Another driver exists, named i2c-parport-light, which doesn't depend
747 on the parport driver. This is meant for embedded systems. Don't say
748 Y here if you intend to say Y or M there.
750 This support is also available as a module. If so, the module
751 will be called i2c-parport.
753 config I2C_PARPORT_LIGHT
754 tristate "Parallel port adapter (light)"
758 This supports parallel port I2C adapters such as the ones made by
759 Philips or Velleman, Analog Devices evaluation boards, and more.
760 Basically any adapter using the parallel port as an I2C bus with
761 no extra chipset is supported by this driver, or could be.
763 This driver is a light version of i2c-parport. It doesn't depend
764 on the parport driver, and uses direct I/O access instead. This
765 might be preferred on embedded systems where wasting memory for
766 the clean but heavy parport handling is not an option. The
767 drawback is a reduced portability and the impossibility to
768 daisy-chain other parallel port devices.
770 Don't say Y here if you said Y or M to i2c-parport. Saying M to
771 both is possible but both modules should not be loaded at the same
774 This support is also available as a module. If so, the module
775 will be called i2c-parport-light.
778 tristate "TAOS evaluation module"
779 depends on EXPERIMENTAL
784 This supports TAOS evaluation modules on serial port. In order to
785 use this driver, you will need the inputattach tool, which is part
786 of the input-utils package.
790 This support is also available as a module. If so, the module
791 will be called i2c-taos-evm.
794 tristate "Tiny-USB adapter"
797 If you say yes to this option, support will be included for the
798 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
799 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
801 This driver can also be built as a module. If so, the module
802 will be called i2c-tiny-usb.
804 comment "Other I2C/SMBus bus drivers"
807 tristate "Acorn IOC/IOMD I2C bus support"
808 depends on ARCH_ACORN
812 Say yes if you want to support the I2C bus on Acorn platforms.
814 If you don't know, say Y.
817 tristate "Elektor ISA card"
818 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
821 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
824 This support is also available as a module. If so, the module
825 will be called i2c-elektor.
828 tristate "PCA9564/PCA9665 on an ISA bus"
833 This driver supports ISA boards using the Philips PCA9564/PCA9665
834 parallel bus to I2C bus controller.
836 This driver can also be built as a module. If so, the module
837 will be called i2c-pca-isa.
839 This device is almost undetectable and using this driver on a
840 system which doesn't have this device will result in long
841 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
842 time). If unsure, say N.
845 tristate "SiByte SMBus interface"
846 depends on SIBYTE_SB1xxx_SOC
848 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
851 tristate "I2C/SMBus Test Stub"
852 depends on EXPERIMENTAL && m
855 This module may be useful to developers of SMBus client drivers,
856 especially for certain kinds of sensor chips.
858 If you do build this module, be sure to read the notes and warnings
859 in <file:Documentation/i2c/i2c-stub>.
861 If you don't know what to do here, definitely say N.
864 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
865 depends on SCx200_GPIO
868 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
870 If you don't know what to do here, say N.
872 This support is also available as a module. If so, the module
873 will be called scx200_i2c.
875 This driver is deprecated and will be dropped soon. Use i2c-gpio
876 (or scx200_acb) instead.
878 config SCx200_I2C_SCL
879 int "GPIO pin used for SCL"
880 depends on SCx200_I2C
883 Enter the GPIO pin number used for the SCL signal. This value can
884 also be specified with a module parameter.
886 config SCx200_I2C_SDA
887 int "GPIO pin used for SDA"
888 depends on SCx200_I2C
891 Enter the GPIO pin number used for the SSA signal. This value can
892 also be specified with a module parameter.
895 tristate "Geode ACCESS.bus support"
896 depends on X86_32 && PCI
898 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
899 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
901 If you don't know what to do here, say N.
903 This support is also available as a module. If so, the module
904 will be called scx200_acb.