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)
108 This driver can also be built as a module. If so, the module
109 will be called i2c-i801.
112 tristate "Intel SCH SMBus 1.0"
116 Say Y here if you want to use SMBus controller on the Intel SCH
119 This driver can also be built as a module. If so, the module
120 will be called i2c-isch.
123 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
126 If you say yes to this option, support will be included for the Intel
127 PIIX4 family of mainboard I2C interfaces. Specifically, the following
128 versions of the chipset are supported (note that Serverworks is part
146 Some AMD chipsets contain two PIIX4-compatible SMBus
147 controllers. This driver will attempt to use both controllers
148 on the SB700/SP5100, if they have been initialized by the BIOS.
150 This driver can also be built as a module. If so, the module
151 will be called i2c-piix4.
154 tristate "Nvidia nForce2, nForce3 and nForce4"
157 If you say yes to this option, support will be included for the Nvidia
158 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
160 This driver can also be built as a module. If so, the module
161 will be called i2c-nforce2.
163 config I2C_NFORCE2_S4985
164 tristate "SMBus multiplexing on the Tyan S4985"
165 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
167 Enabling this option will add specific SMBus support for the Tyan
168 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
169 over 4 different channels, where the various memory module EEPROMs
170 live. Saying yes here will give you access to these in addition
173 This driver can also be built as a module. If so, the module
174 will be called i2c-nforce2-s4985.
180 If you say yes to this option, support will be included for the
181 SiS5595 SMBus (a subset of I2C) interface.
183 This driver can also be built as a module. If so, the module
184 will be called i2c-sis5595.
187 tristate "SiS 630/730"
190 If you say yes to this option, support will be included for the
191 SiS630 and SiS730 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-sis630.
200 If you say yes to this option, support will be included for the SiS
201 96x SMBus (a subset of I2C) interfaces. Specifically, the following
202 chipsets are supported:
211 This driver can also be built as a module. If so, the module
212 will be called i2c-sis96x.
215 tristate "VIA VT82C586B"
216 depends on PCI && EXPERIMENTAL
219 If you say yes to this option, support will be included for the VIA
220 82C586B I2C interface
222 This driver can also be built as a module. If so, the module
223 will be called i2c-via.
226 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
229 If you say yes to this option, support will be included for the VIA
230 VT82C596 and later SMBus interface. Specifically, the following
231 chipsets are supported:
243 This driver can also be built as a module. If so, the module
244 will be called i2c-viapro.
248 comment "ACPI drivers"
251 tristate "SMBus Control Method Interface"
253 This driver supports the SMBus Control Method Interface. It needs the
254 BIOS to declare ACPI control methods as described in the SMBus Control
255 Method Interface specification.
257 To compile this driver as a module, choose M here:
258 the module will be called i2c-scmi.
262 comment "Mac SMBus host controller drivers"
263 depends on PPC_CHRP || PPC_PMAC
266 tristate "CHRP Apple Hydra Mac I/O I2C interface"
267 depends on PCI && PPC_CHRP && EXPERIMENTAL
270 This supports the use of the I2C interface in the Apple Hydra Mac
271 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
274 This support is also available as a module. If so, the module
275 will be called i2c-hydra.
278 tristate "Powermac I2C interface"
282 This exposes the various PowerMac i2c interfaces to the linux i2c
283 layer and to userland. It is used by various drivers on the PowerMac
284 platform, and should generally be enabled.
286 This support is also available as a module. If so, the module
287 will be called i2c-powermac.
289 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
292 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
293 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
295 This supports the use of the I2C interface on Atmel AT91
298 This driver is BROKEN because the controller which it uses
299 will easily trigger RX overrun and TX underrun errors. Using
300 low I2C clock rates may partially work around those issues
301 on some systems. Another serious problem is that there is no
302 documented way to issue repeated START conditions, as needed
303 to support combined I2C messages. Use the i2c-gpio driver
304 unless your system can cope with those limitations.
307 tristate "Au1550/Au1200/Au1300 SMBus interface"
308 depends on MIPS_ALCHEMY
310 If you say yes to this option, support will be included for the
311 Au1550/Au1200/Au1300 SMBus interface.
313 This driver can also be built as a module. If so, the module
314 will be called i2c-au1550.
316 config I2C_BLACKFIN_TWI
317 tristate "Blackfin TWI I2C support"
319 depends on !BF561 && !BF531 && !BF532 && !BF533
321 This is the I2C bus driver for Blackfin on-chip TWI interface.
323 This driver can also be built as a module. If so, the module
324 will be called i2c-bfin-twi.
326 config I2C_BLACKFIN_TWI_CLK_KHZ
327 int "Blackfin TWI I2C clock (kHz)"
328 depends on I2C_BLACKFIN_TWI
332 The unit of the TWI clock is kHz.
335 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
336 depends on (CPM1 || CPM2) && OF_I2C
338 This supports the use of the I2C interface on Freescale
339 processors with CPM1 or CPM2.
341 This driver can also be built as a module. If so, the module
342 will be called i2c-cpm.
345 tristate "DaVinci I2C driver"
346 depends on ARCH_DAVINCI
348 Support for TI DaVinci I2C controller driver.
350 This driver can also be built as a module. If so, the module
351 will be called i2c-davinci.
353 Please note that this driver might be needed to bring up other
354 devices such as DaVinci NIC.
355 For details please see http://www.ti.com/davinci
357 config I2C_DESIGNWARE_PLATFORM
358 tristate "Synopsys DesignWare Platform"
361 If you say yes to this option, support will be included for the
362 Synopsys DesignWare I2C adapter. Only master mode is supported.
364 This driver can also be built as a module. If so, the module
365 will be called i2c-designware-platform.
367 config I2C_DESIGNWARE_PCI
368 tristate "Synopsys DesignWare PCI"
371 If you say yes to this option, support will be included for the
372 Synopsys DesignWare I2C adapter. Only master mode is supported.
374 This driver can also be built as a module. If so, the module
375 will be called i2c-designware-pci.
378 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
381 This driver is for PCH(Platform controller Hub) I2C of EG20T which
382 is an IOH(Input/Output Hub) for x86 embedded processor.
383 This driver can access PCH I2C bus device.
385 This driver also can be used for LAPIS Semiconductor IOH(Input/
386 Output Hub), ML7213, ML7223 and ML7831.
387 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
388 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
389 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
390 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
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 "MPC107/824x/85xx/512x/52xx/83xx/86xx"
456 If you say yes to this option, support will be included for the
457 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
458 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
460 This driver can also be built as a module. If so, the module
461 will be called i2c-mpc.
464 tristate "Marvell mv64xxx I2C Controller"
465 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
467 If you say yes to this option, support will be included for the
468 built-in I2C interface on the Marvell 64xxx line of host bridges.
470 This driver can also be built as a module. If so, the module
471 will be called i2c-mv64xxx.
474 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 "CSR SiRFprimaII I2C interface"
642 depends on ARCH_PRIMA2
644 If you say yes to this option, support will be included for the
645 CSR SiRFprimaII I2C interface.
647 This driver can also be built as a module. If so, the module
648 will be called i2c-sirf.
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 "XLR I2C support"
705 This driver enables support for the on-chip I2C interface of
706 the Netlogic XLR/XLS MIPS processors.
708 This driver can also be built as a module. If so, the module
709 will be called i2c-xlr.
711 comment "External I2C/SMBus adapter drivers"
713 config I2C_DIOLAN_U2C
714 tristate "Diolan U2C-12 USB adapter"
717 If you say yes to this option, support will be included for Diolan
718 U2C-12, a USB to I2C interface.
720 This driver can also be built as a module. If so, the module
721 will be called i2c-diolan-u2c.
724 tristate "Parallel port adapter"
729 This supports parallel port I2C adapters such as the ones made by
730 Philips or Velleman, Analog Devices evaluation boards, and more.
731 Basically any adapter using the parallel port as an I2C bus with
732 no extra chipset is supported by this driver, or could be.
734 This driver is a replacement for (and was inspired by) an older
735 driver named i2c-philips-par. The new driver supports more devices,
736 and makes it easier to add support for new devices.
738 An adapter type parameter is now mandatory. Please read the file
739 Documentation/i2c/busses/i2c-parport for details.
741 Another driver exists, named i2c-parport-light, which doesn't depend
742 on the parport driver. This is meant for embedded systems. Don't say
743 Y here if you intend to say Y or M there.
745 This support is also available as a module. If so, the module
746 will be called i2c-parport.
748 config I2C_PARPORT_LIGHT
749 tristate "Parallel port adapter (light)"
753 This supports parallel port I2C adapters such as the ones made by
754 Philips or Velleman, Analog Devices evaluation boards, and more.
755 Basically any adapter using the parallel port as an I2C bus with
756 no extra chipset is supported by this driver, or could be.
758 This driver is a light version of i2c-parport. It doesn't depend
759 on the parport driver, and uses direct I/O access instead. This
760 might be preferred on embedded systems where wasting memory for
761 the clean but heavy parport handling is not an option. The
762 drawback is a reduced portability and the impossibility to
763 daisy-chain other parallel port devices.
765 Don't say Y here if you said Y or M to i2c-parport. Saying M to
766 both is possible but both modules should not be loaded at the same
769 This support is also available as a module. If so, the module
770 will be called i2c-parport-light.
773 tristate "TAOS evaluation module"
774 depends on EXPERIMENTAL
779 This supports TAOS evaluation modules on serial port. In order to
780 use this driver, you will need the inputattach tool, which is part
781 of the input-utils package.
785 This support is also available as a module. If so, the module
786 will be called i2c-taos-evm.
789 tristate "Tiny-USB adapter"
792 If you say yes to this option, support will be included for the
793 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
794 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
796 This driver can also be built as a module. If so, the module
797 will be called i2c-tiny-usb.
799 comment "Other I2C/SMBus bus drivers"
802 tristate "Acorn IOC/IOMD I2C bus support"
803 depends on ARCH_ACORN
807 Say yes if you want to support the I2C bus on Acorn platforms.
809 If you don't know, say Y.
812 tristate "Elektor ISA card"
813 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
816 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
819 This support is also available as a module. If so, the module
820 will be called i2c-elektor.
823 tristate "PCA9564/PCA9665 on an ISA bus"
828 This driver supports ISA boards using the Philips PCA9564/PCA9665
829 parallel bus to I2C bus controller.
831 This driver can also be built as a module. If so, the module
832 will be called i2c-pca-isa.
834 This device is almost undetectable and using this driver on a
835 system which doesn't have this device will result in long
836 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
837 time). If unsure, say N.
840 tristate "SiByte SMBus interface"
841 depends on SIBYTE_SB1xxx_SOC
843 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
846 tristate "I2C/SMBus Test Stub"
847 depends on EXPERIMENTAL && m
850 This module may be useful to developers of SMBus client drivers,
851 especially for certain kinds of sensor chips.
853 If you do build this module, be sure to read the notes and warnings
854 in <file:Documentation/i2c/i2c-stub>.
856 If you don't know what to do here, definitely say N.
859 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
860 depends on SCx200_GPIO
863 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
865 If you don't know what to do here, say N.
867 This support is also available as a module. If so, the module
868 will be called scx200_i2c.
870 This driver is deprecated and will be dropped soon. Use i2c-gpio
871 (or scx200_acb) instead.
873 config SCx200_I2C_SCL
874 int "GPIO pin used for SCL"
875 depends on SCx200_I2C
878 Enter the GPIO pin number used for the SCL signal. This value can
879 also be specified with a module parameter.
881 config SCx200_I2C_SDA
882 int "GPIO pin used for SDA"
883 depends on SCx200_I2C
886 Enter the GPIO pin number used for the SSA signal. This value can
887 also be specified with a module parameter.
890 tristate "Geode ACCESS.bus support"
891 depends on X86_32 && PCI
893 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
894 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
896 If you don't know what to do here, say N.
898 This support is also available as a module. If so, the module
899 will be called scx200_acb.