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 "LiteX I2C support"
727 depends on OF && HAS_IOMEM && LITEX_SOC_CONTROLLER
730 This enables I2C bitbang driver for LiteX SoC builder.
733 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
734 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
736 This driver supports the I2C interface found several NXP
737 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
739 This driver can also be built as a module. If so, the module
740 will be called i2c-lpc2k.
743 tristate "Mellanox BlueField I2C controller"
744 depends on MELLANOX_PLATFORM && ARM64
747 Enabling this option will add I2C SMBus support for Mellanox BlueField
750 This driver can also be built as a module. If so, the module will be
753 This driver implements an I2C SMBus host controller and enables both
754 master and slave functions.
757 tristate "Amlogic Meson I2C controller"
758 depends on ARCH_MESON || COMPILE_TEST
759 depends on COMMON_CLK
761 If you say yes to this option, support will be included for the
762 I2C interface on the Amlogic Meson family of SoCs.
765 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
768 If you say yes to this option, support will be included for the
769 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
770 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
772 This driver can also be built as a module. If so, the module
773 will be called i2c-mpc.
776 tristate "MediaTek I2C adapter"
777 depends on ARCH_MEDIATEK || COMPILE_TEST
779 This selects the MediaTek(R) Integrated Inter Circuit bus driver
780 for MT65xx and MT81xx.
781 If you want to use MediaTek(R) I2C interface, say Y or M here.
785 tristate "MT7621/MT7628 I2C Controller"
786 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
788 Say Y here to include support for I2C controller in the
789 MediaTek MT7621/MT7628 SoCs.
792 tristate "Marvell mv64xxx I2C Controller"
793 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
795 If you say yes to this option, support will be included for the
796 built-in I2C interface on the Marvell 64xxx line of host bridges.
797 This driver is also used for Allwinner SoCs I2C controllers.
799 This driver can also be built as a module. If so, the module
800 will be called i2c-mv64xxx.
803 tristate "Freescale i.MX28 I2C interface"
804 depends on SOC_IMX28 || COMPILE_TEST
807 Say Y here if you want to use the I2C bus controller on
808 the Freescale i.MX28 processors.
810 This driver can also be built as a module. If so, the module
811 will be called i2c-mxs.
814 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
817 If you say yes to this option, support will be included for the
818 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
819 as well as the STA2X11 PCIe I/O HUB.
822 tristate "Nuvoton I2C Controller"
823 depends on ARCH_NPCM7XX || COMPILE_TEST
825 If you say yes to this option, support will be included for the
826 Nuvoton I2C controller, which is available on the NPCM7xx BMC
828 Driver can also support slave mode (select I2C_SLAVE).
831 tristate "OpenCores I2C Controller"
833 If you say yes to this option, support will be included for the
834 OpenCores I2C controller. For details see
835 http://www.opencores.org/projects.cgi/web/i2c/overview
837 This driver can also be built as a module. If so, the module
838 will be called i2c-ocores.
841 tristate "OMAP I2C adapter"
842 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
843 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
845 If you say yes to this option, support will be included for the
846 I2C interface on the Texas Instruments OMAP1/2 family of processors.
847 Like OMAP1510/1610/1710/5912 and OMAP242x.
848 For details see http://www.ti.com/omap.
851 tristate "Actions Semiconductor Owl I2C Controller"
852 depends on ARCH_ACTIONS || COMPILE_TEST
854 Say Y here if you want to use the I2C bus controller on
855 the Actions Semiconductor Owl SoC's.
858 tristate "PA Semi SMBus interface"
859 depends on PPC_PASEMI && PCI
861 Supports the PA Semi PWRficient on-chip SMBus interfaces.
863 config I2C_PCA_PLATFORM
864 tristate "PCA9564/PCA9665 as platform device"
867 This driver supports a memory mapped Philips PCA9564/PCA9665
868 parallel bus to I2C bus controller.
870 This driver can also be built as a module. If so, the module
871 will be called i2c-pca-platform.
874 tristate "PMC MSP I2C TWI Controller"
875 depends on PMC_MSP || COMPILE_TEST
877 This driver supports the PMC TWI controller on MSP devices.
879 This driver can also be built as module. If so, the module
880 will be called i2c-pmcmsp.
883 tristate "I2C bus support for Philips PNX and NXP LPC targets"
884 depends on ARCH_LPC32XX || COMPILE_TEST
886 This driver supports the Philips IP3204 I2C IP block master and/or
889 This driver can also be built as a module. If so, the module
890 will be called i2c-pnx.
893 tristate "Intel PXA2XX I2C adapter"
894 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
896 If you have devices in the PXA I2C bus, say yes to this option.
897 This driver can also be built as a module. If so, the module
898 will be called i2c-pxa.
901 def_bool I2C_PXA && X86_32 && PCI && OF
904 bool "Intel PXA2XX I2C Slave comms support"
905 depends on I2C_PXA && !X86_32
908 Support I2C slave mode communications on the PXA I2C bus. This
909 is necessary for systems where the PXA may be a target on the
913 tristate "Qualcomm Camera Control Interface"
914 depends on ARCH_QCOM || COMPILE_TEST
916 If you say yes to this option, support will be included for the
917 built-in camera control interface on the Qualcomm SoCs.
919 This driver can also be built as a module. If so, the module
920 will be called i2c-qcom-cci.
923 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
924 depends on ARCH_QCOM || COMPILE_TEST
925 depends on QCOM_GENI_SE
927 This driver supports GENI serial engine based I2C controller in
928 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
929 yes to this option, support will be included for the built-in I2C
930 interface on the Qualcomm Technologies Inc.'s SoCs.
932 This driver can also be built as a module. If so, the module
933 will be called i2c-qcom-geni.
936 tristate "Qualcomm QUP based I2C controller"
939 If you say yes to this option, support will be included for the
940 built-in I2C interface on the Qualcomm SoCs.
942 This driver can also be built as a module. If so, the module
943 will be called i2c-qup.
946 tristate "Renesas RIIC adapter"
947 depends on ARCH_RENESAS || COMPILE_TEST
949 If you say yes to this option, support will be included for the
950 Renesas RIIC I2C interface.
952 This driver can also be built as a module. If so, the module
953 will be called i2c-riic.
956 tristate "Rockchip RK3xxx I2C adapter"
957 depends on OF && COMMON_CLK
959 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
962 This driver can also be built as a module. If so, the module will
965 config HAVE_S3C2410_I2C
968 This will include I2C support for Samsung SoCs. If you want to
969 include I2C support for any machine, kindly select this in the
970 respective Kconfig file.
973 tristate "S3C/Exynos I2C Driver"
974 depends on HAVE_S3C2410_I2C || COMPILE_TEST
976 Say Y here to include support for I2C controller in the
977 Samsung SoCs (S3C, S5Pv210, Exynos).
980 tristate "Renesas SH7760 I2C Controller"
981 depends on CPU_SUBTYPE_SH7760
983 This driver supports the 2 I2C interfaces on the Renesas SH7760.
985 This driver can also be built as a module. If so, the module
986 will be called i2c-sh7760.
989 tristate "SuperH Mobile I2C Controller"
990 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
992 If you say yes to this option, support will be included for the
993 built-in I2C interface on the Renesas SH-Mobile processor.
995 This driver can also be built as a module. If so, the module
996 will be called i2c-sh_mobile.
999 tristate "Simtec Generic I2C interface"
1002 If you say yes to this option, support will be included for
1003 the Simtec Generic I2C interface. This driver is for the
1004 simple I2C bus used on newer Simtec products for general
1005 I2C, such as DDC on the Simtec BBD2016A.
1007 This driver can also be built as a module. If so, the module
1008 will be called i2c-simtec.
1011 tristate "CSR SiRFprimaII I2C interface"
1012 depends on ARCH_SIRF || COMPILE_TEST
1014 If you say yes to this option, support will be included for the
1015 CSR SiRFprimaII I2C interface.
1017 This driver can also be built as a module. If so, the module
1018 will be called i2c-sirf.
1021 tristate "Spreadtrum I2C interface"
1022 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1024 If you say yes to this option, support will be included for the
1025 Spreadtrum I2C interface.
1028 tristate "STMicroelectronics SSC I2C support"
1029 depends on ARCH_STI || COMPILE_TEST
1031 Enable this option to add support for STMicroelectronics SoCs
1032 hardware SSC (Synchronous Serial Controller) as an I2C controller.
1034 This driver can also be built as module. If so, the module
1035 will be called i2c-st.
1038 tristate "STMicroelectronics STM32F4 I2C support"
1039 depends on ARCH_STM32 || COMPILE_TEST
1041 Enable this option to add support for STM32 I2C controller embedded
1044 This driver can also be built as module. If so, the module
1045 will be called i2c-stm32f4.
1048 tristate "STMicroelectronics STM32F7 I2C support"
1049 depends on ARCH_STM32 || COMPILE_TEST
1053 Enable this option to add support for STM32 I2C controller embedded
1056 This driver can also be built as module. If so, the module
1057 will be called i2c-stm32f7.
1060 tristate "ST Microelectronics DDC I2C interface"
1061 depends on MACH_U300 || COMPILE_TEST
1062 default y if MACH_U300
1064 If you say yes to this option, support will be included for the
1065 I2C interface from ST Microelectronics simply called "DDC I2C"
1066 supporting both I2C and DDC, used in e.g. the U300 series
1069 This driver can also be built as a module. If so, the module
1070 will be called i2c-stu300.
1072 config I2C_SUN6I_P2WI
1073 tristate "Allwinner sun6i internal P2WI controller"
1074 depends on RESET_CONTROLLER
1075 depends on MACH_SUN6I || COMPILE_TEST
1077 If you say yes to this option, support will be included for the
1078 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1080 The P2WI looks like an SMBus controller (which supports only byte
1081 accesses), except that it only supports one slave device.
1082 This interface is used to connect to specific PMIC devices (like the
1085 config I2C_SYNQUACER
1086 tristate "Socionext SynQuacer I2C controller"
1087 depends on ARCH_SYNQUACER || COMPILE_TEST
1089 Say Y here to include support for the I2C controller used in some
1090 Fujitsu and Socionext SoCs.
1092 This driver can also be built as a module. If so, the module
1093 will be called i2c-synquacer.
1096 tristate "NVIDIA Tegra internal I2C controller"
1097 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1098 # COMPILE_TEST needs architectures with readsX()/writesX() primitives
1100 If you say yes to this option, support will be included for the
1101 I2C controller embedded in NVIDIA Tegra SOCs
1103 config I2C_TEGRA_BPMP
1104 tristate "NVIDIA Tegra BPMP I2C controller"
1105 depends on TEGRA_BPMP || COMPILE_TEST
1106 default y if TEGRA_BPMP
1108 If you say yes to this option, support will be included for the I2C
1109 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1111 This I2C driver is a 'virtual' I2C driver. The real driver is part
1112 of the BPMP firmware, and this driver merely communicates with that
1116 tristate "UniPhier FIFO-less I2C controller"
1117 depends on ARCH_UNIPHIER || COMPILE_TEST
1119 If you say yes to this option, support will be included for
1120 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1121 or older UniPhier SoCs.
1123 config I2C_UNIPHIER_F
1124 tristate "UniPhier FIFO-builtin I2C controller"
1125 depends on ARCH_UNIPHIER || COMPILE_TEST
1127 If you say yes to this option, support will be included for
1128 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1129 PH1-Pro5, or newer UniPhier SoCs.
1131 config I2C_VERSATILE
1132 tristate "ARM Versatile/Realview I2C bus support"
1133 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1136 Say yes if you want to support the I2C serial bus on ARMs Versatile
1139 This driver can also be built as a module. If so, the module
1140 will be called i2c-versatile.
1143 tristate "Wondermedia WM8xxx SoC I2C bus support"
1144 depends on ARCH_VT8500 || COMPILE_TEST
1146 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1149 This driver can also be built as a module. If so, the module will be
1153 tristate "Cavium OCTEON I2C bus support"
1154 depends on CAVIUM_OCTEON_SOC
1156 Say yes if you want to support the I2C serial bus on Cavium
1159 This driver can also be built as a module. If so, the module
1160 will be called i2c-octeon.
1163 tristate "Cavium ThunderX I2C bus support"
1164 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1167 Say yes if you want to support the I2C serial bus on Cavium
1170 This driver can also be built as a module. If so, the module
1171 will be called i2c-thunderx.
1174 tristate "Xilinx I2C Controller"
1175 depends on HAS_IOMEM
1177 If you say yes to this option, support will be included for the
1178 Xilinx I2C controller.
1180 This driver can also be built as a module. If so, the module
1181 will be called xilinx_i2c.
1184 tristate "Netlogic XLR and Sigma Designs I2C support"
1185 depends on CPU_XLR || ARCH_TANGO || COMPILE_TEST
1187 This driver enables support for the on-chip I2C interface of
1188 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1190 This driver can also be built as a module. If so, the module
1191 will be called i2c-xlr.
1194 tristate "XLP9XX I2C support"
1195 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1197 This driver enables support for the on-chip I2C interface of
1198 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1200 This driver can also be built as a module. If so, the module will
1201 be called i2c-xlp9xx.
1204 tristate "Renesas R-Car I2C Controller"
1205 depends on ARCH_RENESAS || COMPILE_TEST
1208 select RESET_CONTROLLER if ARCH_RCAR_GEN3
1210 If you say yes to this option, support will be included for the
1211 R-Car I2C controller.
1213 This driver can also be built as a module. If so, the module
1214 will be called i2c-rcar.
1216 comment "External I2C/SMBus adapter drivers"
1218 config I2C_DIOLAN_U2C
1219 tristate "Diolan U2C-12 USB adapter"
1222 If you say yes to this option, support will be included for Diolan
1223 U2C-12, a USB to I2C interface.
1225 This driver can also be built as a module. If so, the module
1226 will be called i2c-diolan-u2c.
1229 tristate "Diolan DLN-2 USB I2C adapter"
1232 If you say yes to this option, support will be included for Diolan
1233 DLN2, a USB to I2C interface.
1235 This driver can also be built as a module. If so, the module
1236 will be called i2c-dln2.
1239 tristate "Parallel port adapter"
1244 This supports parallel port I2C adapters such as the ones made by
1245 Philips or Velleman, Analog Devices evaluation boards, and more.
1246 Basically any adapter using the parallel port as an I2C bus with
1247 no extra chipset is supported by this driver, or could be. Please
1248 read the file Documentation/i2c/busses/i2c-parport.rst for details.
1250 This support is also available as a module. If so, the module
1251 will be called i2c-parport.
1253 config I2C_ROBOTFUZZ_OSIF
1254 tristate "RobotFuzz Open Source InterFace USB adapter"
1257 If you say yes to this option, support will be included for the
1258 RobotFuzz Open Source InterFace USB to I2C interface.
1260 This driver can also be built as a module. If so, the module
1261 will be called i2c-osif.
1264 tristate "TAOS evaluation module"
1267 select SERIO_SERPORT
1269 This supports TAOS evaluation modules on serial port. In order to
1270 use this driver, you will need the inputattach tool, which is part
1271 of the input-utils package.
1275 This support is also available as a module. If so, the module
1276 will be called i2c-taos-evm.
1279 tristate "Tiny-USB adapter"
1282 If you say yes to this option, support will be included for the
1283 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1284 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1286 This driver can also be built as a module. If so, the module
1287 will be called i2c-tiny-usb.
1289 config I2C_VIPERBOARD
1290 tristate "Viperboard I2C master support"
1291 depends on MFD_VIPERBOARD && USB
1293 Say yes here to access the I2C part of the Nano River
1294 Technologies Viperboard as I2C master.
1295 See viperboard API specification and Nano
1296 River Tech's viperboard.h for detailed meaning
1297 of the module parameters.
1299 comment "Other I2C/SMBus bus drivers"
1302 tristate "Acorn IOC/IOMD I2C bus support"
1303 depends on ARCH_ACORN
1307 Say yes if you want to support the I2C bus on Acorn platforms.
1309 If you don't know, say Y.
1312 tristate "Elektor ISA card"
1313 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1316 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1319 This support is also available as a module. If so, the module
1320 will be called i2c-elektor.
1323 tristate "ICY Zorro card"
1327 This supports the PCF8584 Zorro bus I2C adapter, known as ICY.
1328 Say Y if you own such an adapter.
1330 This support is also available as a module. If so, the module
1331 will be called i2c-icy.
1333 If you have a 2019 edition board with an LTC2990 sensor at address
1334 0x4c, loading the module 'ltc2990' is sufficient to enable it.
1337 tristate "Mellanox I2C driver"
1338 depends on X86_64 || COMPILE_TEST
1340 This exposes the Mellanox platform I2C busses to the linux I2C layer
1341 for X86 based systems.
1342 Controller is implemented as CPLD logic.
1344 This driver can also be built as a module. If so, the module will be
1345 called as i2c-mlxcpld.
1348 tristate "PCA9564/PCA9665 on an ISA bus"
1352 This driver supports ISA boards using the Philips PCA9564/PCA9665
1353 parallel bus to I2C bus controller.
1355 This driver can also be built as a module. If so, the module
1356 will be called i2c-pca-isa.
1358 This device is almost undetectable and using this driver on a
1359 system which doesn't have this device will result in long
1360 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1361 time). If unsure, say N.
1364 tristate "SiByte SMBus interface"
1365 depends on SIBYTE_SB1xxx_SOC
1367 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1369 config I2C_CROS_EC_TUNNEL
1370 tristate "ChromeOS EC tunnel I2C bus"
1373 If you say yes here you get an I2C bus that will tunnel i2c commands
1374 through to the other side of the ChromeOS EC to the i2c bus
1375 connected there. This will work whatever the interface used to
1376 talk to the EC (SPI, I2C or LPC).
1378 config I2C_XGENE_SLIMPRO
1379 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1380 depends on ARCH_XGENE && MAILBOX
1382 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1383 co-processor. The I2C device access the I2C bus via the X-Gene
1384 to SLIMpro (On chip coprocessor) mailbox mechanism.
1388 tristate "Geode ACCESS.bus support"
1389 depends on X86_32 && PCI
1391 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1392 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1394 If you don't know what to do here, say N.
1396 This support is also available as a module. If so, the module
1397 will be called scx200_acb.
1400 tristate "IBM OPAL I2C driver"
1401 depends on PPC_POWERNV
1404 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1405 the driver is based on the OPAL interfaces.
1407 This driver can also be built as a module. If so, the module will be
1411 tristate "ZTE ZX2967 I2C support"
1415 Selecting this option will add ZX2967 I2C driver.
1416 This driver can also be built as a module. If so, the module will be
1420 tristate "FSI I2C driver"
1423 Driver for FSI bus attached I2C masters. These are I2C masters that
1424 are connected to the system over an FSI bus, instead of the more
1425 common PCI or MMIO interface.
1427 This driver can also be built as a module. If so, the module will be