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)
150 This driver can also be built as a module. If so, the module
151 will be called i2c-i801.
154 tristate "Intel SCH SMBus 1.0"
158 Say Y here if you want to use SMBus controller on the Intel SCH
161 This driver can also be built as a module. If so, the module
162 will be called i2c-isch.
165 tristate "Intel iSMT SMBus Controller"
166 depends on PCI && X86
168 If you say yes to this option, support will be included for the Intel
169 iSMT SMBus host controller interface.
171 This driver can also be built as a module. If so, the module will be
175 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
178 If you say yes to this option, support will be included for the Intel
179 PIIX4 family of mainboard I2C interfaces. Specifically, the following
180 versions of the chipset are supported (note that Serverworks is part
201 Some AMD chipsets contain two PIIX4-compatible SMBus
202 controllers. This driver will attempt to use both controllers
203 on the SB700/SP5100, if they have been initialized by the BIOS.
205 This driver can also be built as a module. If so, the module
206 will be called i2c-piix4.
209 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
210 depends on INTEL_SOC_PMIC_CHTWC
212 If you say yes to this option, support will be included for the
213 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
214 found on some Intel Cherry Trail systems.
216 Note this controller is hooked up to a TI bq24292i charger-IC,
217 combined with a FUSB302 Type-C port-controller as such it is advised
218 to also select CONFIG_TYPEC_FUSB302=m.
221 tristate "Nvidia nForce2, nForce3 and nForce4"
224 If you say yes to this option, support will be included for the Nvidia
225 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
227 This driver can also be built as a module. If so, the module
228 will be called i2c-nforce2.
230 config I2C_NFORCE2_S4985
231 tristate "SMBus multiplexing on the Tyan S4985"
232 depends on I2C_NFORCE2 && X86
234 Enabling this option will add specific SMBus support for the Tyan
235 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
236 over 4 different channels, where the various memory module EEPROMs
237 live. Saying yes here will give you access to these in addition
240 This driver can also be built as a module. If so, the module
241 will be called i2c-nforce2-s4985.
243 config I2C_NVIDIA_GPU
244 tristate "NVIDIA GPU I2C controller"
247 If you say yes to this option, support will be included for the
248 NVIDIA GPU I2C controller which is used to communicate with the GPU's
249 Type-C controller. This driver can also be built as a module called
256 If you say yes to this option, support will be included for the
257 SiS5595 SMBus (a subset of I2C) interface.
259 This driver can also be built as a module. If so, the module
260 will be called i2c-sis5595.
263 tristate "SiS 630/730/964"
266 If you say yes to this option, support will be included for the
267 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
269 This driver can also be built as a module. If so, the module
270 will be called i2c-sis630.
276 If you say yes to this option, support will be included for the SiS
277 96x SMBus (a subset of I2C) interfaces. Specifically, the following
278 chipsets are supported:
287 This driver can also be built as a module. If so, the module
288 will be called i2c-sis96x.
291 tristate "VIA VT82C586B"
295 If you say yes to this option, support will be included for the VIA
296 82C586B I2C interface
298 This driver can also be built as a module. If so, the module
299 will be called i2c-via.
302 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
305 If you say yes to this option, support will be included for the VIA
306 VT82C596 and later SMBus interface. Specifically, the following
307 chipsets are supported:
320 This driver can also be built as a module. If so, the module
321 will be called i2c-viapro.
325 comment "ACPI drivers"
328 tristate "SMBus Control Method Interface"
330 This driver supports the SMBus Control Method Interface. It needs the
331 BIOS to declare ACPI control methods as described in the SMBus Control
332 Method Interface specification.
334 To compile this driver as a module, choose M here:
335 the module will be called i2c-scmi.
339 comment "Mac SMBus host controller drivers"
340 depends on PPC_CHRP || PPC_PMAC
343 tristate "CHRP Apple Hydra Mac I/O I2C interface"
344 depends on PCI && PPC_CHRP
347 This supports the use of the I2C interface in the Apple Hydra Mac
348 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
351 This support is also available as a module. If so, the module
352 will be called i2c-hydra.
355 tristate "Powermac I2C interface"
359 This exposes the various PowerMac i2c interfaces to the linux i2c
360 layer and to userland. It is used by various drivers on the PowerMac
361 platform, and should generally be enabled.
363 This support is also available as a module. If so, the module
364 will be called i2c-powermac.
366 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
369 tristate "Altera Soft IP I2C"
370 depends on ARCH_SOCFPGA || NIOS2 || COMPILE_TEST
373 If you say yes to this option, support will be included for the
374 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
376 This driver can also be built as a module. If so, the module
377 will be called i2c-altera.
380 tristate "Aspeed I2C Controller"
381 depends on ARCH_ASPEED || COMPILE_TEST
383 If you say yes to this option, support will be included for the
384 Aspeed I2C controller.
386 This driver can also be built as a module. If so, the module
387 will be called i2c-aspeed.
390 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
391 depends on ARCH_AT91 || COMPILE_TEST
393 This supports the use of the I2C interface on Atmel AT91
396 A serious problem is that there is no documented way to issue
397 repeated START conditions for more than two messages, as needed
398 to support combined I2C messages. Use the i2c-gpio driver
399 unless your system can cope with this limitation.
401 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
402 don't have clock stretching in transmission mode. For that reason,
403 you can encounter underrun issues causing premature stop sendings if
404 the latency to fill the transmission register is too long. If you
405 are facing this situation, use the i2c-gpio driver.
407 config I2C_AT91_SLAVE_EXPERIMENTAL
408 tristate "Microchip AT91 I2C experimental slave mode"
412 If you say yes to this option, support for the slave mode will be
413 added. Caution: do not use it for production. This feature has not
414 been tested in a heavy way, help wanted.
415 There are known bugs:
416 - It can hang, on a SAMA5D4, after several transfers.
417 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
421 tristate "Au1550/Au1200/Au1300 SMBus interface"
422 depends on MIPS_ALCHEMY
424 If you say yes to this option, support will be included for the
425 Au1550/Au1200/Au1300 SMBus interface.
427 This driver can also be built as a module. If so, the module
428 will be called i2c-au1550.
431 tristate "Axxia I2C controller"
432 depends on ARCH_AXXIA || COMPILE_TEST
436 Say yes if you want to support the I2C bus on Axxia platforms.
438 Please note that this controller is limited to transfers of maximum
439 255 bytes in length. Any attempt to to a larger transfer will return
443 tristate "Broadcom BCM2835 I2C controller"
444 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
445 depends on COMMON_CLK
447 If you say yes to this option, support will be included for the
448 BCM2835 I2C controller.
450 If you don't know what to do here, say N.
452 This support is also available as a module. If so, the module
453 will be called i2c-bcm2835.
456 tristate "Broadcom iProc I2C controller"
457 depends on ARCH_BCM_IPROC || COMPILE_TEST
458 default ARCH_BCM_IPROC
461 If you say yes to this option, support will be included for the
462 Broadcom iProc I2C controller.
464 If you don't know what to do here, say N.
467 tristate "BCM Kona I2C adapter"
468 depends on ARCH_BCM_MOBILE || COMPILE_TEST
469 default y if ARCH_BCM_MOBILE
471 If you say yes to this option, support will be included for the
472 I2C interface on the Broadcom Kona family of processors.
474 If you do not need KONA I2C interface, say N.
477 tristate "BRCM Settop/DSL I2C controller"
478 depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
479 ARCH_BCM_63XX || COMPILE_TEST
482 If you say yes to this option, support will be included for the
483 I2C interface on the Broadcom Settop/DSL SoCs.
485 If you do not need I2C interface, say N.
488 tristate "Cadence I2C Controller"
489 depends on ARCH_ZYNQ || ARM64 || XTENSA
491 Say yes here to select Cadence I2C Host Controller. This controller is
492 e.g. used by Xilinx Zynq.
495 tristate "CBUS I2C driver"
496 depends on GPIOLIB || COMPILE_TEST
498 Support for CBUS access using I2C API. Mostly relevant for Nokia
499 Internet Tablets (770, N800 and N810).
501 This driver can also be built as a module. If so, the module
502 will be called i2c-cbus-gpio.
505 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
506 depends on CPM1 || CPM2
508 This supports the use of the I2C interface on Freescale
509 processors with CPM1 or CPM2.
511 This driver can also be built as a module. If so, the module
512 will be called i2c-cpm.
515 tristate "DaVinci I2C driver"
516 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
518 Support for TI DaVinci I2C controller driver.
520 This driver can also be built as a module. If so, the module
521 will be called i2c-davinci.
523 Please note that this driver might be needed to bring up other
524 devices such as DaVinci NIC.
525 For details please see http://www.ti.com/davinci
527 config I2C_DESIGNWARE_CORE
530 config I2C_DESIGNWARE_SLAVE
531 bool "Synopsys DesignWare Slave"
534 If you say yes to this option, support will be included for the
535 Synopsys DesignWare I2C slave adapter.
537 This is not a standalone module, this module compiles together with
540 config I2C_DESIGNWARE_PLATFORM
541 tristate "Synopsys DesignWare Platform"
542 select I2C_DESIGNWARE_CORE
543 depends on (ACPI && COMMON_CLK) || !ACPI
545 If you say yes to this option, support will be included for the
546 Synopsys DesignWare I2C adapter.
548 This driver can also be built as a module. If so, the module
549 will be called i2c-designware-platform.
551 config I2C_DESIGNWARE_PCI
552 tristate "Synopsys DesignWare PCI"
554 select I2C_DESIGNWARE_CORE
556 If you say yes to this option, support will be included for the
557 Synopsys DesignWare I2C adapter. Only master mode is supported.
559 This driver can also be built as a module. If so, the module
560 will be called i2c-designware-pci.
562 config I2C_DESIGNWARE_BAYTRAIL
563 bool "Intel Baytrail I2C semaphore support"
565 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
566 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
568 This driver enables managed host access to the PMIC I2C bus on select
569 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
570 the host to request uninterrupted access to the PMIC's I2C bus from
571 the platform firmware controlling it. You should say Y if running on
572 a BayTrail system using the AXP288.
575 tristate "Conexant Digicolor I2C driver"
576 depends on ARCH_DIGICOLOR || COMPILE_TEST
578 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
580 This driver can also be built as a module. If so, the module
581 will be called i2c-digicolor.
584 tristate "EFM32 I2C controller"
585 depends on ARCH_EFM32 || COMPILE_TEST
587 This driver supports the i2c block found in Energy Micro's EFM32
591 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
592 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
594 This driver is for PCH(Platform controller Hub) I2C of EG20T which
595 is an IOH(Input/Output Hub) for x86 embedded processor.
596 This driver can access PCH I2C bus device.
598 This driver also can be used for LAPIS Semiconductor IOH(Input/
599 Output Hub), ML7213, ML7223 and ML7831.
600 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
601 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
602 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
603 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
606 tristate "EMMA Mobile series I2C adapter"
610 If you say yes to this option, support will be included for the
611 I2C interface on the Renesas Electronics EM/EV family of processors.
614 tristate "Exynos high-speed I2C driver"
616 depends on ARCH_EXYNOS || COMPILE_TEST
617 default y if ARCH_EXYNOS
619 High-speed I2C controller on Exynos5 and newer Samsung SoCs.
622 tristate "GPIO-based bitbanging I2C"
623 depends on GPIOLIB || COMPILE_TEST
626 This is a very simple bitbanging I2C driver utilizing the
627 arch-neutral GPIO API to control the SCL and SDA lines.
629 config I2C_GPIO_FAULT_INJECTOR
630 bool "GPIO-based fault injector"
633 This adds some functionality to the i2c-gpio driver which can inject
634 faults to an I2C bus, so another bus master can be stress-tested.
635 This is for debugging. If unsure, say 'no'.
637 config I2C_HIGHLANDER
638 tristate "Highlander FPGA SMBus interface"
639 depends on SH_HIGHLANDER || COMPILE_TEST
641 If you say yes to this option, support will be included for
642 the SMBus interface located in the FPGA on various Highlander
643 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
644 FPGAs. This is wholly unrelated to the SoC I2C.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-highlander.
650 tristate "IBM PPC 4xx on-chip I2C interface"
653 Say Y here if you want to use IIC peripheral found on
654 embedded IBM PPC 4xx based systems.
656 This driver can also be built as a module. If so, the module
657 will be called i2c-ibm_iic.
660 tristate "Imagination Technologies I2C SCB Controller"
661 depends on MIPS || COMPILE_TEST
663 Say Y here if you want to use the IMG I2C SCB controller,
664 available on the TZ1090 and other IMG SoCs.
666 This driver can also be built as a module. If so, the module
667 will be called i2c-img-scb.
670 tristate "IMX I2C interface"
671 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
673 Say Y here if you want to use the IIC bus controller on
674 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
676 This driver can also be built as a module. If so, the module
677 will be called i2c-imx.
680 tristate "IMX Low Power I2C interface"
681 depends on ARCH_MXC || COMPILE_TEST
683 Say Y here if you want to use the Low Power IIC bus controller
684 on the Freescale i.MX processors.
686 This driver can also be built as a module. If so, the module
687 will be called i2c-imx-lpi2c.
690 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
691 depends on ARCH_IOP32X || ARCH_IXP4XX || COMPILE_TEST
693 Say Y here if you want to use the IIC bus controller on
694 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
696 This driver can also be built as a module. If so, the module
697 will be called i2c-iop3xx.
700 tristate "JZ4780 I2C controller interface support"
701 depends on MIPS || COMPILE_TEST
703 If you say yes to this option, support will be included for the
704 Ingenic JZ4780 I2C controller.
706 If you don't know what to do here, say N.
709 tristate "Kontron COM I2C Controller"
710 depends on MFD_KEMPLD
712 This enables support for the I2C bus interface on some Kontron ETX
713 and COMexpress (ETXexpress) modules.
715 This driver can also be built as a module. If so, the module
716 will be called i2c-kempld.
719 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
720 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
722 This driver supports the I2C interface found several NXP
723 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
725 This driver can also be built as a module. If so, the module
726 will be called i2c-lpc2k.
729 tristate "Amlogic Meson I2C controller"
730 depends on ARCH_MESON || COMPILE_TEST
731 depends on COMMON_CLK
733 If you say yes to this option, support will be included for the
734 I2C interface on the Amlogic Meson family of SoCs.
737 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
740 If you say yes to this option, support will be included for the
741 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
742 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
744 This driver can also be built as a module. If so, the module
745 will be called i2c-mpc.
748 tristate "MediaTek I2C adapter"
749 depends on ARCH_MEDIATEK || COMPILE_TEST
751 This selects the MediaTek(R) Integrated Inter Circuit bus driver
752 for MT65xx and MT81xx.
753 If you want to use MediaTek(R) I2C interface, say Y or M here.
757 tristate "MT7621/MT7628 I2C Controller"
758 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
760 Say Y here to include support for I2C controller in the
761 MediaTek MT7621/MT7628 SoCs.
764 tristate "Marvell mv64xxx I2C Controller"
765 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
767 If you say yes to this option, support will be included for the
768 built-in I2C interface on the Marvell 64xxx line of host bridges.
769 This driver is also used for Allwinner SoCs I2C controllers.
771 This driver can also be built as a module. If so, the module
772 will be called i2c-mv64xxx.
775 tristate "Freescale i.MX28 I2C interface"
776 depends on SOC_IMX28 || COMPILE_TEST
779 Say Y here if you want to use the I2C bus controller on
780 the Freescale i.MX28 processors.
782 This driver can also be built as a module. If so, the module
783 will be called i2c-mxs.
786 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
789 If you say yes to this option, support will be included for the
790 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
791 as well as the STA2X11 PCIe I/O HUB.
794 tristate "OpenCores I2C Controller"
796 If you say yes to this option, support will be included for the
797 OpenCores I2C controller. For details see
798 http://www.opencores.org/projects.cgi/web/i2c/overview
800 This driver can also be built as a module. If so, the module
801 will be called i2c-ocores.
804 tristate "OMAP I2C adapter"
805 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
806 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
808 If you say yes to this option, support will be included for the
809 I2C interface on the Texas Instruments OMAP1/2 family of processors.
810 Like OMAP1510/1610/1710/5912 and OMAP242x.
811 For details see http://www.ti.com/omap.
814 tristate "Actions Semiconductor Owl I2C Controller"
815 depends on ARCH_ACTIONS || COMPILE_TEST
817 Say Y here if you want to use the I2C bus controller on
818 the Actions Semiconductor Owl SoC's.
821 tristate "PA Semi SMBus interface"
822 depends on PPC_PASEMI && PCI
824 Supports the PA Semi PWRficient on-chip SMBus interfaces.
826 config I2C_PCA_PLATFORM
827 tristate "PCA9564/PCA9665 as platform device"
831 This driver supports a memory mapped Philips PCA9564/PCA9665
832 parallel bus to I2C bus controller.
834 This driver can also be built as a module. If so, the module
835 will be called i2c-pca-platform.
838 tristate "PMC MSP I2C TWI Controller"
839 depends on PMC_MSP || COMPILE_TEST
841 This driver supports the PMC TWI controller on MSP devices.
843 This driver can also be built as module. If so, the module
844 will be called i2c-pmcmsp.
847 tristate "I2C bus support for Philips PNX and NXP LPC targets"
848 depends on ARCH_LPC32XX || COMPILE_TEST
850 This driver supports the Philips IP3204 I2C IP block master and/or
853 This driver can also be built as a module. If so, the module
854 will be called i2c-pnx.
857 tristate "PKUnity v3 I2C bus support"
858 depends on UNICORE32 && ARCH_PUV3
861 This driver supports the I2C IP inside the PKUnity-v3 SoC.
862 This I2C bus controller is under AMBA/AXI bus.
864 This driver can also be built as a module. If so, the module
865 will be called i2c-puv3.
868 tristate "Intel PXA2XX I2C adapter"
869 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
871 If you have devices in the PXA I2C bus, say yes to this option.
872 This driver can also be built as a module. If so, the module
873 will be called i2c-pxa.
876 def_bool I2C_PXA && X86_32 && PCI && OF
879 bool "Intel PXA2XX I2C Slave comms support"
880 depends on I2C_PXA && !X86_32
883 Support I2C slave mode communications on the PXA I2C bus. This
884 is necessary for systems where the PXA may be a target on the
888 tristate "Qualcomm Camera Control Interface"
889 depends on ARCH_QCOM || COMPILE_TEST
891 If you say yes to this option, support will be included for the
892 built-in camera control interface on the Qualcomm SoCs.
894 This driver can also be built as a module. If so, the module
895 will be called i2c-qcom-cci.
898 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
899 depends on ARCH_QCOM || COMPILE_TEST
900 depends on QCOM_GENI_SE
902 This driver supports GENI serial engine based I2C controller in
903 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
904 yes to this option, support will be included for the built-in I2C
905 interface on the Qualcomm Technologies Inc.'s SoCs.
907 This driver can also be built as a module. If so, the module
908 will be called i2c-qcom-geni.
911 tristate "Qualcomm QUP based I2C controller"
914 If you say yes to this option, support will be included for the
915 built-in I2C interface on the Qualcomm SoCs.
917 This driver can also be built as a module. If so, the module
918 will be called i2c-qup.
921 tristate "Renesas RIIC adapter"
922 depends on ARCH_RENESAS || COMPILE_TEST
924 If you say yes to this option, support will be included for the
925 Renesas RIIC I2C interface.
927 This driver can also be built as a module. If so, the module
928 will be called i2c-riic.
931 tristate "Rockchip RK3xxx I2C adapter"
932 depends on OF && COMMON_CLK
934 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
937 This driver can also be built as a module. If so, the module will
940 config HAVE_S3C2410_I2C
943 This will include I2C support for Samsung SoCs. If you want to
944 include I2C support for any machine, kindly select this in the
945 respective Kconfig file.
948 tristate "S3C/Exynos I2C Driver"
949 depends on HAVE_S3C2410_I2C || COMPILE_TEST
951 Say Y here to include support for I2C controller in the
952 Samsung SoCs (S3C, S5Pv210, Exynos).
955 tristate "Renesas SH7760 I2C Controller"
956 depends on CPU_SUBTYPE_SH7760
958 This driver supports the 2 I2C interfaces on the Renesas SH7760.
960 This driver can also be built as a module. If so, the module
961 will be called i2c-sh7760.
964 tristate "SuperH Mobile I2C Controller"
965 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
967 If you say yes to this option, support will be included for the
968 built-in I2C interface on the Renesas SH-Mobile processor.
970 This driver can also be built as a module. If so, the module
971 will be called i2c-sh_mobile.
974 tristate "Simtec Generic I2C interface"
977 If you say yes to this option, support will be included for
978 the Simtec Generic I2C interface. This driver is for the
979 simple I2C bus used on newer Simtec products for general
980 I2C, such as DDC on the Simtec BBD2016A.
982 This driver can also be built as a module. If so, the module
983 will be called i2c-simtec.
986 tristate "CSR SiRFprimaII I2C interface"
987 depends on ARCH_SIRF || COMPILE_TEST
989 If you say yes to this option, support will be included for the
990 CSR SiRFprimaII I2C interface.
992 This driver can also be built as a module. If so, the module
993 will be called i2c-sirf.
996 tristate "Spreadtrum I2C interface"
997 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
999 If you say yes to this option, support will be included for the
1000 Spreadtrum I2C interface.
1003 tristate "STMicroelectronics SSC I2C support"
1004 depends on ARCH_STI || COMPILE_TEST
1006 Enable this option to add support for STMicroelectronics SoCs
1007 hardware SSC (Synchronous Serial Controller) as an I2C controller.
1009 This driver can also be built as module. If so, the module
1010 will be called i2c-st.
1013 tristate "STMicroelectronics STM32F4 I2C support"
1014 depends on ARCH_STM32 || COMPILE_TEST
1016 Enable this option to add support for STM32 I2C controller embedded
1019 This driver can also be built as module. If so, the module
1020 will be called i2c-stm32f4.
1023 tristate "STMicroelectronics STM32F7 I2C support"
1024 depends on ARCH_STM32 || COMPILE_TEST
1027 Enable this option to add support for STM32 I2C controller embedded
1030 This driver can also be built as module. If so, the module
1031 will be called i2c-stm32f7.
1034 tristate "ST Microelectronics DDC I2C interface"
1035 depends on MACH_U300 || COMPILE_TEST
1036 default y if MACH_U300
1038 If you say yes to this option, support will be included for the
1039 I2C interface from ST Microelectronics simply called "DDC I2C"
1040 supporting both I2C and DDC, used in e.g. the U300 series
1043 This driver can also be built as a module. If so, the module
1044 will be called i2c-stu300.
1046 config I2C_SUN6I_P2WI
1047 tristate "Allwinner sun6i internal P2WI controller"
1048 depends on RESET_CONTROLLER
1049 depends on MACH_SUN6I || COMPILE_TEST
1051 If you say yes to this option, support will be included for the
1052 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1054 The P2WI looks like an SMBus controller (which supports only byte
1055 accesses), except that it only supports one slave device.
1056 This interface is used to connect to specific PMIC devices (like the
1059 config I2C_SYNQUACER
1060 tristate "Socionext SynQuacer I2C controller"
1061 depends on ARCH_SYNQUACER || COMPILE_TEST
1063 Say Y here to include support for the I2C controller used in some
1064 Fujitsu and Socionext SoCs.
1066 This driver can also be built as a module. If so, the module
1067 will be called i2c-synquacer.
1070 tristate "NVIDIA Tegra internal I2C controller"
1071 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1072 # COMPILE_TEST needs architectures with readsX()/writesX() primitives
1074 If you say yes to this option, support will be included for the
1075 I2C controller embedded in NVIDIA Tegra SOCs
1077 config I2C_TEGRA_BPMP
1078 tristate "NVIDIA Tegra BPMP I2C controller"
1079 depends on TEGRA_BPMP || COMPILE_TEST
1080 default y if TEGRA_BPMP
1082 If you say yes to this option, support will be included for the I2C
1083 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1085 This I2C driver is a 'virtual' I2C driver. The real driver is part
1086 of the BPMP firmware, and this driver merely communicates with that
1090 tristate "UniPhier FIFO-less I2C controller"
1091 depends on ARCH_UNIPHIER || COMPILE_TEST
1093 If you say yes to this option, support will be included for
1094 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1095 or older UniPhier SoCs.
1097 config I2C_UNIPHIER_F
1098 tristate "UniPhier FIFO-builtin I2C controller"
1099 depends on ARCH_UNIPHIER || COMPILE_TEST
1101 If you say yes to this option, support will be included for
1102 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1103 PH1-Pro5, or newer UniPhier SoCs.
1105 config I2C_VERSATILE
1106 tristate "ARM Versatile/Realview I2C bus support"
1107 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1110 Say yes if you want to support the I2C serial bus on ARMs Versatile
1113 This driver can also be built as a module. If so, the module
1114 will be called i2c-versatile.
1117 tristate "Wondermedia WM8xxx SoC I2C bus support"
1118 depends on ARCH_VT8500 || COMPILE_TEST
1120 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1123 This driver can also be built as a module. If so, the module will be
1127 tristate "Cavium OCTEON I2C bus support"
1128 depends on CAVIUM_OCTEON_SOC
1130 Say yes if you want to support the I2C serial bus on Cavium
1133 This driver can also be built as a module. If so, the module
1134 will be called i2c-octeon.
1137 tristate "Cavium ThunderX I2C bus support"
1138 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1141 Say yes if you want to support the I2C serial bus on Cavium
1144 This driver can also be built as a module. If so, the module
1145 will be called i2c-thunderx.
1148 tristate "Xilinx I2C Controller"
1149 depends on HAS_IOMEM
1151 If you say yes to this option, support will be included for the
1152 Xilinx I2C controller.
1154 This driver can also be built as a module. If so, the module
1155 will be called xilinx_i2c.
1158 tristate "Netlogic XLR and Sigma Designs I2C support"
1159 depends on CPU_XLR || ARCH_TANGO || COMPILE_TEST
1161 This driver enables support for the on-chip I2C interface of
1162 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1164 This driver can also be built as a module. If so, the module
1165 will be called i2c-xlr.
1168 tristate "XLP9XX I2C support"
1169 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1171 This driver enables support for the on-chip I2C interface of
1172 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1174 This driver can also be built as a module. If so, the module will
1175 be called i2c-xlp9xx.
1178 tristate "Renesas R-Car I2C Controller"
1179 depends on ARCH_RENESAS || COMPILE_TEST
1182 If you say yes to this option, support will be included for the
1183 R-Car I2C controller.
1185 This driver can also be built as a module. If so, the module
1186 will be called i2c-rcar.
1188 comment "External I2C/SMBus adapter drivers"
1190 config I2C_DIOLAN_U2C
1191 tristate "Diolan U2C-12 USB adapter"
1194 If you say yes to this option, support will be included for Diolan
1195 U2C-12, a USB to I2C interface.
1197 This driver can also be built as a module. If so, the module
1198 will be called i2c-diolan-u2c.
1201 tristate "Diolan DLN-2 USB I2C adapter"
1204 If you say yes to this option, support will be included for Diolan
1205 DLN2, a USB to I2C interface.
1207 This driver can also be built as a module. If so, the module
1208 will be called i2c-dln2.
1211 tristate "Parallel port adapter"
1216 This supports parallel port I2C adapters such as the ones made by
1217 Philips or Velleman, Analog Devices evaluation boards, and more.
1218 Basically any adapter using the parallel port as an I2C bus with
1219 no extra chipset is supported by this driver, or could be. Please
1220 read the file Documentation/i2c/busses/i2c-parport.rst for details.
1222 This support is also available as a module. If so, the module
1223 will be called i2c-parport.
1225 config I2C_ROBOTFUZZ_OSIF
1226 tristate "RobotFuzz Open Source InterFace USB adapter"
1229 If you say yes to this option, support will be included for the
1230 RobotFuzz Open Source InterFace USB to I2C interface.
1232 This driver can also be built as a module. If so, the module
1233 will be called i2c-osif.
1236 tristate "TAOS evaluation module"
1239 select SERIO_SERPORT
1242 This supports TAOS evaluation modules on serial port. In order to
1243 use this driver, you will need the inputattach tool, which is part
1244 of the input-utils package.
1248 This support is also available as a module. If so, the module
1249 will be called i2c-taos-evm.
1252 tristate "Tiny-USB adapter"
1255 If you say yes to this option, support will be included for the
1256 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1257 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1259 This driver can also be built as a module. If so, the module
1260 will be called i2c-tiny-usb.
1262 config I2C_VIPERBOARD
1263 tristate "Viperboard I2C master support"
1264 depends on MFD_VIPERBOARD && USB
1266 Say yes here to access the I2C part of the Nano River
1267 Technologies Viperboard as I2C master.
1268 See viperboard API specification and Nano
1269 River Tech's viperboard.h for detailed meaning
1270 of the module parameters.
1272 comment "Other I2C/SMBus bus drivers"
1275 tristate "Acorn IOC/IOMD I2C bus support"
1276 depends on ARCH_ACORN
1280 Say yes if you want to support the I2C bus on Acorn platforms.
1282 If you don't know, say Y.
1285 tristate "Elektor ISA card"
1286 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1289 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1292 This support is also available as a module. If so, the module
1293 will be called i2c-elektor.
1296 tristate "ICY Zorro card"
1300 This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1301 Say Y if you own such an adapter.
1303 This support is also available as a module. If so, the module
1304 will be called i2c-icy.
1306 If you have a 2019 edition board with an LTC2990 sensor at address
1307 0x4c, loading the module 'ltc2990' is sufficient to enable it.
1310 tristate "Mellanox I2C driver"
1311 depends on X86_64 || COMPILE_TEST
1313 This exposes the Mellanox platform I2C busses to the linux I2C layer
1314 for X86 based systems.
1315 Controller is implemented as CPLD logic.
1317 This driver can also be built as a module. If so, the module will be
1318 called as i2c-mlxcpld.
1321 tristate "PCA9564/PCA9665 on an ISA bus"
1326 This driver supports ISA boards using the Philips PCA9564/PCA9665
1327 parallel bus to I2C bus controller.
1329 This driver can also be built as a module. If so, the module
1330 will be called i2c-pca-isa.
1332 This device is almost undetectable and using this driver on a
1333 system which doesn't have this device will result in long
1334 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1335 time). If unsure, say N.
1338 tristate "SiByte SMBus interface"
1339 depends on SIBYTE_SB1xxx_SOC
1341 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1343 config I2C_CROS_EC_TUNNEL
1344 tristate "ChromeOS EC tunnel I2C bus"
1347 If you say yes here you get an I2C bus that will tunnel i2c commands
1348 through to the other side of the ChromeOS EC to the i2c bus
1349 connected there. This will work whatever the interface used to
1350 talk to the EC (SPI, I2C or LPC).
1352 config I2C_XGENE_SLIMPRO
1353 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1354 depends on ARCH_XGENE && MAILBOX
1356 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1357 co-processor. The I2C device access the I2C bus via the X-Gene
1358 to SLIMpro (On chip coprocessor) mailbox mechanism.
1362 tristate "Geode ACCESS.bus support"
1363 depends on X86_32 && PCI
1365 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1366 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1368 If you don't know what to do here, say N.
1370 This support is also available as a module. If so, the module
1371 will be called scx200_acb.
1374 tristate "IBM OPAL I2C driver"
1375 depends on PPC_POWERNV
1378 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1379 the driver is based on the OPAL interfaces.
1381 This driver can also be built as a module. If so, the module will be
1385 tristate "ZTE ZX2967 I2C support"
1389 Selecting this option will add ZX2967 I2C driver.
1390 This driver can also be built as a module. If so, the module will be
1394 tristate "FSI I2C driver"
1397 Driver for FSI bus attached I2C masters. These are I2C masters that
1398 are connected to the system over an FSI bus, instead of the more
1399 common PCI or MMIO interface.
1401 This driver can also be built as a module. If so, the module will be