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"
15 A common module to provide an API to instantiate UCSI device
16 for Cypress CCGx Type-C controller. Individual bus drivers
17 need to select this one on demand.
21 depends on PCI && HAS_IOPORT
23 If you say yes to this option, support will be included for the SMB
24 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
25 controller is part of the 7101 device, which is an ACPI-compliant
26 Power Management Unit (PMU).
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1535.
33 depends on PCI && HAS_IOPORT
35 If you say yes to this option, support will be included for the SMB
36 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
37 controller is part of the 7101 device, which is an ACPI-compliant
38 Power Management Unit (PMU).
40 This driver can also be built as a module. If so, the module
41 will be called i2c-ali1563.
45 depends on PCI && HAS_IOPORT
47 If you say yes to this option, support will be included for the
48 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
50 This driver can also be built as a module. If so, the module
51 will be called i2c-ali15x3.
54 tristate "AMD 756/766/768/8111 and nVidia nForce"
55 depends on PCI && HAS_IOPORT
57 If you say yes to this option, support will be included for the AMD
58 756/766/768 mainboard I2C interfaces. The driver also includes
59 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
60 the nVidia nForce I2C interface.
62 This driver can also be built as a module. If so, the module
63 will be called i2c-amd756.
65 config I2C_AMD756_S4882
66 tristate "SMBus multiplexing on the Tyan S4882"
67 depends on I2C_AMD756 && X86
69 Enabling this option will add specific SMBus support for the Tyan
70 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
71 over 8 different channels, where the various memory module EEPROMs
72 and temperature sensors live. Saying yes here will give you access
73 to these in addition to the trunk.
75 This driver can also be built as a module. If so, the module
76 will be called i2c-amd756-s4882.
80 depends on PCI && HAS_IOPORT
82 If you say yes to this option, support will be included for the
83 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
85 This driver can also be built as a module. If so, the module
86 will be called i2c-amd8111.
89 tristate "AMD MP2 PCIe"
90 depends on PCI && ACPI
92 If you say yes to this option, support will be included for the AMD
95 This driver can also be built as modules. If so, the modules will
96 be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
99 tristate "Hix5hd2 high-speed I2C driver"
100 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
102 Say Y here to include support for the high-speed I2C controller
103 used in HiSilicon hix5hd2 SoCs.
105 This driver can also be built as a module. If so, the module
106 will be called i2c-hix5hd2.
109 tristate "Intel 82801 (ICH/PCH)"
110 depends on PCI && HAS_IOPORT
112 select CHECK_SIGNATURE if X86 && DMI
115 If you say yes to this option, support will be included for the Intel
116 801 family of mainboard I2C interfaces. Specifically, the following
117 versions of the chipset are supported:
123 82801EB/ER (ICH5/ICH5R)
160 Meteor Lake (SOC and PCH)
163 This driver can also be built as a module. If so, the module
164 will be called i2c-i801.
168 depends on DMI && I2C_MUX_GPIO
169 depends on !(I2C_I801=y && I2C_MUX=m)
171 Optional support for multiplexed SMBUS on certain systems with
172 more than 8 memory slots.
175 tristate "Intel SCH SMBus 1.0"
176 depends on PCI && HAS_IOPORT
179 Say Y here if you want to use SMBus controller on the Intel SCH
182 This driver can also be built as a module. If so, the module
183 will be called i2c-isch.
186 tristate "Intel iSMT SMBus Controller"
187 depends on PCI && X86
189 If you say yes to this option, support will be included for the Intel
190 iSMT SMBus host controller interface.
192 This driver can also be built as a module. If so, the module will be
196 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
197 depends on PCI && HAS_IOPORT
199 If you say yes to this option, support will be included for the Intel
200 PIIX4 family of mainboard I2C interfaces. Specifically, the following
201 versions of the chipset are supported (note that Serverworks is part
222 Some AMD chipsets contain two PIIX4-compatible SMBus
223 controllers. This driver will attempt to use both controllers
224 on the SB700/SP5100, if they have been initialized by the BIOS.
226 This driver can also be built as a module. If so, the module
227 will be called i2c-piix4.
230 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
231 depends on INTEL_SOC_PMIC_CHTWC
233 If you say yes to this option, support will be included for the
234 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
235 found on some Intel Cherry Trail systems.
237 Note this controller is hooked up to a TI bq24292i charger-IC,
238 combined with a FUSB302 Type-C port-controller as such it is advised
239 to also select CONFIG_TYPEC_FUSB302=m.
242 tristate "Nvidia nForce2, nForce3 and nForce4"
243 depends on PCI && HAS_IOPORT
245 If you say yes to this option, support will be included for the Nvidia
246 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
248 This driver can also be built as a module. If so, the module
249 will be called i2c-nforce2.
251 config I2C_NFORCE2_S4985
252 tristate "SMBus multiplexing on the Tyan S4985"
253 depends on I2C_NFORCE2 && X86
255 Enabling this option will add specific SMBus support for the Tyan
256 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
257 over 4 different channels, where the various memory module EEPROMs
258 live. Saying yes here will give you access to these in addition
261 This driver can also be built as a module. If so, the module
262 will be called i2c-nforce2-s4985.
264 config I2C_NVIDIA_GPU
265 tristate "NVIDIA GPU I2C controller"
269 If you say yes to this option, support will be included for the
270 NVIDIA GPU I2C controller which is used to communicate with the GPU's
271 Type-C controller. This driver can also be built as a module called
276 depends on PCI && HAS_IOPORT
278 If you say yes to this option, support will be included for the
279 SiS5595 SMBus (a subset of I2C) interface.
281 This driver can also be built as a module. If so, the module
282 will be called i2c-sis5595.
285 tristate "SiS 630/730/964"
286 depends on PCI && HAS_IOPORT
288 If you say yes to this option, support will be included for the
289 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
291 This driver can also be built as a module. If so, the module
292 will be called i2c-sis630.
296 depends on PCI && HAS_IOPORT
298 If you say yes to this option, support will be included for the SiS
299 96x SMBus (a subset of I2C) interfaces. Specifically, the following
300 chipsets are supported:
309 This driver can also be built as a module. If so, the module
310 will be called i2c-sis96x.
313 tristate "VIA VT82C586B"
314 depends on PCI && HAS_IOPORT
317 If you say yes to this option, support will be included for the VIA
318 82C586B I2C interface
320 This driver can also be built as a module. If so, the module
321 will be called i2c-via.
324 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
325 depends on PCI && HAS_IOPORT
327 If you say yes to this option, support will be included for the VIA
328 VT82C596 and later SMBus interface. Specifically, the following
329 chipsets are supported:
342 This driver can also be built as a module. If so, the module
343 will be called i2c-viapro.
348 tristate "Zhaoxin I2C Interface"
349 depends on PCI || COMPILE_TEST
351 If you say yes to this option, support will be included for the
352 ZHAOXIN I2C interface
354 This driver can also be built as a module. If so, the module
355 will be called i2c-zhaoxin.
357 comment "ACPI drivers"
360 tristate "SMBus Control Method Interface"
362 This driver supports the SMBus Control Method Interface. It needs the
363 BIOS to declare ACPI control methods as described in the SMBus Control
364 Method Interface specification.
366 To compile this driver as a module, choose M here:
367 the module will be called i2c-scmi.
371 comment "Mac SMBus host controller drivers"
372 depends on PPC_CHRP || PPC_PMAC
375 tristate "CHRP Apple Hydra Mac I/O I2C interface"
376 depends on PCI && PPC_CHRP
379 This supports the use of the I2C interface in the Apple Hydra Mac
380 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
383 This support is also available as a module. If so, the module
384 will be called i2c-hydra.
387 tristate "Powermac I2C interface"
391 This exposes the various PowerMac i2c interfaces to the linux i2c
392 layer and to userland. It is used by various drivers on the PowerMac
393 platform, and should generally be enabled.
395 This support is also available as a module. If so, the module
396 will be called i2c-powermac.
398 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
401 tristate "Altera Soft IP I2C"
402 depends on ARCH_INTEL_SOCFPGA || NIOS2 || COMPILE_TEST
405 If you say yes to this option, support will be included for the
406 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
408 This driver can also be built as a module. If so, the module
409 will be called i2c-altera.
412 tristate "Aspeed I2C Controller"
413 depends on ARCH_ASPEED || COMPILE_TEST
415 If you say yes to this option, support will be included for the
416 Aspeed I2C controller.
418 This driver can also be built as a module. If so, the module
419 will be called i2c-aspeed.
422 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
423 depends on ARCH_AT91 || COMPILE_TEST
425 This supports the use of the I2C interface on Atmel AT91
428 A serious problem is that there is no documented way to issue
429 repeated START conditions for more than two messages, as needed
430 to support combined I2C messages. Use the i2c-gpio driver
431 unless your system can cope with this limitation.
433 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
434 don't have clock stretching in transmission mode. For that reason,
435 you can encounter underrun issues causing premature stop sendings if
436 the latency to fill the transmission register is too long. If you
437 are facing this situation, use the i2c-gpio driver.
439 config I2C_AT91_SLAVE_EXPERIMENTAL
440 tristate "Microchip AT91 I2C experimental slave mode"
444 If you say yes to this option, support for the slave mode will be
445 added. Caution: do not use it for production. This feature has not
446 been tested in a heavy way, help wanted.
447 There are known bugs:
448 - It can hang, on a SAMA5D4, after several transfers.
449 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
453 tristate "Au1550/Au1200/Au1300 SMBus interface"
454 depends on MIPS_ALCHEMY
456 If you say yes to this option, support will be included for the
457 Au1550/Au1200/Au1300 SMBus interface.
459 This driver can also be built as a module. If so, the module
460 will be called i2c-au1550.
463 tristate "Axxia I2C controller"
464 depends on ARCH_AXXIA || COMPILE_TEST
468 Say yes if you want to support the I2C bus on Axxia platforms.
470 Please note that this controller is limited to transfers of maximum
471 255 bytes in length. Any attempt to to a larger transfer will return
475 tristate "Broadcom BCM2835 I2C controller"
476 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
477 depends on COMMON_CLK
479 If you say yes to this option, support will be included for the
480 BCM2835 I2C controller.
482 If you don't know what to do here, say N.
484 This support is also available as a module. If so, the module
485 will be called i2c-bcm2835.
488 tristate "Broadcom iProc I2C controller"
489 depends on ARCH_BCM_IPROC || COMPILE_TEST
490 default ARCH_BCM_IPROC
493 If you say yes to this option, support will be included for the
494 Broadcom iProc I2C controller.
496 If you don't know what to do here, say N.
499 tristate "BCM Kona I2C adapter"
500 depends on ARCH_BCM_MOBILE || COMPILE_TEST
501 default y if ARCH_BCM_MOBILE
503 If you say yes to this option, support will be included for the
504 I2C interface on the Broadcom Kona family of processors.
506 If you do not need KONA I2C interface, say N.
509 tristate "BRCM Settop/DSL I2C controller"
510 depends on ARCH_BCM2835 || ARCH_BCMBCA || ARCH_BRCMSTB || \
511 BMIPS_GENERIC || COMPILE_TEST
514 If you say yes to this option, support will be included for the
515 I2C interface on the Broadcom Settop/DSL SoCs.
517 If you do not need I2C interface, say N.
520 tristate "Cadence I2C Controller"
521 depends on ARCH_ZYNQ || ARM64 || XTENSA || RISCV || COMPILE_TEST
523 Say yes here to select Cadence I2C Host Controller. This controller is
524 e.g. used by Xilinx Zynq.
527 tristate "CBUS I2C driver"
528 depends on GPIOLIB || COMPILE_TEST
530 Support for CBUS access using I2C API. Mostly relevant for Nokia
531 Internet Tablets (770, N800 and N810).
533 This driver can also be built as a module. If so, the module
534 will be called i2c-cbus-gpio.
537 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
538 depends on CPM1 || CPM2
540 This supports the use of the I2C interface on Freescale
541 processors with CPM1 or CPM2.
543 This driver can also be built as a module. If so, the module
544 will be called i2c-cpm.
547 tristate "DaVinci I2C driver"
548 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
550 Support for TI DaVinci I2C controller driver.
552 This driver can also be built as a module. If so, the module
553 will be called i2c-davinci.
555 Please note that this driver might be needed to bring up other
556 devices such as DaVinci NIC.
557 For details please see http://www.ti.com/davinci
559 config I2C_DESIGNWARE_CORE
563 config I2C_DESIGNWARE_SLAVE
564 bool "Synopsys DesignWare Slave"
565 depends on I2C_DESIGNWARE_CORE
568 If you say yes to this option, support will be included for the
569 Synopsys DesignWare I2C slave adapter.
571 This is not a standalone module, this module compiles together with
574 config I2C_DESIGNWARE_PLATFORM
575 tristate "Synopsys DesignWare Platform"
576 depends on (ACPI && COMMON_CLK) || !ACPI
577 select I2C_DESIGNWARE_CORE
578 select MFD_SYSCON if MIPS_BAIKAL_T1
580 If you say yes to this option, support will be included for the
581 Synopsys DesignWare I2C adapter.
583 This driver can also be built as a module. If so, the module
584 will be called i2c-designware-platform.
586 config I2C_DESIGNWARE_AMDPSP
587 bool "AMD PSP I2C semaphore support"
589 depends on CRYPTO_DEV_SP_PSP
591 depends on I2C_DESIGNWARE_PLATFORM
592 depends on (I2C_DESIGNWARE_PLATFORM=y && CRYPTO_DEV_CCP_DD=y) || \
593 (I2C_DESIGNWARE_PLATFORM=m && CRYPTO_DEV_CCP_DD)
595 This driver enables managed host access to the selected I2C bus shared
596 between AMD CPU and AMD PSP.
598 You should say Y if running on an AMD system equipped with the PSP.
600 config I2C_DESIGNWARE_BAYTRAIL
601 bool "Intel Baytrail I2C semaphore support"
603 depends on I2C_DESIGNWARE_PLATFORM
604 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
605 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
607 This driver enables managed host access to the PMIC I2C bus on select
608 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
609 the host to request uninterrupted access to the PMIC's I2C bus from
610 the platform firmware controlling it. You should say Y if running on
611 a BayTrail system using the AXP288.
613 config I2C_DESIGNWARE_PCI
614 tristate "Synopsys DesignWare PCI"
616 select I2C_DESIGNWARE_CORE
619 If you say yes to this option, support will be included for the
620 Synopsys DesignWare I2C adapter. Only master mode is supported.
622 This driver can also be built as a module. If so, the module
623 will be called i2c-designware-pci.
626 tristate "Conexant Digicolor I2C driver"
627 depends on ARCH_DIGICOLOR || COMPILE_TEST
629 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
631 This driver can also be built as a module. If so, the module
632 will be called i2c-digicolor.
635 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
636 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
638 This driver is for PCH(Platform controller Hub) I2C of EG20T which
639 is an IOH(Input/Output Hub) for x86 embedded processor.
640 This driver can access PCH I2C bus device.
642 This driver also can be used for LAPIS Semiconductor IOH(Input/
643 Output Hub), ML7213, ML7223 and ML7831.
644 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
645 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
646 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
647 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
650 tristate "EMMA Mobile series I2C adapter"
654 If you say yes to this option, support will be included for the
655 I2C interface on the Renesas Electronics EM/EV family of processors.
658 tristate "Exynos high-speed I2C driver"
660 depends on ARCH_EXYNOS || COMPILE_TEST
661 default y if ARCH_EXYNOS
663 High-speed I2C controller on Samsung Exynos5 and newer Samsung SoCs:
664 Exynos5250, Exynos5260, Exynos5410, Exynos542x, Exynos5800,
665 Exynos5433, Exynos7, Exynos850 and ExynosAutoV9.
666 Choose Y here only if you build for such Samsung SoC.
669 tristate "GPIO-based bitbanging I2C"
670 depends on GPIOLIB || COMPILE_TEST
673 This is a very simple bitbanging I2C driver utilizing the
674 arch-neutral GPIO API to control the SCL and SDA lines.
676 config I2C_GPIO_FAULT_INJECTOR
677 bool "GPIO-based fault injector"
680 This adds some functionality to the i2c-gpio driver which can inject
681 faults to an I2C bus, so another bus master can be stress-tested.
682 This is for debugging. If unsure, say 'no'.
685 tristate "GXP I2C Interface"
686 depends on ARCH_HPE_GXP || COMPILE_TEST
688 This enables support for GXP I2C interface. The I2C engines can be
689 either I2C master or I2C slaves.
691 config I2C_HIGHLANDER
692 tristate "Highlander FPGA SMBus interface"
693 depends on SH_HIGHLANDER || COMPILE_TEST
695 If you say yes to this option, support will be included for
696 the SMBus interface located in the FPGA on various Highlander
697 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
698 FPGAs. This is wholly unrelated to the SoC I2C.
700 This driver can also be built as a module. If so, the module
701 will be called i2c-highlander.
704 tristate "HiSilicon I2C controller"
705 depends on ARM64 || COMPILE_TEST
707 Say Y here if you want to have Hisilicon I2C controller support
708 available on the Kunpeng Server.
710 This driver can also be built as a module. If so, the module
711 will be called i2c-hisi.
714 tristate "IBM PPC 4xx on-chip I2C interface"
717 Say Y here if you want to use IIC peripheral found on
718 embedded IBM PPC 4xx based systems.
720 This driver can also be built as a module. If so, the module
721 will be called i2c-ibm_iic.
724 tristate "Imagination Technologies I2C SCB Controller"
725 depends on MIPS || COMPILE_TEST
727 Say Y here if you want to use the IMG I2C SCB controller,
728 available on the TZ1090 and other IMG SoCs.
730 This driver can also be built as a module. If so, the module
731 will be called i2c-img-scb.
734 tristate "IMX I2C interface"
735 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE || COMPILE_TEST
738 Say Y here if you want to use the IIC bus controller on
739 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
741 This driver can also be built as a module. If so, the module
742 will be called i2c-imx.
745 tristate "IMX Low Power I2C interface"
746 depends on ARCH_MXC || COMPILE_TEST
748 Say Y here if you want to use the Low Power IIC bus controller
749 on the Freescale i.MX processors.
751 This driver can also be built as a module. If so, the module
752 will be called i2c-imx-lpi2c.
755 tristate "Intel IXP4xx on-chip I2C interface"
756 depends on ARCH_IXP4XX || COMPILE_TEST
758 Say Y here if you want to use the IIC bus controller on
759 the Intel IXP4xx Network Processors.
761 This driver can also be built as a module. If so, the module
762 will be called i2c-iop3xx.
765 tristate "JZ4780 I2C controller interface support"
766 depends on MIPS || COMPILE_TEST
768 If you say yes to this option, support will be included for the
769 Ingenic JZ4780 I2C controller.
771 If you don't know what to do here, say N.
774 tristate "Kontron COM I2C Controller"
775 depends on MFD_KEMPLD
777 This enables support for the I2C bus interface on some Kontron ETX
778 and COMexpress (ETXexpress) modules.
780 This driver can also be built as a module. If so, the module
781 will be called i2c-kempld.
784 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
785 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
787 This driver supports the I2C interface found several NXP
788 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
790 This driver can also be built as a module. If so, the module
791 will be called i2c-lpc2k.
794 tristate "Loongson LS2X I2C adapter"
795 depends on MACH_LOONGSON64 || COMPILE_TEST
797 If you say yes to this option, support will be included for the
798 I2C interface on the Loongson-2K SoCs and Loongson LS7A bridge
801 This driver can also be built as a module. If so, the module
802 will be called i2c-ls2x.
805 tristate "Mellanox BlueField I2C controller"
806 depends on MELLANOX_PLATFORM && ARM64
810 Enabling this option will add I2C SMBus support for Mellanox BlueField
813 This driver can also be built as a module. If so, the module will be
816 This driver implements an I2C SMBus host controller and enables both
817 master and slave functions.
820 tristate "Amlogic Meson I2C controller"
821 depends on ARCH_MESON || COMPILE_TEST
822 depends on COMMON_CLK
824 If you say yes to this option, support will be included for the
825 I2C interface on the Amlogic Meson family of SoCs.
827 config I2C_MICROCHIP_CORE
828 tristate "Microchip FPGA I2C controller"
829 depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST
832 If you say yes to this option, support will be included for the
833 I2C interface on Microchip FPGAs.
835 This driver can also be built as a module. If so, the module will be
836 called i2c-microchip-core.
839 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
842 If you say yes to this option, support will be included for the
843 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
844 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
846 This driver can also be built as a module. If so, the module
847 will be called i2c-mpc.
850 tristate "MediaTek I2C adapter"
851 depends on ARCH_MEDIATEK || COMPILE_TEST
853 This selects the MediaTek(R) Integrated Inter Circuit bus driver
854 for MT65xx and MT81xx.
855 If you want to use MediaTek(R) I2C interface, say Y or M here.
859 tristate "MT7621/MT7628 I2C Controller"
860 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
862 Say Y here to include support for I2C controller in the
863 MediaTek MT7621/MT7628 SoCs.
866 tristate "Marvell mv64xxx I2C Controller"
867 depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
869 If you say yes to this option, support will be included for the
870 built-in I2C interface on the Marvell 64xxx line of host bridges.
871 This driver is also used for Allwinner SoCs I2C controllers.
873 This driver can also be built as a module. If so, the module
874 will be called i2c-mv64xxx.
877 tristate "Freescale i.MX28 I2C interface"
878 depends on SOC_IMX28 || COMPILE_TEST
881 Say Y here if you want to use the I2C bus controller on
882 the Freescale i.MX28 processors.
884 This driver can also be built as a module. If so, the module
885 will be called i2c-mxs.
888 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
891 If you say yes to this option, support will be included for the
892 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
893 as well as the STA2X11 PCIe I/O HUB.
896 tristate "Nuvoton I2C Controller"
897 depends on ARCH_NPCM || COMPILE_TEST
899 If you say yes to this option, support will be included for the
900 Nuvoton I2C controller, which is available on the NPCM BMC
902 Driver can also support slave mode (select I2C_SLAVE).
905 tristate "OpenCores I2C Controller"
907 If you say yes to this option, support will be included for the
908 OpenCores I2C controller. For details see
909 http://www.opencores.org/projects.cgi/web/i2c/overview
911 This driver can also be built as a module. If so, the module
912 will be called i2c-ocores.
915 tristate "OMAP I2C adapter"
916 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
917 default MACH_OMAP_OSK
919 If you say yes to this option, support will be included for the
920 I2C interface on the Texas Instruments OMAP1/2 family of processors.
921 Like OMAP1510/1610/1710/5912 and OMAP242x.
922 For details see http://www.ti.com/omap.
925 tristate "Actions Semiconductor Owl I2C Controller"
926 depends on ARCH_ACTIONS || COMPILE_TEST
928 Say Y here if you want to use the I2C bus controller on
929 the Actions Semiconductor Owl SoC's.
932 tristate "PA Semi SMBus interface"
933 depends on PPC_PASEMI && PCI
935 Supports the PA Semi PWRficient on-chip SMBus interfaces.
938 tristate "Apple SMBus platform driver"
939 depends on !I2C_PASEMI
940 depends on ARCH_APPLE || COMPILE_TEST
943 Say Y here if you want to use the I2C controller present on Apple
944 Silicon chips such as the M1.
946 This driver can also be built as a module. If so, the module
947 will be called i2c-apple.
949 config I2C_PCA_PLATFORM
950 tristate "PCA9564/PCA9665 as platform device"
953 This driver supports a memory mapped Philips PCA9564/PCA9665
954 parallel bus to I2C bus controller.
956 This driver can also be built as a module. If so, the module
957 will be called i2c-pca-platform.
960 tristate "I2C bus support for Philips PNX and NXP LPC targets"
961 depends on ARCH_LPC32XX || COMPILE_TEST
963 This driver supports the Philips IP3204 I2C IP block master and/or
966 This driver can also be built as a module. If so, the module
967 will be called i2c-pnx.
970 tristate "Intel PXA2XX I2C adapter"
971 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
973 If you have devices in the PXA I2C bus, say yes to this option.
974 This driver can also be built as a module. If so, the module
975 will be called i2c-pxa.
978 def_bool I2C_PXA && X86_32 && PCI && OF
981 bool "Intel PXA2XX I2C Slave comms support"
982 depends on I2C_PXA && !X86_32
985 Support I2C slave mode communications on the PXA I2C bus. This
986 is necessary for systems where the PXA may be a target on the
990 tristate "Qualcomm Camera Control Interface"
991 depends on ARCH_QCOM || COMPILE_TEST
993 If you say yes to this option, support will be included for the
994 built-in camera control interface on the Qualcomm SoCs.
996 This driver can also be built as a module. If so, the module
997 will be called i2c-qcom-cci.
1000 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
1001 depends on ARCH_QCOM || COMPILE_TEST
1002 depends on QCOM_GENI_SE
1004 This driver supports GENI serial engine based I2C controller in
1005 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
1006 yes to this option, support will be included for the built-in I2C
1007 interface on the Qualcomm Technologies Inc.'s SoCs.
1009 This driver can also be built as a module. If so, the module
1010 will be called i2c-qcom-geni.
1013 tristate "Qualcomm QUP based I2C controller"
1014 depends on ARCH_QCOM || COMPILE_TEST
1016 If you say yes to this option, support will be included for the
1017 built-in I2C interface on the Qualcomm SoCs.
1019 This driver can also be built as a module. If so, the module
1020 will be called i2c-qup.
1023 tristate "Renesas RIIC adapter"
1024 depends on ARCH_RENESAS || COMPILE_TEST
1026 If you say yes to this option, support will be included for the
1027 Renesas RIIC I2C interface.
1029 This driver can also be built as a module. If so, the module
1030 will be called i2c-riic.
1033 tristate "Rockchip RK3xxx I2C adapter"
1034 depends on OF && COMMON_CLK
1036 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
1039 This driver can also be built as a module. If so, the module will
1043 tristate "Renesas RZ/V2M adapter"
1044 depends on ARCH_RENESAS || COMPILE_TEST
1046 If you say yes to this option, support will be included for the
1047 Renesas RZ/V2M I2C interface.
1049 This driver can also be built as a module. If so, the module
1050 will be called i2c-rzv2m.
1053 tristate "S3C/Exynos I2C Driver"
1054 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST
1056 Say Y here to include support for I2C controller in the
1057 Samsung SoCs (S3C, S5Pv210, Exynos).
1060 tristate "Renesas SH7760 I2C Controller"
1061 depends on CPU_SUBTYPE_SH7760
1063 This driver supports the 2 I2C interfaces on the Renesas SH7760.
1065 This driver can also be built as a module. If so, the module
1066 will be called i2c-sh7760.
1068 config I2C_SH_MOBILE
1069 tristate "SuperH Mobile I2C Controller"
1070 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
1072 If you say yes to this option, support will be included for the
1073 built-in I2C interface on the Renesas SH-Mobile processor.
1075 This driver can also be built as a module. If so, the module
1076 will be called i2c-sh_mobile.
1079 tristate "Simtec Generic I2C interface"
1082 If you say yes to this option, support will be included for
1083 the Simtec Generic I2C interface. This driver is for the
1084 simple I2C bus used on newer Simtec products for general
1085 I2C, such as DDC on the Simtec BBD2016A.
1087 This driver can also be built as a module. If so, the module
1088 will be called i2c-simtec.
1091 tristate "Spreadtrum I2C interface"
1092 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1093 depends on COMMON_CLK
1095 If you say yes to this option, support will be included for the
1096 Spreadtrum I2C interface.
1099 tristate "STMicroelectronics SSC I2C support"
1100 depends on ARCH_STI || COMPILE_TEST
1102 Enable this option to add support for STMicroelectronics SoCs
1103 hardware SSC (Synchronous Serial Controller) as an I2C controller.
1105 This driver can also be built as module. If so, the module
1106 will be called i2c-st.
1109 tristate "STMicroelectronics STM32F4 I2C support"
1110 depends on ARCH_STM32 || COMPILE_TEST
1112 Enable this option to add support for STM32 I2C controller embedded
1115 This driver can also be built as module. If so, the module
1116 will be called i2c-stm32f4.
1119 tristate "STMicroelectronics STM32F7 I2C support"
1120 depends on ARCH_STM32 || COMPILE_TEST
1124 Enable this option to add support for STM32 I2C controller embedded
1127 This driver can also be built as module. If so, the module
1128 will be called i2c-stm32f7.
1130 config I2C_SUN6I_P2WI
1131 tristate "Allwinner sun6i internal P2WI controller"
1132 depends on RESET_CONTROLLER
1133 depends on MACH_SUN6I || COMPILE_TEST
1135 If you say yes to this option, support will be included for the
1136 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1138 The P2WI looks like an SMBus controller (which supports only byte
1139 accesses), except that it only supports one slave device.
1140 This interface is used to connect to specific PMIC devices (like the
1143 config I2C_SYNQUACER
1144 tristate "Socionext SynQuacer I2C controller"
1145 depends on ARCH_SYNQUACER || COMPILE_TEST
1147 Say Y here to include support for the I2C controller used in some
1148 Fujitsu and Socionext SoCs.
1150 This driver can also be built as a module. If so, the module
1151 will be called i2c-synquacer.
1154 tristate "NVIDIA Tegra internal I2C controller"
1155 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1156 # COMPILE_TEST needs architectures with readsX()/writesX() primitives
1158 If you say yes to this option, support will be included for the
1159 I2C controller embedded in NVIDIA Tegra SOCs
1161 config I2C_TEGRA_BPMP
1162 tristate "NVIDIA Tegra BPMP I2C controller"
1163 depends on TEGRA_BPMP || COMPILE_TEST
1164 default y if TEGRA_BPMP
1166 If you say yes to this option, support will be included for the I2C
1167 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1169 This I2C driver is a 'virtual' I2C driver. The real driver is part
1170 of the BPMP firmware, and this driver merely communicates with that
1174 tristate "UniPhier FIFO-less I2C controller"
1175 depends on ARCH_UNIPHIER || COMPILE_TEST
1177 If you say yes to this option, support will be included for
1178 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1179 or older UniPhier SoCs.
1181 config I2C_UNIPHIER_F
1182 tristate "UniPhier FIFO-builtin I2C controller"
1183 depends on ARCH_UNIPHIER || COMPILE_TEST
1185 If you say yes to this option, support will be included for
1186 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1187 PH1-Pro5, or newer UniPhier SoCs.
1189 config I2C_VERSATILE
1190 tristate "ARM Versatile/Realview I2C bus support"
1191 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1194 Say yes if you want to support the I2C serial bus on ARMs Versatile
1197 This driver can also be built as a module. If so, the module
1198 will be called i2c-versatile.
1201 tristate "Wondermedia WM8xxx SoC I2C bus support"
1202 depends on ARCH_VT8500 || COMPILE_TEST
1204 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1207 This driver can also be built as a module. If so, the module will be
1211 tristate "Cavium OCTEON I2C bus support"
1212 depends on CAVIUM_OCTEON_SOC
1214 Say yes if you want to support the I2C serial bus on Cavium
1217 This driver can also be built as a module. If so, the module
1218 will be called i2c-octeon.
1221 tristate "Cavium ThunderX I2C bus support"
1222 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1225 Say yes if you want to support the I2C serial bus on Cavium
1228 This driver can also be built as a module. If so, the module
1229 will be called i2c-thunderx.
1232 tristate "Xilinx I2C Controller"
1233 depends on HAS_IOMEM
1235 If you say yes to this option, support will be included for the
1236 Xilinx I2C controller.
1238 This driver can also be built as a module. If so, the module
1239 will be called xilinx_i2c.
1242 tristate "Cavium ThunderX2 I2C support"
1243 depends on ARCH_THUNDER2 || COMPILE_TEST
1245 This driver enables support for the on-chip I2C interface of
1246 the Cavium ThunderX2 processors. (Originally on Netlogic XLP SoCs.)
1248 This driver can also be built as a module. If so, the module will
1249 be called i2c-xlp9xx.
1252 tristate "Renesas R-Car I2C Controller"
1253 depends on ARCH_RENESAS || COMPILE_TEST
1256 select RESET_CONTROLLER if ARCH_RCAR_GEN3 || ARCH_RCAR_GEN4
1258 If you say yes to this option, support will be included for the
1259 R-Car I2C controller.
1261 This driver can also be built as a module. If so, the module
1262 will be called i2c-rcar.
1264 comment "External I2C/SMBus adapter drivers"
1266 config I2C_DIOLAN_U2C
1267 tristate "Diolan U2C-12 USB adapter"
1270 If you say yes to this option, support will be included for Diolan
1271 U2C-12, a USB to I2C interface.
1273 This driver can also be built as a module. If so, the module
1274 will be called i2c-diolan-u2c.
1277 tristate "Diolan DLN-2 USB I2C adapter"
1280 If you say yes to this option, support will be included for Diolan
1281 DLN2, a USB to I2C interface.
1283 This driver can also be built as a module. If so, the module
1284 will be called i2c-dln2.
1287 tristate "I2C functionality of Intel La Jolla Cove Adapter"
1291 If you say yes to this option, I2C functionality support of Intel
1292 La Jolla Cove Adapter (LJCA) will be included.
1294 This driver can also be built as a module. If so, the module
1295 will be called i2c-ljca.
1298 tristate "Silicon Labs CP2615 USB sound card and I2C adapter"
1301 If you say yes to this option, support will be included for Silicon
1302 Labs CP2615's I2C interface.
1304 This driver can also be built as a module. If so, the module
1305 will be called i2c-cp2615.
1308 tristate "Parallel port adapter"
1313 This supports parallel port I2C adapters such as the ones made by
1314 Philips or Velleman, Analog Devices evaluation boards, and more.
1315 Basically any adapter using the parallel port as an I2C bus with
1316 no extra chipset is supported by this driver, or could be. Please
1317 read the file Documentation/i2c/busses/i2c-parport.rst for details.
1319 This support is also available as a module. If so, the module
1320 will be called i2c-parport.
1323 tristate "PCI1XXXX I2C Host Adapter"
1326 If you say yes to this option, support will be included for
1327 Microchip PCI1XXXX's I2C interface.
1329 This driver can also be built as a module. If so, the module will
1330 be called i2c-mchp-pci1xxxx.
1332 config I2C_ROBOTFUZZ_OSIF
1333 tristate "RobotFuzz Open Source InterFace USB adapter"
1336 If you say yes to this option, support will be included for the
1337 RobotFuzz Open Source InterFace USB to I2C interface.
1339 This driver can also be built as a module. If so, the module
1340 will be called i2c-osif.
1343 tristate "TAOS evaluation module"
1346 select SERIO_SERPORT
1348 This supports TAOS evaluation modules on serial port. In order to
1349 use this driver, you will need the inputattach tool, which is part
1350 of the input-utils package.
1354 This support is also available as a module. If so, the module
1355 will be called i2c-taos-evm.
1358 tristate "Tiny-USB adapter"
1361 If you say yes to this option, support will be included for the
1362 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1363 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1365 This driver can also be built as a module. If so, the module
1366 will be called i2c-tiny-usb.
1368 config I2C_VIPERBOARD
1369 tristate "Viperboard I2C master support"
1370 depends on MFD_VIPERBOARD && USB
1372 Say yes here to access the I2C part of the Nano River
1373 Technologies Viperboard as I2C master.
1374 See viperboard API specification and Nano
1375 River Tech's viperboard.h for detailed meaning
1376 of the module parameters.
1378 comment "Other I2C/SMBus bus drivers"
1381 tristate "Acorn IOC/IOMD I2C bus support"
1382 depends on ARCH_ACORN
1386 Say yes if you want to support the I2C bus on Acorn platforms.
1388 If you don't know, say Y.
1391 tristate "Elektor ISA card"
1392 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1395 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1398 This support is also available as a module. If so, the module
1399 will be called i2c-elektor.
1402 tristate "ICY Zorro card"
1406 This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1407 Say Y if you own such an adapter.
1409 This support is also available as a module. If so, the module
1410 will be called i2c-icy.
1412 If you have a 2019 edition board with an LTC2990 sensor at address
1413 0x4c, loading the module 'ltc2990' is sufficient to enable it.
1416 tristate "Mellanox I2C driver"
1417 depends on X86_64 || (ARM64 && ACPI) || COMPILE_TEST
1418 depends on HAS_IOPORT
1420 This exposes the Mellanox platform I2C busses to the linux I2C layer
1421 for X86 and ARM64/ACPI based systems.
1422 Controller is implemented as CPLD logic.
1424 This driver can also be built as a module. If so, the module will be
1425 called as i2c-mlxcpld.
1428 tristate "PCA9564/PCA9665 on an ISA bus"
1432 This driver supports ISA boards using the Philips PCA9564/PCA9665
1433 parallel bus to I2C bus controller.
1435 This driver can also be built as a module. If so, the module
1436 will be called i2c-pca-isa.
1438 This device is almost undetectable and using this driver on a
1439 system which doesn't have this device will result in long
1440 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1441 time). If unsure, say N.
1444 tristate "SiByte SMBus interface"
1445 depends on SIBYTE_SB1xxx_SOC
1447 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1449 config I2C_CROS_EC_TUNNEL
1450 tristate "ChromeOS EC tunnel I2C bus"
1453 If you say yes here you get an I2C bus that will tunnel i2c commands
1454 through to the other side of the ChromeOS EC to the i2c bus
1455 connected there. This will work whatever the interface used to
1456 talk to the EC (SPI, I2C or LPC).
1458 config I2C_XGENE_SLIMPRO
1459 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1460 depends on ARCH_XGENE && MAILBOX
1462 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1463 co-processor. The I2C device access the I2C bus via the X-Gene
1464 to SLIMpro (On chip coprocessor) mailbox mechanism.
1468 tristate "Geode ACCESS.bus support"
1469 depends on X86_32 && PCI
1471 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1472 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1474 If you don't know what to do here, say N.
1476 This support is also available as a module. If so, the module
1477 will be called scx200_acb.
1480 tristate "IBM OPAL I2C driver"
1481 depends on PPC_POWERNV
1484 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1485 the driver is based on the OPAL interfaces.
1487 This driver can also be built as a module. If so, the module will be
1491 tristate "FSI I2C driver"
1494 Driver for FSI bus attached I2C masters. These are I2C masters that
1495 are connected to the system over an FSI bus, instead of the more
1496 common PCI or MMIO interface.
1498 This driver can also be built as a module. If so, the module will be
1502 tristate "Virtio I2C Adapter"
1505 If you say yes to this option, support will be included for the virtio
1506 I2C adapter driver. The hardware can be emulated by any device model
1507 software according to the virtio protocol.
1509 This driver can also be built as a module. If so, the module
1510 will be called i2c-virtio.