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 "Hix5hd2 high-speed I2C driver"
82 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
84 Say Y here to include support for the high-speed I2C controller
85 used in HiSilicon hix5hd2 SoCs.
87 This driver can also be built as a module. If so, the module
88 will be called i2c-hix5hd2.
91 tristate "Intel 82801 (ICH/PCH)"
93 select CHECK_SIGNATURE if X86 && DMI
96 If you say yes to this option, support will be included for the Intel
97 801 family of mainboard I2C interfaces. Specifically, the following
98 versions of the chipset are supported:
104 82801EB/ER (ICH5/ICH5R)
124 Wildcat Point-LP (PCH)
126 Sunrise Point-H (PCH)
127 Sunrise Point-LP (PCH)
136 This driver can also be built as a module. If so, the module
137 will be called i2c-i801.
140 tristate "Intel SCH SMBus 1.0"
144 Say Y here if you want to use SMBus controller on the Intel SCH
147 This driver can also be built as a module. If so, the module
148 will be called i2c-isch.
151 tristate "Intel iSMT SMBus Controller"
152 depends on PCI && X86
154 If you say yes to this option, support will be included for the Intel
155 iSMT SMBus host controller interface.
157 This driver can also be built as a module. If so, the module will be
161 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
164 If you say yes to this option, support will be included for the Intel
165 PIIX4 family of mainboard I2C interfaces. Specifically, the following
166 versions of the chipset are supported (note that Serverworks is part
186 Some AMD chipsets contain two PIIX4-compatible SMBus
187 controllers. This driver will attempt to use both controllers
188 on the SB700/SP5100, if they have been initialized by the BIOS.
190 This driver can also be built as a module. If so, the module
191 will be called i2c-piix4.
194 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
195 depends on INTEL_SOC_PMIC_CHTWC
197 If you say yes to this option, support will be included for the
198 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
199 found on some Intel Cherry Trail systems.
202 tristate "Nvidia nForce2, nForce3 and nForce4"
205 If you say yes to this option, support will be included for the Nvidia
206 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
208 This driver can also be built as a module. If so, the module
209 will be called i2c-nforce2.
211 config I2C_NFORCE2_S4985
212 tristate "SMBus multiplexing on the Tyan S4985"
213 depends on I2C_NFORCE2 && X86
215 Enabling this option will add specific SMBus support for the Tyan
216 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
217 over 4 different channels, where the various memory module EEPROMs
218 live. Saying yes here will give you access to these in addition
221 This driver can also be built as a module. If so, the module
222 will be called i2c-nforce2-s4985.
228 If you say yes to this option, support will be included for the
229 SiS5595 SMBus (a subset of I2C) interface.
231 This driver can also be built as a module. If so, the module
232 will be called i2c-sis5595.
235 tristate "SiS 630/730/964"
238 If you say yes to this option, support will be included for the
239 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
241 This driver can also be built as a module. If so, the module
242 will be called i2c-sis630.
248 If you say yes to this option, support will be included for the SiS
249 96x SMBus (a subset of I2C) interfaces. Specifically, the following
250 chipsets are supported:
259 This driver can also be built as a module. If so, the module
260 will be called i2c-sis96x.
263 tristate "VIA VT82C586B"
267 If you say yes to this option, support will be included for the VIA
268 82C586B I2C interface
270 This driver can also be built as a module. If so, the module
271 will be called i2c-via.
274 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
277 If you say yes to this option, support will be included for the VIA
278 VT82C596 and later SMBus interface. Specifically, the following
279 chipsets are supported:
292 This driver can also be built as a module. If so, the module
293 will be called i2c-viapro.
297 comment "ACPI drivers"
300 tristate "SMBus Control Method Interface"
302 This driver supports the SMBus Control Method Interface. It needs the
303 BIOS to declare ACPI control methods as described in the SMBus Control
304 Method Interface specification.
306 To compile this driver as a module, choose M here:
307 the module will be called i2c-scmi.
311 comment "Mac SMBus host controller drivers"
312 depends on PPC_CHRP || PPC_PMAC
315 tristate "CHRP Apple Hydra Mac I/O I2C interface"
316 depends on PCI && PPC_CHRP
319 This supports the use of the I2C interface in the Apple Hydra Mac
320 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
323 This support is also available as a module. If so, the module
324 will be called i2c-hydra.
327 tristate "Powermac I2C interface"
331 This exposes the various PowerMac i2c interfaces to the linux i2c
332 layer and to userland. It is used by various drivers on the PowerMac
333 platform, and should generally be enabled.
335 This support is also available as a module. If so, the module
336 will be called i2c-powermac.
338 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
341 tristate "Altera Soft IP I2C"
342 depends on (ARCH_SOCFPGA || NIOS2) && OF
344 If you say yes to this option, support will be included for the
345 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
347 This driver can also be built as a module. If so, the module
348 will be called i2c-altera.
351 tristate "Aspeed I2C Controller"
352 depends on ARCH_ASPEED || COMPILE_TEST
354 If you say yes to this option, support will be included for the
355 Aspeed I2C controller.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-aspeed.
361 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
364 This supports the use of the I2C interface on Atmel AT91
367 A serious problem is that there is no documented way to issue
368 repeated START conditions for more than two messages, as needed
369 to support combined I2C messages. Use the i2c-gpio driver
370 unless your system can cope with this limitation.
372 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
373 don't have clock stretching in transmission mode. For that reason,
374 you can encounter underrun issues causing premature stop sendings if
375 the latency to fill the transmission register is too long. If you
376 are facing this situation, use the i2c-gpio driver.
379 tristate "Au1550/Au1200/Au1300 SMBus interface"
380 depends on MIPS_ALCHEMY
382 If you say yes to this option, support will be included for the
383 Au1550/Au1200/Au1300 SMBus interface.
385 This driver can also be built as a module. If so, the module
386 will be called i2c-au1550.
389 tristate "Axxia I2C controller"
390 depends on ARCH_AXXIA || COMPILE_TEST
393 Say yes if you want to support the I2C bus on Axxia platforms.
395 Please note that this controller is limited to transfers of maximum
396 255 bytes in length. Any attempt to to a larger transfer will return
400 tristate "Broadcom BCM2835 I2C controller"
401 depends on ARCH_BCM2835
403 If you say yes to this option, support will be included for the
404 BCM2835 I2C controller.
406 If you don't know what to do here, say N.
408 This support is also available as a module. If so, the module
409 will be called i2c-bcm2835.
412 tristate "Broadcom iProc I2C controller"
413 depends on ARCH_BCM_IPROC || COMPILE_TEST
414 default ARCH_BCM_IPROC
416 If you say yes to this option, support will be included for the
417 Broadcom iProc I2C controller.
419 If you don't know what to do here, say N.
422 tristate "BCM Kona I2C adapter"
423 depends on ARCH_BCM_MOBILE
426 If you say yes to this option, support will be included for the
427 I2C interface on the Broadcom Kona family of processors.
429 If you do not need KONA I2C interface, say N.
432 tristate "BRCM Settop/DSL I2C controller"
433 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
437 If you say yes to this option, support will be included for the
438 I2C interface on the Broadcom Settop/DSL SoCs.
440 If you do not need I2C interface, say N.
442 config I2C_BLACKFIN_TWI
443 tristate "Blackfin TWI I2C support"
445 depends on !BF561 && !BF531 && !BF532 && !BF533
447 This is the I2C bus driver for Blackfin on-chip TWI interface.
449 This driver can also be built as a module. If so, the module
450 will be called i2c-bfin-twi.
452 config I2C_BLACKFIN_TWI_CLK_KHZ
453 int "Blackfin TWI I2C clock (kHz)"
454 depends on I2C_BLACKFIN_TWI
458 The unit of the TWI clock is kHz.
461 tristate "Cadence I2C Controller"
462 depends on ARCH_ZYNQ || ARM64 || XTENSA
464 Say yes here to select Cadence I2C Host Controller. This controller is
465 e.g. used by Xilinx Zynq.
468 tristate "CBUS I2C driver"
469 depends on GPIOLIB || COMPILE_TEST
471 Support for CBUS access using I2C API. Mostly relevant for Nokia
472 Internet Tablets (770, N800 and N810).
474 This driver can also be built as a module. If so, the module
475 will be called i2c-cbus-gpio.
478 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
479 depends on CPM1 || CPM2
481 This supports the use of the I2C interface on Freescale
482 processors with CPM1 or CPM2.
484 This driver can also be built as a module. If so, the module
485 will be called i2c-cpm.
488 tristate "DaVinci I2C driver"
489 depends on ARCH_DAVINCI || ARCH_KEYSTONE
491 Support for TI DaVinci I2C controller driver.
493 This driver can also be built as a module. If so, the module
494 will be called i2c-davinci.
496 Please note that this driver might be needed to bring up other
497 devices such as DaVinci NIC.
498 For details please see http://www.ti.com/davinci
500 config I2C_DESIGNWARE_CORE
503 config I2C_DESIGNWARE_PLATFORM
504 tristate "Synopsys DesignWare Platform"
505 select I2C_DESIGNWARE_CORE
506 depends on (ACPI && COMMON_CLK) || !ACPI
508 If you say yes to this option, support will be included for the
509 Synopsys DesignWare I2C adapter.
511 This driver can also be built as a module. If so, the module
512 will be called i2c-designware-platform.
514 config I2C_DESIGNWARE_SLAVE
515 bool "Synopsys DesignWare Slave"
517 depends on I2C_DESIGNWARE_PLATFORM
519 If you say yes to this option, support will be included for the
520 Synopsys DesignWare I2C slave adapter.
522 This is not a standalone module, this module compiles together with
525 config I2C_DESIGNWARE_PCI
526 tristate "Synopsys DesignWare PCI"
528 select I2C_DESIGNWARE_CORE
530 If you say yes to this option, support will be included for the
531 Synopsys DesignWare I2C adapter. Only master mode is supported.
533 This driver can also be built as a module. If so, the module
534 will be called i2c-designware-pci.
536 config I2C_DESIGNWARE_BAYTRAIL
537 bool "Intel Baytrail I2C semaphore support"
539 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
540 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
542 This driver enables managed host access to the PMIC I2C bus on select
543 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
544 the host to request uninterrupted access to the PMIC's I2C bus from
545 the platform firmware controlling it. You should say Y if running on
546 a BayTrail system using the AXP288.
549 tristate "Conexant Digicolor I2C driver"
550 depends on ARCH_DIGICOLOR
552 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-digicolor.
558 tristate "EFM32 I2C controller"
559 depends on ARCH_EFM32 || COMPILE_TEST
561 This driver supports the i2c block found in Energy Micro's EFM32
565 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
566 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
568 This driver is for PCH(Platform controller Hub) I2C of EG20T which
569 is an IOH(Input/Output Hub) for x86 embedded processor.
570 This driver can access PCH I2C bus device.
572 This driver also can be used for LAPIS Semiconductor IOH(Input/
573 Output Hub), ML7213, ML7223 and ML7831.
574 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
575 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
576 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
577 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
580 tristate "EMMA Mobile series I2C adapter"
584 If you say yes to this option, support will be included for the
585 I2C interface on the Renesas Electronics EM/EV family of processors.
588 tristate "Exynos5 high-speed I2C driver"
589 depends on ARCH_EXYNOS && OF
592 High-speed I2C controller on Exynos5 based Samsung SoCs.
595 tristate "GPIO-based bitbanging I2C"
596 depends on GPIOLIB || COMPILE_TEST
599 This is a very simple bitbanging I2C driver utilizing the
600 arch-neutral GPIO API to control the SCL and SDA lines.
602 config I2C_HIGHLANDER
603 tristate "Highlander FPGA SMBus interface"
604 depends on SH_HIGHLANDER
606 If you say yes to this option, support will be included for
607 the SMBus interface located in the FPGA on various Highlander
608 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
609 FPGAs. This is wholly unrelated to the SoC I2C.
611 This driver can also be built as a module. If so, the module
612 will be called i2c-highlander.
615 tristate "IBM PPC 4xx on-chip I2C interface"
618 Say Y here if you want to use IIC peripheral found on
619 embedded IBM PPC 4xx based systems.
621 This driver can also be built as a module. If so, the module
622 will be called i2c-ibm_iic.
625 tristate "Imagination Technologies I2C SCB Controller"
626 depends on MIPS || METAG || COMPILE_TEST
628 Say Y here if you want to use the IMG I2C SCB controller,
629 available on the TZ1090 and other IMG SoCs.
631 This driver can also be built as a module. If so, the module
632 will be called i2c-img-scb.
635 tristate "IMX I2C interface"
636 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
638 Say Y here if you want to use the IIC bus controller on
639 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
641 This driver can also be built as a module. If so, the module
642 will be called i2c-imx.
645 tristate "IMX Low Power I2C interface"
646 depends on ARCH_MXC || COMPILE_TEST
648 Say Y here if you want to use the Low Power IIC bus controller
649 on the Freescale i.MX processors.
651 This driver can also be built as a module. If so, the module
652 will be called i2c-imx-lpi2c.
655 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
656 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
658 Say Y here if you want to use the IIC bus controller on
659 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
661 This driver can also be built as a module. If so, the module
662 will be called i2c-iop3xx.
665 tristate "JZ4780 I2C controller interface support"
666 depends on MACH_JZ4780 || COMPILE_TEST
668 If you say yes to this option, support will be included for the
669 Ingenic JZ4780 I2C controller.
671 If you don't know what to do here, say N.
674 tristate "Kontron COM I2C Controller"
675 depends on MFD_KEMPLD
677 This enables support for the I2C bus interface on some Kontron ETX
678 and COMexpress (ETXexpress) modules.
680 This driver can also be built as a module. If so, the module
681 will be called i2c-kempld.
684 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
685 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
687 This driver supports the I2C interface found several NXP
688 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
690 This driver can also be built as a module. If so, the module
691 will be called i2c-lpc2k.
694 tristate "Amlogic Meson I2C controller"
695 depends on ARCH_MESON || COMPILE_TEST
697 If you say yes to this option, support will be included for the
698 I2C interface on the Amlogic Meson family of SoCs.
701 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
704 If you say yes to this option, support will be included for the
705 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
706 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
708 This driver can also be built as a module. If so, the module
709 will be called i2c-mpc.
712 tristate "MediaTek I2C adapter"
713 depends on ARCH_MEDIATEK || COMPILE_TEST
716 This selects the MediaTek(R) Integrated Inter Circuit bus driver
717 for MT65xx and MT81xx.
718 If you want to use MediaTek(R) I2C interface, say Y or M here.
722 tristate "Marvell mv64xxx I2C Controller"
723 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
725 If you say yes to this option, support will be included for the
726 built-in I2C interface on the Marvell 64xxx line of host bridges.
727 This driver is also used for Allwinner SoCs I2C controllers.
729 This driver can also be built as a module. If so, the module
730 will be called i2c-mv64xxx.
733 tristate "Freescale i.MX28 I2C interface"
737 Say Y here if you want to use the I2C bus controller on
738 the Freescale i.MX28 processors.
740 This driver can also be built as a module. If so, the module
741 will be called i2c-mxs.
744 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
747 If you say yes to this option, support will be included for the
748 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
749 as well as the STA2X11 PCIe I/O HUB.
752 tristate "OpenCores I2C Controller"
754 If you say yes to this option, support will be included for the
755 OpenCores I2C controller. For details see
756 http://www.opencores.org/projects.cgi/web/i2c/overview
758 This driver can also be built as a module. If so, the module
759 will be called i2c-ocores.
762 tristate "OMAP I2C adapter"
764 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
766 If you say yes to this option, support will be included for the
767 I2C interface on the Texas Instruments OMAP1/2 family of processors.
768 Like OMAP1510/1610/1710/5912 and OMAP242x.
769 For details see http://www.ti.com/omap.
772 tristate "PA Semi SMBus interface"
773 depends on PPC_PASEMI && PCI
775 Supports the PA Semi PWRficient on-chip SMBus interfaces.
777 config I2C_PCA_PLATFORM
778 tristate "PCA9564/PCA9665 as platform device"
782 This driver supports a memory mapped Philips PCA9564/PCA9665
783 parallel bus to I2C bus controller.
785 This driver can also be built as a module. If so, the module
786 will be called i2c-pca-platform.
789 tristate "PMC MSP I2C TWI Controller"
792 This driver supports the PMC TWI controller on MSP devices.
794 This driver can also be built as module. If so, the module
795 will be called i2c-pmcmsp.
798 tristate "I2C bus support for Philips PNX and NXP LPC targets"
799 depends on ARCH_LPC32XX
801 This driver supports the Philips IP3204 I2C IP block master and/or
804 This driver can also be built as a module. If so, the module
805 will be called i2c-pnx.
808 tristate "PKUnity v3 I2C bus support"
809 depends on UNICORE32 && ARCH_PUV3
812 This driver supports the I2C IP inside the PKUnity-v3 SoC.
813 This I2C bus controller is under AMBA/AXI bus.
815 This driver can also be built as a module. If so, the module
816 will be called i2c-puv3.
819 tristate "Intel PXA2XX I2C adapter"
820 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
822 If you have devices in the PXA I2C bus, say yes to this option.
823 This driver can also be built as a module. If so, the module
824 will be called i2c-pxa.
827 def_bool I2C_PXA && X86_32 && PCI && OF
830 bool "Intel PXA2XX I2C Slave comms support"
831 depends on I2C_PXA && !X86_32
833 Support I2C slave mode communications on the PXA I2C bus. This
834 is necessary for systems where the PXA may be a target on the
838 tristate "Qualcomm QUP based I2C controller"
841 If you say yes to this option, support will be included for the
842 built-in I2C interface on the Qualcomm SoCs.
844 This driver can also be built as a module. If so, the module
845 will be called i2c-qup.
848 tristate "Renesas RIIC adapter"
849 depends on ARCH_RENESAS || COMPILE_TEST
851 If you say yes to this option, support will be included for the
852 Renesas RIIC I2C interface.
854 This driver can also be built as a module. If so, the module
855 will be called i2c-riic.
858 tristate "Rockchip RK3xxx I2C adapter"
859 depends on OF && COMMON_CLK
861 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
864 This driver can also be built as a module. If so, the module will
867 config HAVE_S3C2410_I2C
870 This will include I2C support for Samsung SoCs. If you want to
871 include I2C support for any machine, kindly select this in the
872 respective Kconfig file.
875 tristate "S3C2410 I2C Driver"
876 depends on HAVE_S3C2410_I2C
878 Say Y here to include support for I2C controller in the
882 tristate "Renesas SH7760 I2C Controller"
883 depends on CPU_SUBTYPE_SH7760
885 This driver supports the 2 I2C interfaces on the Renesas SH7760.
887 This driver can also be built as a module. If so, the module
888 will be called i2c-sh7760.
891 tristate "SuperH Mobile I2C Controller"
893 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
895 If you say yes to this option, support will be included for the
896 built-in I2C interface on the Renesas SH-Mobile processor.
898 This driver can also be built as a module. If so, the module
899 will be called i2c-sh_mobile.
902 tristate "Simtec Generic I2C interface"
905 If you say yes to this option, support will be included for
906 the Simtec Generic I2C interface. This driver is for the
907 simple I2C bus used on newer Simtec products for general
908 I2C, such as DDC on the Simtec BBD2016A.
910 This driver can also be built as a module. If so, the module
911 will be called i2c-simtec.
914 tristate "CSR SiRFprimaII I2C interface"
917 If you say yes to this option, support will be included for the
918 CSR SiRFprimaII I2C interface.
920 This driver can also be built as a module. If so, the module
921 will be called i2c-sirf.
924 bool "Spreadtrum I2C interface"
925 depends on I2C=y && ARCH_SPRD
927 If you say yes to this option, support will be included for the
928 Spreadtrum I2C interface.
931 tristate "STMicroelectronics SSC I2C support"
934 Enable this option to add support for STMicroelectronics SoCs
935 hardware SSC (Synchronous Serial Controller) as an I2C controller.
937 This driver can also be built as module. If so, the module
938 will be called i2c-st.
941 tristate "STMicroelectronics STM32F4 I2C support"
942 depends on ARCH_STM32 || COMPILE_TEST
944 Enable this option to add support for STM32 I2C controller embedded
947 This driver can also be built as module. If so, the module
948 will be called i2c-stm32f4.
951 tristate "STMicroelectronics STM32F7 I2C support"
952 depends on ARCH_STM32 || COMPILE_TEST
954 Enable this option to add support for STM32 I2C controller embedded
957 This driver can also be built as module. If so, the module
958 will be called i2c-stm32f7.
961 tristate "ST Microelectronics DDC I2C interface"
963 default y if MACH_U300
965 If you say yes to this option, support will be included for the
966 I2C interface from ST Microelectronics simply called "DDC I2C"
967 supporting both I2C and DDC, used in e.g. the U300 series
970 This driver can also be built as a module. If so, the module
971 will be called i2c-stu300.
973 config I2C_SUN6I_P2WI
974 tristate "Allwinner sun6i internal P2WI controller"
975 depends on RESET_CONTROLLER
976 depends on MACH_SUN6I || COMPILE_TEST
978 If you say yes to this option, support will be included for the
979 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
981 The P2WI looks like an SMBus controller (which supports only byte
982 accesses), except that it only supports one slave device.
983 This interface is used to connect to specific PMIC devices (like the
987 tristate "NVIDIA Tegra internal I2C controller"
988 depends on ARCH_TEGRA
990 If you say yes to this option, support will be included for the
991 I2C controller embedded in NVIDIA Tegra SOCs
993 config I2C_TEGRA_BPMP
994 tristate "NVIDIA Tegra BPMP I2C controller"
995 depends on TEGRA_BPMP
998 If you say yes to this option, support will be included for the I2C
999 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1001 This I2C driver is a 'virtual' I2C driver. The real driver is part
1002 of the BPMP firmware, and this driver merely communicates with that
1006 tristate "UniPhier FIFO-less I2C controller"
1007 depends on ARCH_UNIPHIER || COMPILE_TEST
1009 If you say yes to this option, support will be included for
1010 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1011 or older UniPhier SoCs.
1013 config I2C_UNIPHIER_F
1014 tristate "UniPhier FIFO-builtin I2C controller"
1015 depends on ARCH_UNIPHIER || COMPILE_TEST
1017 If you say yes to this option, support will be included for
1018 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1019 PH1-Pro5, or newer UniPhier SoCs.
1021 config I2C_VERSATILE
1022 tristate "ARM Versatile/Realview I2C bus support"
1023 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1026 Say yes if you want to support the I2C serial bus on ARMs Versatile
1029 This driver can also be built as a module. If so, the module
1030 will be called i2c-versatile.
1033 tristate "Wondermedia WM8xxx SoC I2C bus support"
1034 depends on ARCH_VT8500
1036 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1039 This driver can also be built as a module. If so, the module will be
1043 tristate "Cavium OCTEON I2C bus support"
1044 depends on CAVIUM_OCTEON_SOC
1046 Say yes if you want to support the I2C serial bus on Cavium
1049 This driver can also be built as a module. If so, the module
1050 will be called i2c-octeon.
1053 tristate "Cavium ThunderX I2C bus support"
1054 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1057 Say yes if you want to support the I2C serial bus on Cavium
1060 This driver can also be built as a module. If so, the module
1061 will be called i2c-thunderx.
1064 tristate "Xilinx I2C Controller"
1065 depends on HAS_IOMEM
1067 If you say yes to this option, support will be included for the
1068 Xilinx I2C controller.
1070 This driver can also be built as a module. If so, the module
1071 will be called xilinx_i2c.
1074 tristate "Netlogic XLR and Sigma Designs I2C support"
1075 depends on CPU_XLR || ARCH_TANGO
1077 This driver enables support for the on-chip I2C interface of
1078 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1080 This driver can also be built as a module. If so, the module
1081 will be called i2c-xlr.
1084 tristate "XLP9XX I2C support"
1085 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1087 This driver enables support for the on-chip I2C interface of
1088 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1090 This driver can also be built as a module. If so, the module will
1091 be called i2c-xlp9xx.
1094 tristate "Renesas R-Car I2C Controller"
1096 depends on ARCH_RENESAS || COMPILE_TEST
1098 select RESET_CONTROLLER if ARCH_RCAR_GEN3
1100 If you say yes to this option, support will be included for the
1101 R-Car I2C controller.
1103 This driver can also be built as a module. If so, the module
1104 will be called i2c-rcar.
1106 comment "External I2C/SMBus adapter drivers"
1108 config I2C_DIOLAN_U2C
1109 tristate "Diolan U2C-12 USB adapter"
1112 If you say yes to this option, support will be included for Diolan
1113 U2C-12, a USB to I2C interface.
1115 This driver can also be built as a module. If so, the module
1116 will be called i2c-diolan-u2c.
1119 tristate "Diolan DLN-2 USB I2C adapter"
1122 If you say yes to this option, support will be included for Diolan
1123 DLN2, a USB to I2C interface.
1125 This driver can also be built as a module. If so, the module
1126 will be called i2c-dln2.
1129 tristate "Parallel port adapter"
1134 This supports parallel port I2C adapters such as the ones made by
1135 Philips or Velleman, Analog Devices evaluation boards, and more.
1136 Basically any adapter using the parallel port as an I2C bus with
1137 no extra chipset is supported by this driver, or could be.
1139 This driver is a replacement for (and was inspired by) an older
1140 driver named i2c-philips-par. The new driver supports more devices,
1141 and makes it easier to add support for new devices.
1143 An adapter type parameter is now mandatory. Please read the file
1144 Documentation/i2c/busses/i2c-parport for details.
1146 Another driver exists, named i2c-parport-light, which doesn't depend
1147 on the parport driver. This is meant for embedded systems. Don't say
1148 Y here if you intend to say Y or M there.
1150 This support is also available as a module. If so, the module
1151 will be called i2c-parport.
1153 config I2C_PARPORT_LIGHT
1154 tristate "Parallel port adapter (light)"
1158 This supports parallel port I2C adapters such as the ones made by
1159 Philips or Velleman, Analog Devices evaluation boards, and more.
1160 Basically any adapter using the parallel port as an I2C bus with
1161 no extra chipset is supported by this driver, or could be.
1163 This driver is a light version of i2c-parport. It doesn't depend
1164 on the parport driver, and uses direct I/O access instead. This
1165 might be preferred on embedded systems where wasting memory for
1166 the clean but heavy parport handling is not an option. The
1167 drawback is a reduced portability and the impossibility to
1168 daisy-chain other parallel port devices.
1170 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1171 both is possible but both modules should not be loaded at the same
1174 This support is also available as a module. If so, the module
1175 will be called i2c-parport-light.
1177 config I2C_ROBOTFUZZ_OSIF
1178 tristate "RobotFuzz Open Source InterFace USB adapter"
1181 If you say yes to this option, support will be included for the
1182 RobotFuzz Open Source InterFace USB to I2C interface.
1184 This driver can also be built as a module. If so, the module
1185 will be called i2c-osif.
1188 tristate "TAOS evaluation module"
1191 select SERIO_SERPORT
1194 This supports TAOS evaluation modules on serial port. In order to
1195 use this driver, you will need the inputattach tool, which is part
1196 of the input-utils package.
1200 This support is also available as a module. If so, the module
1201 will be called i2c-taos-evm.
1204 tristate "Tiny-USB adapter"
1207 If you say yes to this option, support will be included for the
1208 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1209 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1211 This driver can also be built as a module. If so, the module
1212 will be called i2c-tiny-usb.
1214 config I2C_VIPERBOARD
1215 tristate "Viperboard I2C master support"
1216 depends on MFD_VIPERBOARD && USB
1218 Say yes here to access the I2C part of the Nano River
1219 Technologies Viperboard as I2C master.
1220 See viperboard API specification and Nano
1221 River Tech's viperboard.h for detailed meaning
1222 of the module parameters.
1224 comment "Other I2C/SMBus bus drivers"
1227 tristate "Acorn IOC/IOMD I2C bus support"
1228 depends on ARCH_ACORN
1232 Say yes if you want to support the I2C bus on Acorn platforms.
1234 If you don't know, say Y.
1237 tristate "Elektor ISA card"
1238 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1241 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1244 This support is also available as a module. If so, the module
1245 will be called i2c-elektor.
1248 tristate "Mellanox I2C driver"
1251 This exposes the Mellanox platform I2C busses to the linux I2C layer
1252 for X86 based systems.
1253 Controller is implemented as CPLD logic.
1255 This driver can also be built as a module. If so, the module will be
1256 called as i2c-mlxcpld.
1259 tristate "PCA9564/PCA9665 on an ISA bus"
1264 This driver supports ISA boards using the Philips PCA9564/PCA9665
1265 parallel bus to I2C bus controller.
1267 This driver can also be built as a module. If so, the module
1268 will be called i2c-pca-isa.
1270 This device is almost undetectable and using this driver on a
1271 system which doesn't have this device will result in long
1272 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1273 time). If unsure, say N.
1276 tristate "SiByte SMBus interface"
1277 depends on SIBYTE_SB1xxx_SOC
1279 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1281 config I2C_CROS_EC_TUNNEL
1282 tristate "ChromeOS EC tunnel I2C bus"
1283 depends on MFD_CROS_EC
1285 If you say yes here you get an I2C bus that will tunnel i2c commands
1286 through to the other side of the ChromeOS EC to the i2c bus
1287 connected there. This will work whatever the interface used to
1288 talk to the EC (SPI, I2C or LPC).
1290 config I2C_XGENE_SLIMPRO
1291 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1292 depends on ARCH_XGENE && MAILBOX
1294 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1295 co-processor. The I2C device access the I2C bus via the X-Gene
1296 to SLIMpro (On chip coprocessor) mailbox mechanism.
1300 tristate "Geode ACCESS.bus support"
1301 depends on X86_32 && PCI
1303 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1304 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1306 If you don't know what to do here, say N.
1308 This support is also available as a module. If so, the module
1309 will be called scx200_acb.
1312 tristate "IBM OPAL I2C driver"
1313 depends on PPC_POWERNV
1316 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1317 the driver is based on the OPAL interfaces.
1319 This driver can also be built as a module. If so, the module will be
1323 tristate "ZTE ZX2967 I2C support"
1327 Selecting this option will add ZX2967 I2C driver.
1328 This driver can also be built as a module. If so, the module will be