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)
107 This driver can also be built as a module. If so, the module
108 will be called i2c-i801.
111 tristate "Intel SCH SMBus 1.0"
115 Say Y here if you want to use SMBus controller on the Intel SCH
118 This driver can also be built as a module. If so, the module
119 will be called i2c-isch.
122 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
125 If you say yes to this option, support will be included for the Intel
126 PIIX4 family of mainboard I2C interfaces. Specifically, the following
127 versions of the chipset are supported (note that Serverworks is part
145 This driver can also be built as a module. If so, the module
146 will be called i2c-piix4.
149 tristate "Nvidia nForce2, nForce3 and nForce4"
152 If you say yes to this option, support will be included for the Nvidia
153 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
155 This driver can also be built as a module. If so, the module
156 will be called i2c-nforce2.
158 config I2C_NFORCE2_S4985
159 tristate "SMBus multiplexing on the Tyan S4985"
160 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
162 Enabling this option will add specific SMBus support for the Tyan
163 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
164 over 4 different channels, where the various memory module EEPROMs
165 live. Saying yes here will give you access to these in addition
168 This driver can also be built as a module. If so, the module
169 will be called i2c-nforce2-s4985.
175 If you say yes to this option, support will be included for the
176 SiS5595 SMBus (a subset of I2C) interface.
178 This driver can also be built as a module. If so, the module
179 will be called i2c-sis5595.
182 tristate "SiS 630/730"
185 If you say yes to this option, support will be included for the
186 SiS630 and SiS730 SMBus (a subset of I2C) interface.
188 This driver can also be built as a module. If so, the module
189 will be called i2c-sis630.
195 If you say yes to this option, support will be included for the SiS
196 96x SMBus (a subset of I2C) interfaces. Specifically, the following
197 chipsets are supported:
206 This driver can also be built as a module. If so, the module
207 will be called i2c-sis96x.
210 tristate "VIA VT82C586B"
211 depends on PCI && EXPERIMENTAL
214 If you say yes to this option, support will be included for the VIA
215 82C586B I2C interface
217 This driver can also be built as a module. If so, the module
218 will be called i2c-via.
221 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx"
224 If you say yes to this option, support will be included for the VIA
225 VT82C596 and later SMBus interface. Specifically, the following
226 chipsets are supported:
238 This driver can also be built as a module. If so, the module
239 will be called i2c-viapro.
243 comment "ACPI drivers"
246 tristate "SMBus Control Method Interface"
248 This driver supports the SMBus Control Method Interface. It needs the
249 BIOS to declare ACPI control methods as described in the SMBus Control
250 Method Interface specification.
252 To compile this driver as a module, choose M here:
253 the module will be called i2c-scmi.
257 comment "Mac SMBus host controller drivers"
258 depends on PPC_CHRP || PPC_PMAC
261 tristate "CHRP Apple Hydra Mac I/O I2C interface"
262 depends on PCI && PPC_CHRP && EXPERIMENTAL
265 This supports the use of the I2C interface in the Apple Hydra Mac
266 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
269 This support is also available as a module. If so, the module
270 will be called i2c-hydra.
273 tristate "Powermac I2C interface"
277 This exposes the various PowerMac i2c interfaces to the linux i2c
278 layer and to userland. It is used by various drivers on the PowerMac
279 platform, and should generally be enabled.
281 This support is also available as a module. If so, the module
282 will be called i2c-powermac.
284 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
287 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
288 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
290 This supports the use of the I2C interface on Atmel AT91
293 This driver is BROKEN because the controller which it uses
294 will easily trigger RX overrun and TX underrun errors. Using
295 low I2C clock rates may partially work around those issues
296 on some systems. Another serious problem is that there is no
297 documented way to issue repeated START conditions, as needed
298 to support combined I2C messages. Use the i2c-gpio driver
299 unless your system can cope with those limitations.
302 tristate "Au1550/Au1200 SMBus interface"
303 depends on SOC_AU1550 || SOC_AU1200
305 If you say yes to this option, support will be included for the
306 Au1550 and Au1200 SMBus interface.
308 This driver can also be built as a module. If so, the module
309 will be called i2c-au1550.
311 config I2C_BLACKFIN_TWI
312 tristate "Blackfin TWI I2C support"
314 depends on !BF561 && !BF531 && !BF532 && !BF533
316 This is the I2C bus driver for Blackfin on-chip TWI interface.
318 This driver can also be built as a module. If so, the module
319 will be called i2c-bfin-twi.
321 config I2C_BLACKFIN_TWI_CLK_KHZ
322 int "Blackfin TWI I2C clock (kHz)"
323 depends on I2C_BLACKFIN_TWI
327 The unit of the TWI clock is kHz.
330 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
331 depends on (CPM1 || CPM2) && OF_I2C
333 This supports the use of the I2C interface on Freescale
334 processors with CPM1 or CPM2.
336 This driver can also be built as a module. If so, the module
337 will be called i2c-cpm.
340 tristate "DaVinci I2C driver"
341 depends on ARCH_DAVINCI
343 Support for TI DaVinci I2C controller driver.
345 This driver can also be built as a module. If so, the module
346 will be called i2c-davinci.
348 Please note that this driver might be needed to bring up other
349 devices such as DaVinci NIC.
350 For details please see http://www.ti.com/davinci
352 config I2C_DESIGNWARE
353 tristate "Synopsys DesignWare"
356 If you say yes to this option, support will be included for the
357 Synopsys DesignWare I2C adapter. Only master mode is supported.
359 This driver can also be built as a module. If so, the module
360 will be called i2c-designware.
363 tristate "GPIO-based bitbanging I2C"
364 depends on GENERIC_GPIO
367 This is a very simple bitbanging I2C driver utilizing the
368 arch-neutral GPIO API to control the SCL and SDA lines.
370 config I2C_HIGHLANDER
371 tristate "Highlander FPGA SMBus interface"
372 depends on SH_HIGHLANDER
374 If you say yes to this option, support will be included for
375 the SMBus interface located in the FPGA on various Highlander
376 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
377 FPGAs. This is wholly unrelated to the SoC I2C.
379 This driver can also be built as a module. If so, the module
380 will be called i2c-highlander.
383 tristate "IBM PPC 4xx on-chip I2C interface"
386 Say Y here if you want to use IIC peripheral found on
387 embedded IBM PPC 4xx based systems.
389 This driver can also be built as a module. If so, the module
390 will be called i2c-ibm_iic.
393 tristate "IMX I2C interface"
396 Say Y here if you want to use the IIC bus controller on
397 the Freescale i.MX/MXC processors.
399 This driver can also be built as a module. If so, the module
400 will be called i2c-imx.
403 tristate "Intel Moorestown/Medfield Platform I2C controller"
406 Say Y here if you have an Intel Moorestown/Medfield platform I2C
409 This support is also available as a module. If so, the module
410 will be called i2c-intel-mid.
413 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
414 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
416 Say Y here if you want to use the IIC bus controller on
417 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
419 This driver can also be built as a module. If so, the module
420 will be called i2c-iop3xx.
423 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
424 depends on ARCH_IXP2000
427 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
428 system and are using GPIO lines for an I2C bus.
430 This support is also available as a module. If so, the module
431 will be called i2c-ixp2000.
433 This driver is deprecated and will be dropped soon. Use i2c-gpio
437 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
440 If you say yes to this option, support will be included for the
441 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
442 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
444 This driver can also be built as a module. If so, the module
445 will be called i2c-mpc.
448 tristate "Marvell mv64xxx I2C Controller"
449 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
451 If you say yes to this option, support will be included for the
452 built-in I2C interface on the Marvell 64xxx line of host bridges.
454 This driver can also be built as a module. If so, the module
455 will be called i2c-mv64xxx.
458 tristate "Freescale i.MX28 I2C interface"
461 Say Y here if you want to use the I2C bus controller on
462 the Freescale i.MX28 processors.
464 This driver can also be built as a module. If so, the module
465 will be called i2c-mxs.
468 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
469 depends on PLAT_NOMADIK
471 If you say yes to this option, support will be included for the
472 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures.
475 tristate "NUC900 I2C Driver"
476 depends on ARCH_W90X900
478 Say Y here to include support for I2C controller in the
479 Winbond/Nuvoton NUC900 based System-on-Chip devices.
482 tristate "OpenCores I2C Controller"
483 depends on EXPERIMENTAL
485 If you say yes to this option, support will be included for the
486 OpenCores I2C controller. For details see
487 http://www.opencores.org/projects.cgi/web/i2c/overview
489 This driver can also be built as a module. If so, the module
490 will be called i2c-ocores.
493 tristate "OMAP I2C adapter"
495 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
497 If you say yes to this option, support will be included for the
498 I2C interface on the Texas Instruments OMAP1/2 family of processors.
499 Like OMAP1510/1610/1710/5912 and OMAP242x.
500 For details see http://www.ti.com/omap.
503 tristate "PA Semi SMBus interface"
504 depends on PPC_PASEMI && PCI
506 Supports the PA Semi PWRficient on-chip SMBus interfaces.
508 config I2C_PCA_PLATFORM
509 tristate "PCA9564/PCA9665 as platform device"
513 This driver supports a memory mapped Philips PCA9564/PCA9665
514 parallel bus to I2C bus controller.
516 This driver can also be built as a module. If so, the module
517 will be called i2c-pca-platform.
520 tristate "PMC MSP I2C TWI Controller"
523 This driver supports the PMC TWI controller on MSP devices.
525 This driver can also be built as module. If so, the module
526 will be called i2c-pmcmsp.
529 tristate "I2C bus support for Philips PNX and NXP LPC targets"
530 depends on ARCH_PNX4008 || ARCH_LPC32XX
532 This driver supports the Philips IP3204 I2C IP block master and/or
535 This driver can also be built as a module. If so, the module
536 will be called i2c-pnx.
539 tristate "PKUnity v3 I2C bus support"
540 depends on UNICORE32 && ARCH_PUV3
543 This driver supports the I2C IP inside the PKUnity-v3 SoC.
544 This I2C bus controller is under AMBA/AXI bus.
546 This driver can also be built as a module. If so, the module
547 will be called i2c-puv3.
550 tristate "Intel PXA2XX I2C adapter"
551 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
553 If you have devices in the PXA I2C bus, say yes to this option.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-pxa.
558 def_bool I2C_PXA && X86_32 && PCI && OF
561 bool "Intel PXA2XX I2C Slave comms support"
562 depends on I2C_PXA && !X86_32
564 Support I2C slave mode communications on the PXA I2C bus. This
565 is necessary for systems where the PXA may be a target on the
568 config HAVE_S3C2410_I2C
571 This will include I2C support for Samsung SoCs. If you want to
572 include I2C support for any machine, kindly select this in the
573 respective Kconfig file.
576 tristate "S3C2410 I2C Driver"
577 depends on HAVE_S3C2410_I2C
579 Say Y here to include support for I2C controller in the
583 tristate "S6000 I2C support"
584 depends on XTENSA_VARIANT_S6000
586 This driver supports the on chip I2C device on the
587 S6000 xtensa processor family.
589 To compile this driver as a module, choose M here. The module
590 will be called i2c-s6000.
593 tristate "Renesas SH7760 I2C Controller"
594 depends on CPU_SUBTYPE_SH7760
596 This driver supports the 2 I2C interfaces on the Renesas SH7760.
598 This driver can also be built as a module. If so, the module
599 will be called i2c-sh7760.
602 tristate "SuperH Mobile I2C Controller"
603 depends on SUPERH || ARCH_SHMOBILE
605 If you say yes to this option, support will be included for the
606 built-in I2C interface on the Renesas SH-Mobile processor.
608 This driver can also be built as a module. If so, the module
609 will be called i2c-sh_mobile.
612 tristate "Simtec Generic I2C interface"
615 If you say yes to this option, support will be included for
616 the Simtec Generic I2C interface. This driver is for the
617 simple I2C bus used on newer Simtec products for general
618 I2C, such as DDC on the Simtec BBD2016A.
620 This driver can also be built as a module. If so, the module
621 will be called i2c-simtec.
624 tristate "ST Microelectronics DDC I2C interface"
626 default y if MACH_U300
628 If you say yes to this option, support will be included for the
629 I2C interface from ST Microelectronics simply called "DDC I2C"
630 supporting both I2C and DDC, used in e.g. the U300 series
633 This driver can also be built as a module. If so, the module
634 will be called i2c-stu300.
637 tristate "NVIDIA Tegra internal I2C controller"
638 depends on ARCH_TEGRA
640 If you say yes to this option, support will be included for the
641 I2C controller embedded in NVIDIA Tegra SOCs
644 tristate "ARM Versatile/Realview I2C bus support"
645 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
648 Say yes if you want to support the I2C serial bus on ARMs Versatile
651 This driver can also be built as a module. If so, the module
652 will be called i2c-versatile.
655 tristate "Cavium OCTEON I2C bus support"
656 depends on CPU_CAVIUM_OCTEON
658 Say yes if you want to support the I2C serial bus on Cavium
661 This driver can also be built as a module. If so, the module
662 will be called i2c-octeon.
665 tristate "Xilinx I2C Controller"
666 depends on EXPERIMENTAL && HAS_IOMEM
668 If you say yes to this option, support will be included for the
669 Xilinx I2C controller.
671 This driver can also be built as a module. If so, the module
672 will be called xilinx_i2c.
675 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)"
678 This driver is for PCH(Platform controller Hub) I2C of EG20T which
679 is an IOH(Input/Output Hub) for x86 embedded processor.
680 This driver can access PCH I2C bus device.
682 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
683 Output Hub), ML7213 and ML7223.
684 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is
685 for MP(Media Phone) use.
686 ML7213/ML7223 is companion chip for Intel Atom E6xx series.
687 ML7213/ML7223 is completely compatible for Intel EG20T PCH.
689 comment "External I2C/SMBus adapter drivers"
691 config I2C_DIOLAN_U2C
692 tristate "Diolan U2C-12 USB adapter"
695 If you say yes to this option, support will be included for Diolan
696 U2C-12, a USB to I2C interface.
698 This driver can also be built as a module. If so, the module
699 will be called i2c-diolan-u2c.
702 tristate "Parallel port adapter"
707 This supports parallel port I2C adapters such as the ones made by
708 Philips or Velleman, Analog Devices evaluation boards, and more.
709 Basically any adapter using the parallel port as an I2C bus with
710 no extra chipset is supported by this driver, or could be.
712 This driver is a replacement for (and was inspired by) an older
713 driver named i2c-philips-par. The new driver supports more devices,
714 and makes it easier to add support for new devices.
716 An adapter type parameter is now mandatory. Please read the file
717 Documentation/i2c/busses/i2c-parport for details.
719 Another driver exists, named i2c-parport-light, which doesn't depend
720 on the parport driver. This is meant for embedded systems. Don't say
721 Y here if you intend to say Y or M there.
723 This support is also available as a module. If so, the module
724 will be called i2c-parport.
726 config I2C_PARPORT_LIGHT
727 tristate "Parallel port adapter (light)"
731 This supports parallel port I2C adapters such as the ones made by
732 Philips or Velleman, Analog Devices evaluation boards, and more.
733 Basically any adapter using the parallel port as an I2C bus with
734 no extra chipset is supported by this driver, or could be.
736 This driver is a light version of i2c-parport. It doesn't depend
737 on the parport driver, and uses direct I/O access instead. This
738 might be preferred on embedded systems where wasting memory for
739 the clean but heavy parport handling is not an option. The
740 drawback is a reduced portability and the impossibility to
741 daisy-chain other parallel port devices.
743 Don't say Y here if you said Y or M to i2c-parport. Saying M to
744 both is possible but both modules should not be loaded at the same
747 This support is also available as a module. If so, the module
748 will be called i2c-parport-light.
751 tristate "TAOS evaluation module"
752 depends on EXPERIMENTAL
757 This supports TAOS evaluation modules on serial port. In order to
758 use this driver, you will need the inputattach tool, which is part
759 of the input-utils package.
763 This support is also available as a module. If so, the module
764 will be called i2c-taos-evm.
767 tristate "Tiny-USB adapter"
770 If you say yes to this option, support will be included for the
771 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
772 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
774 This driver can also be built as a module. If so, the module
775 will be called i2c-tiny-usb.
777 comment "Other I2C/SMBus bus drivers"
780 tristate "Acorn IOC/IOMD I2C bus support"
781 depends on ARCH_ACORN
785 Say yes if you want to support the I2C bus on Acorn platforms.
787 If you don't know, say Y.
790 tristate "Elektor ISA card"
791 depends on ISA && BROKEN_ON_SMP
794 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
797 This support is also available as a module. If so, the module
798 will be called i2c-elektor.
801 tristate "PCA9564/PCA9665 on an ISA bus"
806 This driver supports ISA boards using the Philips PCA9564/PCA9665
807 parallel bus to I2C bus controller.
809 This driver can also be built as a module. If so, the module
810 will be called i2c-pca-isa.
812 This device is almost undetectable and using this driver on a
813 system which doesn't have this device will result in long
814 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
815 time). If unsure, say N.
818 tristate "SiByte SMBus interface"
819 depends on SIBYTE_SB1xxx_SOC
821 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
824 tristate "I2C/SMBus Test Stub"
825 depends on EXPERIMENTAL && m
828 This module may be useful to developers of SMBus client drivers,
829 especially for certain kinds of sensor chips.
831 If you do build this module, be sure to read the notes and warnings
832 in <file:Documentation/i2c/i2c-stub>.
834 If you don't know what to do here, definitely say N.
837 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
838 depends on SCx200_GPIO
841 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
843 If you don't know what to do here, say N.
845 This support is also available as a module. If so, the module
846 will be called scx200_i2c.
848 This driver is deprecated and will be dropped soon. Use i2c-gpio
849 (or scx200_acb) instead.
851 config SCx200_I2C_SCL
852 int "GPIO pin used for SCL"
853 depends on SCx200_I2C
856 Enter the GPIO pin number used for the SCL signal. This value can
857 also be specified with a module parameter.
859 config SCx200_I2C_SDA
860 int "GPIO pin used for SDA"
861 depends on SCx200_I2C
864 Enter the GPIO pin number used for the SSA signal. This value can
865 also be specified with a module parameter.
868 tristate "Geode ACCESS.bus support"
869 depends on X86_32 && PCI
871 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
872 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
874 If you don't know what to do here, say N.
876 This support is also available as a module. If so, the module
877 will be called scx200_acb.