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"
13 tristate "BCM2708 BSC"
14 depends on ARCH_BCM2835
16 Enabling this option will add BSC (Broadcom Serial Controller)
17 support for the BCM2708. BSC is a Broadcom proprietary bus compatible
20 config I2C_BCM2708_BAUDRATE
21 prompt "BCM2708 I2C baudrate"
22 depends on I2C_BCM2708
26 Set the I2C baudrate. This will alter the default value. A
27 different baudrate can be set by using a module parameter as well. If
28 no parameter is provided when loading, this is the value that will be
35 If you say yes to this option, support will be included for the SMB
36 Host controller on Acer Labs Inc. (ALI) M1535 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-ali1535.
47 If you say yes to this option, support will be included for the SMB
48 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
49 controller is part of the 7101 device, which is an ACPI-compliant
50 Power Management Unit (PMU).
52 This driver can also be built as a module. If so, the module
53 will be called i2c-ali1563.
59 If you say yes to this option, support will be included for the
60 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
62 This driver can also be built as a module. If so, the module
63 will be called i2c-ali15x3.
66 tristate "AMD 756/766/768/8111 and nVidia nForce"
69 If you say yes to this option, support will be included for the AMD
70 756/766/768 mainboard I2C interfaces. The driver also includes
71 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
72 the nVidia nForce I2C interface.
74 This driver can also be built as a module. If so, the module
75 will be called i2c-amd756.
77 config I2C_AMD756_S4882
78 tristate "SMBus multiplexing on the Tyan S4882"
79 depends on I2C_AMD756 && X86
81 Enabling this option will add specific SMBus support for the Tyan
82 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
83 over 8 different channels, where the various memory module EEPROMs
84 and temperature sensors live. Saying yes here will give you access
85 to these in addition to the trunk.
87 This driver can also be built as a module. If so, the module
88 will be called i2c-amd756-s4882.
94 If you say yes to this option, support will be included for the
95 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
97 This driver can also be built as a module. If so, the module
98 will be called i2c-amd8111.
101 tristate "AMD MP2 PCIe"
102 depends on PCI && ACPI
104 If you say yes to this option, support will be included for the AMD
105 MP2 PCIe I2C adapter.
107 This driver can also be built as modules. If so, the modules will
108 be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
111 tristate "Hix5hd2 high-speed I2C driver"
112 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
114 Say Y here to include support for the high-speed I2C controller
115 used in HiSilicon hix5hd2 SoCs.
117 This driver can also be built as a module. If so, the module
118 will be called i2c-hix5hd2.
121 tristate "Intel 82801 (ICH/PCH)"
123 select CHECK_SIGNATURE if X86 && DMI
126 If you say yes to this option, support will be included for the Intel
127 801 family of mainboard I2C interfaces. Specifically, the following
128 versions of the chipset are supported:
134 82801EB/ER (ICH5/ICH5R)
171 This driver can also be built as a module. If so, the module
172 will be called i2c-i801.
175 tristate "Intel SCH SMBus 1.0"
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)"
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"
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"
268 If you say yes to this option, support will be included for the
269 NVIDIA GPU I2C controller which is used to communicate with the GPU's
270 Type-C controller. This driver can also be built as a module called
277 If you say yes to this option, support will be included for the
278 SiS5595 SMBus (a subset of I2C) interface.
280 This driver can also be built as a module. If so, the module
281 will be called i2c-sis5595.
284 tristate "SiS 630/730/964"
287 If you say yes to this option, support will be included for the
288 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
290 This driver can also be built as a module. If so, the module
291 will be called i2c-sis630.
297 If you say yes to this option, support will be included for the SiS
298 96x SMBus (a subset of I2C) interfaces. Specifically, the following
299 chipsets are supported:
308 This driver can also be built as a module. If so, the module
309 will be called i2c-sis96x.
312 tristate "VIA VT82C586B"
316 If you say yes to this option, support will be included for the VIA
317 82C586B I2C interface
319 This driver can also be built as a module. If so, the module
320 will be called i2c-via.
323 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
326 If you say yes to this option, support will be included for the VIA
327 VT82C596 and later SMBus interface. Specifically, the following
328 chipsets are supported:
341 This driver can also be built as a module. If so, the module
342 will be called i2c-viapro.
346 comment "ACPI drivers"
349 tristate "SMBus Control Method Interface"
351 This driver supports the SMBus Control Method Interface. It needs the
352 BIOS to declare ACPI control methods as described in the SMBus Control
353 Method Interface specification.
355 To compile this driver as a module, choose M here:
356 the module will be called i2c-scmi.
360 comment "Mac SMBus host controller drivers"
361 depends on PPC_CHRP || PPC_PMAC
364 tristate "CHRP Apple Hydra Mac I/O I2C interface"
365 depends on PCI && PPC_CHRP
368 This supports the use of the I2C interface in the Apple Hydra Mac
369 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
372 This support is also available as a module. If so, the module
373 will be called i2c-hydra.
376 tristate "Powermac I2C interface"
380 This exposes the various PowerMac i2c interfaces to the linux i2c
381 layer and to userland. It is used by various drivers on the PowerMac
382 platform, and should generally be enabled.
384 This support is also available as a module. If so, the module
385 will be called i2c-powermac.
387 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
390 tristate "Altera Soft IP I2C"
391 depends on ARCH_INTEL_SOCFPGA || NIOS2 || COMPILE_TEST
394 If you say yes to this option, support will be included for the
395 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-altera.
401 tristate "Aspeed I2C Controller"
402 depends on ARCH_ASPEED || COMPILE_TEST
404 If you say yes to this option, support will be included for the
405 Aspeed I2C controller.
407 This driver can also be built as a module. If so, the module
408 will be called i2c-aspeed.
411 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
412 depends on ARCH_AT91 || COMPILE_TEST
414 This supports the use of the I2C interface on Atmel AT91
417 A serious problem is that there is no documented way to issue
418 repeated START conditions for more than two messages, as needed
419 to support combined I2C messages. Use the i2c-gpio driver
420 unless your system can cope with this limitation.
422 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
423 don't have clock stretching in transmission mode. For that reason,
424 you can encounter underrun issues causing premature stop sendings if
425 the latency to fill the transmission register is too long. If you
426 are facing this situation, use the i2c-gpio driver.
428 config I2C_AT91_SLAVE_EXPERIMENTAL
429 tristate "Microchip AT91 I2C experimental slave mode"
433 If you say yes to this option, support for the slave mode will be
434 added. Caution: do not use it for production. This feature has not
435 been tested in a heavy way, help wanted.
436 There are known bugs:
437 - It can hang, on a SAMA5D4, after several transfers.
438 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
442 tristate "Au1550/Au1200/Au1300 SMBus interface"
443 depends on MIPS_ALCHEMY
445 If you say yes to this option, support will be included for the
446 Au1550/Au1200/Au1300 SMBus interface.
448 This driver can also be built as a module. If so, the module
449 will be called i2c-au1550.
452 tristate "Axxia I2C controller"
453 depends on ARCH_AXXIA || COMPILE_TEST
457 Say yes if you want to support the I2C bus on Axxia platforms.
459 Please note that this controller is limited to transfers of maximum
460 255 bytes in length. Any attempt to to a larger transfer will return
464 tristate "Broadcom BCM2835 I2C controller"
465 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
466 depends on COMMON_CLK
468 If you say yes to this option, support will be included for the
469 BCM2835 I2C controller.
471 If you don't know what to do here, say N.
473 This support is also available as a module. If so, the module
474 will be called i2c-bcm2835.
477 tristate "Broadcom iProc I2C controller"
478 depends on ARCH_BCM_IPROC || COMPILE_TEST
479 default ARCH_BCM_IPROC
482 If you say yes to this option, support will be included for the
483 Broadcom iProc I2C controller.
485 If you don't know what to do here, say N.
488 tristate "BCM Kona I2C adapter"
489 depends on ARCH_BCM_MOBILE || COMPILE_TEST
490 default y if ARCH_BCM_MOBILE
492 If you say yes to this option, support will be included for the
493 I2C interface on the Broadcom Kona family of processors.
495 If you do not need KONA I2C interface, say N.
498 tristate "BRCM Settop/DSL I2C controller"
499 depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
500 ARCH_BCM_63XX || COMPILE_TEST
503 If you say yes to this option, support will be included for the
504 I2C interface on the Broadcom Settop/DSL SoCs.
506 If you do not need I2C interface, say N.
509 tristate "Cadence I2C Controller"
510 depends on ARCH_ZYNQ || ARM64 || XTENSA || COMPILE_TEST
512 Say yes here to select Cadence I2C Host Controller. This controller is
513 e.g. used by Xilinx Zynq.
516 tristate "CBUS I2C driver"
517 depends on GPIOLIB || COMPILE_TEST
519 Support for CBUS access using I2C API. Mostly relevant for Nokia
520 Internet Tablets (770, N800 and N810).
522 This driver can also be built as a module. If so, the module
523 will be called i2c-cbus-gpio.
526 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
527 depends on CPM1 || CPM2
529 This supports the use of the I2C interface on Freescale
530 processors with CPM1 or CPM2.
532 This driver can also be built as a module. If so, the module
533 will be called i2c-cpm.
536 tristate "DaVinci I2C driver"
537 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
539 Support for TI DaVinci I2C controller driver.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-davinci.
544 Please note that this driver might be needed to bring up other
545 devices such as DaVinci NIC.
546 For details please see http://www.ti.com/davinci
548 config I2C_DESIGNWARE_CORE
552 config I2C_DESIGNWARE_SLAVE
553 bool "Synopsys DesignWare Slave"
554 depends on I2C_DESIGNWARE_CORE
557 If you say yes to this option, support will be included for the
558 Synopsys DesignWare I2C slave adapter.
560 This is not a standalone module, this module compiles together with
563 config I2C_DESIGNWARE_PLATFORM
564 tristate "Synopsys DesignWare Platform"
565 depends on (ACPI && COMMON_CLK) || !ACPI
566 select I2C_DESIGNWARE_CORE
567 select MFD_SYSCON if MIPS_BAIKAL_T1
569 If you say yes to this option, support will be included for the
570 Synopsys DesignWare I2C adapter.
572 This driver can also be built as a module. If so, the module
573 will be called i2c-designware-platform.
575 config I2C_DESIGNWARE_BAYTRAIL
576 bool "Intel Baytrail I2C semaphore support"
578 depends on I2C_DESIGNWARE_PLATFORM
579 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
580 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
582 This driver enables managed host access to the PMIC I2C bus on select
583 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
584 the host to request uninterrupted access to the PMIC's I2C bus from
585 the platform firmware controlling it. You should say Y if running on
586 a BayTrail system using the AXP288.
588 config I2C_DESIGNWARE_PCI
589 tristate "Synopsys DesignWare PCI"
591 select I2C_DESIGNWARE_CORE
593 If you say yes to this option, support will be included for the
594 Synopsys DesignWare I2C adapter. Only master mode is supported.
596 This driver can also be built as a module. If so, the module
597 will be called i2c-designware-pci.
600 tristate "Conexant Digicolor I2C driver"
601 depends on ARCH_DIGICOLOR || COMPILE_TEST
603 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
605 This driver can also be built as a module. If so, the module
606 will be called i2c-digicolor.
609 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
610 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
612 This driver is for PCH(Platform controller Hub) I2C of EG20T which
613 is an IOH(Input/Output Hub) for x86 embedded processor.
614 This driver can access PCH I2C bus device.
616 This driver also can be used for LAPIS Semiconductor IOH(Input/
617 Output Hub), ML7213, ML7223 and ML7831.
618 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
619 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
620 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
621 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
624 tristate "EMMA Mobile series I2C adapter"
628 If you say yes to this option, support will be included for the
629 I2C interface on the Renesas Electronics EM/EV family of processors.
632 tristate "Exynos high-speed I2C driver"
634 depends on ARCH_EXYNOS || COMPILE_TEST
635 default y if ARCH_EXYNOS
637 High-speed I2C controller on Exynos5 and newer Samsung SoCs.
640 tristate "GPIO-based bitbanging I2C"
641 depends on GPIOLIB || COMPILE_TEST
644 This is a very simple bitbanging I2C driver utilizing the
645 arch-neutral GPIO API to control the SCL and SDA lines.
647 config I2C_GPIO_FAULT_INJECTOR
648 bool "GPIO-based fault injector"
651 This adds some functionality to the i2c-gpio driver which can inject
652 faults to an I2C bus, so another bus master can be stress-tested.
653 This is for debugging. If unsure, say 'no'.
655 config I2C_HIGHLANDER
656 tristate "Highlander FPGA SMBus interface"
657 depends on SH_HIGHLANDER || COMPILE_TEST
659 If you say yes to this option, support will be included for
660 the SMBus interface located in the FPGA on various Highlander
661 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
662 FPGAs. This is wholly unrelated to the SoC I2C.
664 This driver can also be built as a module. If so, the module
665 will be called i2c-highlander.
668 tristate "HiSilicon I2C controller"
669 depends on (ARM64 && ACPI) || COMPILE_TEST
671 Say Y here if you want to have Hisilicon I2C controller support
672 available on the Kunpeng Server.
674 This driver can also be built as a module. If so, the module
675 will be called i2c-hisi.
678 tristate "IBM PPC 4xx on-chip I2C interface"
681 Say Y here if you want to use IIC peripheral found on
682 embedded IBM PPC 4xx based systems.
684 This driver can also be built as a module. If so, the module
685 will be called i2c-ibm_iic.
688 tristate "Imagination Technologies I2C SCB Controller"
689 depends on MIPS || COMPILE_TEST
691 Say Y here if you want to use the IMG I2C SCB controller,
692 available on the TZ1090 and other IMG SoCs.
694 This driver can also be built as a module. If so, the module
695 will be called i2c-img-scb.
698 tristate "IMX I2C interface"
699 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE || COMPILE_TEST
702 Say Y here if you want to use the IIC bus controller on
703 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
705 This driver can also be built as a module. If so, the module
706 will be called i2c-imx.
709 tristate "IMX Low Power I2C interface"
710 depends on ARCH_MXC || COMPILE_TEST
712 Say Y here if you want to use the Low Power IIC bus controller
713 on the Freescale i.MX processors.
715 This driver can also be built as a module. If so, the module
716 will be called i2c-imx-lpi2c.
719 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
720 depends on ARCH_IOP32X || ARCH_IXP4XX || COMPILE_TEST
722 Say Y here if you want to use the IIC bus controller on
723 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
725 This driver can also be built as a module. If so, the module
726 will be called i2c-iop3xx.
729 tristate "JZ4780 I2C controller interface support"
730 depends on MIPS || COMPILE_TEST
732 If you say yes to this option, support will be included for the
733 Ingenic JZ4780 I2C controller.
735 If you don't know what to do here, say N.
738 tristate "Kontron COM I2C Controller"
739 depends on MFD_KEMPLD
741 This enables support for the I2C bus interface on some Kontron ETX
742 and COMexpress (ETXexpress) modules.
744 This driver can also be built as a module. If so, the module
745 will be called i2c-kempld.
748 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
749 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
751 This driver supports the I2C interface found several NXP
752 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
754 This driver can also be built as a module. If so, the module
755 will be called i2c-lpc2k.
758 tristate "Mellanox BlueField I2C controller"
759 depends on MELLANOX_PLATFORM && ARM64
762 Enabling this option will add I2C SMBus support for Mellanox BlueField
765 This driver can also be built as a module. If so, the module will be
768 This driver implements an I2C SMBus host controller and enables both
769 master and slave functions.
772 tristate "Amlogic Meson I2C controller"
773 depends on ARCH_MESON || COMPILE_TEST
774 depends on COMMON_CLK
776 If you say yes to this option, support will be included for the
777 I2C interface on the Amlogic Meson family of SoCs.
780 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
783 If you say yes to this option, support will be included for the
784 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
785 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
787 This driver can also be built as a module. If so, the module
788 will be called i2c-mpc.
791 tristate "MediaTek I2C adapter"
792 depends on ARCH_MEDIATEK || COMPILE_TEST
794 This selects the MediaTek(R) Integrated Inter Circuit bus driver
795 for MT65xx and MT81xx.
796 If you want to use MediaTek(R) I2C interface, say Y or M here.
800 tristate "MT7621/MT7628 I2C Controller"
801 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || COMPILE_TEST
803 Say Y here to include support for I2C controller in the
804 MediaTek MT7621/MT7628 SoCs.
807 tristate "Marvell mv64xxx I2C Controller"
808 depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST
810 If you say yes to this option, support will be included for the
811 built-in I2C interface on the Marvell 64xxx line of host bridges.
812 This driver is also used for Allwinner SoCs I2C controllers.
814 This driver can also be built as a module. If so, the module
815 will be called i2c-mv64xxx.
818 tristate "Freescale i.MX28 I2C interface"
819 depends on SOC_IMX28 || COMPILE_TEST
822 Say Y here if you want to use the I2C bus controller on
823 the Freescale i.MX28 processors.
825 This driver can also be built as a module. If so, the module
826 will be called i2c-mxs.
829 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
832 If you say yes to this option, support will be included for the
833 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
834 as well as the STA2X11 PCIe I/O HUB.
837 tristate "Nuvoton I2C Controller"
838 depends on ARCH_NPCM7XX || COMPILE_TEST
840 If you say yes to this option, support will be included for the
841 Nuvoton I2C controller, which is available on the NPCM7xx BMC
843 Driver can also support slave mode (select I2C_SLAVE).
846 tristate "OpenCores I2C Controller"
848 If you say yes to this option, support will be included for the
849 OpenCores I2C controller. For details see
850 http://www.opencores.org/projects.cgi/web/i2c/overview
852 This driver can also be built as a module. If so, the module
853 will be called i2c-ocores.
856 tristate "OMAP I2C adapter"
857 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST
858 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
860 If you say yes to this option, support will be included for the
861 I2C interface on the Texas Instruments OMAP1/2 family of processors.
862 Like OMAP1510/1610/1710/5912 and OMAP242x.
863 For details see http://www.ti.com/omap.
866 tristate "Actions Semiconductor Owl I2C Controller"
867 depends on ARCH_ACTIONS || COMPILE_TEST
869 Say Y here if you want to use the I2C bus controller on
870 the Actions Semiconductor Owl SoC's.
873 tristate "PA Semi SMBus interface"
874 depends on PPC_PASEMI && PCI
876 Supports the PA Semi PWRficient on-chip SMBus interfaces.
878 config I2C_PCA_PLATFORM
879 tristate "PCA9564/PCA9665 as platform device"
882 This driver supports a memory mapped Philips PCA9564/PCA9665
883 parallel bus to I2C bus controller.
885 This driver can also be built as a module. If so, the module
886 will be called i2c-pca-platform.
889 tristate "I2C bus support for Philips PNX and NXP LPC targets"
890 depends on ARCH_LPC32XX || COMPILE_TEST
892 This driver supports the Philips IP3204 I2C IP block master and/or
895 This driver can also be built as a module. If so, the module
896 will be called i2c-pnx.
899 tristate "Intel PXA2XX I2C adapter"
900 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST
902 If you have devices in the PXA I2C bus, say yes to this option.
903 This driver can also be built as a module. If so, the module
904 will be called i2c-pxa.
907 def_bool I2C_PXA && X86_32 && PCI && OF
910 bool "Intel PXA2XX I2C Slave comms support"
911 depends on I2C_PXA && !X86_32
914 Support I2C slave mode communications on the PXA I2C bus. This
915 is necessary for systems where the PXA may be a target on the
919 tristate "Qualcomm Camera Control Interface"
920 depends on ARCH_QCOM || COMPILE_TEST
922 If you say yes to this option, support will be included for the
923 built-in camera control interface on the Qualcomm SoCs.
925 This driver can also be built as a module. If so, the module
926 will be called i2c-qcom-cci.
929 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
930 depends on ARCH_QCOM || COMPILE_TEST
931 depends on QCOM_GENI_SE
933 This driver supports GENI serial engine based I2C controller in
934 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
935 yes to this option, support will be included for the built-in I2C
936 interface on the Qualcomm Technologies Inc.'s SoCs.
938 This driver can also be built as a module. If so, the module
939 will be called i2c-qcom-geni.
942 tristate "Qualcomm QUP based I2C controller"
943 depends on ARCH_QCOM || COMPILE_TEST
945 If you say yes to this option, support will be included for the
946 built-in I2C interface on the Qualcomm SoCs.
948 This driver can also be built as a module. If so, the module
949 will be called i2c-qup.
952 tristate "Renesas RIIC adapter"
953 depends on ARCH_RENESAS || COMPILE_TEST
955 If you say yes to this option, support will be included for the
956 Renesas RIIC I2C interface.
958 This driver can also be built as a module. If so, the module
959 will be called i2c-riic.
962 tristate "Rockchip RK3xxx I2C adapter"
963 depends on OF && COMMON_CLK
965 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
968 This driver can also be built as a module. If so, the module will
971 config HAVE_S3C2410_I2C
974 This will include I2C support for Samsung SoCs. If you want to
975 include I2C support for any machine, kindly select this in the
976 respective Kconfig file.
979 tristate "S3C/Exynos I2C Driver"
980 depends on HAVE_S3C2410_I2C || COMPILE_TEST
982 Say Y here to include support for I2C controller in the
983 Samsung SoCs (S3C, S5Pv210, Exynos).
986 tristate "Renesas SH7760 I2C Controller"
987 depends on CPU_SUBTYPE_SH7760
989 This driver supports the 2 I2C interfaces on the Renesas SH7760.
991 This driver can also be built as a module. If so, the module
992 will be called i2c-sh7760.
995 tristate "SuperH Mobile I2C Controller"
996 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
998 If you say yes to this option, support will be included for the
999 built-in I2C interface on the Renesas SH-Mobile processor.
1001 This driver can also be built as a module. If so, the module
1002 will be called i2c-sh_mobile.
1005 tristate "Simtec Generic I2C interface"
1008 If you say yes to this option, support will be included for
1009 the Simtec Generic I2C interface. This driver is for the
1010 simple I2C bus used on newer Simtec products for general
1011 I2C, such as DDC on the Simtec BBD2016A.
1013 This driver can also be built as a module. If so, the module
1014 will be called i2c-simtec.
1017 tristate "Spreadtrum I2C interface"
1018 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST)
1019 depends on COMMON_CLK
1021 If you say yes to this option, support will be included for the
1022 Spreadtrum I2C interface.
1025 tristate "STMicroelectronics SSC I2C support"
1026 depends on ARCH_STI || COMPILE_TEST
1028 Enable this option to add support for STMicroelectronics SoCs
1029 hardware SSC (Synchronous Serial Controller) as an I2C controller.
1031 This driver can also be built as module. If so, the module
1032 will be called i2c-st.
1035 tristate "STMicroelectronics STM32F4 I2C support"
1036 depends on ARCH_STM32 || COMPILE_TEST
1038 Enable this option to add support for STM32 I2C controller embedded
1041 This driver can also be built as module. If so, the module
1042 will be called i2c-stm32f4.
1045 tristate "STMicroelectronics STM32F7 I2C support"
1046 depends on ARCH_STM32 || COMPILE_TEST
1050 Enable this option to add support for STM32 I2C controller embedded
1053 This driver can also be built as module. If so, the module
1054 will be called i2c-stm32f7.
1056 config I2C_SUN6I_P2WI
1057 tristate "Allwinner sun6i internal P2WI controller"
1058 depends on RESET_CONTROLLER
1059 depends on MACH_SUN6I || COMPILE_TEST
1061 If you say yes to this option, support will be included for the
1062 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1064 The P2WI looks like an SMBus controller (which supports only byte
1065 accesses), except that it only supports one slave device.
1066 This interface is used to connect to specific PMIC devices (like the
1069 config I2C_SYNQUACER
1070 tristate "Socionext SynQuacer I2C controller"
1071 depends on ARCH_SYNQUACER || COMPILE_TEST
1073 Say Y here to include support for the I2C controller used in some
1074 Fujitsu and Socionext SoCs.
1076 This driver can also be built as a module. If so, the module
1077 will be called i2c-synquacer.
1080 tristate "NVIDIA Tegra internal I2C controller"
1081 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC))
1082 # COMPILE_TEST needs architectures with readsX()/writesX() primitives
1084 If you say yes to this option, support will be included for the
1085 I2C controller embedded in NVIDIA Tegra SOCs
1087 config I2C_TEGRA_BPMP
1088 tristate "NVIDIA Tegra BPMP I2C controller"
1089 depends on TEGRA_BPMP || COMPILE_TEST
1090 default y if TEGRA_BPMP
1092 If you say yes to this option, support will be included for the I2C
1093 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1095 This I2C driver is a 'virtual' I2C driver. The real driver is part
1096 of the BPMP firmware, and this driver merely communicates with that
1100 tristate "UniPhier FIFO-less I2C controller"
1101 depends on ARCH_UNIPHIER || COMPILE_TEST
1103 If you say yes to this option, support will be included for
1104 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1105 or older UniPhier SoCs.
1107 config I2C_UNIPHIER_F
1108 tristate "UniPhier FIFO-builtin I2C controller"
1109 depends on ARCH_UNIPHIER || COMPILE_TEST
1111 If you say yes to this option, support will be included for
1112 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1113 PH1-Pro5, or newer UniPhier SoCs.
1115 config I2C_VERSATILE
1116 tristate "ARM Versatile/Realview I2C bus support"
1117 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1120 Say yes if you want to support the I2C serial bus on ARMs Versatile
1123 This driver can also be built as a module. If so, the module
1124 will be called i2c-versatile.
1127 tristate "Wondermedia WM8xxx SoC I2C bus support"
1128 depends on ARCH_VT8500 || COMPILE_TEST
1130 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1133 This driver can also be built as a module. If so, the module will be
1137 tristate "Cavium OCTEON I2C bus support"
1138 depends on CAVIUM_OCTEON_SOC
1140 Say yes if you want to support the I2C serial bus on Cavium
1143 This driver can also be built as a module. If so, the module
1144 will be called i2c-octeon.
1147 tristate "Cavium ThunderX I2C bus support"
1148 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1151 Say yes if you want to support the I2C serial bus on Cavium
1154 This driver can also be built as a module. If so, the module
1155 will be called i2c-thunderx.
1158 tristate "Xilinx I2C Controller"
1159 depends on HAS_IOMEM
1161 If you say yes to this option, support will be included for the
1162 Xilinx I2C controller.
1164 This driver can also be built as a module. If so, the module
1165 will be called xilinx_i2c.
1168 tristate "Netlogic XLR I2C support"
1169 depends on CPU_XLR || COMPILE_TEST
1171 This driver enables support for the on-chip I2C interface of
1172 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1174 This driver can also be built as a module. If so, the module
1175 will be called i2c-xlr.
1178 tristate "XLP9XX I2C support"
1179 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1181 This driver enables support for the on-chip I2C interface of
1182 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1184 This driver can also be built as a module. If so, the module will
1185 be called i2c-xlp9xx.
1188 tristate "Renesas R-Car I2C Controller"
1189 depends on ARCH_RENESAS || COMPILE_TEST
1192 select RESET_CONTROLLER if ARCH_RCAR_GEN3
1194 If you say yes to this option, support will be included for the
1195 R-Car I2C controller.
1197 This driver can also be built as a module. If so, the module
1198 will be called i2c-rcar.
1200 comment "External I2C/SMBus adapter drivers"
1202 config I2C_DIOLAN_U2C
1203 tristate "Diolan U2C-12 USB adapter"
1206 If you say yes to this option, support will be included for Diolan
1207 U2C-12, a USB to I2C interface.
1209 This driver can also be built as a module. If so, the module
1210 will be called i2c-diolan-u2c.
1213 tristate "Diolan DLN-2 USB I2C adapter"
1216 If you say yes to this option, support will be included for Diolan
1217 DLN2, a USB to I2C interface.
1219 This driver can also be built as a module. If so, the module
1220 will be called i2c-dln2.
1223 tristate "Silicon Labs CP2615 USB sound card and I2C adapter"
1226 If you say yes to this option, support will be included for Silicon
1227 Labs CP2615's I2C interface.
1229 This driver can also be built as a module. If so, the module
1230 will be called i2c-cp2615.
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 "FSI I2C driver"
1408 Driver for FSI bus attached I2C masters. These are I2C masters that
1409 are connected to the system over an FSI bus, instead of the more
1410 common PCI or MMIO interface.
1412 This driver can also be built as a module. If so, the module will be
1416 tristate "Virtio I2C Adapter"
1419 If you say yes to this option, support will be included for the virtio
1420 I2C adapter driver. The hardware can be emulated by any device model
1421 software according to the virtio protocol.
1423 This driver can also be built as a module. If so, the module
1424 will be called i2c-virtio.