2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
8 comment "PC SMBus host controller drivers"
15 If you say yes to this option, support will be included for the SMB
16 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
17 controller is part of the 7101 device, which is an ACPI-compliant
18 Power Management Unit (PMU).
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
25 depends on PCI && EXPERIMENTAL
27 If you say yes to this option, support will be included for the SMB
28 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
29 controller is part of the 7101 device, which is an ACPI-compliant
30 Power Management Unit (PMU).
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
39 If you say yes to this option, support will be included for the
40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
46 tristate "AMD 756/766/768/8111 and nVidia nForce"
49 If you say yes to this option, support will be included for the AMD
50 756/766/768 mainboard I2C interfaces. The driver also includes
51 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
52 the nVidia nForce I2C interface.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
57 config I2C_AMD756_S4882
58 tristate "SMBus multiplexing on the Tyan S4882"
59 depends on I2C_AMD756 && X86 && EXPERIMENTAL
61 Enabling this option will add specific SMBus support for the Tyan
62 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
63 over 8 different channels, where the various memory module EEPROMs
64 and temperature sensors live. Saying yes here will give you access
65 to these in addition to the trunk.
67 This driver can also be built as a module. If so, the module
68 will be called i2c-amd756-s4882.
74 If you say yes to this option, support will be included for the
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
77 This driver can also be built as a module. If so, the module
78 will be called i2c-amd8111.
81 tristate "Intel 82801 (ICH/PCH)"
83 select CHECK_SIGNATURE if X86 && DMI
85 If you say yes to this option, support will be included for the Intel
86 801 family of mainboard I2C interfaces. Specifically, the following
87 versions of the chipset are supported:
93 82801EB/ER (ICH5/ICH5R)
110 This driver can also be built as a module. If so, the module
111 will be called i2c-i801.
114 tristate "Intel SCH SMBus 1.0"
118 Say Y here if you want to use SMBus controller on the Intel SCH
121 This driver can also be built as a module. If so, the module
122 will be called i2c-isch.
125 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
128 If you say yes to this option, support will be included for the Intel
129 PIIX4 family of mainboard I2C interfaces. Specifically, the following
130 versions of the chipset are supported (note that Serverworks is part
148 Some AMD chipsets contain two PIIX4-compatible SMBus
149 controllers. This driver will attempt to use both controllers
150 on the SB700/SP5100, if they have been initialized by the BIOS.
152 This driver can also be built as a module. If so, the module
153 will be called i2c-piix4.
156 tristate "Nvidia nForce2, nForce3 and nForce4"
159 If you say yes to this option, support will be included for the Nvidia
160 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
162 This driver can also be built as a module. If so, the module
163 will be called i2c-nforce2.
165 config I2C_NFORCE2_S4985
166 tristate "SMBus multiplexing on the Tyan S4985"
167 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
169 Enabling this option will add specific SMBus support for the Tyan
170 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
171 over 4 different channels, where the various memory module EEPROMs
172 live. Saying yes here will give you access to these in addition
175 This driver can also be built as a module. If so, the module
176 will be called i2c-nforce2-s4985.
182 If you say yes to this option, support will be included for the
183 SiS5595 SMBus (a subset of I2C) interface.
185 This driver can also be built as a module. If so, the module
186 will be called i2c-sis5595.
189 tristate "SiS 630/730"
192 If you say yes to this option, support will be included for the
193 SiS630 and SiS730 SMBus (a subset of I2C) interface.
195 This driver can also be built as a module. If so, the module
196 will be called i2c-sis630.
202 If you say yes to this option, support will be included for the SiS
203 96x SMBus (a subset of I2C) interfaces. Specifically, the following
204 chipsets are supported:
213 This driver can also be built as a module. If so, the module
214 will be called i2c-sis96x.
217 tristate "VIA VT82C586B"
218 depends on PCI && EXPERIMENTAL
221 If you say yes to this option, support will be included for the VIA
222 82C586B I2C interface
224 This driver can also be built as a module. If so, the module
225 will be called i2c-via.
228 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
231 If you say yes to this option, support will be included for the VIA
232 VT82C596 and later SMBus interface. Specifically, the following
233 chipsets are supported:
246 This driver can also be built as a module. If so, the module
247 will be called i2c-viapro.
251 comment "ACPI drivers"
254 tristate "SMBus Control Method Interface"
256 This driver supports the SMBus Control Method Interface. It needs the
257 BIOS to declare ACPI control methods as described in the SMBus Control
258 Method Interface specification.
260 To compile this driver as a module, choose M here:
261 the module will be called i2c-scmi.
265 comment "Mac SMBus host controller drivers"
266 depends on PPC_CHRP || PPC_PMAC
269 tristate "CHRP Apple Hydra Mac I/O I2C interface"
270 depends on PCI && PPC_CHRP && EXPERIMENTAL
273 This supports the use of the I2C interface in the Apple Hydra Mac
274 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
277 This support is also available as a module. If so, the module
278 will be called i2c-hydra.
281 tristate "Powermac I2C interface"
285 This exposes the various PowerMac i2c interfaces to the linux i2c
286 layer and to userland. It is used by various drivers on the PowerMac
287 platform, and should generally be enabled.
289 This support is also available as a module. If so, the module
290 will be called i2c-powermac.
292 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
295 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
296 depends on ARCH_AT91 && EXPERIMENTAL
298 This supports the use of the I2C interface on Atmel AT91
301 A serious problem is that there is no documented way to issue
302 repeated START conditions for more than two messages, as needed
303 to support combined I2C messages. Use the i2c-gpio driver
304 unless your system can cope with this limitation.
306 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
307 don't have clock stretching in transmission mode. For that reason,
308 you can encounter underrun issues causing premature stop sendings if
309 the latency to fill the transmission register is too long. If you
310 are facing this situation, use the i2c-gpio driver.
313 tristate "Au1550/Au1200/Au1300 SMBus interface"
314 depends on MIPS_ALCHEMY
316 If you say yes to this option, support will be included for the
317 Au1550/Au1200/Au1300 SMBus interface.
319 This driver can also be built as a module. If so, the module
320 will be called i2c-au1550.
322 config I2C_BLACKFIN_TWI
323 tristate "Blackfin TWI I2C support"
325 depends on !BF561 && !BF531 && !BF532 && !BF533
327 This is the I2C bus driver for Blackfin on-chip TWI interface.
329 This driver can also be built as a module. If so, the module
330 will be called i2c-bfin-twi.
332 config I2C_BLACKFIN_TWI_CLK_KHZ
333 int "Blackfin TWI I2C clock (kHz)"
334 depends on I2C_BLACKFIN_TWI
338 The unit of the TWI clock is kHz.
341 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
342 depends on (CPM1 || CPM2) && OF_I2C
344 This supports the use of the I2C interface on Freescale
345 processors with CPM1 or CPM2.
347 This driver can also be built as a module. If so, the module
348 will be called i2c-cpm.
351 tristate "DaVinci I2C driver"
352 depends on ARCH_DAVINCI
354 Support for TI DaVinci I2C controller driver.
356 This driver can also be built as a module. If so, the module
357 will be called i2c-davinci.
359 Please note that this driver might be needed to bring up other
360 devices such as DaVinci NIC.
361 For details please see http://www.ti.com/davinci
363 config I2C_DESIGNWARE_CORE
366 config I2C_DESIGNWARE_PLATFORM
367 tristate "Synopsys DesignWare Platform"
369 select I2C_DESIGNWARE_CORE
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-platform.
377 config I2C_DESIGNWARE_PCI
378 tristate "Synopsys DesignWare PCI"
380 select I2C_DESIGNWARE_CORE
382 If you say yes to this option, support will be included for the
383 Synopsys DesignWare I2C adapter. Only master mode is supported.
385 This driver can also be built as a module. If so, the module
386 will be called i2c-designware-pci.
389 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
392 This driver is for PCH(Platform controller Hub) I2C of EG20T which
393 is an IOH(Input/Output Hub) for x86 embedded processor.
394 This driver can access PCH I2C bus device.
396 This driver also can be used for LAPIS Semiconductor IOH(Input/
397 Output Hub), ML7213, ML7223 and ML7831.
398 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
399 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
400 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
401 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
404 tristate "GPIO-based bitbanging I2C"
405 depends on GENERIC_GPIO
408 This is a very simple bitbanging I2C driver utilizing the
409 arch-neutral GPIO API to control the SCL and SDA lines.
411 config I2C_HIGHLANDER
412 tristate "Highlander FPGA SMBus interface"
413 depends on SH_HIGHLANDER
415 If you say yes to this option, support will be included for
416 the SMBus interface located in the FPGA on various Highlander
417 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
418 FPGAs. This is wholly unrelated to the SoC I2C.
420 This driver can also be built as a module. If so, the module
421 will be called i2c-highlander.
424 tristate "IBM PPC 4xx on-chip I2C interface"
427 Say Y here if you want to use IIC peripheral found on
428 embedded IBM PPC 4xx based systems.
430 This driver can also be built as a module. If so, the module
431 will be called i2c-ibm_iic.
434 tristate "IMX I2C interface"
437 Say Y here if you want to use the IIC bus controller on
438 the Freescale i.MX/MXC processors.
440 This driver can also be built as a module. If so, the module
441 will be called i2c-imx.
444 tristate "Intel Moorestown/Medfield Platform I2C controller"
447 Say Y here if you have an Intel Moorestown/Medfield platform I2C
450 This support is also available as a module. If so, the module
451 will be called i2c-intel-mid.
454 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
455 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
457 Say Y here if you want to use the IIC bus controller on
458 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
460 This driver can also be built as a module. If so, the module
461 will be called i2c-iop3xx.
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)
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"
489 Say Y here if you want to use the I2C bus controller on
490 the Freescale i.MX28 processors.
492 This driver can also be built as a module. If so, the module
493 will be called i2c-mxs.
496 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
499 If you say yes to this option, support will be included for the
500 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
501 as well as the STA2X11 PCIe I/O HUB.
504 tristate "NUC900 I2C Driver"
505 depends on ARCH_W90X900
507 Say Y here to include support for I2C controller in the
508 Winbond/Nuvoton NUC900 based System-on-Chip devices.
511 tristate "OpenCores I2C Controller"
512 depends on EXPERIMENTAL
514 If you say yes to this option, support will be included for the
515 OpenCores I2C controller. For details see
516 http://www.opencores.org/projects.cgi/web/i2c/overview
518 This driver can also be built as a module. If so, the module
519 will be called i2c-ocores.
522 tristate "OMAP I2C adapter"
524 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
526 If you say yes to this option, support will be included for the
527 I2C interface on the Texas Instruments OMAP1/2 family of processors.
528 Like OMAP1510/1610/1710/5912 and OMAP242x.
529 For details see http://www.ti.com/omap.
532 tristate "PA Semi SMBus interface"
533 depends on PPC_PASEMI && PCI
535 Supports the PA Semi PWRficient on-chip SMBus interfaces.
537 config I2C_PCA_PLATFORM
538 tristate "PCA9564/PCA9665 as platform device"
542 This driver supports a memory mapped Philips PCA9564/PCA9665
543 parallel bus to I2C bus controller.
545 This driver can also be built as a module. If so, the module
546 will be called i2c-pca-platform.
549 tristate "PMC MSP I2C TWI Controller"
552 This driver supports the PMC TWI controller on MSP devices.
554 This driver can also be built as module. If so, the module
555 will be called i2c-pmcmsp.
558 tristate "I2C bus support for Philips PNX and NXP LPC targets"
559 depends on ARCH_LPC32XX
561 This driver supports the Philips IP3204 I2C IP block master and/or
564 This driver can also be built as a module. If so, the module
565 will be called i2c-pnx.
568 tristate "PKUnity v3 I2C bus support"
569 depends on UNICORE32 && ARCH_PUV3
572 This driver supports the I2C IP inside the PKUnity-v3 SoC.
573 This I2C bus controller is under AMBA/AXI bus.
575 This driver can also be built as a module. If so, the module
576 will be called i2c-puv3.
579 tristate "Intel PXA2XX I2C adapter"
580 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
582 If you have devices in the PXA I2C bus, say yes to this option.
583 This driver can also be built as a module. If so, the module
584 will be called i2c-pxa.
587 def_bool I2C_PXA && X86_32 && PCI && OF
590 bool "Intel PXA2XX I2C Slave comms support"
591 depends on I2C_PXA && !X86_32
593 Support I2C slave mode communications on the PXA I2C bus. This
594 is necessary for systems where the PXA may be a target on the
597 config HAVE_S3C2410_I2C
600 This will include I2C support for Samsung SoCs. If you want to
601 include I2C support for any machine, kindly select this in the
602 respective Kconfig file.
605 tristate "S3C2410 I2C Driver"
606 depends on HAVE_S3C2410_I2C
608 Say Y here to include support for I2C controller in the
612 tristate "S6000 I2C support"
613 depends on XTENSA_VARIANT_S6000
615 This driver supports the on chip I2C device on the
616 S6000 xtensa processor family.
618 To compile this driver as a module, choose M here. The module
619 will be called i2c-s6000.
622 tristate "Renesas SH7760 I2C Controller"
623 depends on CPU_SUBTYPE_SH7760
625 This driver supports the 2 I2C interfaces on the Renesas SH7760.
627 This driver can also be built as a module. If so, the module
628 will be called i2c-sh7760.
631 tristate "SuperH Mobile I2C Controller"
632 depends on SUPERH || ARCH_SHMOBILE
634 If you say yes to this option, support will be included for the
635 built-in I2C interface on the Renesas SH-Mobile processor.
637 This driver can also be built as a module. If so, the module
638 will be called i2c-sh_mobile.
641 tristate "Simtec Generic I2C interface"
644 If you say yes to this option, support will be included for
645 the Simtec Generic I2C interface. This driver is for the
646 simple I2C bus used on newer Simtec products for general
647 I2C, such as DDC on the Simtec BBD2016A.
649 This driver can also be built as a module. If so, the module
650 will be called i2c-simtec.
653 tristate "CSR SiRFprimaII I2C interface"
654 depends on ARCH_PRIMA2
656 If you say yes to this option, support will be included for the
657 CSR SiRFprimaII I2C interface.
659 This driver can also be built as a module. If so, the module
660 will be called i2c-sirf.
663 tristate "ST Microelectronics DDC I2C interface"
665 default y if MACH_U300
667 If you say yes to this option, support will be included for the
668 I2C interface from ST Microelectronics simply called "DDC I2C"
669 supporting both I2C and DDC, used in e.g. the U300 series
672 This driver can also be built as a module. If so, the module
673 will be called i2c-stu300.
676 tristate "NVIDIA Tegra internal I2C controller"
677 depends on ARCH_TEGRA
679 If you say yes to this option, support will be included for the
680 I2C controller embedded in NVIDIA Tegra SOCs
683 tristate "ARM Versatile/Realview I2C bus support"
684 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
687 Say yes if you want to support the I2C serial bus on ARMs Versatile
690 This driver can also be built as a module. If so, the module
691 will be called i2c-versatile.
694 tristate "Cavium OCTEON I2C bus support"
695 depends on CPU_CAVIUM_OCTEON
697 Say yes if you want to support the I2C serial bus on Cavium
700 This driver can also be built as a module. If so, the module
701 will be called i2c-octeon.
704 tristate "Xilinx I2C Controller"
705 depends on EXPERIMENTAL && HAS_IOMEM
707 If you say yes to this option, support will be included for the
708 Xilinx I2C controller.
710 This driver can also be built as a module. If so, the module
711 will be called xilinx_i2c.
714 tristate "XLR I2C support"
717 This driver enables support for the on-chip I2C interface of
718 the Netlogic XLR/XLS MIPS processors.
720 This driver can also be built as a module. If so, the module
721 will be called i2c-xlr.
724 tristate "Renesas R-Car I2C Controller"
725 depends on ARCH_SHMOBILE && I2C
727 If you say yes to this option, support will be included for the
728 R-Car I2C controller.
730 This driver can also be built as a module. If so, the module
731 will be called i2c-rcar.
733 comment "External I2C/SMBus adapter drivers"
735 config I2C_DIOLAN_U2C
736 tristate "Diolan U2C-12 USB adapter"
739 If you say yes to this option, support will be included for Diolan
740 U2C-12, a USB to I2C interface.
742 This driver can also be built as a module. If so, the module
743 will be called i2c-diolan-u2c.
746 tristate "Parallel port adapter"
751 This supports parallel port I2C adapters such as the ones made by
752 Philips or Velleman, Analog Devices evaluation boards, and more.
753 Basically any adapter using the parallel port as an I2C bus with
754 no extra chipset is supported by this driver, or could be.
756 This driver is a replacement for (and was inspired by) an older
757 driver named i2c-philips-par. The new driver supports more devices,
758 and makes it easier to add support for new devices.
760 An adapter type parameter is now mandatory. Please read the file
761 Documentation/i2c/busses/i2c-parport for details.
763 Another driver exists, named i2c-parport-light, which doesn't depend
764 on the parport driver. This is meant for embedded systems. Don't say
765 Y here if you intend to say Y or M there.
767 This support is also available as a module. If so, the module
768 will be called i2c-parport.
770 config I2C_PARPORT_LIGHT
771 tristate "Parallel port adapter (light)"
775 This supports parallel port I2C adapters such as the ones made by
776 Philips or Velleman, Analog Devices evaluation boards, and more.
777 Basically any adapter using the parallel port as an I2C bus with
778 no extra chipset is supported by this driver, or could be.
780 This driver is a light version of i2c-parport. It doesn't depend
781 on the parport driver, and uses direct I/O access instead. This
782 might be preferred on embedded systems where wasting memory for
783 the clean but heavy parport handling is not an option. The
784 drawback is a reduced portability and the impossibility to
785 daisy-chain other parallel port devices.
787 Don't say Y here if you said Y or M to i2c-parport. Saying M to
788 both is possible but both modules should not be loaded at the same
791 This support is also available as a module. If so, the module
792 will be called i2c-parport-light.
795 tristate "TAOS evaluation module"
796 depends on EXPERIMENTAL
801 This supports TAOS evaluation modules on serial port. In order to
802 use this driver, you will need the inputattach tool, which is part
803 of the input-utils package.
807 This support is also available as a module. If so, the module
808 will be called i2c-taos-evm.
811 tristate "Tiny-USB adapter"
814 If you say yes to this option, support will be included for the
815 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
816 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
818 This driver can also be built as a module. If so, the module
819 will be called i2c-tiny-usb.
821 comment "Other I2C/SMBus bus drivers"
824 tristate "Acorn IOC/IOMD I2C bus support"
825 depends on ARCH_ACORN
829 Say yes if you want to support the I2C bus on Acorn platforms.
831 If you don't know, say Y.
834 tristate "Elektor ISA card"
835 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
838 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
841 This support is also available as a module. If so, the module
842 will be called i2c-elektor.
845 tristate "PCA9564/PCA9665 on an ISA bus"
850 This driver supports ISA boards using the Philips PCA9564/PCA9665
851 parallel bus to I2C bus controller.
853 This driver can also be built as a module. If so, the module
854 will be called i2c-pca-isa.
856 This device is almost undetectable and using this driver on a
857 system which doesn't have this device will result in long
858 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
859 time). If unsure, say N.
862 tristate "SiByte SMBus interface"
863 depends on SIBYTE_SB1xxx_SOC
865 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
868 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
869 depends on SCx200_GPIO
872 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
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_i2c.
879 This driver is deprecated and will be dropped soon. Use i2c-gpio
880 (or scx200_acb) instead.
882 config SCx200_I2C_SCL
883 int "GPIO pin used for SCL"
884 depends on SCx200_I2C
887 Enter the GPIO pin number used for the SCL signal. This value can
888 also be specified with a module parameter.
890 config SCx200_I2C_SDA
891 int "GPIO pin used for SDA"
892 depends on SCx200_I2C
895 Enter the GPIO pin number used for the SSA signal. This value can
896 also be specified with a module parameter.
899 tristate "Geode ACCESS.bus support"
900 depends on X86_32 && PCI
902 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
903 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
905 If you don't know what to do here, say N.
907 This support is also available as a module. If so, the module
908 will be called scx200_acb.