1 # SPDX-License-Identifier: GPL-2.0-only
3 # Sensor device configuration
6 menu "I2C Hardware Bus support"
9 comment "PC SMBus host controller drivers"
16 If you say yes to this option, support will be included for the SMB
17 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
18 controller is part of the 7101 device, which is an ACPI-compliant
19 Power Management Unit (PMU).
21 This driver can also be built as a module. If so, the module
22 will be called i2c-ali1535.
28 If you say yes to this option, support will be included for the SMB
29 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
30 controller is part of the 7101 device, which is an ACPI-compliant
31 Power Management Unit (PMU).
33 This driver can also be built as a module. If so, the module
34 will be called i2c-ali1563.
40 If you say yes to this option, support will be included for the
41 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
43 This driver can also be built as a module. If so, the module
44 will be called i2c-ali15x3.
47 tristate "AMD 756/766/768/8111 and nVidia nForce"
50 If you say yes to this option, support will be included for the AMD
51 756/766/768 mainboard I2C interfaces. The driver also includes
52 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
53 the nVidia nForce I2C interface.
55 This driver can also be built as a module. If so, the module
56 will be called i2c-amd756.
58 config I2C_AMD756_S4882
59 tristate "SMBus multiplexing on the Tyan S4882"
60 depends on I2C_AMD756 && X86
62 Enabling this option will add specific SMBus support for the Tyan
63 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
64 over 8 different channels, where the various memory module EEPROMs
65 and temperature sensors live. Saying yes here will give you access
66 to these in addition to the trunk.
68 This driver can also be built as a module. If so, the module
69 will be called i2c-amd756-s4882.
75 If you say yes to this option, support will be included for the
76 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
78 This driver can also be built as a module. If so, the module
79 will be called i2c-amd8111.
82 tristate "AMD MP2 PCIe"
83 depends on PCI && ACPI
85 If you say yes to this option, support will be included for the AMD
88 This driver can also be built as modules. If so, the modules will
89 be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
92 tristate "Hix5hd2 high-speed I2C driver"
93 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
95 Say Y here to include support for the high-speed I2C controller
96 used in HiSilicon hix5hd2 SoCs.
98 This driver can also be built as a module. If so, the module
99 will be called i2c-hix5hd2.
102 tristate "Intel 82801 (ICH/PCH)"
104 select CHECK_SIGNATURE if X86 && DMI
107 If you say yes to this option, support will be included for the Intel
108 801 family of mainboard I2C interfaces. Specifically, the following
109 versions of the chipset are supported:
115 82801EB/ER (ICH5/ICH5R)
149 This driver can also be built as a module. If so, the module
150 will be called i2c-i801.
153 tristate "Intel SCH SMBus 1.0"
157 Say Y here if you want to use SMBus controller on the Intel SCH
160 This driver can also be built as a module. If so, the module
161 will be called i2c-isch.
164 tristate "Intel iSMT SMBus Controller"
165 depends on PCI && X86
167 If you say yes to this option, support will be included for the Intel
168 iSMT SMBus host controller interface.
170 This driver can also be built as a module. If so, the module will be
174 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
177 If you say yes to this option, support will be included for the Intel
178 PIIX4 family of mainboard I2C interfaces. Specifically, the following
179 versions of the chipset are supported (note that Serverworks is part
200 Some AMD chipsets contain two PIIX4-compatible SMBus
201 controllers. This driver will attempt to use both controllers
202 on the SB700/SP5100, if they have been initialized by the BIOS.
204 This driver can also be built as a module. If so, the module
205 will be called i2c-piix4.
208 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
209 depends on INTEL_SOC_PMIC_CHTWC
211 If you say yes to this option, support will be included for the
212 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
213 found on some Intel Cherry Trail systems.
215 Note this controller is hooked up to a TI bq24292i charger-IC,
216 combined with a FUSB302 Type-C port-controller as such it is advised
217 to also select CONFIG_TYPEC_FUSB302=m.
220 tristate "Nvidia nForce2, nForce3 and nForce4"
223 If you say yes to this option, support will be included for the Nvidia
224 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
226 This driver can also be built as a module. If so, the module
227 will be called i2c-nforce2.
229 config I2C_NFORCE2_S4985
230 tristate "SMBus multiplexing on the Tyan S4985"
231 depends on I2C_NFORCE2 && X86
233 Enabling this option will add specific SMBus support for the Tyan
234 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
235 over 4 different channels, where the various memory module EEPROMs
236 live. Saying yes here will give you access to these in addition
239 This driver can also be built as a module. If so, the module
240 will be called i2c-nforce2-s4985.
242 config I2C_NVIDIA_GPU
243 tristate "NVIDIA GPU I2C controller"
246 If you say yes to this option, support will be included for the
247 NVIDIA GPU I2C controller which is used to communicate with the GPU's
248 Type-C controller. This driver can also be built as a module called
255 If you say yes to this option, support will be included for the
256 SiS5595 SMBus (a subset of I2C) interface.
258 This driver can also be built as a module. If so, the module
259 will be called i2c-sis5595.
262 tristate "SiS 630/730/964"
265 If you say yes to this option, support will be included for the
266 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
268 This driver can also be built as a module. If so, the module
269 will be called i2c-sis630.
275 If you say yes to this option, support will be included for the SiS
276 96x SMBus (a subset of I2C) interfaces. Specifically, the following
277 chipsets are supported:
286 This driver can also be built as a module. If so, the module
287 will be called i2c-sis96x.
290 tristate "VIA VT82C586B"
294 If you say yes to this option, support will be included for the VIA
295 82C586B I2C interface
297 This driver can also be built as a module. If so, the module
298 will be called i2c-via.
301 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
304 If you say yes to this option, support will be included for the VIA
305 VT82C596 and later SMBus interface. Specifically, the following
306 chipsets are supported:
319 This driver can also be built as a module. If so, the module
320 will be called i2c-viapro.
324 comment "ACPI drivers"
327 tristate "SMBus Control Method Interface"
329 This driver supports the SMBus Control Method Interface. It needs the
330 BIOS to declare ACPI control methods as described in the SMBus Control
331 Method Interface specification.
333 To compile this driver as a module, choose M here:
334 the module will be called i2c-scmi.
338 comment "Mac SMBus host controller drivers"
339 depends on PPC_CHRP || PPC_PMAC
342 tristate "CHRP Apple Hydra Mac I/O I2C interface"
343 depends on PCI && PPC_CHRP
346 This supports the use of the I2C interface in the Apple Hydra Mac
347 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
350 This support is also available as a module. If so, the module
351 will be called i2c-hydra.
354 tristate "Powermac I2C interface"
358 This exposes the various PowerMac i2c interfaces to the linux i2c
359 layer and to userland. It is used by various drivers on the PowerMac
360 platform, and should generally be enabled.
362 This support is also available as a module. If so, the module
363 will be called i2c-powermac.
365 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
368 tristate "Altera Soft IP I2C"
369 depends on (ARCH_SOCFPGA || NIOS2) && OF
371 If you say yes to this option, support will be included for the
372 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
374 This driver can also be built as a module. If so, the module
375 will be called i2c-altera.
378 tristate "Aspeed I2C Controller"
379 depends on ARCH_ASPEED || COMPILE_TEST
381 If you say yes to this option, support will be included for the
382 Aspeed I2C controller.
384 This driver can also be built as a module. If so, the module
385 will be called i2c-aspeed.
388 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
391 This supports the use of the I2C interface on Atmel AT91
394 A serious problem is that there is no documented way to issue
395 repeated START conditions for more than two messages, as needed
396 to support combined I2C messages. Use the i2c-gpio driver
397 unless your system can cope with this limitation.
399 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
400 don't have clock stretching in transmission mode. For that reason,
401 you can encounter underrun issues causing premature stop sendings if
402 the latency to fill the transmission register is too long. If you
403 are facing this situation, use the i2c-gpio driver.
405 config I2C_AT91_SLAVE_EXPERIMENTAL
406 tristate "Microchip AT91 I2C experimental slave mode"
410 If you say yes to this option, support for the slave mode will be
411 added. Caution: do not use it for production. This feature has not
412 been tested in a heavy way, help wanted.
413 There are known bugs:
414 - It can hang, on a SAMA5D4, after several transfers.
415 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
419 tristate "Au1550/Au1200/Au1300 SMBus interface"
420 depends on MIPS_ALCHEMY
422 If you say yes to this option, support will be included for the
423 Au1550/Au1200/Au1300 SMBus interface.
425 This driver can also be built as a module. If so, the module
426 will be called i2c-au1550.
429 tristate "Axxia I2C controller"
430 depends on ARCH_AXXIA || COMPILE_TEST
433 Say yes if you want to support the I2C bus on Axxia platforms.
435 Please note that this controller is limited to transfers of maximum
436 255 bytes in length. Any attempt to to a larger transfer will return
440 tristate "Broadcom BCM2835 I2C controller"
441 depends on ARCH_BCM2835 || ARCH_BRCMSTB
443 If you say yes to this option, support will be included for the
444 BCM2835 I2C controller.
446 If you don't know what to do here, say N.
448 This support is also available as a module. If so, the module
449 will be called i2c-bcm2835.
452 tristate "Broadcom iProc I2C controller"
453 depends on ARCH_BCM_IPROC || COMPILE_TEST
454 default ARCH_BCM_IPROC
457 If you say yes to this option, support will be included for the
458 Broadcom iProc I2C controller.
460 If you don't know what to do here, say N.
463 tristate "BCM Kona I2C adapter"
464 depends on ARCH_BCM_MOBILE
467 If you say yes to this option, support will be included for the
468 I2C interface on the Broadcom Kona family of processors.
470 If you do not need KONA I2C interface, say N.
473 tristate "BRCM Settop/DSL I2C controller"
474 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
478 If you say yes to this option, support will be included for the
479 I2C interface on the Broadcom Settop/DSL SoCs.
481 If you do not need I2C interface, say N.
484 tristate "Cadence I2C Controller"
485 depends on ARCH_ZYNQ || ARM64 || XTENSA
487 Say yes here to select Cadence I2C Host Controller. This controller is
488 e.g. used by Xilinx Zynq.
491 tristate "CBUS I2C driver"
492 depends on GPIOLIB || COMPILE_TEST
494 Support for CBUS access using I2C API. Mostly relevant for Nokia
495 Internet Tablets (770, N800 and N810).
497 This driver can also be built as a module. If so, the module
498 will be called i2c-cbus-gpio.
501 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
502 depends on CPM1 || CPM2
504 This supports the use of the I2C interface on Freescale
505 processors with CPM1 or CPM2.
507 This driver can also be built as a module. If so, the module
508 will be called i2c-cpm.
511 tristate "DaVinci I2C driver"
512 depends on ARCH_DAVINCI || ARCH_KEYSTONE
514 Support for TI DaVinci I2C controller driver.
516 This driver can also be built as a module. If so, the module
517 will be called i2c-davinci.
519 Please note that this driver might be needed to bring up other
520 devices such as DaVinci NIC.
521 For details please see http://www.ti.com/davinci
523 config I2C_DESIGNWARE_CORE
526 config I2C_DESIGNWARE_PLATFORM
527 tristate "Synopsys DesignWare Platform"
528 select I2C_DESIGNWARE_CORE
529 depends on (ACPI && COMMON_CLK) || !ACPI
531 If you say yes to this option, support will be included for the
532 Synopsys DesignWare I2C adapter.
534 This driver can also be built as a module. If so, the module
535 will be called i2c-designware-platform.
537 config I2C_DESIGNWARE_SLAVE
538 bool "Synopsys DesignWare Slave"
540 depends on I2C_DESIGNWARE_PLATFORM
542 If you say yes to this option, support will be included for the
543 Synopsys DesignWare I2C slave adapter.
545 This is not a standalone module, this module compiles together with
548 config I2C_DESIGNWARE_PCI
549 tristate "Synopsys DesignWare PCI"
551 select I2C_DESIGNWARE_CORE
553 If you say yes to this option, support will be included for the
554 Synopsys DesignWare I2C adapter. Only master mode is supported.
556 This driver can also be built as a module. If so, the module
557 will be called i2c-designware-pci.
559 config I2C_DESIGNWARE_BAYTRAIL
560 bool "Intel Baytrail I2C semaphore support"
562 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
563 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
565 This driver enables managed host access to the PMIC I2C bus on select
566 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
567 the host to request uninterrupted access to the PMIC's I2C bus from
568 the platform firmware controlling it. You should say Y if running on
569 a BayTrail system using the AXP288.
572 tristate "Conexant Digicolor I2C driver"
573 depends on ARCH_DIGICOLOR
575 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
577 This driver can also be built as a module. If so, the module
578 will be called i2c-digicolor.
581 tristate "EFM32 I2C controller"
582 depends on ARCH_EFM32 || COMPILE_TEST
584 This driver supports the i2c block found in Energy Micro's EFM32
588 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
589 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
591 This driver is for PCH(Platform controller Hub) I2C of EG20T which
592 is an IOH(Input/Output Hub) for x86 embedded processor.
593 This driver can access PCH I2C bus device.
595 This driver also can be used for LAPIS Semiconductor IOH(Input/
596 Output Hub), ML7213, ML7223 and ML7831.
597 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
598 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
599 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
600 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
603 tristate "EMMA Mobile series I2C adapter"
607 If you say yes to this option, support will be included for the
608 I2C interface on the Renesas Electronics EM/EV family of processors.
611 tristate "Exynos5 high-speed I2C driver"
612 depends on ARCH_EXYNOS && OF
615 High-speed I2C controller on Exynos5 based Samsung SoCs.
618 tristate "GPIO-based bitbanging I2C"
619 depends on GPIOLIB || COMPILE_TEST
622 This is a very simple bitbanging I2C driver utilizing the
623 arch-neutral GPIO API to control the SCL and SDA lines.
625 config I2C_GPIO_FAULT_INJECTOR
626 bool "GPIO-based fault injector"
629 This adds some functionality to the i2c-gpio driver which can inject
630 faults to an I2C bus, so another bus master can be stress-tested.
631 This is for debugging. If unsure, say 'no'.
633 config I2C_HIGHLANDER
634 tristate "Highlander FPGA SMBus interface"
635 depends on SH_HIGHLANDER
637 If you say yes to this option, support will be included for
638 the SMBus interface located in the FPGA on various Highlander
639 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
640 FPGAs. This is wholly unrelated to the SoC I2C.
642 This driver can also be built as a module. If so, the module
643 will be called i2c-highlander.
646 tristate "IBM PPC 4xx on-chip I2C interface"
649 Say Y here if you want to use IIC peripheral found on
650 embedded IBM PPC 4xx based systems.
652 This driver can also be built as a module. If so, the module
653 will be called i2c-ibm_iic.
656 tristate "Imagination Technologies I2C SCB Controller"
657 depends on MIPS || COMPILE_TEST
659 Say Y here if you want to use the IMG I2C SCB controller,
660 available on the TZ1090 and other IMG SoCs.
662 This driver can also be built as a module. If so, the module
663 will be called i2c-img-scb.
666 tristate "IMX I2C interface"
667 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
669 Say Y here if you want to use the IIC bus controller on
670 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
672 This driver can also be built as a module. If so, the module
673 will be called i2c-imx.
676 tristate "IMX Low Power I2C interface"
677 depends on ARCH_MXC || COMPILE_TEST
679 Say Y here if you want to use the Low Power IIC bus controller
680 on the Freescale i.MX processors.
682 This driver can also be built as a module. If so, the module
683 will be called i2c-imx-lpi2c.
686 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
687 depends on ARCH_IOP32X || ARCH_IXP4XX
689 Say Y here if you want to use the IIC bus controller on
690 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
692 This driver can also be built as a module. If so, the module
693 will be called i2c-iop3xx.
696 tristate "JZ4780 I2C controller interface support"
697 depends on MIPS || COMPILE_TEST
699 If you say yes to this option, support will be included for the
700 Ingenic JZ4780 I2C controller.
702 If you don't know what to do here, say N.
705 tristate "Kontron COM I2C Controller"
706 depends on MFD_KEMPLD
708 This enables support for the I2C bus interface on some Kontron ETX
709 and COMexpress (ETXexpress) modules.
711 This driver can also be built as a module. If so, the module
712 will be called i2c-kempld.
715 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
716 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
718 This driver supports the I2C interface found several NXP
719 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
721 This driver can also be built as a module. If so, the module
722 will be called i2c-lpc2k.
725 tristate "Amlogic Meson I2C controller"
726 depends on ARCH_MESON || COMPILE_TEST
728 If you say yes to this option, support will be included for the
729 I2C interface on the Amlogic Meson family of SoCs.
732 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
735 If you say yes to this option, support will be included for the
736 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
737 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
739 This driver can also be built as a module. If so, the module
740 will be called i2c-mpc.
743 tristate "MediaTek I2C adapter"
744 depends on ARCH_MEDIATEK || COMPILE_TEST
746 This selects the MediaTek(R) Integrated Inter Circuit bus driver
747 for MT65xx and MT81xx.
748 If you want to use MediaTek(R) I2C interface, say Y or M here.
752 tristate "MT7621/MT7628 I2C Controller"
753 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
755 Say Y here to include support for I2C controller in the
756 MediaTek MT7621/MT7628 SoCs.
759 tristate "Marvell mv64xxx I2C Controller"
760 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
762 If you say yes to this option, support will be included for the
763 built-in I2C interface on the Marvell 64xxx line of host bridges.
764 This driver is also used for Allwinner SoCs I2C controllers.
766 This driver can also be built as a module. If so, the module
767 will be called i2c-mv64xxx.
770 tristate "Freescale i.MX28 I2C interface"
774 Say Y here if you want to use the I2C bus controller on
775 the Freescale i.MX28 processors.
777 This driver can also be built as a module. If so, the module
778 will be called i2c-mxs.
781 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
784 If you say yes to this option, support will be included for the
785 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
786 as well as the STA2X11 PCIe I/O HUB.
789 tristate "OpenCores I2C Controller"
791 If you say yes to this option, support will be included for the
792 OpenCores I2C controller. For details see
793 http://www.opencores.org/projects.cgi/web/i2c/overview
795 This driver can also be built as a module. If so, the module
796 will be called i2c-ocores.
799 tristate "OMAP I2C adapter"
800 depends on ARCH_OMAP || ARCH_K3
801 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
803 If you say yes to this option, support will be included for the
804 I2C interface on the Texas Instruments OMAP1/2 family of processors.
805 Like OMAP1510/1610/1710/5912 and OMAP242x.
806 For details see http://www.ti.com/omap.
809 tristate "Actions Semiconductor Owl I2C Controller"
810 depends on ARCH_ACTIONS || COMPILE_TEST
812 Say Y here if you want to use the I2C bus controller on
813 the Actions Semiconductor Owl SoC's.
816 tristate "PA Semi SMBus interface"
817 depends on PPC_PASEMI && PCI
819 Supports the PA Semi PWRficient on-chip SMBus interfaces.
821 config I2C_PCA_PLATFORM
822 tristate "PCA9564/PCA9665 as platform device"
826 This driver supports a memory mapped Philips PCA9564/PCA9665
827 parallel bus to I2C bus controller.
829 This driver can also be built as a module. If so, the module
830 will be called i2c-pca-platform.
833 tristate "PMC MSP I2C TWI Controller"
836 This driver supports the PMC TWI controller on MSP devices.
838 This driver can also be built as module. If so, the module
839 will be called i2c-pmcmsp.
842 tristate "I2C bus support for Philips PNX and NXP LPC targets"
843 depends on ARCH_LPC32XX
845 This driver supports the Philips IP3204 I2C IP block master and/or
848 This driver can also be built as a module. If so, the module
849 will be called i2c-pnx.
852 tristate "PKUnity v3 I2C bus support"
853 depends on UNICORE32 && ARCH_PUV3
856 This driver supports the I2C IP inside the PKUnity-v3 SoC.
857 This I2C bus controller is under AMBA/AXI bus.
859 This driver can also be built as a module. If so, the module
860 will be called i2c-puv3.
863 tristate "Intel PXA2XX I2C adapter"
864 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
866 If you have devices in the PXA I2C bus, say yes to this option.
867 This driver can also be built as a module. If so, the module
868 will be called i2c-pxa.
871 def_bool I2C_PXA && X86_32 && PCI && OF
874 bool "Intel PXA2XX I2C Slave comms support"
875 depends on I2C_PXA && !X86_32
877 Support I2C slave mode communications on the PXA I2C bus. This
878 is necessary for systems where the PXA may be a target on the
882 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
883 depends on ARCH_QCOM || COMPILE_TEST
884 depends on QCOM_GENI_SE
886 This driver supports GENI serial engine based I2C controller in
887 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
888 yes to this option, support will be included for the built-in I2C
889 interface on the Qualcomm Technologies Inc.'s SoCs.
891 This driver can also be built as a module. If so, the module
892 will be called i2c-qcom-geni.
895 tristate "Qualcomm QUP based I2C controller"
898 If you say yes to this option, support will be included for the
899 built-in I2C interface on the Qualcomm SoCs.
901 This driver can also be built as a module. If so, the module
902 will be called i2c-qup.
905 tristate "Renesas RIIC adapter"
906 depends on ARCH_RENESAS || COMPILE_TEST
908 If you say yes to this option, support will be included for the
909 Renesas RIIC I2C interface.
911 This driver can also be built as a module. If so, the module
912 will be called i2c-riic.
915 tristate "Rockchip RK3xxx I2C adapter"
916 depends on OF && COMMON_CLK
918 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
921 This driver can also be built as a module. If so, the module will
924 config HAVE_S3C2410_I2C
927 This will include I2C support for Samsung SoCs. If you want to
928 include I2C support for any machine, kindly select this in the
929 respective Kconfig file.
932 tristate "S3C2410 I2C Driver"
933 depends on HAVE_S3C2410_I2C
935 Say Y here to include support for I2C controller in the
939 tristate "Renesas SH7760 I2C Controller"
940 depends on CPU_SUBTYPE_SH7760
942 This driver supports the 2 I2C interfaces on the Renesas SH7760.
944 This driver can also be built as a module. If so, the module
945 will be called i2c-sh7760.
948 tristate "SuperH Mobile I2C Controller"
949 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
951 If you say yes to this option, support will be included for the
952 built-in I2C interface on the Renesas SH-Mobile processor.
954 This driver can also be built as a module. If so, the module
955 will be called i2c-sh_mobile.
958 tristate "Simtec Generic I2C interface"
961 If you say yes to this option, support will be included for
962 the Simtec Generic I2C interface. This driver is for the
963 simple I2C bus used on newer Simtec products for general
964 I2C, such as DDC on the Simtec BBD2016A.
966 This driver can also be built as a module. If so, the module
967 will be called i2c-simtec.
970 tristate "CSR SiRFprimaII I2C interface"
973 If you say yes to this option, support will be included for the
974 CSR SiRFprimaII I2C interface.
976 This driver can also be built as a module. If so, the module
977 will be called i2c-sirf.
980 bool "Spreadtrum I2C interface"
981 depends on I2C=y && ARCH_SPRD
983 If you say yes to this option, support will be included for the
984 Spreadtrum I2C interface.
987 tristate "STMicroelectronics SSC I2C support"
990 Enable this option to add support for STMicroelectronics SoCs
991 hardware SSC (Synchronous Serial Controller) as an I2C controller.
993 This driver can also be built as module. If so, the module
994 will be called i2c-st.
997 tristate "STMicroelectronics STM32F4 I2C support"
998 depends on ARCH_STM32 || COMPILE_TEST
1000 Enable this option to add support for STM32 I2C controller embedded
1003 This driver can also be built as module. If so, the module
1004 will be called i2c-stm32f4.
1007 tristate "STMicroelectronics STM32F7 I2C support"
1008 depends on ARCH_STM32 || COMPILE_TEST
1011 Enable this option to add support for STM32 I2C controller embedded
1014 This driver can also be built as module. If so, the module
1015 will be called i2c-stm32f7.
1018 tristate "ST Microelectronics DDC I2C interface"
1019 depends on MACH_U300
1020 default y if MACH_U300
1022 If you say yes to this option, support will be included for the
1023 I2C interface from ST Microelectronics simply called "DDC I2C"
1024 supporting both I2C and DDC, used in e.g. the U300 series
1027 This driver can also be built as a module. If so, the module
1028 will be called i2c-stu300.
1030 config I2C_SUN6I_P2WI
1031 tristate "Allwinner sun6i internal P2WI controller"
1032 depends on RESET_CONTROLLER
1033 depends on MACH_SUN6I || COMPILE_TEST
1035 If you say yes to this option, support will be included for the
1036 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1038 The P2WI looks like an SMBus controller (which supports only byte
1039 accesses), except that it only supports one slave device.
1040 This interface is used to connect to specific PMIC devices (like the
1043 config I2C_SYNQUACER
1044 tristate "Socionext SynQuacer I2C controller"
1045 depends on ARCH_SYNQUACER || COMPILE_TEST
1047 Say Y here to include support for the I2C controller used in some
1048 Fujitsu and Socionext SoCs.
1050 This driver can also be built as a module. If so, the module
1051 will be called i2c-synquacer.
1054 tristate "NVIDIA Tegra internal I2C controller"
1055 depends on ARCH_TEGRA
1057 If you say yes to this option, support will be included for the
1058 I2C controller embedded in NVIDIA Tegra SOCs
1060 config I2C_TEGRA_BPMP
1061 tristate "NVIDIA Tegra BPMP I2C controller"
1062 depends on TEGRA_BPMP
1065 If you say yes to this option, support will be included for the I2C
1066 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1068 This I2C driver is a 'virtual' I2C driver. The real driver is part
1069 of the BPMP firmware, and this driver merely communicates with that
1073 tristate "UniPhier FIFO-less I2C controller"
1074 depends on ARCH_UNIPHIER || COMPILE_TEST
1076 If you say yes to this option, support will be included for
1077 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1078 or older UniPhier SoCs.
1080 config I2C_UNIPHIER_F
1081 tristate "UniPhier FIFO-builtin I2C controller"
1082 depends on ARCH_UNIPHIER || COMPILE_TEST
1084 If you say yes to this option, support will be included for
1085 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1086 PH1-Pro5, or newer UniPhier SoCs.
1088 config I2C_VERSATILE
1089 tristate "ARM Versatile/Realview I2C bus support"
1090 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1093 Say yes if you want to support the I2C serial bus on ARMs Versatile
1096 This driver can also be built as a module. If so, the module
1097 will be called i2c-versatile.
1100 tristate "Wondermedia WM8xxx SoC I2C bus support"
1101 depends on ARCH_VT8500
1103 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1106 This driver can also be built as a module. If so, the module will be
1110 tristate "Cavium OCTEON I2C bus support"
1111 depends on CAVIUM_OCTEON_SOC
1113 Say yes if you want to support the I2C serial bus on Cavium
1116 This driver can also be built as a module. If so, the module
1117 will be called i2c-octeon.
1120 tristate "Cavium ThunderX I2C bus support"
1121 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1124 Say yes if you want to support the I2C serial bus on Cavium
1127 This driver can also be built as a module. If so, the module
1128 will be called i2c-thunderx.
1131 tristate "Xilinx I2C Controller"
1132 depends on HAS_IOMEM
1134 If you say yes to this option, support will be included for the
1135 Xilinx I2C controller.
1137 This driver can also be built as a module. If so, the module
1138 will be called xilinx_i2c.
1141 tristate "Netlogic XLR and Sigma Designs I2C support"
1142 depends on CPU_XLR || ARCH_TANGO
1144 This driver enables support for the on-chip I2C interface of
1145 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1147 This driver can also be built as a module. If so, the module
1148 will be called i2c-xlr.
1151 tristate "XLP9XX I2C support"
1152 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1154 This driver enables support for the on-chip I2C interface of
1155 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1157 This driver can also be built as a module. If so, the module will
1158 be called i2c-xlp9xx.
1161 tristate "Renesas R-Car I2C Controller"
1162 depends on ARCH_RENESAS || COMPILE_TEST
1165 If you say yes to this option, support will be included for the
1166 R-Car I2C controller.
1168 This driver can also be built as a module. If so, the module
1169 will be called i2c-rcar.
1171 comment "External I2C/SMBus adapter drivers"
1173 config I2C_DIOLAN_U2C
1174 tristate "Diolan U2C-12 USB adapter"
1177 If you say yes to this option, support will be included for Diolan
1178 U2C-12, a USB to I2C interface.
1180 This driver can also be built as a module. If so, the module
1181 will be called i2c-diolan-u2c.
1184 tristate "Diolan DLN-2 USB I2C adapter"
1187 If you say yes to this option, support will be included for Diolan
1188 DLN2, a USB to I2C interface.
1190 This driver can also be built as a module. If so, the module
1191 will be called i2c-dln2.
1194 tristate "Parallel port adapter"
1199 This supports parallel port I2C adapters such as the ones made by
1200 Philips or Velleman, Analog Devices evaluation boards, and more.
1201 Basically any adapter using the parallel port as an I2C bus with
1202 no extra chipset is supported by this driver, or could be.
1204 This driver is a replacement for (and was inspired by) an older
1205 driver named i2c-philips-par. The new driver supports more devices,
1206 and makes it easier to add support for new devices.
1208 An adapter type parameter is now mandatory. Please read the file
1209 Documentation/i2c/busses/i2c-parport for details.
1211 Another driver exists, named i2c-parport-light, which doesn't depend
1212 on the parport driver. This is meant for embedded systems. Don't say
1213 Y here if you intend to say Y or M there.
1215 This support is also available as a module. If so, the module
1216 will be called i2c-parport.
1218 config I2C_PARPORT_LIGHT
1219 tristate "Parallel port adapter (light)"
1223 This supports parallel port I2C adapters such as the ones made by
1224 Philips or Velleman, Analog Devices evaluation boards, and more.
1225 Basically any adapter using the parallel port as an I2C bus with
1226 no extra chipset is supported by this driver, or could be.
1228 This driver is a light version of i2c-parport. It doesn't depend
1229 on the parport driver, and uses direct I/O access instead. This
1230 might be preferred on embedded systems where wasting memory for
1231 the clean but heavy parport handling is not an option. The
1232 drawback is a reduced portability and the impossibility to
1233 daisy-chain other parallel port devices.
1235 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1236 both is possible but both modules should not be loaded at the same
1239 This support is also available as a module. If so, the module
1240 will be called i2c-parport-light.
1242 config I2C_ROBOTFUZZ_OSIF
1243 tristate "RobotFuzz Open Source InterFace USB adapter"
1246 If you say yes to this option, support will be included for the
1247 RobotFuzz Open Source InterFace USB to I2C interface.
1249 This driver can also be built as a module. If so, the module
1250 will be called i2c-osif.
1253 tristate "TAOS evaluation module"
1256 select SERIO_SERPORT
1259 This supports TAOS evaluation modules on serial port. In order to
1260 use this driver, you will need the inputattach tool, which is part
1261 of the input-utils package.
1265 This support is also available as a module. If so, the module
1266 will be called i2c-taos-evm.
1269 tristate "Tiny-USB adapter"
1272 If you say yes to this option, support will be included for the
1273 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1274 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1276 This driver can also be built as a module. If so, the module
1277 will be called i2c-tiny-usb.
1279 config I2C_VIPERBOARD
1280 tristate "Viperboard I2C master support"
1281 depends on MFD_VIPERBOARD && USB
1283 Say yes here to access the I2C part of the Nano River
1284 Technologies Viperboard as I2C master.
1285 See viperboard API specification and Nano
1286 River Tech's viperboard.h for detailed meaning
1287 of the module parameters.
1289 comment "Other I2C/SMBus bus drivers"
1292 tristate "Acorn IOC/IOMD I2C bus support"
1293 depends on ARCH_ACORN
1297 Say yes if you want to support the I2C bus on Acorn platforms.
1299 If you don't know, say Y.
1302 tristate "Elektor ISA card"
1303 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1306 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1309 This support is also available as a module. If so, the module
1310 will be called i2c-elektor.
1313 tristate "Mellanox I2C driver"
1316 This exposes the Mellanox platform I2C busses to the linux I2C layer
1317 for X86 based systems.
1318 Controller is implemented as CPLD logic.
1320 This driver can also be built as a module. If so, the module will be
1321 called as i2c-mlxcpld.
1324 tristate "PCA9564/PCA9665 on an ISA bus"
1329 This driver supports ISA boards using the Philips PCA9564/PCA9665
1330 parallel bus to I2C bus controller.
1332 This driver can also be built as a module. If so, the module
1333 will be called i2c-pca-isa.
1335 This device is almost undetectable and using this driver on a
1336 system which doesn't have this device will result in long
1337 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1338 time). If unsure, say N.
1341 tristate "SiByte SMBus interface"
1342 depends on SIBYTE_SB1xxx_SOC
1344 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1346 config I2C_CROS_EC_TUNNEL
1347 tristate "ChromeOS EC tunnel I2C bus"
1348 depends on MFD_CROS_EC
1350 If you say yes here you get an I2C bus that will tunnel i2c commands
1351 through to the other side of the ChromeOS EC to the i2c bus
1352 connected there. This will work whatever the interface used to
1353 talk to the EC (SPI, I2C or LPC).
1355 config I2C_XGENE_SLIMPRO
1356 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1357 depends on ARCH_XGENE && MAILBOX
1359 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1360 co-processor. The I2C device access the I2C bus via the X-Gene
1361 to SLIMpro (On chip coprocessor) mailbox mechanism.
1365 tristate "Geode ACCESS.bus support"
1366 depends on X86_32 && PCI
1368 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1369 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1371 If you don't know what to do here, say N.
1373 This support is also available as a module. If so, the module
1374 will be called scx200_acb.
1377 tristate "IBM OPAL I2C driver"
1378 depends on PPC_POWERNV
1381 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1382 the driver is based on the OPAL interfaces.
1384 This driver can also be built as a module. If so, the module will be
1388 tristate "ZTE ZX2967 I2C support"
1392 Selecting this option will add ZX2967 I2C driver.
1393 This driver can also be built as a module. If so, the module will be
1397 tristate "FSI I2C driver"
1400 Driver for FSI bus attached I2C masters. These are I2C masters that
1401 are connected to the system over an FSI bus, instead of the more
1402 common PCI or MMIO interface.
1404 This driver can also be built as a module. If so, the module will be