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.
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
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
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"
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
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)"
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 "CBUS I2C driver"
342 depends on GENERIC_GPIO
344 Support for CBUS access using I2C API. Mostly relevant for Nokia
345 Internet Tablets (770, N800 and N810).
347 This driver can also be built as a module. If so, the module
348 will be called i2c-cbus-gpio.
351 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
352 depends on (CPM1 || CPM2) && OF_I2C
354 This supports the use of the I2C interface on Freescale
355 processors with CPM1 or CPM2.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-cpm.
361 tristate "DaVinci I2C driver"
362 depends on ARCH_DAVINCI
364 Support for TI DaVinci I2C controller driver.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-davinci.
369 Please note that this driver might be needed to bring up other
370 devices such as DaVinci NIC.
371 For details please see http://www.ti.com/davinci
373 config I2C_DESIGNWARE_CORE
376 config I2C_DESIGNWARE_PLATFORM
377 tristate "Synopsys DesignWare Platform"
379 select I2C_DESIGNWARE_CORE
381 If you say yes to this option, support will be included for the
382 Synopsys DesignWare I2C adapter. Only master mode is supported.
384 This driver can also be built as a module. If so, the module
385 will be called i2c-designware-platform.
387 config I2C_DESIGNWARE_PCI
388 tristate "Synopsys DesignWare PCI"
390 select I2C_DESIGNWARE_CORE
392 If you say yes to this option, support will be included for the
393 Synopsys DesignWare I2C adapter. Only master mode is supported.
395 This driver can also be built as a module. If so, the module
396 will be called i2c-designware-pci.
399 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
402 This driver is for PCH(Platform controller Hub) I2C of EG20T which
403 is an IOH(Input/Output Hub) for x86 embedded processor.
404 This driver can access PCH I2C bus device.
406 This driver also can be used for LAPIS Semiconductor IOH(Input/
407 Output Hub), ML7213, ML7223 and ML7831.
408 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
409 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
410 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
411 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
414 tristate "GPIO-based bitbanging I2C"
415 depends on GENERIC_GPIO
418 This is a very simple bitbanging I2C driver utilizing the
419 arch-neutral GPIO API to control the SCL and SDA lines.
421 config I2C_HIGHLANDER
422 tristate "Highlander FPGA SMBus interface"
423 depends on SH_HIGHLANDER
425 If you say yes to this option, support will be included for
426 the SMBus interface located in the FPGA on various Highlander
427 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
428 FPGAs. This is wholly unrelated to the SoC I2C.
430 This driver can also be built as a module. If so, the module
431 will be called i2c-highlander.
434 tristate "IBM PPC 4xx on-chip I2C interface"
437 Say Y here if you want to use IIC peripheral found on
438 embedded IBM PPC 4xx based systems.
440 This driver can also be built as a module. If so, the module
441 will be called i2c-ibm_iic.
444 tristate "IMX I2C interface"
447 Say Y here if you want to use the IIC bus controller on
448 the Freescale i.MX/MXC processors.
450 This driver can also be built as a module. If so, the module
451 will be called i2c-imx.
454 tristate "Intel Moorestown/Medfield Platform I2C controller"
457 Say Y here if you have an Intel Moorestown/Medfield platform I2C
460 This support is also available as a module. If so, the module
461 will be called i2c-intel-mid.
464 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
465 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
467 Say Y here if you want to use the IIC bus controller on
468 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
470 This driver can also be built as a module. If so, the module
471 will be called i2c-iop3xx.
474 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
477 If you say yes to this option, support will be included for the
478 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
479 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
481 This driver can also be built as a module. If so, the module
482 will be called i2c-mpc.
485 tristate "Marvell mv64xxx I2C Controller"
486 depends on (MV64X60 || PLAT_ORION)
488 If you say yes to this option, support will be included for the
489 built-in I2C interface on the Marvell 64xxx line of host bridges.
491 This driver can also be built as a module. If so, the module
492 will be called i2c-mv64xxx.
495 tristate "Freescale i.MX28 I2C interface"
499 Say Y here if you want to use the I2C bus controller on
500 the Freescale i.MX28 processors.
502 This driver can also be built as a module. If so, the module
503 will be called i2c-mxs.
506 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
509 If you say yes to this option, support will be included for the
510 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
511 as well as the STA2X11 PCIe I/O HUB.
514 tristate "NUC900 I2C Driver"
515 depends on ARCH_W90X900
517 Say Y here to include support for I2C controller in the
518 Winbond/Nuvoton NUC900 based System-on-Chip devices.
521 tristate "OpenCores I2C Controller"
523 If you say yes to this option, support will be included for the
524 OpenCores I2C controller. For details see
525 http://www.opencores.org/projects.cgi/web/i2c/overview
527 This driver can also be built as a module. If so, the module
528 will be called i2c-ocores.
531 tristate "OMAP I2C adapter"
533 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
535 If you say yes to this option, support will be included for the
536 I2C interface on the Texas Instruments OMAP1/2 family of processors.
537 Like OMAP1510/1610/1710/5912 and OMAP242x.
538 For details see http://www.ti.com/omap.
541 tristate "PA Semi SMBus interface"
542 depends on PPC_PASEMI && PCI
544 Supports the PA Semi PWRficient on-chip SMBus interfaces.
546 config I2C_PCA_PLATFORM
547 tristate "PCA9564/PCA9665 as platform device"
551 This driver supports a memory mapped Philips PCA9564/PCA9665
552 parallel bus to I2C bus controller.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-pca-platform.
558 tristate "PMC MSP I2C TWI Controller"
561 This driver supports the PMC TWI controller on MSP devices.
563 This driver can also be built as module. If so, the module
564 will be called i2c-pmcmsp.
567 tristate "I2C bus support for Philips PNX and NXP LPC targets"
568 depends on ARCH_LPC32XX
570 This driver supports the Philips IP3204 I2C IP block master and/or
573 This driver can also be built as a module. If so, the module
574 will be called i2c-pnx.
577 tristate "PKUnity v3 I2C bus support"
578 depends on UNICORE32 && ARCH_PUV3
581 This driver supports the I2C IP inside the PKUnity-v3 SoC.
582 This I2C bus controller is under AMBA/AXI bus.
584 This driver can also be built as a module. If so, the module
585 will be called i2c-puv3.
588 tristate "Intel PXA2XX I2C adapter"
589 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
591 If you have devices in the PXA I2C bus, say yes to this option.
592 This driver can also be built as a module. If so, the module
593 will be called i2c-pxa.
596 def_bool I2C_PXA && X86_32 && PCI && OF
599 bool "Intel PXA2XX I2C Slave comms support"
600 depends on I2C_PXA && !X86_32
602 Support I2C slave mode communications on the PXA I2C bus. This
603 is necessary for systems where the PXA may be a target on the
606 config HAVE_S3C2410_I2C
609 This will include I2C support for Samsung SoCs. If you want to
610 include I2C support for any machine, kindly select this in the
611 respective Kconfig file.
614 tristate "S3C2410 I2C Driver"
615 depends on HAVE_S3C2410_I2C
617 Say Y here to include support for I2C controller in the
621 tristate "S6000 I2C support"
622 depends on XTENSA_VARIANT_S6000
624 This driver supports the on chip I2C device on the
625 S6000 xtensa processor family.
627 To compile this driver as a module, choose M here. The module
628 will be called i2c-s6000.
631 tristate "Renesas SH7760 I2C Controller"
632 depends on CPU_SUBTYPE_SH7760
634 This driver supports the 2 I2C interfaces on the Renesas SH7760.
636 This driver can also be built as a module. If so, the module
637 will be called i2c-sh7760.
640 tristate "SuperH Mobile I2C Controller"
641 depends on SUPERH || ARCH_SHMOBILE
643 If you say yes to this option, support will be included for the
644 built-in I2C interface on the Renesas SH-Mobile processor.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-sh_mobile.
650 tristate "Simtec Generic I2C interface"
653 If you say yes to this option, support will be included for
654 the Simtec Generic I2C interface. This driver is for the
655 simple I2C bus used on newer Simtec products for general
656 I2C, such as DDC on the Simtec BBD2016A.
658 This driver can also be built as a module. If so, the module
659 will be called i2c-simtec.
662 tristate "CSR SiRFprimaII I2C interface"
663 depends on ARCH_PRIMA2
665 If you say yes to this option, support will be included for the
666 CSR SiRFprimaII I2C interface.
668 This driver can also be built as a module. If so, the module
669 will be called i2c-sirf.
672 tristate "ST Microelectronics DDC I2C interface"
674 default y if MACH_U300
676 If you say yes to this option, support will be included for the
677 I2C interface from ST Microelectronics simply called "DDC I2C"
678 supporting both I2C and DDC, used in e.g. the U300 series
681 This driver can also be built as a module. If so, the module
682 will be called i2c-stu300.
685 tristate "NVIDIA Tegra internal I2C controller"
686 depends on ARCH_TEGRA
688 If you say yes to this option, support will be included for the
689 I2C controller embedded in NVIDIA Tegra SOCs
692 tristate "ARM Versatile/Realview I2C bus support"
693 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
696 Say yes if you want to support the I2C serial bus on ARMs Versatile
699 This driver can also be built as a module. If so, the module
700 will be called i2c-versatile.
703 tristate "Cavium OCTEON I2C bus support"
704 depends on CPU_CAVIUM_OCTEON
706 Say yes if you want to support the I2C serial bus on Cavium
709 This driver can also be built as a module. If so, the module
710 will be called i2c-octeon.
713 tristate "Xilinx I2C Controller"
716 If you say yes to this option, support will be included for the
717 Xilinx I2C controller.
719 This driver can also be built as a module. If so, the module
720 will be called xilinx_i2c.
723 tristate "XLR I2C support"
726 This driver enables support for the on-chip I2C interface of
727 the Netlogic XLR/XLS MIPS processors.
729 This driver can also be built as a module. If so, the module
730 will be called i2c-xlr.
733 tristate "Renesas R-Car I2C Controller"
734 depends on ARCH_SHMOBILE && I2C
736 If you say yes to this option, support will be included for the
737 R-Car I2C controller.
739 This driver can also be built as a module. If so, the module
740 will be called i2c-rcar.
742 comment "External I2C/SMBus adapter drivers"
744 config I2C_DIOLAN_U2C
745 tristate "Diolan U2C-12 USB adapter"
748 If you say yes to this option, support will be included for Diolan
749 U2C-12, a USB to I2C interface.
751 This driver can also be built as a module. If so, the module
752 will be called i2c-diolan-u2c.
755 tristate "Parallel port adapter"
760 This supports parallel port I2C adapters such as the ones made by
761 Philips or Velleman, Analog Devices evaluation boards, and more.
762 Basically any adapter using the parallel port as an I2C bus with
763 no extra chipset is supported by this driver, or could be.
765 This driver is a replacement for (and was inspired by) an older
766 driver named i2c-philips-par. The new driver supports more devices,
767 and makes it easier to add support for new devices.
769 An adapter type parameter is now mandatory. Please read the file
770 Documentation/i2c/busses/i2c-parport for details.
772 Another driver exists, named i2c-parport-light, which doesn't depend
773 on the parport driver. This is meant for embedded systems. Don't say
774 Y here if you intend to say Y or M there.
776 This support is also available as a module. If so, the module
777 will be called i2c-parport.
779 config I2C_PARPORT_LIGHT
780 tristate "Parallel port adapter (light)"
784 This supports parallel port I2C adapters such as the ones made by
785 Philips or Velleman, Analog Devices evaluation boards, and more.
786 Basically any adapter using the parallel port as an I2C bus with
787 no extra chipset is supported by this driver, or could be.
789 This driver is a light version of i2c-parport. It doesn't depend
790 on the parport driver, and uses direct I/O access instead. This
791 might be preferred on embedded systems where wasting memory for
792 the clean but heavy parport handling is not an option. The
793 drawback is a reduced portability and the impossibility to
794 daisy-chain other parallel port devices.
796 Don't say Y here if you said Y or M to i2c-parport. Saying M to
797 both is possible but both modules should not be loaded at the same
800 This support is also available as a module. If so, the module
801 will be called i2c-parport-light.
804 tristate "TAOS evaluation module"
810 This supports TAOS evaluation modules on serial port. In order to
811 use this driver, you will need the inputattach tool, which is part
812 of the input-utils package.
816 This support is also available as a module. If so, the module
817 will be called i2c-taos-evm.
820 tristate "Tiny-USB adapter"
823 If you say yes to this option, support will be included for the
824 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
825 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
827 This driver can also be built as a module. If so, the module
828 will be called i2c-tiny-usb.
830 config I2C_VIPERBOARD
831 tristate "Viperboard I2C master support"
832 depends on MFD_VIPERBOARD && USB
834 Say yes here to access the I2C part of the Nano River
835 Technologies Viperboard as I2C master.
836 See viperboard API specification and Nano
837 River Tech's viperboard.h for detailed meaning
838 of the module parameters.
840 comment "Other I2C/SMBus bus drivers"
843 tristate "Acorn IOC/IOMD I2C bus support"
844 depends on ARCH_ACORN
848 Say yes if you want to support the I2C bus on Acorn platforms.
850 If you don't know, say Y.
853 tristate "Elektor ISA card"
854 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
857 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
860 This support is also available as a module. If so, the module
861 will be called i2c-elektor.
864 tristate "PCA9564/PCA9665 on an ISA bus"
869 This driver supports ISA boards using the Philips PCA9564/PCA9665
870 parallel bus to I2C bus controller.
872 This driver can also be built as a module. If so, the module
873 will be called i2c-pca-isa.
875 This device is almost undetectable and using this driver on a
876 system which doesn't have this device will result in long
877 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
878 time). If unsure, say N.
881 tristate "SiByte SMBus interface"
882 depends on SIBYTE_SB1xxx_SOC
884 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
887 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
888 depends on SCx200_GPIO
891 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
893 If you don't know what to do here, say N.
895 This support is also available as a module. If so, the module
896 will be called scx200_i2c.
898 This driver is deprecated and will be dropped soon. Use i2c-gpio
899 (or scx200_acb) instead.
901 config SCx200_I2C_SCL
902 int "GPIO pin used for SCL"
903 depends on SCx200_I2C
906 Enter the GPIO pin number used for the SCL signal. This value can
907 also be specified with a module parameter.
909 config SCx200_I2C_SDA
910 int "GPIO pin used for SDA"
911 depends on SCx200_I2C
914 Enter the GPIO pin number used for the SSA signal. This value can
915 also be specified with a module parameter.
918 tristate "Geode ACCESS.bus support"
919 depends on X86_32 && PCI
921 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
922 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
924 If you don't know what to do here, say N.
926 This support is also available as a module. If so, the module
927 will be called scx200_acb.