2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
8 comment "PC SMBus host controller drivers"
15 If you say yes to this option, support will be included for the SMB
16 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
17 controller is part of the 7101 device, which is an ACPI-compliant
18 Power Management Unit (PMU).
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
27 If you say yes to this option, support will be included for the SMB
28 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
29 controller is part of the 7101 device, which is an ACPI-compliant
30 Power Management Unit (PMU).
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
39 If you say yes to this option, support will be included for the
40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
46 tristate "AMD 756/766/768/8111 and nVidia nForce"
49 If you say yes to this option, support will be included for the AMD
50 756/766/768 mainboard I2C interfaces. The driver also includes
51 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
52 the nVidia nForce I2C interface.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
57 config I2C_AMD756_S4882
58 tristate "SMBus multiplexing on the Tyan S4882"
59 depends on I2C_AMD756 && X86
61 Enabling this option will add specific SMBus support for the Tyan
62 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
63 over 8 different channels, where the various memory module EEPROMs
64 and temperature sensors live. Saying yes here will give you access
65 to these in addition to the trunk.
67 This driver can also be built as a module. If so, the module
68 will be called i2c-amd756-s4882.
74 If you say yes to this option, support will be included for the
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
77 This driver can also be built as a module. If so, the module
78 will be called i2c-amd8111.
81 tristate "Hix5hd2 high-speed I2C driver"
82 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
84 Say Y here to include support for the high-speed I2C controller
85 used in HiSilicon hix5hd2 SoCs.
87 This driver can also be built as a module. If so, the module
88 will be called i2c-hix5hd2.
91 tristate "Intel 82801 (ICH/PCH)"
93 select CHECK_SIGNATURE if X86 && DMI
96 If you say yes to this option, support will be included for the Intel
97 801 family of mainboard I2C interfaces. Specifically, the following
98 versions of the chipset are supported:
104 82801EB/ER (ICH5/ICH5R)
135 This driver can also be built as a module. If so, the module
136 will be called i2c-i801.
139 tristate "Intel SCH SMBus 1.0"
143 Say Y here if you want to use SMBus controller on the Intel SCH
146 This driver can also be built as a module. If so, the module
147 will be called i2c-isch.
150 tristate "Intel iSMT SMBus Controller"
151 depends on PCI && X86
153 If you say yes to this option, support will be included for the Intel
154 iSMT SMBus host controller interface.
156 This driver can also be built as a module. If so, the module will be
160 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
163 If you say yes to this option, support will be included for the Intel
164 PIIX4 family of mainboard I2C interfaces. Specifically, the following
165 versions of the chipset are supported (note that Serverworks is part
185 Some AMD chipsets contain two PIIX4-compatible SMBus
186 controllers. This driver will attempt to use both controllers
187 on the SB700/SP5100, if they have been initialized by the BIOS.
189 This driver can also be built as a module. If so, the module
190 will be called i2c-piix4.
193 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
194 depends on INTEL_SOC_PMIC_CHTWC
196 If you say yes to this option, support will be included for the
197 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
198 found on some Intel Cherry Trail systems.
200 Note this controller is hooked up to a TI bq24292i charger-IC,
201 combined with a FUSB302 Type-C port-controller as such it is advised
202 to also select CONFIG_TYPEC_FUSB302=m.
205 tristate "Nvidia nForce2, nForce3 and nForce4"
208 If you say yes to this option, support will be included for the Nvidia
209 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
211 This driver can also be built as a module. If so, the module
212 will be called i2c-nforce2.
214 config I2C_NFORCE2_S4985
215 tristate "SMBus multiplexing on the Tyan S4985"
216 depends on I2C_NFORCE2 && X86
218 Enabling this option will add specific SMBus support for the Tyan
219 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
220 over 4 different channels, where the various memory module EEPROMs
221 live. Saying yes here will give you access to these in addition
224 This driver can also be built as a module. If so, the module
225 will be called i2c-nforce2-s4985.
227 config I2C_NVIDIA_GPU
228 tristate "NVIDIA GPU I2C controller"
231 If you say yes to this option, support will be included for the
232 NVIDIA GPU I2C controller which is used to communicate with the GPU's
233 Type-C controller. This driver can also be built as a module called
240 If you say yes to this option, support will be included for the
241 SiS5595 SMBus (a subset of I2C) interface.
243 This driver can also be built as a module. If so, the module
244 will be called i2c-sis5595.
247 tristate "SiS 630/730/964"
250 If you say yes to this option, support will be included for the
251 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
253 This driver can also be built as a module. If so, the module
254 will be called i2c-sis630.
260 If you say yes to this option, support will be included for the SiS
261 96x SMBus (a subset of I2C) interfaces. Specifically, the following
262 chipsets are supported:
271 This driver can also be built as a module. If so, the module
272 will be called i2c-sis96x.
275 tristate "VIA VT82C586B"
279 If you say yes to this option, support will be included for the VIA
280 82C586B I2C interface
282 This driver can also be built as a module. If so, the module
283 will be called i2c-via.
286 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
289 If you say yes to this option, support will be included for the VIA
290 VT82C596 and later SMBus interface. Specifically, the following
291 chipsets are supported:
304 This driver can also be built as a module. If so, the module
305 will be called i2c-viapro.
309 comment "ACPI drivers"
312 tristate "SMBus Control Method Interface"
314 This driver supports the SMBus Control Method Interface. It needs the
315 BIOS to declare ACPI control methods as described in the SMBus Control
316 Method Interface specification.
318 To compile this driver as a module, choose M here:
319 the module will be called i2c-scmi.
323 comment "Mac SMBus host controller drivers"
324 depends on PPC_CHRP || PPC_PMAC
327 tristate "CHRP Apple Hydra Mac I/O I2C interface"
328 depends on PCI && PPC_CHRP
331 This supports the use of the I2C interface in the Apple Hydra Mac
332 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
335 This support is also available as a module. If so, the module
336 will be called i2c-hydra.
339 tristate "Powermac I2C interface"
343 This exposes the various PowerMac i2c interfaces to the linux i2c
344 layer and to userland. It is used by various drivers on the PowerMac
345 platform, and should generally be enabled.
347 This support is also available as a module. If so, the module
348 will be called i2c-powermac.
350 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
353 tristate "Altera Soft IP I2C"
354 depends on (ARCH_SOCFPGA || NIOS2) && OF
356 If you say yes to this option, support will be included for the
357 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
359 This driver can also be built as a module. If so, the module
360 will be called i2c-altera.
363 tristate "Aspeed I2C Controller"
364 depends on ARCH_ASPEED || COMPILE_TEST
366 If you say yes to this option, support will be included for the
367 Aspeed I2C controller.
369 This driver can also be built as a module. If so, the module
370 will be called i2c-aspeed.
373 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
376 This supports the use of the I2C interface on Atmel AT91
379 A serious problem is that there is no documented way to issue
380 repeated START conditions for more than two messages, as needed
381 to support combined I2C messages. Use the i2c-gpio driver
382 unless your system can cope with this limitation.
384 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
385 don't have clock stretching in transmission mode. For that reason,
386 you can encounter underrun issues causing premature stop sendings if
387 the latency to fill the transmission register is too long. If you
388 are facing this situation, use the i2c-gpio driver.
390 config I2C_AT91_SLAVE_EXPERIMENTAL
391 tristate "Microchip AT91 I2C experimental slave mode"
395 If you say yes to this option, support for the slave mode will be
396 added. Caution: do not use it for production. This feature has not
397 been tested in a heavy way, help wanted.
398 There are known bugs:
399 - It can hang, on a SAMA5D4, after several transfers.
400 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
404 tristate "Au1550/Au1200/Au1300 SMBus interface"
405 depends on MIPS_ALCHEMY
407 If you say yes to this option, support will be included for the
408 Au1550/Au1200/Au1300 SMBus interface.
410 This driver can also be built as a module. If so, the module
411 will be called i2c-au1550.
414 tristate "Axxia I2C controller"
415 depends on ARCH_AXXIA || COMPILE_TEST
418 Say yes if you want to support the I2C bus on Axxia platforms.
420 Please note that this controller is limited to transfers of maximum
421 255 bytes in length. Any attempt to to a larger transfer will return
425 tristate "Broadcom BCM2835 I2C controller"
426 depends on ARCH_BCM2835
428 If you say yes to this option, support will be included for the
429 BCM2835 I2C controller.
431 If you don't know what to do here, say N.
433 This support is also available as a module. If so, the module
434 will be called i2c-bcm2835.
437 tristate "Broadcom iProc I2C controller"
438 depends on ARCH_BCM_IPROC || COMPILE_TEST
439 default ARCH_BCM_IPROC
441 If you say yes to this option, support will be included for the
442 Broadcom iProc I2C controller.
444 If you don't know what to do here, say N.
447 tristate "BCM Kona I2C adapter"
448 depends on ARCH_BCM_MOBILE
451 If you say yes to this option, support will be included for the
452 I2C interface on the Broadcom Kona family of processors.
454 If you do not need KONA I2C interface, say N.
457 tristate "BRCM Settop/DSL I2C controller"
458 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
462 If you say yes to this option, support will be included for the
463 I2C interface on the Broadcom Settop/DSL SoCs.
465 If you do not need I2C interface, say N.
468 tristate "Cadence I2C Controller"
469 depends on ARCH_ZYNQ || ARM64 || XTENSA
471 Say yes here to select Cadence I2C Host Controller. This controller is
472 e.g. used by Xilinx Zynq.
475 tristate "CBUS I2C driver"
476 depends on GPIOLIB || COMPILE_TEST
478 Support for CBUS access using I2C API. Mostly relevant for Nokia
479 Internet Tablets (770, N800 and N810).
481 This driver can also be built as a module. If so, the module
482 will be called i2c-cbus-gpio.
485 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
486 depends on CPM1 || CPM2
488 This supports the use of the I2C interface on Freescale
489 processors with CPM1 or CPM2.
491 This driver can also be built as a module. If so, the module
492 will be called i2c-cpm.
495 tristate "DaVinci I2C driver"
496 depends on ARCH_DAVINCI || ARCH_KEYSTONE
498 Support for TI DaVinci I2C controller driver.
500 This driver can also be built as a module. If so, the module
501 will be called i2c-davinci.
503 Please note that this driver might be needed to bring up other
504 devices such as DaVinci NIC.
505 For details please see http://www.ti.com/davinci
507 config I2C_DESIGNWARE_CORE
510 config I2C_DESIGNWARE_PLATFORM
511 tristate "Synopsys DesignWare Platform"
512 select I2C_DESIGNWARE_CORE
513 depends on (ACPI && COMMON_CLK) || !ACPI
515 If you say yes to this option, support will be included for the
516 Synopsys DesignWare I2C adapter.
518 This driver can also be built as a module. If so, the module
519 will be called i2c-designware-platform.
521 config I2C_DESIGNWARE_SLAVE
522 bool "Synopsys DesignWare Slave"
524 depends on I2C_DESIGNWARE_PLATFORM
526 If you say yes to this option, support will be included for the
527 Synopsys DesignWare I2C slave adapter.
529 This is not a standalone module, this module compiles together with
532 config I2C_DESIGNWARE_PCI
533 tristate "Synopsys DesignWare PCI"
535 select I2C_DESIGNWARE_CORE
537 If you say yes to this option, support will be included for the
538 Synopsys DesignWare I2C adapter. Only master mode is supported.
540 This driver can also be built as a module. If so, the module
541 will be called i2c-designware-pci.
543 config I2C_DESIGNWARE_BAYTRAIL
544 bool "Intel Baytrail I2C semaphore support"
546 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
547 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
549 This driver enables managed host access to the PMIC I2C bus on select
550 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
551 the host to request uninterrupted access to the PMIC's I2C bus from
552 the platform firmware controlling it. You should say Y if running on
553 a BayTrail system using the AXP288.
556 tristate "Conexant Digicolor I2C driver"
557 depends on ARCH_DIGICOLOR
559 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
561 This driver can also be built as a module. If so, the module
562 will be called i2c-digicolor.
565 tristate "EFM32 I2C controller"
566 depends on ARCH_EFM32 || COMPILE_TEST
568 This driver supports the i2c block found in Energy Micro's EFM32
572 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
573 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
575 This driver is for PCH(Platform controller Hub) I2C of EG20T which
576 is an IOH(Input/Output Hub) for x86 embedded processor.
577 This driver can access PCH I2C bus device.
579 This driver also can be used for LAPIS Semiconductor IOH(Input/
580 Output Hub), ML7213, ML7223 and ML7831.
581 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
582 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
583 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
584 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
587 tristate "EMMA Mobile series I2C adapter"
591 If you say yes to this option, support will be included for the
592 I2C interface on the Renesas Electronics EM/EV family of processors.
595 tristate "Exynos5 high-speed I2C driver"
596 depends on ARCH_EXYNOS && OF
599 High-speed I2C controller on Exynos5 based Samsung SoCs.
602 tristate "GPIO-based bitbanging I2C"
603 depends on GPIOLIB || COMPILE_TEST
606 This is a very simple bitbanging I2C driver utilizing the
607 arch-neutral GPIO API to control the SCL and SDA lines.
609 config I2C_GPIO_FAULT_INJECTOR
610 bool "GPIO-based fault injector"
613 This adds some functionality to the i2c-gpio driver which can inject
614 faults to an I2C bus, so another bus master can be stress-tested.
615 This is for debugging. If unsure, say 'no'.
617 config I2C_HIGHLANDER
618 tristate "Highlander FPGA SMBus interface"
619 depends on SH_HIGHLANDER
621 If you say yes to this option, support will be included for
622 the SMBus interface located in the FPGA on various Highlander
623 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
624 FPGAs. This is wholly unrelated to the SoC I2C.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-highlander.
630 tristate "IBM PPC 4xx on-chip I2C interface"
633 Say Y here if you want to use IIC peripheral found on
634 embedded IBM PPC 4xx based systems.
636 This driver can also be built as a module. If so, the module
637 will be called i2c-ibm_iic.
640 tristate "Imagination Technologies I2C SCB Controller"
641 depends on MIPS || COMPILE_TEST
643 Say Y here if you want to use the IMG I2C SCB controller,
644 available on the TZ1090 and other IMG SoCs.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-img-scb.
650 tristate "IMX I2C interface"
651 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
653 Say Y here if you want to use the IIC bus controller on
654 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
656 This driver can also be built as a module. If so, the module
657 will be called i2c-imx.
660 tristate "IMX Low Power I2C interface"
661 depends on ARCH_MXC || COMPILE_TEST
663 Say Y here if you want to use the Low Power IIC bus controller
664 on the Freescale i.MX processors.
666 This driver can also be built as a module. If so, the module
667 will be called i2c-imx-lpi2c.
670 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
671 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
673 Say Y here if you want to use the IIC bus controller on
674 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
676 This driver can also be built as a module. If so, the module
677 will be called i2c-iop3xx.
680 tristate "JZ4780 I2C controller interface support"
681 depends on MACH_JZ4780 || COMPILE_TEST
683 If you say yes to this option, support will be included for the
684 Ingenic JZ4780 I2C controller.
686 If you don't know what to do here, say N.
689 tristate "Kontron COM I2C Controller"
690 depends on MFD_KEMPLD
692 This enables support for the I2C bus interface on some Kontron ETX
693 and COMexpress (ETXexpress) modules.
695 This driver can also be built as a module. If so, the module
696 will be called i2c-kempld.
699 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
700 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
702 This driver supports the I2C interface found several NXP
703 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
705 This driver can also be built as a module. If so, the module
706 will be called i2c-lpc2k.
709 tristate "Amlogic Meson I2C controller"
710 depends on ARCH_MESON || COMPILE_TEST
712 If you say yes to this option, support will be included for the
713 I2C interface on the Amlogic Meson family of SoCs.
716 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
719 If you say yes to this option, support will be included for the
720 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
721 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
723 This driver can also be built as a module. If so, the module
724 will be called i2c-mpc.
727 tristate "MediaTek I2C adapter"
728 depends on ARCH_MEDIATEK || COMPILE_TEST
730 This selects the MediaTek(R) Integrated Inter Circuit bus driver
731 for MT65xx and MT81xx.
732 If you want to use MediaTek(R) I2C interface, say Y or M here.
736 tristate "Marvell mv64xxx I2C Controller"
737 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
739 If you say yes to this option, support will be included for the
740 built-in I2C interface on the Marvell 64xxx line of host bridges.
741 This driver is also used for Allwinner SoCs I2C controllers.
743 This driver can also be built as a module. If so, the module
744 will be called i2c-mv64xxx.
747 tristate "Freescale i.MX28 I2C interface"
751 Say Y here if you want to use the I2C bus controller on
752 the Freescale i.MX28 processors.
754 This driver can also be built as a module. If so, the module
755 will be called i2c-mxs.
758 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
761 If you say yes to this option, support will be included for the
762 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
763 as well as the STA2X11 PCIe I/O HUB.
766 tristate "OpenCores I2C Controller"
768 If you say yes to this option, support will be included for the
769 OpenCores I2C controller. For details see
770 http://www.opencores.org/projects.cgi/web/i2c/overview
772 This driver can also be built as a module. If so, the module
773 will be called i2c-ocores.
776 tristate "OMAP I2C adapter"
777 depends on ARCH_OMAP || ARCH_K3
778 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
780 If you say yes to this option, support will be included for the
781 I2C interface on the Texas Instruments OMAP1/2 family of processors.
782 Like OMAP1510/1610/1710/5912 and OMAP242x.
783 For details see http://www.ti.com/omap.
786 tristate "Actions Semiconductor Owl I2C Controller"
787 depends on ARCH_ACTIONS || COMPILE_TEST
789 Say Y here if you want to use the I2C bus controller on
790 the Actions Semiconductor Owl SoC's.
793 tristate "PA Semi SMBus interface"
794 depends on PPC_PASEMI && PCI
796 Supports the PA Semi PWRficient on-chip SMBus interfaces.
798 config I2C_PCA_PLATFORM
799 tristate "PCA9564/PCA9665 as platform device"
803 This driver supports a memory mapped Philips PCA9564/PCA9665
804 parallel bus to I2C bus controller.
806 This driver can also be built as a module. If so, the module
807 will be called i2c-pca-platform.
810 tristate "PMC MSP I2C TWI Controller"
813 This driver supports the PMC TWI controller on MSP devices.
815 This driver can also be built as module. If so, the module
816 will be called i2c-pmcmsp.
819 tristate "I2C bus support for Philips PNX and NXP LPC targets"
820 depends on ARCH_LPC32XX
822 This driver supports the Philips IP3204 I2C IP block master and/or
825 This driver can also be built as a module. If so, the module
826 will be called i2c-pnx.
829 tristate "PKUnity v3 I2C bus support"
830 depends on UNICORE32 && ARCH_PUV3
833 This driver supports the I2C IP inside the PKUnity-v3 SoC.
834 This I2C bus controller is under AMBA/AXI bus.
836 This driver can also be built as a module. If so, the module
837 will be called i2c-puv3.
840 tristate "Intel PXA2XX I2C adapter"
841 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
843 If you have devices in the PXA I2C bus, say yes to this option.
844 This driver can also be built as a module. If so, the module
845 will be called i2c-pxa.
848 def_bool I2C_PXA && X86_32 && PCI && OF
851 bool "Intel PXA2XX I2C Slave comms support"
852 depends on I2C_PXA && !X86_32
854 Support I2C slave mode communications on the PXA I2C bus. This
855 is necessary for systems where the PXA may be a target on the
859 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
860 depends on ARCH_QCOM || COMPILE_TEST
861 depends on QCOM_GENI_SE
863 This driver supports GENI serial engine based I2C controller in
864 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
865 yes to this option, support will be included for the built-in I2C
866 interface on the Qualcomm Technologies Inc.'s SoCs.
868 This driver can also be built as a module. If so, the module
869 will be called i2c-qcom-geni.
872 tristate "Qualcomm QUP based I2C controller"
875 If you say yes to this option, support will be included for the
876 built-in I2C interface on the Qualcomm SoCs.
878 This driver can also be built as a module. If so, the module
879 will be called i2c-qup.
882 tristate "Renesas RIIC adapter"
883 depends on ARCH_RENESAS || COMPILE_TEST
885 If you say yes to this option, support will be included for the
886 Renesas RIIC I2C interface.
888 This driver can also be built as a module. If so, the module
889 will be called i2c-riic.
892 tristate "Rockchip RK3xxx I2C adapter"
893 depends on OF && COMMON_CLK
895 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
898 This driver can also be built as a module. If so, the module will
901 config HAVE_S3C2410_I2C
904 This will include I2C support for Samsung SoCs. If you want to
905 include I2C support for any machine, kindly select this in the
906 respective Kconfig file.
909 tristate "S3C2410 I2C Driver"
910 depends on HAVE_S3C2410_I2C
912 Say Y here to include support for I2C controller in the
916 tristate "Renesas SH7760 I2C Controller"
917 depends on CPU_SUBTYPE_SH7760
919 This driver supports the 2 I2C interfaces on the Renesas SH7760.
921 This driver can also be built as a module. If so, the module
922 will be called i2c-sh7760.
925 tristate "SuperH Mobile I2C Controller"
926 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
928 If you say yes to this option, support will be included for the
929 built-in I2C interface on the Renesas SH-Mobile processor.
931 This driver can also be built as a module. If so, the module
932 will be called i2c-sh_mobile.
935 tristate "Simtec Generic I2C interface"
938 If you say yes to this option, support will be included for
939 the Simtec Generic I2C interface. This driver is for the
940 simple I2C bus used on newer Simtec products for general
941 I2C, such as DDC on the Simtec BBD2016A.
943 This driver can also be built as a module. If so, the module
944 will be called i2c-simtec.
947 tristate "CSR SiRFprimaII I2C interface"
950 If you say yes to this option, support will be included for the
951 CSR SiRFprimaII I2C interface.
953 This driver can also be built as a module. If so, the module
954 will be called i2c-sirf.
957 bool "Spreadtrum I2C interface"
958 depends on I2C=y && ARCH_SPRD
960 If you say yes to this option, support will be included for the
961 Spreadtrum I2C interface.
964 tristate "STMicroelectronics SSC I2C support"
967 Enable this option to add support for STMicroelectronics SoCs
968 hardware SSC (Synchronous Serial Controller) as an I2C controller.
970 This driver can also be built as module. If so, the module
971 will be called i2c-st.
974 tristate "STMicroelectronics STM32F4 I2C support"
975 depends on ARCH_STM32 || COMPILE_TEST
977 Enable this option to add support for STM32 I2C controller embedded
980 This driver can also be built as module. If so, the module
981 will be called i2c-stm32f4.
984 tristate "STMicroelectronics STM32F7 I2C support"
985 depends on ARCH_STM32 || COMPILE_TEST
988 Enable this option to add support for STM32 I2C controller embedded
991 This driver can also be built as module. If so, the module
992 will be called i2c-stm32f7.
995 tristate "ST Microelectronics DDC I2C interface"
997 default y if MACH_U300
999 If you say yes to this option, support will be included for the
1000 I2C interface from ST Microelectronics simply called "DDC I2C"
1001 supporting both I2C and DDC, used in e.g. the U300 series
1004 This driver can also be built as a module. If so, the module
1005 will be called i2c-stu300.
1007 config I2C_SUN6I_P2WI
1008 tristate "Allwinner sun6i internal P2WI controller"
1009 depends on RESET_CONTROLLER
1010 depends on MACH_SUN6I || COMPILE_TEST
1012 If you say yes to this option, support will be included for the
1013 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1015 The P2WI looks like an SMBus controller (which supports only byte
1016 accesses), except that it only supports one slave device.
1017 This interface is used to connect to specific PMIC devices (like the
1020 config I2C_SYNQUACER
1021 tristate "Socionext SynQuacer I2C controller"
1022 depends on ARCH_SYNQUACER || COMPILE_TEST
1024 Say Y here to include support for the I2C controller used in some
1025 Fujitsu and Socionext SoCs.
1027 This driver can also be built as a module. If so, the module
1028 will be called i2c-synquacer.
1031 tristate "NVIDIA Tegra internal I2C controller"
1032 depends on ARCH_TEGRA
1034 If you say yes to this option, support will be included for the
1035 I2C controller embedded in NVIDIA Tegra SOCs
1037 config I2C_TEGRA_BPMP
1038 tristate "NVIDIA Tegra BPMP I2C controller"
1039 depends on TEGRA_BPMP
1042 If you say yes to this option, support will be included for the I2C
1043 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1045 This I2C driver is a 'virtual' I2C driver. The real driver is part
1046 of the BPMP firmware, and this driver merely communicates with that
1050 tristate "UniPhier FIFO-less I2C controller"
1051 depends on ARCH_UNIPHIER || COMPILE_TEST
1053 If you say yes to this option, support will be included for
1054 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1055 or older UniPhier SoCs.
1057 config I2C_UNIPHIER_F
1058 tristate "UniPhier FIFO-builtin I2C controller"
1059 depends on ARCH_UNIPHIER || COMPILE_TEST
1061 If you say yes to this option, support will be included for
1062 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1063 PH1-Pro5, or newer UniPhier SoCs.
1065 config I2C_VERSATILE
1066 tristate "ARM Versatile/Realview I2C bus support"
1067 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1070 Say yes if you want to support the I2C serial bus on ARMs Versatile
1073 This driver can also be built as a module. If so, the module
1074 will be called i2c-versatile.
1077 tristate "Wondermedia WM8xxx SoC I2C bus support"
1078 depends on ARCH_VT8500
1080 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1083 This driver can also be built as a module. If so, the module will be
1087 tristate "Cavium OCTEON I2C bus support"
1088 depends on CAVIUM_OCTEON_SOC
1090 Say yes if you want to support the I2C serial bus on Cavium
1093 This driver can also be built as a module. If so, the module
1094 will be called i2c-octeon.
1097 tristate "Cavium ThunderX I2C bus support"
1098 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1101 Say yes if you want to support the I2C serial bus on Cavium
1104 This driver can also be built as a module. If so, the module
1105 will be called i2c-thunderx.
1108 tristate "Xilinx I2C Controller"
1109 depends on HAS_IOMEM
1111 If you say yes to this option, support will be included for the
1112 Xilinx I2C controller.
1114 This driver can also be built as a module. If so, the module
1115 will be called xilinx_i2c.
1118 tristate "Netlogic XLR and Sigma Designs I2C support"
1119 depends on CPU_XLR || ARCH_TANGO
1121 This driver enables support for the on-chip I2C interface of
1122 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1124 This driver can also be built as a module. If so, the module
1125 will be called i2c-xlr.
1128 tristate "XLP9XX I2C support"
1129 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1131 This driver enables support for the on-chip I2C interface of
1132 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1134 This driver can also be built as a module. If so, the module will
1135 be called i2c-xlp9xx.
1138 tristate "Renesas R-Car I2C Controller"
1139 depends on ARCH_RENESAS || COMPILE_TEST
1142 If you say yes to this option, support will be included for the
1143 R-Car I2C controller.
1145 This driver can also be built as a module. If so, the module
1146 will be called i2c-rcar.
1148 comment "External I2C/SMBus adapter drivers"
1150 config I2C_DIOLAN_U2C
1151 tristate "Diolan U2C-12 USB adapter"
1154 If you say yes to this option, support will be included for Diolan
1155 U2C-12, a USB to I2C interface.
1157 This driver can also be built as a module. If so, the module
1158 will be called i2c-diolan-u2c.
1161 tristate "Diolan DLN-2 USB I2C adapter"
1164 If you say yes to this option, support will be included for Diolan
1165 DLN2, a USB to I2C interface.
1167 This driver can also be built as a module. If so, the module
1168 will be called i2c-dln2.
1171 tristate "Parallel port adapter"
1176 This supports parallel port I2C adapters such as the ones made by
1177 Philips or Velleman, Analog Devices evaluation boards, and more.
1178 Basically any adapter using the parallel port as an I2C bus with
1179 no extra chipset is supported by this driver, or could be.
1181 This driver is a replacement for (and was inspired by) an older
1182 driver named i2c-philips-par. The new driver supports more devices,
1183 and makes it easier to add support for new devices.
1185 An adapter type parameter is now mandatory. Please read the file
1186 Documentation/i2c/busses/i2c-parport for details.
1188 Another driver exists, named i2c-parport-light, which doesn't depend
1189 on the parport driver. This is meant for embedded systems. Don't say
1190 Y here if you intend to say Y or M there.
1192 This support is also available as a module. If so, the module
1193 will be called i2c-parport.
1195 config I2C_PARPORT_LIGHT
1196 tristate "Parallel port adapter (light)"
1200 This supports parallel port I2C adapters such as the ones made by
1201 Philips or Velleman, Analog Devices evaluation boards, and more.
1202 Basically any adapter using the parallel port as an I2C bus with
1203 no extra chipset is supported by this driver, or could be.
1205 This driver is a light version of i2c-parport. It doesn't depend
1206 on the parport driver, and uses direct I/O access instead. This
1207 might be preferred on embedded systems where wasting memory for
1208 the clean but heavy parport handling is not an option. The
1209 drawback is a reduced portability and the impossibility to
1210 daisy-chain other parallel port devices.
1212 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1213 both is possible but both modules should not be loaded at the same
1216 This support is also available as a module. If so, the module
1217 will be called i2c-parport-light.
1219 config I2C_ROBOTFUZZ_OSIF
1220 tristate "RobotFuzz Open Source InterFace USB adapter"
1223 If you say yes to this option, support will be included for the
1224 RobotFuzz Open Source InterFace USB to I2C interface.
1226 This driver can also be built as a module. If so, the module
1227 will be called i2c-osif.
1230 tristate "TAOS evaluation module"
1233 select SERIO_SERPORT
1236 This supports TAOS evaluation modules on serial port. In order to
1237 use this driver, you will need the inputattach tool, which is part
1238 of the input-utils package.
1242 This support is also available as a module. If so, the module
1243 will be called i2c-taos-evm.
1246 tristate "Tiny-USB adapter"
1249 If you say yes to this option, support will be included for the
1250 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1251 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1253 This driver can also be built as a module. If so, the module
1254 will be called i2c-tiny-usb.
1256 config I2C_VIPERBOARD
1257 tristate "Viperboard I2C master support"
1258 depends on MFD_VIPERBOARD && USB
1260 Say yes here to access the I2C part of the Nano River
1261 Technologies Viperboard as I2C master.
1262 See viperboard API specification and Nano
1263 River Tech's viperboard.h for detailed meaning
1264 of the module parameters.
1266 comment "Other I2C/SMBus bus drivers"
1269 tristate "Acorn IOC/IOMD I2C bus support"
1270 depends on ARCH_ACORN
1274 Say yes if you want to support the I2C bus on Acorn platforms.
1276 If you don't know, say Y.
1279 tristate "Elektor ISA card"
1280 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1283 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1286 This support is also available as a module. If so, the module
1287 will be called i2c-elektor.
1290 tristate "Mellanox I2C driver"
1293 This exposes the Mellanox platform I2C busses to the linux I2C layer
1294 for X86 based systems.
1295 Controller is implemented as CPLD logic.
1297 This driver can also be built as a module. If so, the module will be
1298 called as i2c-mlxcpld.
1301 tristate "PCA9564/PCA9665 on an ISA bus"
1306 This driver supports ISA boards using the Philips PCA9564/PCA9665
1307 parallel bus to I2C bus controller.
1309 This driver can also be built as a module. If so, the module
1310 will be called i2c-pca-isa.
1312 This device is almost undetectable and using this driver on a
1313 system which doesn't have this device will result in long
1314 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1315 time). If unsure, say N.
1318 tristate "SiByte SMBus interface"
1319 depends on SIBYTE_SB1xxx_SOC
1321 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1323 config I2C_CROS_EC_TUNNEL
1324 tristate "ChromeOS EC tunnel I2C bus"
1325 depends on MFD_CROS_EC
1327 If you say yes here you get an I2C bus that will tunnel i2c commands
1328 through to the other side of the ChromeOS EC to the i2c bus
1329 connected there. This will work whatever the interface used to
1330 talk to the EC (SPI, I2C or LPC).
1332 config I2C_XGENE_SLIMPRO
1333 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1334 depends on ARCH_XGENE && MAILBOX
1336 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1337 co-processor. The I2C device access the I2C bus via the X-Gene
1338 to SLIMpro (On chip coprocessor) mailbox mechanism.
1342 tristate "Geode ACCESS.bus support"
1343 depends on X86_32 && PCI
1345 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1346 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1348 If you don't know what to do here, say N.
1350 This support is also available as a module. If so, the module
1351 will be called scx200_acb.
1354 tristate "IBM OPAL I2C driver"
1355 depends on PPC_POWERNV
1358 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1359 the driver is based on the OPAL interfaces.
1361 This driver can also be built as a module. If so, the module will be
1365 tristate "ZTE ZX2967 I2C support"
1369 Selecting this option will add ZX2967 I2C driver.
1370 This driver can also be built as a module. If so, the module will be
1374 tristate "FSI I2C driver"
1377 Driver for FSI bus attached I2C masters. These are I2C masters that
1378 are connected to the system over an FSI bus, instead of the more
1379 common PCI or MMIO interface.
1381 This driver can also be built as a module. If so, the module will be