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
84 select GPIOLIB if I2C_MUX
86 If you say yes to this option, support will be included for the Intel
87 801 family of mainboard I2C interfaces. Specifically, the following
88 versions of the chipset are supported:
94 82801EB/ER (ICH5/ICH5R)
111 This driver can also be built as a module. If so, the module
112 will be called i2c-i801.
115 tristate "Intel SCH SMBus 1.0"
119 Say Y here if you want to use SMBus controller on the Intel SCH
122 This driver can also be built as a module. If so, the module
123 will be called i2c-isch.
126 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
129 If you say yes to this option, support will be included for the Intel
130 PIIX4 family of mainboard I2C interfaces. Specifically, the following
131 versions of the chipset are supported (note that Serverworks is part
149 Some AMD chipsets contain two PIIX4-compatible SMBus
150 controllers. This driver will attempt to use both controllers
151 on the SB700/SP5100, if they have been initialized by the BIOS.
153 This driver can also be built as a module. If so, the module
154 will be called i2c-piix4.
157 tristate "Nvidia nForce2, nForce3 and nForce4"
160 If you say yes to this option, support will be included for the Nvidia
161 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
163 This driver can also be built as a module. If so, the module
164 will be called i2c-nforce2.
166 config I2C_NFORCE2_S4985
167 tristate "SMBus multiplexing on the Tyan S4985"
168 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL
170 Enabling this option will add specific SMBus support for the Tyan
171 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
172 over 4 different channels, where the various memory module EEPROMs
173 live. Saying yes here will give you access to these in addition
176 This driver can also be built as a module. If so, the module
177 will be called i2c-nforce2-s4985.
183 If you say yes to this option, support will be included for the
184 SiS5595 SMBus (a subset of I2C) interface.
186 This driver can also be built as a module. If so, the module
187 will be called i2c-sis5595.
190 tristate "SiS 630/730"
193 If you say yes to this option, support will be included for the
194 SiS630 and SiS730 SMBus (a subset of I2C) interface.
196 This driver can also be built as a module. If so, the module
197 will be called i2c-sis630.
203 If you say yes to this option, support will be included for the SiS
204 96x SMBus (a subset of I2C) interfaces. Specifically, the following
205 chipsets are supported:
214 This driver can also be built as a module. If so, the module
215 will be called i2c-sis96x.
218 tristate "VIA VT82C586B"
219 depends on PCI && EXPERIMENTAL
222 If you say yes to this option, support will be included for the VIA
223 82C586B I2C interface
225 This driver can also be built as a module. If so, the module
226 will be called i2c-via.
229 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
232 If you say yes to this option, support will be included for the VIA
233 VT82C596 and later SMBus interface. Specifically, the following
234 chipsets are supported:
247 This driver can also be built as a module. If so, the module
248 will be called i2c-viapro.
252 comment "ACPI drivers"
255 tristate "SMBus Control Method Interface"
257 This driver supports the SMBus Control Method Interface. It needs the
258 BIOS to declare ACPI control methods as described in the SMBus Control
259 Method Interface specification.
261 To compile this driver as a module, choose M here:
262 the module will be called i2c-scmi.
266 comment "Mac SMBus host controller drivers"
267 depends on PPC_CHRP || PPC_PMAC
270 tristate "CHRP Apple Hydra Mac I/O I2C interface"
271 depends on PCI && PPC_CHRP && EXPERIMENTAL
274 This supports the use of the I2C interface in the Apple Hydra Mac
275 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
278 This support is also available as a module. If so, the module
279 will be called i2c-hydra.
282 tristate "Powermac I2C interface"
286 This exposes the various PowerMac i2c interfaces to the linux i2c
287 layer and to userland. It is used by various drivers on the PowerMac
288 platform, and should generally be enabled.
290 This support is also available as a module. If so, the module
291 will be called i2c-powermac.
293 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
296 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
297 depends on ARCH_AT91 && EXPERIMENTAL
299 This supports the use of the I2C interface on Atmel AT91
302 A serious problem is that there is no documented way to issue
303 repeated START conditions for more than two messages, as needed
304 to support combined I2C messages. Use the i2c-gpio driver
305 unless your system can cope with this limitation.
307 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
308 don't have clock stretching in transmission mode. For that reason,
309 you can encounter underrun issues causing premature stop sendings if
310 the latency to fill the transmission register is too long. If you
311 are facing this situation, use the i2c-gpio driver.
314 tristate "Au1550/Au1200/Au1300 SMBus interface"
315 depends on MIPS_ALCHEMY
317 If you say yes to this option, support will be included for the
318 Au1550/Au1200/Au1300 SMBus interface.
320 This driver can also be built as a module. If so, the module
321 will be called i2c-au1550.
323 config I2C_BLACKFIN_TWI
324 tristate "Blackfin TWI I2C support"
326 depends on !BF561 && !BF531 && !BF532 && !BF533
328 This is the I2C bus driver for Blackfin on-chip TWI interface.
330 This driver can also be built as a module. If so, the module
331 will be called i2c-bfin-twi.
333 config I2C_BLACKFIN_TWI_CLK_KHZ
334 int "Blackfin TWI I2C clock (kHz)"
335 depends on I2C_BLACKFIN_TWI
339 The unit of the TWI clock is kHz.
342 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
343 depends on (CPM1 || CPM2) && OF_I2C
345 This supports the use of the I2C interface on Freescale
346 processors with CPM1 or CPM2.
348 This driver can also be built as a module. If so, the module
349 will be called i2c-cpm.
352 tristate "DaVinci I2C driver"
353 depends on ARCH_DAVINCI
355 Support for TI DaVinci I2C controller driver.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-davinci.
360 Please note that this driver might be needed to bring up other
361 devices such as DaVinci NIC.
362 For details please see http://www.ti.com/davinci
364 config I2C_DESIGNWARE_CORE
367 config I2C_DESIGNWARE_PLATFORM
368 tristate "Synopsys DesignWare Platform"
370 select I2C_DESIGNWARE_CORE
372 If you say yes to this option, support will be included for the
373 Synopsys DesignWare I2C adapter. Only master mode is supported.
375 This driver can also be built as a module. If so, the module
376 will be called i2c-designware-platform.
378 config I2C_DESIGNWARE_PCI
379 tristate "Synopsys DesignWare PCI"
381 select I2C_DESIGNWARE_CORE
383 If you say yes to this option, support will be included for the
384 Synopsys DesignWare I2C adapter. Only master mode is supported.
386 This driver can also be built as a module. If so, the module
387 will be called i2c-designware-pci.
390 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
393 This driver is for PCH(Platform controller Hub) I2C of EG20T which
394 is an IOH(Input/Output Hub) for x86 embedded processor.
395 This driver can access PCH I2C bus device.
397 This driver also can be used for LAPIS Semiconductor IOH(Input/
398 Output Hub), ML7213, ML7223 and ML7831.
399 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
400 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
401 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
402 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
405 tristate "GPIO-based bitbanging I2C"
406 depends on GENERIC_GPIO
409 This is a very simple bitbanging I2C driver utilizing the
410 arch-neutral GPIO API to control the SCL and SDA lines.
412 config I2C_HIGHLANDER
413 tristate "Highlander FPGA SMBus interface"
414 depends on SH_HIGHLANDER
416 If you say yes to this option, support will be included for
417 the SMBus interface located in the FPGA on various Highlander
418 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
419 FPGAs. This is wholly unrelated to the SoC I2C.
421 This driver can also be built as a module. If so, the module
422 will be called i2c-highlander.
425 tristate "IBM PPC 4xx on-chip I2C interface"
428 Say Y here if you want to use IIC peripheral found on
429 embedded IBM PPC 4xx based systems.
431 This driver can also be built as a module. If so, the module
432 will be called i2c-ibm_iic.
435 tristate "IMX I2C interface"
438 Say Y here if you want to use the IIC bus controller on
439 the Freescale i.MX/MXC processors.
441 This driver can also be built as a module. If so, the module
442 will be called i2c-imx.
445 tristate "Intel Moorestown/Medfield Platform I2C controller"
448 Say Y here if you have an Intel Moorestown/Medfield platform I2C
451 This support is also available as a module. If so, the module
452 will be called i2c-intel-mid.
455 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
456 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
458 Say Y here if you want to use the IIC bus controller on
459 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
461 This driver can also be built as a module. If so, the module
462 will be called i2c-iop3xx.
465 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
468 If you say yes to this option, support will be included for the
469 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
470 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
472 This driver can also be built as a module. If so, the module
473 will be called i2c-mpc.
476 tristate "Marvell mv64xxx I2C Controller"
477 depends on (MV64X60 || PLAT_ORION)
479 If you say yes to this option, support will be included for the
480 built-in I2C interface on the Marvell 64xxx line of host bridges.
482 This driver can also be built as a module. If so, the module
483 will be called i2c-mv64xxx.
486 tristate "Freescale i.MX28 I2C interface"
490 Say Y here if you want to use the I2C bus controller on
491 the Freescale i.MX28 processors.
493 This driver can also be built as a module. If so, the module
494 will be called i2c-mxs.
497 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
500 If you say yes to this option, support will be included for the
501 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
502 as well as the STA2X11 PCIe I/O HUB.
505 tristate "NUC900 I2C Driver"
506 depends on ARCH_W90X900
508 Say Y here to include support for I2C controller in the
509 Winbond/Nuvoton NUC900 based System-on-Chip devices.
512 tristate "OpenCores I2C Controller"
513 depends on EXPERIMENTAL
515 If you say yes to this option, support will be included for the
516 OpenCores I2C controller. For details see
517 http://www.opencores.org/projects.cgi/web/i2c/overview
519 This driver can also be built as a module. If so, the module
520 will be called i2c-ocores.
523 tristate "OMAP I2C adapter"
525 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
527 If you say yes to this option, support will be included for the
528 I2C interface on the Texas Instruments OMAP1/2 family of processors.
529 Like OMAP1510/1610/1710/5912 and OMAP242x.
530 For details see http://www.ti.com/omap.
533 tristate "PA Semi SMBus interface"
534 depends on PPC_PASEMI && PCI
536 Supports the PA Semi PWRficient on-chip SMBus interfaces.
538 config I2C_PCA_PLATFORM
539 tristate "PCA9564/PCA9665 as platform device"
543 This driver supports a memory mapped Philips PCA9564/PCA9665
544 parallel bus to I2C bus controller.
546 This driver can also be built as a module. If so, the module
547 will be called i2c-pca-platform.
550 tristate "PMC MSP I2C TWI Controller"
553 This driver supports the PMC TWI controller on MSP devices.
555 This driver can also be built as module. If so, the module
556 will be called i2c-pmcmsp.
559 tristate "I2C bus support for Philips PNX and NXP LPC targets"
560 depends on ARCH_LPC32XX
562 This driver supports the Philips IP3204 I2C IP block master and/or
565 This driver can also be built as a module. If so, the module
566 will be called i2c-pnx.
569 tristate "PKUnity v3 I2C bus support"
570 depends on UNICORE32 && ARCH_PUV3
573 This driver supports the I2C IP inside the PKUnity-v3 SoC.
574 This I2C bus controller is under AMBA/AXI bus.
576 This driver can also be built as a module. If so, the module
577 will be called i2c-puv3.
580 tristate "Intel PXA2XX I2C adapter"
581 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
583 If you have devices in the PXA I2C bus, say yes to this option.
584 This driver can also be built as a module. If so, the module
585 will be called i2c-pxa.
588 def_bool I2C_PXA && X86_32 && PCI && OF
591 bool "Intel PXA2XX I2C Slave comms support"
592 depends on I2C_PXA && !X86_32
594 Support I2C slave mode communications on the PXA I2C bus. This
595 is necessary for systems where the PXA may be a target on the
598 config HAVE_S3C2410_I2C
601 This will include I2C support for Samsung SoCs. If you want to
602 include I2C support for any machine, kindly select this in the
603 respective Kconfig file.
606 tristate "S3C2410 I2C Driver"
607 depends on HAVE_S3C2410_I2C
609 Say Y here to include support for I2C controller in the
613 tristate "S6000 I2C support"
614 depends on XTENSA_VARIANT_S6000
616 This driver supports the on chip I2C device on the
617 S6000 xtensa processor family.
619 To compile this driver as a module, choose M here. The module
620 will be called i2c-s6000.
623 tristate "Renesas SH7760 I2C Controller"
624 depends on CPU_SUBTYPE_SH7760
626 This driver supports the 2 I2C interfaces on the Renesas SH7760.
628 This driver can also be built as a module. If so, the module
629 will be called i2c-sh7760.
632 tristate "SuperH Mobile I2C Controller"
633 depends on SUPERH || ARCH_SHMOBILE
635 If you say yes to this option, support will be included for the
636 built-in I2C interface on the Renesas SH-Mobile processor.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-sh_mobile.
642 tristate "Simtec Generic I2C interface"
645 If you say yes to this option, support will be included for
646 the Simtec Generic I2C interface. This driver is for the
647 simple I2C bus used on newer Simtec products for general
648 I2C, such as DDC on the Simtec BBD2016A.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-simtec.
654 tristate "CSR SiRFprimaII I2C interface"
655 depends on ARCH_PRIMA2
657 If you say yes to this option, support will be included for the
658 CSR SiRFprimaII I2C interface.
660 This driver can also be built as a module. If so, the module
661 will be called i2c-sirf.
664 tristate "ST Microelectronics DDC I2C interface"
666 default y if MACH_U300
668 If you say yes to this option, support will be included for the
669 I2C interface from ST Microelectronics simply called "DDC I2C"
670 supporting both I2C and DDC, used in e.g. the U300 series
673 This driver can also be built as a module. If so, the module
674 will be called i2c-stu300.
677 tristate "NVIDIA Tegra internal I2C controller"
678 depends on ARCH_TEGRA
680 If you say yes to this option, support will be included for the
681 I2C controller embedded in NVIDIA Tegra SOCs
684 tristate "ARM Versatile/Realview I2C bus support"
685 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
688 Say yes if you want to support the I2C serial bus on ARMs Versatile
691 This driver can also be built as a module. If so, the module
692 will be called i2c-versatile.
695 tristate "Cavium OCTEON I2C bus support"
696 depends on CPU_CAVIUM_OCTEON
698 Say yes if you want to support the I2C serial bus on Cavium
701 This driver can also be built as a module. If so, the module
702 will be called i2c-octeon.
705 tristate "Xilinx I2C Controller"
706 depends on EXPERIMENTAL && HAS_IOMEM
708 If you say yes to this option, support will be included for the
709 Xilinx I2C controller.
711 This driver can also be built as a module. If so, the module
712 will be called xilinx_i2c.
715 tristate "XLR I2C support"
718 This driver enables support for the on-chip I2C interface of
719 the Netlogic XLR/XLS MIPS processors.
721 This driver can also be built as a module. If so, the module
722 will be called i2c-xlr.
725 tristate "Renesas R-Car I2C Controller"
726 depends on ARCH_SHMOBILE && I2C
728 If you say yes to this option, support will be included for the
729 R-Car I2C controller.
731 This driver can also be built as a module. If so, the module
732 will be called i2c-rcar.
734 comment "External I2C/SMBus adapter drivers"
736 config I2C_DIOLAN_U2C
737 tristate "Diolan U2C-12 USB adapter"
740 If you say yes to this option, support will be included for Diolan
741 U2C-12, a USB to I2C interface.
743 This driver can also be built as a module. If so, the module
744 will be called i2c-diolan-u2c.
747 tristate "Parallel port adapter"
752 This supports parallel port I2C adapters such as the ones made by
753 Philips or Velleman, Analog Devices evaluation boards, and more.
754 Basically any adapter using the parallel port as an I2C bus with
755 no extra chipset is supported by this driver, or could be.
757 This driver is a replacement for (and was inspired by) an older
758 driver named i2c-philips-par. The new driver supports more devices,
759 and makes it easier to add support for new devices.
761 An adapter type parameter is now mandatory. Please read the file
762 Documentation/i2c/busses/i2c-parport for details.
764 Another driver exists, named i2c-parport-light, which doesn't depend
765 on the parport driver. This is meant for embedded systems. Don't say
766 Y here if you intend to say Y or M there.
768 This support is also available as a module. If so, the module
769 will be called i2c-parport.
771 config I2C_PARPORT_LIGHT
772 tristate "Parallel port adapter (light)"
776 This supports parallel port I2C adapters such as the ones made by
777 Philips or Velleman, Analog Devices evaluation boards, and more.
778 Basically any adapter using the parallel port as an I2C bus with
779 no extra chipset is supported by this driver, or could be.
781 This driver is a light version of i2c-parport. It doesn't depend
782 on the parport driver, and uses direct I/O access instead. This
783 might be preferred on embedded systems where wasting memory for
784 the clean but heavy parport handling is not an option. The
785 drawback is a reduced portability and the impossibility to
786 daisy-chain other parallel port devices.
788 Don't say Y here if you said Y or M to i2c-parport. Saying M to
789 both is possible but both modules should not be loaded at the same
792 This support is also available as a module. If so, the module
793 will be called i2c-parport-light.
796 tristate "TAOS evaluation module"
797 depends on EXPERIMENTAL
802 This supports TAOS evaluation modules on serial port. In order to
803 use this driver, you will need the inputattach tool, which is part
804 of the input-utils package.
808 This support is also available as a module. If so, the module
809 will be called i2c-taos-evm.
812 tristate "Tiny-USB adapter"
815 If you say yes to this option, support will be included for the
816 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
817 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
819 This driver can also be built as a module. If so, the module
820 will be called i2c-tiny-usb.
822 comment "Other I2C/SMBus bus drivers"
825 tristate "Acorn IOC/IOMD I2C bus support"
826 depends on ARCH_ACORN
830 Say yes if you want to support the I2C bus on Acorn platforms.
832 If you don't know, say Y.
835 tristate "Elektor ISA card"
836 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
839 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
842 This support is also available as a module. If so, the module
843 will be called i2c-elektor.
846 tristate "PCA9564/PCA9665 on an ISA bus"
851 This driver supports ISA boards using the Philips PCA9564/PCA9665
852 parallel bus to I2C bus controller.
854 This driver can also be built as a module. If so, the module
855 will be called i2c-pca-isa.
857 This device is almost undetectable and using this driver on a
858 system which doesn't have this device will result in long
859 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
860 time). If unsure, say N.
863 tristate "SiByte SMBus interface"
864 depends on SIBYTE_SB1xxx_SOC
866 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
869 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
870 depends on SCx200_GPIO
873 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
875 If you don't know what to do here, say N.
877 This support is also available as a module. If so, the module
878 will be called scx200_i2c.
880 This driver is deprecated and will be dropped soon. Use i2c-gpio
881 (or scx200_acb) instead.
883 config SCx200_I2C_SCL
884 int "GPIO pin used for SCL"
885 depends on SCx200_I2C
888 Enter the GPIO pin number used for the SCL signal. This value can
889 also be specified with a module parameter.
891 config SCx200_I2C_SDA
892 int "GPIO pin used for SDA"
893 depends on SCx200_I2C
896 Enter the GPIO pin number used for the SSA signal. This value can
897 also be specified with a module parameter.
900 tristate "Geode ACCESS.bus support"
901 depends on X86_32 && PCI
903 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
904 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
906 If you don't know what to do here, say N.
908 This support is also available as a module. If so, the module
909 will be called scx200_acb.