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)
147 This driver can also be built as a module. If so, the module
148 will be called i2c-i801.
151 tristate "Intel SCH SMBus 1.0"
155 Say Y here if you want to use SMBus controller on the Intel SCH
158 This driver can also be built as a module. If so, the module
159 will be called i2c-isch.
162 tristate "Intel iSMT SMBus Controller"
163 depends on PCI && X86
165 If you say yes to this option, support will be included for the Intel
166 iSMT SMBus host controller interface.
168 This driver can also be built as a module. If so, the module will be
172 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
175 If you say yes to this option, support will be included for the Intel
176 PIIX4 family of mainboard I2C interfaces. Specifically, the following
177 versions of the chipset are supported (note that Serverworks is part
198 Some AMD chipsets contain two PIIX4-compatible SMBus
199 controllers. This driver will attempt to use both controllers
200 on the SB700/SP5100, if they have been initialized by the BIOS.
202 This driver can also be built as a module. If so, the module
203 will be called i2c-piix4.
206 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
207 depends on INTEL_SOC_PMIC_CHTWC
209 If you say yes to this option, support will be included for the
210 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
211 found on some Intel Cherry Trail systems.
213 Note this controller is hooked up to a TI bq24292i charger-IC,
214 combined with a FUSB302 Type-C port-controller as such it is advised
215 to also select CONFIG_TYPEC_FUSB302=m.
218 tristate "Nvidia nForce2, nForce3 and nForce4"
221 If you say yes to this option, support will be included for the Nvidia
222 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
224 This driver can also be built as a module. If so, the module
225 will be called i2c-nforce2.
227 config I2C_NFORCE2_S4985
228 tristate "SMBus multiplexing on the Tyan S4985"
229 depends on I2C_NFORCE2 && X86
231 Enabling this option will add specific SMBus support for the Tyan
232 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
233 over 4 different channels, where the various memory module EEPROMs
234 live. Saying yes here will give you access to these in addition
237 This driver can also be built as a module. If so, the module
238 will be called i2c-nforce2-s4985.
240 config I2C_NVIDIA_GPU
241 tristate "NVIDIA GPU I2C controller"
244 If you say yes to this option, support will be included for the
245 NVIDIA GPU I2C controller which is used to communicate with the GPU's
246 Type-C controller. This driver can also be built as a module called
253 If you say yes to this option, support will be included for the
254 SiS5595 SMBus (a subset of I2C) interface.
256 This driver can also be built as a module. If so, the module
257 will be called i2c-sis5595.
260 tristate "SiS 630/730/964"
263 If you say yes to this option, support will be included for the
264 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
266 This driver can also be built as a module. If so, the module
267 will be called i2c-sis630.
273 If you say yes to this option, support will be included for the SiS
274 96x SMBus (a subset of I2C) interfaces. Specifically, the following
275 chipsets are supported:
284 This driver can also be built as a module. If so, the module
285 will be called i2c-sis96x.
288 tristate "VIA VT82C586B"
292 If you say yes to this option, support will be included for the VIA
293 82C586B I2C interface
295 This driver can also be built as a module. If so, the module
296 will be called i2c-via.
299 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
302 If you say yes to this option, support will be included for the VIA
303 VT82C596 and later SMBus interface. Specifically, the following
304 chipsets are supported:
317 This driver can also be built as a module. If so, the module
318 will be called i2c-viapro.
322 comment "ACPI drivers"
325 tristate "SMBus Control Method Interface"
327 This driver supports the SMBus Control Method Interface. It needs the
328 BIOS to declare ACPI control methods as described in the SMBus Control
329 Method Interface specification.
331 To compile this driver as a module, choose M here:
332 the module will be called i2c-scmi.
336 comment "Mac SMBus host controller drivers"
337 depends on PPC_CHRP || PPC_PMAC
340 tristate "CHRP Apple Hydra Mac I/O I2C interface"
341 depends on PCI && PPC_CHRP
344 This supports the use of the I2C interface in the Apple Hydra Mac
345 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
348 This support is also available as a module. If so, the module
349 will be called i2c-hydra.
352 tristate "Powermac I2C interface"
356 This exposes the various PowerMac i2c interfaces to the linux i2c
357 layer and to userland. It is used by various drivers on the PowerMac
358 platform, and should generally be enabled.
360 This support is also available as a module. If so, the module
361 will be called i2c-powermac.
363 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
366 tristate "Altera Soft IP I2C"
367 depends on (ARCH_SOCFPGA || NIOS2) && OF
369 If you say yes to this option, support will be included for the
370 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
372 This driver can also be built as a module. If so, the module
373 will be called i2c-altera.
376 tristate "Aspeed I2C Controller"
377 depends on ARCH_ASPEED || COMPILE_TEST
379 If you say yes to this option, support will be included for the
380 Aspeed I2C controller.
382 This driver can also be built as a module. If so, the module
383 will be called i2c-aspeed.
386 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
389 This supports the use of the I2C interface on Atmel AT91
392 A serious problem is that there is no documented way to issue
393 repeated START conditions for more than two messages, as needed
394 to support combined I2C messages. Use the i2c-gpio driver
395 unless your system can cope with this limitation.
397 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
398 don't have clock stretching in transmission mode. For that reason,
399 you can encounter underrun issues causing premature stop sendings if
400 the latency to fill the transmission register is too long. If you
401 are facing this situation, use the i2c-gpio driver.
403 config I2C_AT91_SLAVE_EXPERIMENTAL
404 tristate "Microchip AT91 I2C experimental slave mode"
408 If you say yes to this option, support for the slave mode will be
409 added. Caution: do not use it for production. This feature has not
410 been tested in a heavy way, help wanted.
411 There are known bugs:
412 - It can hang, on a SAMA5D4, after several transfers.
413 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
417 tristate "Au1550/Au1200/Au1300 SMBus interface"
418 depends on MIPS_ALCHEMY
420 If you say yes to this option, support will be included for the
421 Au1550/Au1200/Au1300 SMBus interface.
423 This driver can also be built as a module. If so, the module
424 will be called i2c-au1550.
427 tristate "Axxia I2C controller"
428 depends on ARCH_AXXIA || COMPILE_TEST
431 Say yes if you want to support the I2C bus on Axxia platforms.
433 Please note that this controller is limited to transfers of maximum
434 255 bytes in length. Any attempt to to a larger transfer will return
438 tristate "Broadcom BCM2835 I2C controller"
439 depends on ARCH_BCM2835 || ARCH_BRCMSTB
441 If you say yes to this option, support will be included for the
442 BCM2835 I2C controller.
444 If you don't know what to do here, say N.
446 This support is also available as a module. If so, the module
447 will be called i2c-bcm2835.
450 tristate "Broadcom iProc I2C controller"
451 depends on ARCH_BCM_IPROC || COMPILE_TEST
452 default ARCH_BCM_IPROC
455 If you say yes to this option, support will be included for the
456 Broadcom iProc I2C controller.
458 If you don't know what to do here, say N.
461 tristate "BCM Kona I2C adapter"
462 depends on ARCH_BCM_MOBILE
465 If you say yes to this option, support will be included for the
466 I2C interface on the Broadcom Kona family of processors.
468 If you do not need KONA I2C interface, say N.
471 tristate "BRCM Settop/DSL I2C controller"
472 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
476 If you say yes to this option, support will be included for the
477 I2C interface on the Broadcom Settop/DSL SoCs.
479 If you do not need I2C interface, say N.
482 tristate "Cadence I2C Controller"
483 depends on ARCH_ZYNQ || ARM64 || XTENSA
485 Say yes here to select Cadence I2C Host Controller. This controller is
486 e.g. used by Xilinx Zynq.
489 tristate "CBUS I2C driver"
490 depends on GPIOLIB || COMPILE_TEST
492 Support for CBUS access using I2C API. Mostly relevant for Nokia
493 Internet Tablets (770, N800 and N810).
495 This driver can also be built as a module. If so, the module
496 will be called i2c-cbus-gpio.
499 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
500 depends on CPM1 || CPM2
502 This supports the use of the I2C interface on Freescale
503 processors with CPM1 or CPM2.
505 This driver can also be built as a module. If so, the module
506 will be called i2c-cpm.
509 tristate "DaVinci I2C driver"
510 depends on ARCH_DAVINCI || ARCH_KEYSTONE
512 Support for TI DaVinci I2C controller driver.
514 This driver can also be built as a module. If so, the module
515 will be called i2c-davinci.
517 Please note that this driver might be needed to bring up other
518 devices such as DaVinci NIC.
519 For details please see http://www.ti.com/davinci
521 config I2C_DESIGNWARE_CORE
524 config I2C_DESIGNWARE_PLATFORM
525 tristate "Synopsys DesignWare Platform"
526 select I2C_DESIGNWARE_CORE
527 depends on (ACPI && COMMON_CLK) || !ACPI
529 If you say yes to this option, support will be included for the
530 Synopsys DesignWare I2C adapter.
532 This driver can also be built as a module. If so, the module
533 will be called i2c-designware-platform.
535 config I2C_DESIGNWARE_SLAVE
536 bool "Synopsys DesignWare Slave"
538 depends on I2C_DESIGNWARE_PLATFORM
540 If you say yes to this option, support will be included for the
541 Synopsys DesignWare I2C slave adapter.
543 This is not a standalone module, this module compiles together with
546 config I2C_DESIGNWARE_PCI
547 tristate "Synopsys DesignWare PCI"
549 select I2C_DESIGNWARE_CORE
551 If you say yes to this option, support will be included for the
552 Synopsys DesignWare I2C adapter. Only master mode is supported.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-designware-pci.
557 config I2C_DESIGNWARE_BAYTRAIL
558 bool "Intel Baytrail I2C semaphore support"
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.
570 tristate "Conexant Digicolor I2C driver"
571 depends on ARCH_DIGICOLOR
573 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
575 This driver can also be built as a module. If so, the module
576 will be called i2c-digicolor.
579 tristate "EFM32 I2C controller"
580 depends on ARCH_EFM32 || COMPILE_TEST
582 This driver supports the i2c block found in Energy Micro's EFM32
586 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
587 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
589 This driver is for PCH(Platform controller Hub) I2C of EG20T which
590 is an IOH(Input/Output Hub) for x86 embedded processor.
591 This driver can access PCH I2C bus device.
593 This driver also can be used for LAPIS Semiconductor IOH(Input/
594 Output Hub), ML7213, ML7223 and ML7831.
595 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
596 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
597 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
598 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
601 tristate "EMMA Mobile series I2C adapter"
605 If you say yes to this option, support will be included for the
606 I2C interface on the Renesas Electronics EM/EV family of processors.
609 tristate "Exynos5 high-speed I2C driver"
610 depends on ARCH_EXYNOS && OF
613 High-speed I2C controller on Exynos5 based Samsung SoCs.
616 tristate "GPIO-based bitbanging I2C"
617 depends on GPIOLIB || COMPILE_TEST
620 This is a very simple bitbanging I2C driver utilizing the
621 arch-neutral GPIO API to control the SCL and SDA lines.
623 config I2C_GPIO_FAULT_INJECTOR
624 bool "GPIO-based fault injector"
627 This adds some functionality to the i2c-gpio driver which can inject
628 faults to an I2C bus, so another bus master can be stress-tested.
629 This is for debugging. If unsure, say 'no'.
631 config I2C_HIGHLANDER
632 tristate "Highlander FPGA SMBus interface"
633 depends on SH_HIGHLANDER
635 If you say yes to this option, support will be included for
636 the SMBus interface located in the FPGA on various Highlander
637 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
638 FPGAs. This is wholly unrelated to the SoC I2C.
640 This driver can also be built as a module. If so, the module
641 will be called i2c-highlander.
644 tristate "IBM PPC 4xx on-chip I2C interface"
647 Say Y here if you want to use IIC peripheral found on
648 embedded IBM PPC 4xx based systems.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-ibm_iic.
654 tristate "Imagination Technologies I2C SCB Controller"
655 depends on MIPS || COMPILE_TEST
657 Say Y here if you want to use the IMG I2C SCB controller,
658 available on the TZ1090 and other IMG SoCs.
660 This driver can also be built as a module. If so, the module
661 will be called i2c-img-scb.
664 tristate "IMX I2C interface"
665 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
667 Say Y here if you want to use the IIC bus controller on
668 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
670 This driver can also be built as a module. If so, the module
671 will be called i2c-imx.
674 tristate "IMX Low Power I2C interface"
675 depends on ARCH_MXC || COMPILE_TEST
677 Say Y here if you want to use the Low Power IIC bus controller
678 on the Freescale i.MX processors.
680 This driver can also be built as a module. If so, the module
681 will be called i2c-imx-lpi2c.
684 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
685 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
687 Say Y here if you want to use the IIC bus controller on
688 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
690 This driver can also be built as a module. If so, the module
691 will be called i2c-iop3xx.
694 tristate "JZ4780 I2C controller interface support"
695 depends on MACH_JZ4780 || COMPILE_TEST
697 If you say yes to this option, support will be included for the
698 Ingenic JZ4780 I2C controller.
700 If you don't know what to do here, say N.
703 tristate "Kontron COM I2C Controller"
704 depends on MFD_KEMPLD
706 This enables support for the I2C bus interface on some Kontron ETX
707 and COMexpress (ETXexpress) modules.
709 This driver can also be built as a module. If so, the module
710 will be called i2c-kempld.
713 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
714 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
716 This driver supports the I2C interface found several NXP
717 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
719 This driver can also be built as a module. If so, the module
720 will be called i2c-lpc2k.
723 tristate "Amlogic Meson I2C controller"
724 depends on ARCH_MESON || COMPILE_TEST
726 If you say yes to this option, support will be included for the
727 I2C interface on the Amlogic Meson family of SoCs.
730 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
733 If you say yes to this option, support will be included for the
734 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
735 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
737 This driver can also be built as a module. If so, the module
738 will be called i2c-mpc.
741 tristate "MediaTek I2C adapter"
742 depends on ARCH_MEDIATEK || COMPILE_TEST
744 This selects the MediaTek(R) Integrated Inter Circuit bus driver
745 for MT65xx and MT81xx.
746 If you want to use MediaTek(R) I2C interface, say Y or M here.
750 tristate "Marvell mv64xxx I2C Controller"
751 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
753 If you say yes to this option, support will be included for the
754 built-in I2C interface on the Marvell 64xxx line of host bridges.
755 This driver is also used for Allwinner SoCs I2C controllers.
757 This driver can also be built as a module. If so, the module
758 will be called i2c-mv64xxx.
761 tristate "Freescale i.MX28 I2C interface"
765 Say Y here if you want to use the I2C bus controller on
766 the Freescale i.MX28 processors.
768 This driver can also be built as a module. If so, the module
769 will be called i2c-mxs.
772 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
775 If you say yes to this option, support will be included for the
776 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
777 as well as the STA2X11 PCIe I/O HUB.
780 tristate "OpenCores I2C Controller"
782 If you say yes to this option, support will be included for the
783 OpenCores I2C controller. For details see
784 http://www.opencores.org/projects.cgi/web/i2c/overview
786 This driver can also be built as a module. If so, the module
787 will be called i2c-ocores.
790 tristate "OMAP I2C adapter"
791 depends on ARCH_OMAP || ARCH_K3
792 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
794 If you say yes to this option, support will be included for the
795 I2C interface on the Texas Instruments OMAP1/2 family of processors.
796 Like OMAP1510/1610/1710/5912 and OMAP242x.
797 For details see http://www.ti.com/omap.
800 tristate "Actions Semiconductor Owl I2C Controller"
801 depends on ARCH_ACTIONS || COMPILE_TEST
803 Say Y here if you want to use the I2C bus controller on
804 the Actions Semiconductor Owl SoC's.
807 tristate "PA Semi SMBus interface"
808 depends on PPC_PASEMI && PCI
810 Supports the PA Semi PWRficient on-chip SMBus interfaces.
812 config I2C_PCA_PLATFORM
813 tristate "PCA9564/PCA9665 as platform device"
817 This driver supports a memory mapped Philips PCA9564/PCA9665
818 parallel bus to I2C bus controller.
820 This driver can also be built as a module. If so, the module
821 will be called i2c-pca-platform.
824 tristate "PMC MSP I2C TWI Controller"
827 This driver supports the PMC TWI controller on MSP devices.
829 This driver can also be built as module. If so, the module
830 will be called i2c-pmcmsp.
833 tristate "I2C bus support for Philips PNX and NXP LPC targets"
834 depends on ARCH_LPC32XX
836 This driver supports the Philips IP3204 I2C IP block master and/or
839 This driver can also be built as a module. If so, the module
840 will be called i2c-pnx.
843 tristate "PKUnity v3 I2C bus support"
844 depends on UNICORE32 && ARCH_PUV3
847 This driver supports the I2C IP inside the PKUnity-v3 SoC.
848 This I2C bus controller is under AMBA/AXI bus.
850 This driver can also be built as a module. If so, the module
851 will be called i2c-puv3.
854 tristate "Intel PXA2XX I2C adapter"
855 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
857 If you have devices in the PXA I2C bus, say yes to this option.
858 This driver can also be built as a module. If so, the module
859 will be called i2c-pxa.
862 def_bool I2C_PXA && X86_32 && PCI && OF
865 bool "Intel PXA2XX I2C Slave comms support"
866 depends on I2C_PXA && !X86_32
868 Support I2C slave mode communications on the PXA I2C bus. This
869 is necessary for systems where the PXA may be a target on the
873 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
874 depends on ARCH_QCOM || COMPILE_TEST
875 depends on QCOM_GENI_SE
877 This driver supports GENI serial engine based I2C controller in
878 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
879 yes to this option, support will be included for the built-in I2C
880 interface on the Qualcomm Technologies Inc.'s SoCs.
882 This driver can also be built as a module. If so, the module
883 will be called i2c-qcom-geni.
886 tristate "Qualcomm QUP based I2C controller"
889 If you say yes to this option, support will be included for the
890 built-in I2C interface on the Qualcomm SoCs.
892 This driver can also be built as a module. If so, the module
893 will be called i2c-qup.
896 tristate "Renesas RIIC adapter"
897 depends on ARCH_RENESAS || COMPILE_TEST
899 If you say yes to this option, support will be included for the
900 Renesas RIIC I2C interface.
902 This driver can also be built as a module. If so, the module
903 will be called i2c-riic.
906 tristate "Rockchip RK3xxx I2C adapter"
907 depends on OF && COMMON_CLK
909 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
912 This driver can also be built as a module. If so, the module will
915 config HAVE_S3C2410_I2C
918 This will include I2C support for Samsung SoCs. If you want to
919 include I2C support for any machine, kindly select this in the
920 respective Kconfig file.
923 tristate "S3C2410 I2C Driver"
924 depends on HAVE_S3C2410_I2C
926 Say Y here to include support for I2C controller in the
930 tristate "Renesas SH7760 I2C Controller"
931 depends on CPU_SUBTYPE_SH7760
933 This driver supports the 2 I2C interfaces on the Renesas SH7760.
935 This driver can also be built as a module. If so, the module
936 will be called i2c-sh7760.
939 tristate "SuperH Mobile I2C Controller"
940 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
942 If you say yes to this option, support will be included for the
943 built-in I2C interface on the Renesas SH-Mobile processor.
945 This driver can also be built as a module. If so, the module
946 will be called i2c-sh_mobile.
949 tristate "Simtec Generic I2C interface"
952 If you say yes to this option, support will be included for
953 the Simtec Generic I2C interface. This driver is for the
954 simple I2C bus used on newer Simtec products for general
955 I2C, such as DDC on the Simtec BBD2016A.
957 This driver can also be built as a module. If so, the module
958 will be called i2c-simtec.
961 tristate "CSR SiRFprimaII I2C interface"
964 If you say yes to this option, support will be included for the
965 CSR SiRFprimaII I2C interface.
967 This driver can also be built as a module. If so, the module
968 will be called i2c-sirf.
971 bool "Spreadtrum I2C interface"
972 depends on I2C=y && ARCH_SPRD
974 If you say yes to this option, support will be included for the
975 Spreadtrum I2C interface.
978 tristate "STMicroelectronics SSC I2C support"
981 Enable this option to add support for STMicroelectronics SoCs
982 hardware SSC (Synchronous Serial Controller) as an I2C controller.
984 This driver can also be built as module. If so, the module
985 will be called i2c-st.
988 tristate "STMicroelectronics STM32F4 I2C support"
989 depends on ARCH_STM32 || COMPILE_TEST
991 Enable this option to add support for STM32 I2C controller embedded
994 This driver can also be built as module. If so, the module
995 will be called i2c-stm32f4.
998 tristate "STMicroelectronics STM32F7 I2C support"
999 depends on ARCH_STM32 || COMPILE_TEST
1002 Enable this option to add support for STM32 I2C controller embedded
1005 This driver can also be built as module. If so, the module
1006 will be called i2c-stm32f7.
1009 tristate "ST Microelectronics DDC I2C interface"
1010 depends on MACH_U300
1011 default y if MACH_U300
1013 If you say yes to this option, support will be included for the
1014 I2C interface from ST Microelectronics simply called "DDC I2C"
1015 supporting both I2C and DDC, used in e.g. the U300 series
1018 This driver can also be built as a module. If so, the module
1019 will be called i2c-stu300.
1021 config I2C_SUN6I_P2WI
1022 tristate "Allwinner sun6i internal P2WI controller"
1023 depends on RESET_CONTROLLER
1024 depends on MACH_SUN6I || COMPILE_TEST
1026 If you say yes to this option, support will be included for the
1027 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1029 The P2WI looks like an SMBus controller (which supports only byte
1030 accesses), except that it only supports one slave device.
1031 This interface is used to connect to specific PMIC devices (like the
1034 config I2C_SYNQUACER
1035 tristate "Socionext SynQuacer I2C controller"
1036 depends on ARCH_SYNQUACER || COMPILE_TEST
1038 Say Y here to include support for the I2C controller used in some
1039 Fujitsu and Socionext SoCs.
1041 This driver can also be built as a module. If so, the module
1042 will be called i2c-synquacer.
1045 tristate "NVIDIA Tegra internal I2C controller"
1046 depends on ARCH_TEGRA
1048 If you say yes to this option, support will be included for the
1049 I2C controller embedded in NVIDIA Tegra SOCs
1051 config I2C_TEGRA_BPMP
1052 tristate "NVIDIA Tegra BPMP I2C controller"
1053 depends on TEGRA_BPMP
1056 If you say yes to this option, support will be included for the I2C
1057 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1059 This I2C driver is a 'virtual' I2C driver. The real driver is part
1060 of the BPMP firmware, and this driver merely communicates with that
1064 tristate "UniPhier FIFO-less I2C controller"
1065 depends on ARCH_UNIPHIER || COMPILE_TEST
1067 If you say yes to this option, support will be included for
1068 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1069 or older UniPhier SoCs.
1071 config I2C_UNIPHIER_F
1072 tristate "UniPhier FIFO-builtin I2C controller"
1073 depends on ARCH_UNIPHIER || COMPILE_TEST
1075 If you say yes to this option, support will be included for
1076 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1077 PH1-Pro5, or newer UniPhier SoCs.
1079 config I2C_VERSATILE
1080 tristate "ARM Versatile/Realview I2C bus support"
1081 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1084 Say yes if you want to support the I2C serial bus on ARMs Versatile
1087 This driver can also be built as a module. If so, the module
1088 will be called i2c-versatile.
1091 tristate "Wondermedia WM8xxx SoC I2C bus support"
1092 depends on ARCH_VT8500
1094 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1097 This driver can also be built as a module. If so, the module will be
1101 tristate "Cavium OCTEON I2C bus support"
1102 depends on CAVIUM_OCTEON_SOC
1104 Say yes if you want to support the I2C serial bus on Cavium
1107 This driver can also be built as a module. If so, the module
1108 will be called i2c-octeon.
1111 tristate "Cavium ThunderX I2C bus support"
1112 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1115 Say yes if you want to support the I2C serial bus on Cavium
1118 This driver can also be built as a module. If so, the module
1119 will be called i2c-thunderx.
1122 tristate "Xilinx I2C Controller"
1123 depends on HAS_IOMEM
1125 If you say yes to this option, support will be included for the
1126 Xilinx I2C controller.
1128 This driver can also be built as a module. If so, the module
1129 will be called xilinx_i2c.
1132 tristate "Netlogic XLR and Sigma Designs I2C support"
1133 depends on CPU_XLR || ARCH_TANGO
1135 This driver enables support for the on-chip I2C interface of
1136 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1138 This driver can also be built as a module. If so, the module
1139 will be called i2c-xlr.
1142 tristate "XLP9XX I2C support"
1143 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1145 This driver enables support for the on-chip I2C interface of
1146 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1148 This driver can also be built as a module. If so, the module will
1149 be called i2c-xlp9xx.
1152 tristate "Renesas R-Car I2C Controller"
1153 depends on ARCH_RENESAS || COMPILE_TEST
1156 If you say yes to this option, support will be included for the
1157 R-Car I2C controller.
1159 This driver can also be built as a module. If so, the module
1160 will be called i2c-rcar.
1162 comment "External I2C/SMBus adapter drivers"
1164 config I2C_DIOLAN_U2C
1165 tristate "Diolan U2C-12 USB adapter"
1168 If you say yes to this option, support will be included for Diolan
1169 U2C-12, a USB to I2C interface.
1171 This driver can also be built as a module. If so, the module
1172 will be called i2c-diolan-u2c.
1175 tristate "Diolan DLN-2 USB I2C adapter"
1178 If you say yes to this option, support will be included for Diolan
1179 DLN2, a USB to I2C interface.
1181 This driver can also be built as a module. If so, the module
1182 will be called i2c-dln2.
1185 tristate "Parallel port adapter"
1190 This supports parallel port I2C adapters such as the ones made by
1191 Philips or Velleman, Analog Devices evaluation boards, and more.
1192 Basically any adapter using the parallel port as an I2C bus with
1193 no extra chipset is supported by this driver, or could be.
1195 This driver is a replacement for (and was inspired by) an older
1196 driver named i2c-philips-par. The new driver supports more devices,
1197 and makes it easier to add support for new devices.
1199 An adapter type parameter is now mandatory. Please read the file
1200 Documentation/i2c/busses/i2c-parport for details.
1202 Another driver exists, named i2c-parport-light, which doesn't depend
1203 on the parport driver. This is meant for embedded systems. Don't say
1204 Y here if you intend to say Y or M there.
1206 This support is also available as a module. If so, the module
1207 will be called i2c-parport.
1209 config I2C_PARPORT_LIGHT
1210 tristate "Parallel port adapter (light)"
1214 This supports parallel port I2C adapters such as the ones made by
1215 Philips or Velleman, Analog Devices evaluation boards, and more.
1216 Basically any adapter using the parallel port as an I2C bus with
1217 no extra chipset is supported by this driver, or could be.
1219 This driver is a light version of i2c-parport. It doesn't depend
1220 on the parport driver, and uses direct I/O access instead. This
1221 might be preferred on embedded systems where wasting memory for
1222 the clean but heavy parport handling is not an option. The
1223 drawback is a reduced portability and the impossibility to
1224 daisy-chain other parallel port devices.
1226 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1227 both is possible but both modules should not be loaded at the same
1230 This support is also available as a module. If so, the module
1231 will be called i2c-parport-light.
1233 config I2C_ROBOTFUZZ_OSIF
1234 tristate "RobotFuzz Open Source InterFace USB adapter"
1237 If you say yes to this option, support will be included for the
1238 RobotFuzz Open Source InterFace USB to I2C interface.
1240 This driver can also be built as a module. If so, the module
1241 will be called i2c-osif.
1244 tristate "TAOS evaluation module"
1247 select SERIO_SERPORT
1250 This supports TAOS evaluation modules on serial port. In order to
1251 use this driver, you will need the inputattach tool, which is part
1252 of the input-utils package.
1256 This support is also available as a module. If so, the module
1257 will be called i2c-taos-evm.
1260 tristate "Tiny-USB adapter"
1263 If you say yes to this option, support will be included for the
1264 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1265 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1267 This driver can also be built as a module. If so, the module
1268 will be called i2c-tiny-usb.
1270 config I2C_VIPERBOARD
1271 tristate "Viperboard I2C master support"
1272 depends on MFD_VIPERBOARD && USB
1274 Say yes here to access the I2C part of the Nano River
1275 Technologies Viperboard as I2C master.
1276 See viperboard API specification and Nano
1277 River Tech's viperboard.h for detailed meaning
1278 of the module parameters.
1280 comment "Other I2C/SMBus bus drivers"
1283 tristate "Acorn IOC/IOMD I2C bus support"
1284 depends on ARCH_ACORN
1288 Say yes if you want to support the I2C bus on Acorn platforms.
1290 If you don't know, say Y.
1293 tristate "Elektor ISA card"
1294 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1297 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1300 This support is also available as a module. If so, the module
1301 will be called i2c-elektor.
1304 tristate "Mellanox I2C driver"
1307 This exposes the Mellanox platform I2C busses to the linux I2C layer
1308 for X86 based systems.
1309 Controller is implemented as CPLD logic.
1311 This driver can also be built as a module. If so, the module will be
1312 called as i2c-mlxcpld.
1315 tristate "PCA9564/PCA9665 on an ISA bus"
1320 This driver supports ISA boards using the Philips PCA9564/PCA9665
1321 parallel bus to I2C bus controller.
1323 This driver can also be built as a module. If so, the module
1324 will be called i2c-pca-isa.
1326 This device is almost undetectable and using this driver on a
1327 system which doesn't have this device will result in long
1328 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1329 time). If unsure, say N.
1332 tristate "SiByte SMBus interface"
1333 depends on SIBYTE_SB1xxx_SOC
1335 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1337 config I2C_CROS_EC_TUNNEL
1338 tristate "ChromeOS EC tunnel I2C bus"
1339 depends on MFD_CROS_EC
1341 If you say yes here you get an I2C bus that will tunnel i2c commands
1342 through to the other side of the ChromeOS EC to the i2c bus
1343 connected there. This will work whatever the interface used to
1344 talk to the EC (SPI, I2C or LPC).
1346 config I2C_XGENE_SLIMPRO
1347 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1348 depends on ARCH_XGENE && MAILBOX
1350 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1351 co-processor. The I2C device access the I2C bus via the X-Gene
1352 to SLIMpro (On chip coprocessor) mailbox mechanism.
1356 tristate "Geode ACCESS.bus support"
1357 depends on X86_32 && PCI
1359 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1360 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1362 If you don't know what to do here, say N.
1364 This support is also available as a module. If so, the module
1365 will be called scx200_acb.
1368 tristate "IBM OPAL I2C driver"
1369 depends on PPC_POWERNV
1372 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1373 the driver is based on the OPAL interfaces.
1375 This driver can also be built as a module. If so, the module will be
1379 tristate "ZTE ZX2967 I2C support"
1383 Selecting this option will add ZX2967 I2C driver.
1384 This driver can also be built as a module. If so, the module will be
1388 tristate "FSI I2C driver"
1391 Driver for FSI bus attached I2C masters. These are I2C masters that
1392 are connected to the system over an FSI bus, instead of the more
1393 common PCI or MMIO interface.
1395 This driver can also be built as a module. If so, the module will be