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)
152 This driver can also be built as a module. If so, the module
153 will be called i2c-i801.
156 tristate "Intel SCH SMBus 1.0"
160 Say Y here if you want to use SMBus controller on the Intel SCH
163 This driver can also be built as a module. If so, the module
164 will be called i2c-isch.
167 tristate "Intel iSMT SMBus Controller"
168 depends on PCI && X86
170 If you say yes to this option, support will be included for the Intel
171 iSMT SMBus host controller interface.
173 This driver can also be built as a module. If so, the module will be
177 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
180 If you say yes to this option, support will be included for the Intel
181 PIIX4 family of mainboard I2C interfaces. Specifically, the following
182 versions of the chipset are supported (note that Serverworks is part
203 Some AMD chipsets contain two PIIX4-compatible SMBus
204 controllers. This driver will attempt to use both controllers
205 on the SB700/SP5100, if they have been initialized by the BIOS.
207 This driver can also be built as a module. If so, the module
208 will be called i2c-piix4.
211 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
212 depends on INTEL_SOC_PMIC_CHTWC
214 If you say yes to this option, support will be included for the
215 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
216 found on some Intel Cherry Trail systems.
218 Note this controller is hooked up to a TI bq24292i charger-IC,
219 combined with a FUSB302 Type-C port-controller as such it is advised
220 to also select CONFIG_TYPEC_FUSB302=m.
223 tristate "Nvidia nForce2, nForce3 and nForce4"
226 If you say yes to this option, support will be included for the Nvidia
227 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
229 This driver can also be built as a module. If so, the module
230 will be called i2c-nforce2.
232 config I2C_NFORCE2_S4985
233 tristate "SMBus multiplexing on the Tyan S4985"
234 depends on I2C_NFORCE2 && X86
236 Enabling this option will add specific SMBus support for the Tyan
237 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
238 over 4 different channels, where the various memory module EEPROMs
239 live. Saying yes here will give you access to these in addition
242 This driver can also be built as a module. If so, the module
243 will be called i2c-nforce2-s4985.
245 config I2C_NVIDIA_GPU
246 tristate "NVIDIA GPU I2C controller"
249 If you say yes to this option, support will be included for the
250 NVIDIA GPU I2C controller which is used to communicate with the GPU's
251 Type-C controller. This driver can also be built as a module called
258 If you say yes to this option, support will be included for the
259 SiS5595 SMBus (a subset of I2C) interface.
261 This driver can also be built as a module. If so, the module
262 will be called i2c-sis5595.
265 tristate "SiS 630/730/964"
268 If you say yes to this option, support will be included for the
269 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
271 This driver can also be built as a module. If so, the module
272 will be called i2c-sis630.
278 If you say yes to this option, support will be included for the SiS
279 96x SMBus (a subset of I2C) interfaces. Specifically, the following
280 chipsets are supported:
289 This driver can also be built as a module. If so, the module
290 will be called i2c-sis96x.
293 tristate "VIA VT82C586B"
297 If you say yes to this option, support will be included for the VIA
298 82C586B I2C interface
300 This driver can also be built as a module. If so, the module
301 will be called i2c-via.
304 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
307 If you say yes to this option, support will be included for the VIA
308 VT82C596 and later SMBus interface. Specifically, the following
309 chipsets are supported:
322 This driver can also be built as a module. If so, the module
323 will be called i2c-viapro.
327 comment "ACPI drivers"
330 tristate "SMBus Control Method Interface"
332 This driver supports the SMBus Control Method Interface. It needs the
333 BIOS to declare ACPI control methods as described in the SMBus Control
334 Method Interface specification.
336 To compile this driver as a module, choose M here:
337 the module will be called i2c-scmi.
341 comment "Mac SMBus host controller drivers"
342 depends on PPC_CHRP || PPC_PMAC
345 tristate "CHRP Apple Hydra Mac I/O I2C interface"
346 depends on PCI && PPC_CHRP
349 This supports the use of the I2C interface in the Apple Hydra Mac
350 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
353 This support is also available as a module. If so, the module
354 will be called i2c-hydra.
357 tristate "Powermac I2C interface"
361 This exposes the various PowerMac i2c interfaces to the linux i2c
362 layer and to userland. It is used by various drivers on the PowerMac
363 platform, and should generally be enabled.
365 This support is also available as a module. If so, the module
366 will be called i2c-powermac.
368 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
371 tristate "Altera Soft IP I2C"
372 depends on ARCH_SOCFPGA || NIOS2 || COMPILE_TEST
375 If you say yes to this option, support will be included for the
376 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
378 This driver can also be built as a module. If so, the module
379 will be called i2c-altera.
382 tristate "Aspeed I2C Controller"
383 depends on ARCH_ASPEED || COMPILE_TEST
385 If you say yes to this option, support will be included for the
386 Aspeed I2C controller.
388 This driver can also be built as a module. If so, the module
389 will be called i2c-aspeed.
392 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
393 depends on ARCH_AT91 || COMPILE_TEST
395 This supports the use of the I2C interface on Atmel AT91
398 A serious problem is that there is no documented way to issue
399 repeated START conditions for more than two messages, as needed
400 to support combined I2C messages. Use the i2c-gpio driver
401 unless your system can cope with this limitation.
403 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
404 don't have clock stretching in transmission mode. For that reason,
405 you can encounter underrun issues causing premature stop sendings if
406 the latency to fill the transmission register is too long. If you
407 are facing this situation, use the i2c-gpio driver.
409 config I2C_AT91_SLAVE_EXPERIMENTAL
410 tristate "Microchip AT91 I2C experimental slave mode"
414 If you say yes to this option, support for the slave mode will be
415 added. Caution: do not use it for production. This feature has not
416 been tested in a heavy way, help wanted.
417 There are known bugs:
418 - It can hang, on a SAMA5D4, after several transfers.
419 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
423 tristate "Au1550/Au1200/Au1300 SMBus interface"
424 depends on MIPS_ALCHEMY
426 If you say yes to this option, support will be included for the
427 Au1550/Au1200/Au1300 SMBus interface.
429 This driver can also be built as a module. If so, the module
430 will be called i2c-au1550.
433 tristate "Axxia I2C controller"
434 depends on ARCH_AXXIA || COMPILE_TEST
438 Say yes if you want to support the I2C bus on Axxia platforms.
440 Please note that this controller is limited to transfers of maximum
441 255 bytes in length. Any attempt to to a larger transfer will return
445 tristate "Broadcom BCM2835 I2C controller"
446 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
447 depends on COMMON_CLK
449 If you say yes to this option, support will be included for the
450 BCM2835 I2C controller.
452 If you don't know what to do here, say N.
454 This support is also available as a module. If so, the module
455 will be called i2c-bcm2835.
458 tristate "Broadcom iProc I2C controller"
459 depends on ARCH_BCM_IPROC || COMPILE_TEST
460 default ARCH_BCM_IPROC
463 If you say yes to this option, support will be included for the
464 Broadcom iProc I2C controller.
466 If you don't know what to do here, say N.
469 tristate "BCM Kona I2C adapter"
470 depends on ARCH_BCM_MOBILE || COMPILE_TEST
471 default y if ARCH_BCM_MOBILE
473 If you say yes to this option, support will be included for the
474 I2C interface on the Broadcom Kona family of processors.
476 If you do not need KONA I2C interface, say N.
479 tristate "BRCM Settop/DSL I2C controller"
480 depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
481 ARCH_BCM_63XX || COMPILE_TEST
484 If you say yes to this option, support will be included for the
485 I2C interface on the Broadcom Settop/DSL SoCs.
487 If you do not need I2C interface, say N.
490 tristate "Cadence I2C Controller"
491 depends on ARCH_ZYNQ || ARM64 || XTENSA
493 Say yes here to select Cadence I2C Host Controller. This controller is
494 e.g. used by Xilinx Zynq.
497 tristate "CBUS I2C driver"
498 depends on GPIOLIB || COMPILE_TEST
500 Support for CBUS access using I2C API. Mostly relevant for Nokia
501 Internet Tablets (770, N800 and N810).
503 This driver can also be built as a module. If so, the module
504 will be called i2c-cbus-gpio.
507 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
508 depends on CPM1 || CPM2
510 This supports the use of the I2C interface on Freescale
511 processors with CPM1 or CPM2.
513 This driver can also be built as a module. If so, the module
514 will be called i2c-cpm.
517 tristate "DaVinci I2C driver"
518 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
520 Support for TI DaVinci I2C controller driver.
522 This driver can also be built as a module. If so, the module
523 will be called i2c-davinci.
525 Please note that this driver might be needed to bring up other
526 devices such as DaVinci NIC.
527 For details please see http://www.ti.com/davinci
529 config I2C_DESIGNWARE_CORE
533 config I2C_DESIGNWARE_SLAVE
534 bool "Synopsys DesignWare Slave"
535 depends on I2C_DESIGNWARE_CORE
538 If you say yes to this option, support will be included for the
539 Synopsys DesignWare I2C slave adapter.
541 This is not a standalone module, this module compiles together with
544 config I2C_DESIGNWARE_PLATFORM
545 tristate "Synopsys DesignWare Platform"
546 depends on (ACPI && COMMON_CLK) || !ACPI
547 select I2C_DESIGNWARE_CORE
548 select MFD_SYSCON if MIPS_BAIKAL_T1
550 If you say yes to this option, support will be included for the
551 Synopsys DesignWare I2C adapter.
553 This driver can also be built as a module. If so, the module
554 will be called i2c-designware-platform.
556 config I2C_DESIGNWARE_BAYTRAIL
557 bool "Intel Baytrail I2C semaphore support"
559 depends on I2C_DESIGNWARE_PLATFORM
560 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
561 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
563 This driver enables managed host access to the PMIC I2C bus on select
564 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
565 the host to request uninterrupted access to the PMIC's I2C bus from
566 the platform firmware controlling it. You should say Y if running on
567 a BayTrail system using the AXP288.
569 config I2C_DESIGNWARE_PCI
570 tristate "Synopsys DesignWare PCI"
572 select I2C_DESIGNWARE_CORE
574 If you say yes to this option, support will be included for the
575 Synopsys DesignWare I2C adapter. Only master mode is supported.
577 This driver can also be built as a module. If so, the module
578 will be called i2c-designware-pci.
581 tristate "Conexant Digicolor I2C driver"
582 depends on ARCH_DIGICOLOR || COMPILE_TEST
584 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
586 This driver can also be built as a module. If so, the module
587 will be called i2c-digicolor.
590 tristate "EFM32 I2C controller"
591 depends on ARCH_EFM32 || COMPILE_TEST
593 This driver supports the i2c block found in Energy Micro's EFM32
597 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
598 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
600 This driver is for PCH(Platform controller Hub) I2C of EG20T which
601 is an IOH(Input/Output Hub) for x86 embedded processor.
602 This driver can access PCH I2C bus device.
604 This driver also can be used for LAPIS Semiconductor IOH(Input/
605 Output Hub), ML7213, ML7223 and ML7831.
606 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
607 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
608 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
609 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
612 tristate "EMMA Mobile series I2C adapter"
616 If you say yes to this option, support will be included for the
617 I2C interface on the Renesas Electronics EM/EV family of processors.
620 tristate "Exynos high-speed I2C driver"
622 depends on ARCH_EXYNOS || COMPILE_TEST
623 default y if ARCH_EXYNOS
625 High-speed I2C controller on Exynos5 and newer Samsung SoCs.
628 tristate "GPIO-based bitbanging I2C"
629 depends on GPIOLIB || COMPILE_TEST
632 This is a very simple bitbanging I2C driver utilizing the
633 arch-neutral GPIO API to control the SCL and SDA lines.
635 config I2C_GPIO_FAULT_INJECTOR
636 bool "GPIO-based fault injector"
639 This adds some functionality to the i2c-gpio driver which can inject
640 faults to an I2C bus, so another bus master can be stress-tested.
641 This is for debugging. If unsure, say 'no'.
643 config I2C_HIGHLANDER
644 tristate "Highlander FPGA SMBus interface"
645 depends on SH_HIGHLANDER || COMPILE_TEST
647 If you say yes to this option, support will be included for
648 the SMBus interface located in the FPGA on various Highlander
649 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
650 FPGAs. This is wholly unrelated to the SoC I2C.
652 This driver can also be built as a module. If so, the module
653 will be called i2c-highlander.
656 tristate "IBM PPC 4xx on-chip I2C interface"
659 Say Y here if you want to use IIC peripheral found on
660 embedded IBM PPC 4xx based systems.
662 This driver can also be built as a module. If so, the module
663 will be called i2c-ibm_iic.
666 tristate "Imagination Technologies I2C SCB Controller"
667 depends on MIPS || COMPILE_TEST
669 Say Y here if you want to use the IMG I2C SCB controller,
670 available on the TZ1090 and other IMG SoCs.
672 This driver can also be built as a module. If so, the module
673 will be called i2c-img-scb.
676 tristate "IMX I2C interface"
677 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
680 Say Y here if you want to use the IIC bus controller on
681 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
683 This driver can also be built as a module. If so, the module
684 will be called i2c-imx.
687 tristate "IMX Low Power I2C interface"
688 depends on ARCH_MXC || COMPILE_TEST
690 Say Y here if you want to use the Low Power IIC bus controller
691 on the Freescale i.MX processors.
693 This driver can also be built as a module. If so, the module
694 will be called i2c-imx-lpi2c.
697 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
698 depends on ARCH_IOP32X || ARCH_IXP4XX || COMPILE_TEST
700 Say Y here if you want to use the IIC bus controller on
701 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
703 This driver can also be built as a module. If so, the module
704 will be called i2c-iop3xx.
707 tristate "JZ4780 I2C controller interface support"
708 depends on MIPS || COMPILE_TEST
710 If you say yes to this option, support will be included for the
711 Ingenic JZ4780 I2C controller.
713 If you don't know what to do here, say N.
716 tristate "Kontron COM I2C Controller"
717 depends on MFD_KEMPLD
719 This enables support for the I2C bus interface on some Kontron ETX
720 and COMexpress (ETXexpress) modules.
722 This driver can also be built as a module. If so, the module
723 will be called i2c-kempld.
726 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
727 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
729 This driver supports the I2C interface found several NXP
730 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
732 This driver can also be built as a module. If so, the module
733 will be called i2c-lpc2k.
736 tristate "Mellanox BlueField I2C controller"
737 depends on MELLANOX_PLATFORM && ARM64
740 Enabling this option will add I2C SMBus support for Mellanox BlueField
743 This driver can also be built as a module. If so, the module will be
746 This driver implements an I2C SMBus host controller and enables both
747 master and slave functions.
750 tristate "Amlogic Meson I2C controller"
751 depends on ARCH_MESON || COMPILE_TEST
752 depends on COMMON_CLK
754 If you say yes to this option, support will be included for the
755 I2C interface on the Amlogic Meson family of SoCs.
758 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
761 If you say yes to this option, support will be included for the
762 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
763 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
765 This driver can also be built as a module. If so, the module
766 will be called i2c-mpc.
769 tristate "MediaTek I2C adapter"
770 depends on ARCH_MEDIATEK || COMPILE_TEST
772 This selects the MediaTek(R) Integrated Inter Circuit bus driver
773 for MT65xx and MT81xx.
774 If you want to use MediaTek(R) I2C interface, say Y or M here.
778 tristate "MT7621/MT7628 I2C Controller"
779 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
781 Say Y here to include support for I2C controller in the
782 MediaTek MT7621/MT7628 SoCs.
785 tristate "Marvell mv64xxx I2C Controller"
786 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
788 If you say yes to this option, support will be included for the
789 built-in I2C interface on the Marvell 64xxx line of host bridges.
790 This driver is also used for Allwinner SoCs I2C controllers.
792 This driver can also be built as a module. If so, the module
793 will be called i2c-mv64xxx.
796 tristate "Freescale i.MX28 I2C interface"
797 depends on SOC_IMX28 || COMPILE_TEST
800 Say Y here if you want to use the I2C bus controller on
801 the Freescale i.MX28 processors.
803 This driver can also be built as a module. If so, the module
804 will be called i2c-mxs.
807 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
810 If you say yes to this option, support will be included for the
811 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
812 as well as the STA2X11 PCIe I/O HUB.
815 tristate "Nuvoton I2C Controller"
816 depends on ARCH_NPCM7XX || COMPILE_TEST
818 If you say yes to this option, support will be included for the
819 Nuvoton I2C controller, which is available on the NPCM7xx BMC
821 Driver can also support slave mode (select I2C_SLAVE).
824 tristate "OpenCores I2C Controller"
826 If you say yes to this option, support will be included for the
827 OpenCores I2C controller. For details see
828 http://www.opencores.org/projects.cgi/web/i2c/overview
830 This driver can also be built as a module. If so, the module
831 will be called i2c-ocores.
834 tristate "OMAP I2C adapter"
835 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
836 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
838 If you say yes to this option, support will be included for the
839 I2C interface on the Texas Instruments OMAP1/2 family of processors.
840 Like OMAP1510/1610/1710/5912 and OMAP242x.
841 For details see http://www.ti.com/omap.
844 tristate "Actions Semiconductor Owl I2C Controller"
845 depends on ARCH_ACTIONS || COMPILE_TEST
847 Say Y here if you want to use the I2C bus controller on
848 the Actions Semiconductor Owl SoC's.
851 tristate "PA Semi SMBus interface"
852 depends on PPC_PASEMI && PCI
854 Supports the PA Semi PWRficient on-chip SMBus interfaces.
856 config I2C_PCA_PLATFORM
857 tristate "PCA9564/PCA9665 as platform device"
860 This driver supports a memory mapped Philips PCA9564/PCA9665
861 parallel bus to I2C bus controller.
863 This driver can also be built as a module. If so, the module
864 will be called i2c-pca-platform.
867 tristate "PMC MSP I2C TWI Controller"
868 depends on PMC_MSP || COMPILE_TEST
870 This driver supports the PMC TWI controller on MSP devices.
872 This driver can also be built as module. If so, the module
873 will be called i2c-pmcmsp.
876 tristate "I2C bus support for Philips PNX and NXP LPC targets"
877 depends on ARCH_LPC32XX || COMPILE_TEST
879 This driver supports the Philips IP3204 I2C IP block master and/or
882 This driver can also be built as a module. If so, the module
883 will be called i2c-pnx.
886 tristate "Intel PXA2XX I2C adapter"
887 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
889 If you have devices in the PXA I2C bus, say yes to this option.
890 This driver can also be built as a module. If so, the module
891 will be called i2c-pxa.
894 def_bool I2C_PXA && X86_32 && PCI && OF
897 bool "Intel PXA2XX I2C Slave comms support"
898 depends on I2C_PXA && !X86_32
901 Support I2C slave mode communications on the PXA I2C bus. This
902 is necessary for systems where the PXA may be a target on the
906 tristate "Qualcomm Camera Control Interface"
907 depends on ARCH_QCOM || COMPILE_TEST
909 If you say yes to this option, support will be included for the
910 built-in camera control interface on the Qualcomm SoCs.
912 This driver can also be built as a module. If so, the module
913 will be called i2c-qcom-cci.
916 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
917 depends on ARCH_QCOM || COMPILE_TEST
918 depends on QCOM_GENI_SE
920 This driver supports GENI serial engine based I2C controller in
921 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
922 yes to this option, support will be included for the built-in I2C
923 interface on the Qualcomm Technologies Inc.'s SoCs.
925 This driver can also be built as a module. If so, the module
926 will be called i2c-qcom-geni.
929 tristate "Qualcomm QUP based I2C controller"
932 If you say yes to this option, support will be included for the
933 built-in I2C interface on the Qualcomm SoCs.
935 This driver can also be built as a module. If so, the module
936 will be called i2c-qup.
939 tristate "Renesas RIIC adapter"
940 depends on ARCH_RENESAS || COMPILE_TEST
942 If you say yes to this option, support will be included for the
943 Renesas RIIC I2C interface.
945 This driver can also be built as a module. If so, the module
946 will be called i2c-riic.
949 tristate "Rockchip RK3xxx I2C adapter"
950 depends on OF && COMMON_CLK
952 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
955 This driver can also be built as a module. If so, the module will
958 config HAVE_S3C2410_I2C
961 This will include I2C support for Samsung SoCs. If you want to
962 include I2C support for any machine, kindly select this in the
963 respective Kconfig file.
966 tristate "S3C/Exynos I2C Driver"
967 depends on HAVE_S3C2410_I2C || COMPILE_TEST
969 Say Y here to include support for I2C controller in the
970 Samsung SoCs (S3C, S5Pv210, Exynos).
973 tristate "Renesas SH7760 I2C Controller"
974 depends on CPU_SUBTYPE_SH7760
976 This driver supports the 2 I2C interfaces on the Renesas SH7760.
978 This driver can also be built as a module. If so, the module
979 will be called i2c-sh7760.
982 tristate "SuperH Mobile I2C Controller"
983 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
985 If you say yes to this option, support will be included for the
986 built-in I2C interface on the Renesas SH-Mobile processor.
988 This driver can also be built as a module. If so, the module
989 will be called i2c-sh_mobile.
992 tristate "Simtec Generic I2C interface"
995 If you say yes to this option, support will be included for
996 the Simtec Generic I2C interface. This driver is for the
997 simple I2C bus used on newer Simtec products for general
998 I2C, such as DDC on the Simtec BBD2016A.
1000 This driver can also be built as a module. If so, the module
1001 will be called i2c-simtec.
1004 tristate "CSR SiRFprimaII I2C interface"
1005 depends on ARCH_SIRF || COMPILE_TEST
1007 If you say yes to this option, support will be included for the
1008 CSR SiRFprimaII I2C interface.
1010 This driver can also be built as a module. If so, the module
1011 will be called i2c-sirf.
1014 tristate "Spreadtrum I2C interface"
1015 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1016 depends on COMMON_CLK
1018 If you say yes to this option, support will be included for the
1019 Spreadtrum I2C interface.
1022 tristate "STMicroelectronics SSC I2C support"
1023 depends on ARCH_STI || COMPILE_TEST
1025 Enable this option to add support for STMicroelectronics SoCs
1026 hardware SSC (Synchronous Serial Controller) as an I2C controller.
1028 This driver can also be built as module. If so, the module
1029 will be called i2c-st.
1032 tristate "STMicroelectronics STM32F4 I2C support"
1033 depends on ARCH_STM32 || COMPILE_TEST
1035 Enable this option to add support for STM32 I2C controller embedded
1038 This driver can also be built as module. If so, the module
1039 will be called i2c-stm32f4.
1042 tristate "STMicroelectronics STM32F7 I2C support"
1043 depends on ARCH_STM32 || COMPILE_TEST
1047 Enable this option to add support for STM32 I2C controller embedded
1050 This driver can also be built as module. If so, the module
1051 will be called i2c-stm32f7.
1054 tristate "ST Microelectronics DDC I2C interface"
1055 depends on MACH_U300 || COMPILE_TEST
1056 default y if MACH_U300
1058 If you say yes to this option, support will be included for the
1059 I2C interface from ST Microelectronics simply called "DDC I2C"
1060 supporting both I2C and DDC, used in e.g. the U300 series
1063 This driver can also be built as a module. If so, the module
1064 will be called i2c-stu300.
1066 config I2C_SUN6I_P2WI
1067 tristate "Allwinner sun6i internal P2WI controller"
1068 depends on RESET_CONTROLLER
1069 depends on MACH_SUN6I || COMPILE_TEST
1071 If you say yes to this option, support will be included for the
1072 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1074 The P2WI looks like an SMBus controller (which supports only byte
1075 accesses), except that it only supports one slave device.
1076 This interface is used to connect to specific PMIC devices (like the
1079 config I2C_SYNQUACER
1080 tristate "Socionext SynQuacer I2C controller"
1081 depends on ARCH_SYNQUACER || COMPILE_TEST
1083 Say Y here to include support for the I2C controller used in some
1084 Fujitsu and Socionext SoCs.
1086 This driver can also be built as a module. If so, the module
1087 will be called i2c-synquacer.
1090 tristate "NVIDIA Tegra internal I2C controller"
1091 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1092 # COMPILE_TEST needs architectures with readsX()/writesX() primitives
1094 If you say yes to this option, support will be included for the
1095 I2C controller embedded in NVIDIA Tegra SOCs
1097 config I2C_TEGRA_BPMP
1098 tristate "NVIDIA Tegra BPMP I2C controller"
1099 depends on TEGRA_BPMP || COMPILE_TEST
1100 default y if TEGRA_BPMP
1102 If you say yes to this option, support will be included for the I2C
1103 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1105 This I2C driver is a 'virtual' I2C driver. The real driver is part
1106 of the BPMP firmware, and this driver merely communicates with that
1110 tristate "UniPhier FIFO-less I2C controller"
1111 depends on ARCH_UNIPHIER || COMPILE_TEST
1113 If you say yes to this option, support will be included for
1114 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1115 or older UniPhier SoCs.
1117 config I2C_UNIPHIER_F
1118 tristate "UniPhier FIFO-builtin I2C controller"
1119 depends on ARCH_UNIPHIER || COMPILE_TEST
1121 If you say yes to this option, support will be included for
1122 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1123 PH1-Pro5, or newer UniPhier SoCs.
1125 config I2C_VERSATILE
1126 tristate "ARM Versatile/Realview I2C bus support"
1127 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1130 Say yes if you want to support the I2C serial bus on ARMs Versatile
1133 This driver can also be built as a module. If so, the module
1134 will be called i2c-versatile.
1137 tristate "Wondermedia WM8xxx SoC I2C bus support"
1138 depends on ARCH_VT8500 || COMPILE_TEST
1140 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1143 This driver can also be built as a module. If so, the module will be
1147 tristate "Cavium OCTEON I2C bus support"
1148 depends on CAVIUM_OCTEON_SOC
1150 Say yes if you want to support the I2C serial bus on Cavium
1153 This driver can also be built as a module. If so, the module
1154 will be called i2c-octeon.
1157 tristate "Cavium ThunderX I2C bus support"
1158 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1161 Say yes if you want to support the I2C serial bus on Cavium
1164 This driver can also be built as a module. If so, the module
1165 will be called i2c-thunderx.
1168 tristate "Xilinx I2C Controller"
1169 depends on HAS_IOMEM
1171 If you say yes to this option, support will be included for the
1172 Xilinx I2C controller.
1174 This driver can also be built as a module. If so, the module
1175 will be called xilinx_i2c.
1178 tristate "Netlogic XLR I2C support"
1179 depends on CPU_XLR || COMPILE_TEST
1181 This driver enables support for the on-chip I2C interface of
1182 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1184 This driver can also be built as a module. If so, the module
1185 will be called i2c-xlr.
1188 tristate "XLP9XX I2C support"
1189 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1191 This driver enables support for the on-chip I2C interface of
1192 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1194 This driver can also be built as a module. If so, the module will
1195 be called i2c-xlp9xx.
1198 tristate "Renesas R-Car I2C Controller"
1199 depends on ARCH_RENESAS || COMPILE_TEST
1202 select RESET_CONTROLLER if ARCH_RCAR_GEN3
1204 If you say yes to this option, support will be included for the
1205 R-Car I2C controller.
1207 This driver can also be built as a module. If so, the module
1208 will be called i2c-rcar.
1210 comment "External I2C/SMBus adapter drivers"
1212 config I2C_DIOLAN_U2C
1213 tristate "Diolan U2C-12 USB adapter"
1216 If you say yes to this option, support will be included for Diolan
1217 U2C-12, a USB to I2C interface.
1219 This driver can also be built as a module. If so, the module
1220 will be called i2c-diolan-u2c.
1223 tristate "Diolan DLN-2 USB I2C adapter"
1226 If you say yes to this option, support will be included for Diolan
1227 DLN2, a USB to I2C interface.
1229 This driver can also be built as a module. If so, the module
1230 will be called i2c-dln2.
1233 tristate "Parallel port adapter"
1238 This supports parallel port I2C adapters such as the ones made by
1239 Philips or Velleman, Analog Devices evaluation boards, and more.
1240 Basically any adapter using the parallel port as an I2C bus with
1241 no extra chipset is supported by this driver, or could be. Please
1242 read the file Documentation/i2c/busses/i2c-parport.rst for details.
1244 This support is also available as a module. If so, the module
1245 will be called i2c-parport.
1247 config I2C_ROBOTFUZZ_OSIF
1248 tristate "RobotFuzz Open Source InterFace USB adapter"
1251 If you say yes to this option, support will be included for the
1252 RobotFuzz Open Source InterFace USB to I2C interface.
1254 This driver can also be built as a module. If so, the module
1255 will be called i2c-osif.
1258 tristate "TAOS evaluation module"
1261 select SERIO_SERPORT
1263 This supports TAOS evaluation modules on serial port. In order to
1264 use this driver, you will need the inputattach tool, which is part
1265 of the input-utils package.
1269 This support is also available as a module. If so, the module
1270 will be called i2c-taos-evm.
1273 tristate "Tiny-USB adapter"
1276 If you say yes to this option, support will be included for the
1277 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1278 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1280 This driver can also be built as a module. If so, the module
1281 will be called i2c-tiny-usb.
1283 config I2C_VIPERBOARD
1284 tristate "Viperboard I2C master support"
1285 depends on MFD_VIPERBOARD && USB
1287 Say yes here to access the I2C part of the Nano River
1288 Technologies Viperboard as I2C master.
1289 See viperboard API specification and Nano
1290 River Tech's viperboard.h for detailed meaning
1291 of the module parameters.
1293 comment "Other I2C/SMBus bus drivers"
1296 tristate "Acorn IOC/IOMD I2C bus support"
1297 depends on ARCH_ACORN
1301 Say yes if you want to support the I2C bus on Acorn platforms.
1303 If you don't know, say Y.
1306 tristate "Elektor ISA card"
1307 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1310 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1313 This support is also available as a module. If so, the module
1314 will be called i2c-elektor.
1317 tristate "ICY Zorro card"
1321 This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1322 Say Y if you own such an adapter.
1324 This support is also available as a module. If so, the module
1325 will be called i2c-icy.
1327 If you have a 2019 edition board with an LTC2990 sensor at address
1328 0x4c, loading the module 'ltc2990' is sufficient to enable it.
1331 tristate "Mellanox I2C driver"
1332 depends on X86_64 || COMPILE_TEST
1334 This exposes the Mellanox platform I2C busses to the linux I2C layer
1335 for X86 based systems.
1336 Controller is implemented as CPLD logic.
1338 This driver can also be built as a module. If so, the module will be
1339 called as i2c-mlxcpld.
1342 tristate "PCA9564/PCA9665 on an ISA bus"
1346 This driver supports ISA boards using the Philips PCA9564/PCA9665
1347 parallel bus to I2C bus controller.
1349 This driver can also be built as a module. If so, the module
1350 will be called i2c-pca-isa.
1352 This device is almost undetectable and using this driver on a
1353 system which doesn't have this device will result in long
1354 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1355 time). If unsure, say N.
1358 tristate "SiByte SMBus interface"
1359 depends on SIBYTE_SB1xxx_SOC
1361 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1363 config I2C_CROS_EC_TUNNEL
1364 tristate "ChromeOS EC tunnel I2C bus"
1367 If you say yes here you get an I2C bus that will tunnel i2c commands
1368 through to the other side of the ChromeOS EC to the i2c bus
1369 connected there. This will work whatever the interface used to
1370 talk to the EC (SPI, I2C or LPC).
1372 config I2C_XGENE_SLIMPRO
1373 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1374 depends on ARCH_XGENE && MAILBOX
1376 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1377 co-processor. The I2C device access the I2C bus via the X-Gene
1378 to SLIMpro (On chip coprocessor) mailbox mechanism.
1382 tristate "Geode ACCESS.bus support"
1383 depends on X86_32 && PCI
1385 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1386 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1388 If you don't know what to do here, say N.
1390 This support is also available as a module. If so, the module
1391 will be called scx200_acb.
1394 tristate "IBM OPAL I2C driver"
1395 depends on PPC_POWERNV
1398 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1399 the driver is based on the OPAL interfaces.
1401 This driver can also be built as a module. If so, the module will be
1405 tristate "ZTE ZX2967 I2C support"
1409 Selecting this option will add ZX2967 I2C driver.
1410 This driver can also be built as a module. If so, the module will be
1414 tristate "FSI I2C driver"
1417 Driver for FSI bus attached I2C masters. These are I2C masters that
1418 are connected to the system over an FSI bus, instead of the more
1419 common PCI or MMIO interface.
1421 This driver can also be built as a module. If so, the module will be