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
295 This supports the use of the I2C interface on Atmel AT91
298 A serious problem is that there is no documented way to issue
299 repeated START conditions for more than two messages, as needed
300 to support combined I2C messages. Use the i2c-gpio driver
301 unless your system can cope with this limitation.
303 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
304 don't have clock stretching in transmission mode. For that reason,
305 you can encounter underrun issues causing premature stop sendings if
306 the latency to fill the transmission register is too long. If you
307 are facing this situation, use the i2c-gpio driver.
310 tristate "Au1550/Au1200/Au1300 SMBus interface"
311 depends on MIPS_ALCHEMY
313 If you say yes to this option, support will be included for the
314 Au1550/Au1200/Au1300 SMBus interface.
316 This driver can also be built as a module. If so, the module
317 will be called i2c-au1550.
319 config I2C_BLACKFIN_TWI
320 tristate "Blackfin TWI I2C support"
322 depends on !BF561 && !BF531 && !BF532 && !BF533
324 This is the I2C bus driver for Blackfin on-chip TWI interface.
326 This driver can also be built as a module. If so, the module
327 will be called i2c-bfin-twi.
329 config I2C_BLACKFIN_TWI_CLK_KHZ
330 int "Blackfin TWI I2C clock (kHz)"
331 depends on I2C_BLACKFIN_TWI
335 The unit of the TWI clock is kHz.
338 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
339 depends on (CPM1 || CPM2) && OF_I2C
341 This supports the use of the I2C interface on Freescale
342 processors with CPM1 or CPM2.
344 This driver can also be built as a module. If so, the module
345 will be called i2c-cpm.
348 tristate "DaVinci I2C driver"
349 depends on ARCH_DAVINCI
351 Support for TI DaVinci I2C controller driver.
353 This driver can also be built as a module. If so, the module
354 will be called i2c-davinci.
356 Please note that this driver might be needed to bring up other
357 devices such as DaVinci NIC.
358 For details please see http://www.ti.com/davinci
360 config I2C_DESIGNWARE_PLATFORM
361 tristate "Synopsys DesignWare Platform"
364 If you say yes to this option, support will be included for the
365 Synopsys DesignWare I2C adapter. Only master mode is supported.
367 This driver can also be built as a module. If so, the module
368 will be called i2c-designware-platform.
370 config I2C_DESIGNWARE_PCI
371 tristate "Synopsys DesignWare PCI"
374 If you say yes to this option, support will be included for the
375 Synopsys DesignWare I2C adapter. Only master mode is supported.
377 This driver can also be built as a module. If so, the module
378 will be called i2c-designware-pci.
381 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
384 This driver is for PCH(Platform controller Hub) I2C of EG20T which
385 is an IOH(Input/Output Hub) for x86 embedded processor.
386 This driver can access PCH I2C bus device.
388 This driver also can be used for LAPIS Semiconductor IOH(Input/
389 Output Hub), ML7213, ML7223 and ML7831.
390 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
391 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
392 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
393 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
396 tristate "GPIO-based bitbanging I2C"
397 depends on GENERIC_GPIO
400 This is a very simple bitbanging I2C driver utilizing the
401 arch-neutral GPIO API to control the SCL and SDA lines.
403 config I2C_HIGHLANDER
404 tristate "Highlander FPGA SMBus interface"
405 depends on SH_HIGHLANDER
407 If you say yes to this option, support will be included for
408 the SMBus interface located in the FPGA on various Highlander
409 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
410 FPGAs. This is wholly unrelated to the SoC I2C.
412 This driver can also be built as a module. If so, the module
413 will be called i2c-highlander.
416 tristate "IBM PPC 4xx on-chip I2C interface"
419 Say Y here if you want to use IIC peripheral found on
420 embedded IBM PPC 4xx based systems.
422 This driver can also be built as a module. If so, the module
423 will be called i2c-ibm_iic.
426 tristate "IMX I2C interface"
429 Say Y here if you want to use the IIC bus controller on
430 the Freescale i.MX/MXC processors.
432 This driver can also be built as a module. If so, the module
433 will be called i2c-imx.
436 tristate "Intel Moorestown/Medfield Platform I2C controller"
439 Say Y here if you have an Intel Moorestown/Medfield platform I2C
442 This support is also available as a module. If so, the module
443 will be called i2c-intel-mid.
446 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
447 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
449 Say Y here if you want to use the IIC bus controller on
450 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
452 This driver can also be built as a module. If so, the module
453 will be called i2c-iop3xx.
456 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
459 If you say yes to this option, support will be included for the
460 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
461 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
463 This driver can also be built as a module. If so, the module
464 will be called i2c-mpc.
467 tristate "Marvell mv64xxx I2C Controller"
468 depends on (MV64X60 || PLAT_ORION)
470 If you say yes to this option, support will be included for the
471 built-in I2C interface on the Marvell 64xxx line of host bridges.
473 This driver can also be built as a module. If so, the module
474 will be called i2c-mv64xxx.
477 tristate "Freescale i.MX28 I2C interface"
481 Say Y here if you want to use the I2C bus controller on
482 the Freescale i.MX28 processors.
484 This driver can also be built as a module. If so, the module
485 will be called i2c-mxs.
488 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
491 If you say yes to this option, support will be included for the
492 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
493 as well as the STA2X11 PCIe I/O HUB.
496 tristate "NUC900 I2C Driver"
497 depends on ARCH_W90X900
499 Say Y here to include support for I2C controller in the
500 Winbond/Nuvoton NUC900 based System-on-Chip devices.
503 tristate "OpenCores I2C Controller"
504 depends on EXPERIMENTAL
506 If you say yes to this option, support will be included for the
507 OpenCores I2C controller. For details see
508 http://www.opencores.org/projects.cgi/web/i2c/overview
510 This driver can also be built as a module. If so, the module
511 will be called i2c-ocores.
514 tristate "OMAP I2C adapter"
516 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
518 If you say yes to this option, support will be included for the
519 I2C interface on the Texas Instruments OMAP1/2 family of processors.
520 Like OMAP1510/1610/1710/5912 and OMAP242x.
521 For details see http://www.ti.com/omap.
524 tristate "PA Semi SMBus interface"
525 depends on PPC_PASEMI && PCI
527 Supports the PA Semi PWRficient on-chip SMBus interfaces.
529 config I2C_PCA_PLATFORM
530 tristate "PCA9564/PCA9665 as platform device"
534 This driver supports a memory mapped Philips PCA9564/PCA9665
535 parallel bus to I2C bus controller.
537 This driver can also be built as a module. If so, the module
538 will be called i2c-pca-platform.
541 tristate "PMC MSP I2C TWI Controller"
544 This driver supports the PMC TWI controller on MSP devices.
546 This driver can also be built as module. If so, the module
547 will be called i2c-pmcmsp.
550 tristate "I2C bus support for Philips PNX and NXP LPC targets"
551 depends on ARCH_PNX4008 || ARCH_LPC32XX
553 This driver supports the Philips IP3204 I2C IP block master and/or
556 This driver can also be built as a module. If so, the module
557 will be called i2c-pnx.
560 tristate "PKUnity v3 I2C bus support"
561 depends on UNICORE32 && ARCH_PUV3
564 This driver supports the I2C IP inside the PKUnity-v3 SoC.
565 This I2C bus controller is under AMBA/AXI bus.
567 This driver can also be built as a module. If so, the module
568 will be called i2c-puv3.
571 tristate "Intel PXA2XX I2C adapter"
572 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
574 If you have devices in the PXA I2C bus, say yes to this option.
575 This driver can also be built as a module. If so, the module
576 will be called i2c-pxa.
579 def_bool I2C_PXA && X86_32 && PCI && OF
582 bool "Intel PXA2XX I2C Slave comms support"
583 depends on I2C_PXA && !X86_32
585 Support I2C slave mode communications on the PXA I2C bus. This
586 is necessary for systems where the PXA may be a target on the
589 config HAVE_S3C2410_I2C
592 This will include I2C support for Samsung SoCs. If you want to
593 include I2C support for any machine, kindly select this in the
594 respective Kconfig file.
597 tristate "S3C2410 I2C Driver"
598 depends on HAVE_S3C2410_I2C
600 Say Y here to include support for I2C controller in the
604 tristate "S6000 I2C support"
605 depends on XTENSA_VARIANT_S6000
607 This driver supports the on chip I2C device on the
608 S6000 xtensa processor family.
610 To compile this driver as a module, choose M here. The module
611 will be called i2c-s6000.
614 tristate "Renesas SH7760 I2C Controller"
615 depends on CPU_SUBTYPE_SH7760
617 This driver supports the 2 I2C interfaces on the Renesas SH7760.
619 This driver can also be built as a module. If so, the module
620 will be called i2c-sh7760.
623 tristate "SuperH Mobile I2C Controller"
624 depends on SUPERH || ARCH_SHMOBILE
626 If you say yes to this option, support will be included for the
627 built-in I2C interface on the Renesas SH-Mobile processor.
629 This driver can also be built as a module. If so, the module
630 will be called i2c-sh_mobile.
633 tristate "Simtec Generic I2C interface"
636 If you say yes to this option, support will be included for
637 the Simtec Generic I2C interface. This driver is for the
638 simple I2C bus used on newer Simtec products for general
639 I2C, such as DDC on the Simtec BBD2016A.
641 This driver can also be built as a module. If so, the module
642 will be called i2c-simtec.
645 tristate "CSR SiRFprimaII I2C interface"
646 depends on ARCH_PRIMA2
648 If you say yes to this option, support will be included for the
649 CSR SiRFprimaII I2C interface.
651 This driver can also be built as a module. If so, the module
652 will be called i2c-sirf.
655 tristate "ST Microelectronics DDC I2C interface"
657 default y if MACH_U300
659 If you say yes to this option, support will be included for the
660 I2C interface from ST Microelectronics simply called "DDC I2C"
661 supporting both I2C and DDC, used in e.g. the U300 series
664 This driver can also be built as a module. If so, the module
665 will be called i2c-stu300.
668 tristate "NVIDIA Tegra internal I2C controller"
669 depends on ARCH_TEGRA
671 If you say yes to this option, support will be included for the
672 I2C controller embedded in NVIDIA Tegra SOCs
675 tristate "ARM Versatile/Realview I2C bus support"
676 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
679 Say yes if you want to support the I2C serial bus on ARMs Versatile
682 This driver can also be built as a module. If so, the module
683 will be called i2c-versatile.
686 tristate "Cavium OCTEON I2C bus support"
687 depends on CPU_CAVIUM_OCTEON
689 Say yes if you want to support the I2C serial bus on Cavium
692 This driver can also be built as a module. If so, the module
693 will be called i2c-octeon.
696 tristate "Xilinx I2C Controller"
697 depends on EXPERIMENTAL && HAS_IOMEM
699 If you say yes to this option, support will be included for the
700 Xilinx I2C controller.
702 This driver can also be built as a module. If so, the module
703 will be called xilinx_i2c.
706 tristate "XLR I2C support"
709 This driver enables support for the on-chip I2C interface of
710 the Netlogic XLR/XLS MIPS processors.
712 This driver can also be built as a module. If so, the module
713 will be called i2c-xlr.
715 comment "External I2C/SMBus adapter drivers"
717 config I2C_DIOLAN_U2C
718 tristate "Diolan U2C-12 USB adapter"
721 If you say yes to this option, support will be included for Diolan
722 U2C-12, a USB to I2C interface.
724 This driver can also be built as a module. If so, the module
725 will be called i2c-diolan-u2c.
728 tristate "Parallel port adapter"
733 This supports parallel port I2C adapters such as the ones made by
734 Philips or Velleman, Analog Devices evaluation boards, and more.
735 Basically any adapter using the parallel port as an I2C bus with
736 no extra chipset is supported by this driver, or could be.
738 This driver is a replacement for (and was inspired by) an older
739 driver named i2c-philips-par. The new driver supports more devices,
740 and makes it easier to add support for new devices.
742 An adapter type parameter is now mandatory. Please read the file
743 Documentation/i2c/busses/i2c-parport for details.
745 Another driver exists, named i2c-parport-light, which doesn't depend
746 on the parport driver. This is meant for embedded systems. Don't say
747 Y here if you intend to say Y or M there.
749 This support is also available as a module. If so, the module
750 will be called i2c-parport.
752 config I2C_PARPORT_LIGHT
753 tristate "Parallel port adapter (light)"
757 This supports parallel port I2C adapters such as the ones made by
758 Philips or Velleman, Analog Devices evaluation boards, and more.
759 Basically any adapter using the parallel port as an I2C bus with
760 no extra chipset is supported by this driver, or could be.
762 This driver is a light version of i2c-parport. It doesn't depend
763 on the parport driver, and uses direct I/O access instead. This
764 might be preferred on embedded systems where wasting memory for
765 the clean but heavy parport handling is not an option. The
766 drawback is a reduced portability and the impossibility to
767 daisy-chain other parallel port devices.
769 Don't say Y here if you said Y or M to i2c-parport. Saying M to
770 both is possible but both modules should not be loaded at the same
773 This support is also available as a module. If so, the module
774 will be called i2c-parport-light.
777 tristate "TAOS evaluation module"
778 depends on EXPERIMENTAL
783 This supports TAOS evaluation modules on serial port. In order to
784 use this driver, you will need the inputattach tool, which is part
785 of the input-utils package.
789 This support is also available as a module. If so, the module
790 will be called i2c-taos-evm.
793 tristate "Tiny-USB adapter"
796 If you say yes to this option, support will be included for the
797 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
798 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
800 This driver can also be built as a module. If so, the module
801 will be called i2c-tiny-usb.
803 comment "Other I2C/SMBus bus drivers"
806 tristate "Acorn IOC/IOMD I2C bus support"
807 depends on ARCH_ACORN
811 Say yes if you want to support the I2C bus on Acorn platforms.
813 If you don't know, say Y.
816 tristate "Elektor ISA card"
817 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
820 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
823 This support is also available as a module. If so, the module
824 will be called i2c-elektor.
827 tristate "PCA9564/PCA9665 on an ISA bus"
832 This driver supports ISA boards using the Philips PCA9564/PCA9665
833 parallel bus to I2C bus controller.
835 This driver can also be built as a module. If so, the module
836 will be called i2c-pca-isa.
838 This device is almost undetectable and using this driver on a
839 system which doesn't have this device will result in long
840 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
841 time). If unsure, say N.
844 tristate "SiByte SMBus interface"
845 depends on SIBYTE_SB1xxx_SOC
847 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
850 tristate "I2C/SMBus Test Stub"
851 depends on EXPERIMENTAL && m
854 This module may be useful to developers of SMBus client drivers,
855 especially for certain kinds of sensor chips.
857 If you do build this module, be sure to read the notes and warnings
858 in <file:Documentation/i2c/i2c-stub>.
860 If you don't know what to do here, definitely say N.
863 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
864 depends on SCx200_GPIO
867 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
869 If you don't know what to do here, say N.
871 This support is also available as a module. If so, the module
872 will be called scx200_i2c.
874 This driver is deprecated and will be dropped soon. Use i2c-gpio
875 (or scx200_acb) instead.
877 config SCx200_I2C_SCL
878 int "GPIO pin used for SCL"
879 depends on SCx200_I2C
882 Enter the GPIO pin number used for the SCL signal. This value can
883 also be specified with a module parameter.
885 config SCx200_I2C_SDA
886 int "GPIO pin used for SDA"
887 depends on SCx200_I2C
890 Enter the GPIO pin number used for the SSA signal. This value can
891 also be specified with a module parameter.
894 tristate "Geode ACCESS.bus support"
895 depends on X86_32 && PCI
897 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
898 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
900 If you don't know what to do here, say N.
902 This support is also available as a module. If so, the module
903 will be called scx200_acb.