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 "AMD MP2 PCIe"
82 depends on PCI && ACPI
84 If you say yes to this option, support will be included for the AMD
87 This driver can also be built as modules. If so, the modules will
88 be called i2c-amd-mp2-pci and i2c-amd-mp2-plat.
91 tristate "Hix5hd2 high-speed I2C driver"
92 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST
94 Say Y here to include support for the high-speed I2C controller
95 used in HiSilicon hix5hd2 SoCs.
97 This driver can also be built as a module. If so, the module
98 will be called i2c-hix5hd2.
101 tristate "Intel 82801 (ICH/PCH)"
103 select CHECK_SIGNATURE if X86 && DMI
106 If you say yes to this option, support will be included for the Intel
107 801 family of mainboard I2C interfaces. Specifically, the following
108 versions of the chipset are supported:
114 82801EB/ER (ICH5/ICH5R)
146 This driver can also be built as a module. If so, the module
147 will be called i2c-i801.
150 tristate "Intel SCH SMBus 1.0"
154 Say Y here if you want to use SMBus controller on the Intel SCH
157 This driver can also be built as a module. If so, the module
158 will be called i2c-isch.
161 tristate "Intel iSMT SMBus Controller"
162 depends on PCI && X86
164 If you say yes to this option, support will be included for the Intel
165 iSMT SMBus host controller interface.
167 This driver can also be built as a module. If so, the module will be
171 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
174 If you say yes to this option, support will be included for the Intel
175 PIIX4 family of mainboard I2C interfaces. Specifically, the following
176 versions of the chipset are supported (note that Serverworks is part
197 Some AMD chipsets contain two PIIX4-compatible SMBus
198 controllers. This driver will attempt to use both controllers
199 on the SB700/SP5100, if they have been initialized by the BIOS.
201 This driver can also be built as a module. If so, the module
202 will be called i2c-piix4.
205 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
206 depends on INTEL_SOC_PMIC_CHTWC
208 If you say yes to this option, support will be included for the
209 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
210 found on some Intel Cherry Trail systems.
212 Note this controller is hooked up to a TI bq24292i charger-IC,
213 combined with a FUSB302 Type-C port-controller as such it is advised
214 to also select CONFIG_TYPEC_FUSB302=m.
217 tristate "Nvidia nForce2, nForce3 and nForce4"
220 If you say yes to this option, support will be included for the Nvidia
221 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
223 This driver can also be built as a module. If so, the module
224 will be called i2c-nforce2.
226 config I2C_NFORCE2_S4985
227 tristate "SMBus multiplexing on the Tyan S4985"
228 depends on I2C_NFORCE2 && X86
230 Enabling this option will add specific SMBus support for the Tyan
231 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
232 over 4 different channels, where the various memory module EEPROMs
233 live. Saying yes here will give you access to these in addition
236 This driver can also be built as a module. If so, the module
237 will be called i2c-nforce2-s4985.
239 config I2C_NVIDIA_GPU
240 tristate "NVIDIA GPU I2C controller"
243 If you say yes to this option, support will be included for the
244 NVIDIA GPU I2C controller which is used to communicate with the GPU's
245 Type-C controller. This driver can also be built as a module called
252 If you say yes to this option, support will be included for the
253 SiS5595 SMBus (a subset of I2C) interface.
255 This driver can also be built as a module. If so, the module
256 will be called i2c-sis5595.
259 tristate "SiS 630/730/964"
262 If you say yes to this option, support will be included for the
263 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
265 This driver can also be built as a module. If so, the module
266 will be called i2c-sis630.
272 If you say yes to this option, support will be included for the SiS
273 96x SMBus (a subset of I2C) interfaces. Specifically, the following
274 chipsets are supported:
283 This driver can also be built as a module. If so, the module
284 will be called i2c-sis96x.
287 tristate "VIA VT82C586B"
291 If you say yes to this option, support will be included for the VIA
292 82C586B I2C interface
294 This driver can also be built as a module. If so, the module
295 will be called i2c-via.
298 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
301 If you say yes to this option, support will be included for the VIA
302 VT82C596 and later SMBus interface. Specifically, the following
303 chipsets are supported:
316 This driver can also be built as a module. If so, the module
317 will be called i2c-viapro.
321 comment "ACPI drivers"
324 tristate "SMBus Control Method Interface"
326 This driver supports the SMBus Control Method Interface. It needs the
327 BIOS to declare ACPI control methods as described in the SMBus Control
328 Method Interface specification.
330 To compile this driver as a module, choose M here:
331 the module will be called i2c-scmi.
335 comment "Mac SMBus host controller drivers"
336 depends on PPC_CHRP || PPC_PMAC
339 tristate "CHRP Apple Hydra Mac I/O I2C interface"
340 depends on PCI && PPC_CHRP
343 This supports the use of the I2C interface in the Apple Hydra Mac
344 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
347 This support is also available as a module. If so, the module
348 will be called i2c-hydra.
351 tristate "Powermac I2C interface"
355 This exposes the various PowerMac i2c interfaces to the linux i2c
356 layer and to userland. It is used by various drivers on the PowerMac
357 platform, and should generally be enabled.
359 This support is also available as a module. If so, the module
360 will be called i2c-powermac.
362 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
365 tristate "Altera Soft IP I2C"
366 depends on (ARCH_SOCFPGA || NIOS2) && OF
368 If you say yes to this option, support will be included for the
369 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
371 This driver can also be built as a module. If so, the module
372 will be called i2c-altera.
375 tristate "Aspeed I2C Controller"
376 depends on ARCH_ASPEED || COMPILE_TEST
378 If you say yes to this option, support will be included for the
379 Aspeed I2C controller.
381 This driver can also be built as a module. If so, the module
382 will be called i2c-aspeed.
385 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
388 This supports the use of the I2C interface on Atmel AT91
391 A serious problem is that there is no documented way to issue
392 repeated START conditions for more than two messages, as needed
393 to support combined I2C messages. Use the i2c-gpio driver
394 unless your system can cope with this limitation.
396 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
397 don't have clock stretching in transmission mode. For that reason,
398 you can encounter underrun issues causing premature stop sendings if
399 the latency to fill the transmission register is too long. If you
400 are facing this situation, use the i2c-gpio driver.
402 config I2C_AT91_SLAVE_EXPERIMENTAL
403 tristate "Microchip AT91 I2C experimental slave mode"
407 If you say yes to this option, support for the slave mode will be
408 added. Caution: do not use it for production. This feature has not
409 been tested in a heavy way, help wanted.
410 There are known bugs:
411 - It can hang, on a SAMA5D4, after several transfers.
412 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as
416 tristate "Au1550/Au1200/Au1300 SMBus interface"
417 depends on MIPS_ALCHEMY
419 If you say yes to this option, support will be included for the
420 Au1550/Au1200/Au1300 SMBus interface.
422 This driver can also be built as a module. If so, the module
423 will be called i2c-au1550.
426 tristate "Axxia I2C controller"
427 depends on ARCH_AXXIA || COMPILE_TEST
430 Say yes if you want to support the I2C bus on Axxia platforms.
432 Please note that this controller is limited to transfers of maximum
433 255 bytes in length. Any attempt to to a larger transfer will return
437 tristate "Broadcom BCM2835 I2C controller"
438 depends on ARCH_BCM2835
440 If you say yes to this option, support will be included for the
441 BCM2835 I2C controller.
443 If you don't know what to do here, say N.
445 This support is also available as a module. If so, the module
446 will be called i2c-bcm2835.
449 tristate "Broadcom iProc I2C controller"
450 depends on ARCH_BCM_IPROC || COMPILE_TEST
451 default ARCH_BCM_IPROC
454 If you say yes to this option, support will be included for the
455 Broadcom iProc I2C controller.
457 If you don't know what to do here, say N.
460 tristate "BCM Kona I2C adapter"
461 depends on ARCH_BCM_MOBILE
464 If you say yes to this option, support will be included for the
465 I2C interface on the Broadcom Kona family of processors.
467 If you do not need KONA I2C interface, say N.
470 tristate "BRCM Settop/DSL I2C controller"
471 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
475 If you say yes to this option, support will be included for the
476 I2C interface on the Broadcom Settop/DSL SoCs.
478 If you do not need I2C interface, say N.
481 tristate "Cadence I2C Controller"
482 depends on ARCH_ZYNQ || ARM64 || XTENSA
484 Say yes here to select Cadence I2C Host Controller. This controller is
485 e.g. used by Xilinx Zynq.
488 tristate "CBUS I2C driver"
489 depends on GPIOLIB || COMPILE_TEST
491 Support for CBUS access using I2C API. Mostly relevant for Nokia
492 Internet Tablets (770, N800 and N810).
494 This driver can also be built as a module. If so, the module
495 will be called i2c-cbus-gpio.
498 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
499 depends on CPM1 || CPM2
501 This supports the use of the I2C interface on Freescale
502 processors with CPM1 or CPM2.
504 This driver can also be built as a module. If so, the module
505 will be called i2c-cpm.
508 tristate "DaVinci I2C driver"
509 depends on ARCH_DAVINCI || ARCH_KEYSTONE
511 Support for TI DaVinci I2C controller driver.
513 This driver can also be built as a module. If so, the module
514 will be called i2c-davinci.
516 Please note that this driver might be needed to bring up other
517 devices such as DaVinci NIC.
518 For details please see http://www.ti.com/davinci
520 config I2C_DESIGNWARE_CORE
523 config I2C_DESIGNWARE_PLATFORM
524 tristate "Synopsys DesignWare Platform"
525 select I2C_DESIGNWARE_CORE
526 depends on (ACPI && COMMON_CLK) || !ACPI
528 If you say yes to this option, support will be included for the
529 Synopsys DesignWare I2C adapter.
531 This driver can also be built as a module. If so, the module
532 will be called i2c-designware-platform.
534 config I2C_DESIGNWARE_SLAVE
535 bool "Synopsys DesignWare Slave"
537 depends on I2C_DESIGNWARE_PLATFORM
539 If you say yes to this option, support will be included for the
540 Synopsys DesignWare I2C slave adapter.
542 This is not a standalone module, this module compiles together with
545 config I2C_DESIGNWARE_PCI
546 tristate "Synopsys DesignWare PCI"
548 select I2C_DESIGNWARE_CORE
550 If you say yes to this option, support will be included for the
551 Synopsys DesignWare I2C adapter. Only master mode is supported.
553 This driver can also be built as a module. If so, the module
554 will be called i2c-designware-pci.
556 config I2C_DESIGNWARE_BAYTRAIL
557 bool "Intel Baytrail I2C semaphore support"
559 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
560 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
562 This driver enables managed host access to the PMIC I2C bus on select
563 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
564 the host to request uninterrupted access to the PMIC's I2C bus from
565 the platform firmware controlling it. You should say Y if running on
566 a BayTrail system using the AXP288.
569 tristate "Conexant Digicolor I2C driver"
570 depends on ARCH_DIGICOLOR
572 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
574 This driver can also be built as a module. If so, the module
575 will be called i2c-digicolor.
578 tristate "EFM32 I2C controller"
579 depends on ARCH_EFM32 || COMPILE_TEST
581 This driver supports the i2c block found in Energy Micro's EFM32
585 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
586 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
588 This driver is for PCH(Platform controller Hub) I2C of EG20T which
589 is an IOH(Input/Output Hub) for x86 embedded processor.
590 This driver can access PCH I2C bus device.
592 This driver also can be used for LAPIS Semiconductor IOH(Input/
593 Output Hub), ML7213, ML7223 and ML7831.
594 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
595 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
596 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
597 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
600 tristate "EMMA Mobile series I2C adapter"
604 If you say yes to this option, support will be included for the
605 I2C interface on the Renesas Electronics EM/EV family of processors.
608 tristate "Exynos5 high-speed I2C driver"
609 depends on ARCH_EXYNOS && OF
612 High-speed I2C controller on Exynos5 based Samsung SoCs.
615 tristate "GPIO-based bitbanging I2C"
616 depends on GPIOLIB || COMPILE_TEST
619 This is a very simple bitbanging I2C driver utilizing the
620 arch-neutral GPIO API to control the SCL and SDA lines.
622 config I2C_GPIO_FAULT_INJECTOR
623 bool "GPIO-based fault injector"
626 This adds some functionality to the i2c-gpio driver which can inject
627 faults to an I2C bus, so another bus master can be stress-tested.
628 This is for debugging. If unsure, say 'no'.
630 config I2C_HIGHLANDER
631 tristate "Highlander FPGA SMBus interface"
632 depends on SH_HIGHLANDER
634 If you say yes to this option, support will be included for
635 the SMBus interface located in the FPGA on various Highlander
636 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
637 FPGAs. This is wholly unrelated to the SoC I2C.
639 This driver can also be built as a module. If so, the module
640 will be called i2c-highlander.
643 tristate "IBM PPC 4xx on-chip I2C interface"
646 Say Y here if you want to use IIC peripheral found on
647 embedded IBM PPC 4xx based systems.
649 This driver can also be built as a module. If so, the module
650 will be called i2c-ibm_iic.
653 tristate "Imagination Technologies I2C SCB Controller"
654 depends on MIPS || COMPILE_TEST
656 Say Y here if you want to use the IMG I2C SCB controller,
657 available on the TZ1090 and other IMG SoCs.
659 This driver can also be built as a module. If so, the module
660 will be called i2c-img-scb.
663 tristate "IMX I2C interface"
664 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
666 Say Y here if you want to use the IIC bus controller on
667 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
669 This driver can also be built as a module. If so, the module
670 will be called i2c-imx.
673 tristate "IMX Low Power I2C interface"
674 depends on ARCH_MXC || COMPILE_TEST
676 Say Y here if you want to use the Low Power IIC bus controller
677 on the Freescale i.MX processors.
679 This driver can also be built as a module. If so, the module
680 will be called i2c-imx-lpi2c.
683 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
684 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
686 Say Y here if you want to use the IIC bus controller on
687 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
689 This driver can also be built as a module. If so, the module
690 will be called i2c-iop3xx.
693 tristate "JZ4780 I2C controller interface support"
694 depends on MACH_JZ4780 || COMPILE_TEST
696 If you say yes to this option, support will be included for the
697 Ingenic JZ4780 I2C controller.
699 If you don't know what to do here, say N.
702 tristate "Kontron COM I2C Controller"
703 depends on MFD_KEMPLD
705 This enables support for the I2C bus interface on some Kontron ETX
706 and COMexpress (ETXexpress) modules.
708 This driver can also be built as a module. If so, the module
709 will be called i2c-kempld.
712 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
713 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
715 This driver supports the I2C interface found several NXP
716 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
718 This driver can also be built as a module. If so, the module
719 will be called i2c-lpc2k.
722 tristate "Amlogic Meson I2C controller"
723 depends on ARCH_MESON || COMPILE_TEST
725 If you say yes to this option, support will be included for the
726 I2C interface on the Amlogic Meson family of SoCs.
729 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
732 If you say yes to this option, support will be included for the
733 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
734 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
736 This driver can also be built as a module. If so, the module
737 will be called i2c-mpc.
740 tristate "MediaTek I2C adapter"
741 depends on ARCH_MEDIATEK || COMPILE_TEST
743 This selects the MediaTek(R) Integrated Inter Circuit bus driver
744 for MT65xx and MT81xx.
745 If you want to use MediaTek(R) I2C interface, say Y or M here.
749 tristate "Marvell mv64xxx I2C Controller"
750 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
752 If you say yes to this option, support will be included for the
753 built-in I2C interface on the Marvell 64xxx line of host bridges.
754 This driver is also used for Allwinner SoCs I2C controllers.
756 This driver can also be built as a module. If so, the module
757 will be called i2c-mv64xxx.
760 tristate "Freescale i.MX28 I2C interface"
764 Say Y here if you want to use the I2C bus controller on
765 the Freescale i.MX28 processors.
767 This driver can also be built as a module. If so, the module
768 will be called i2c-mxs.
771 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
774 If you say yes to this option, support will be included for the
775 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
776 as well as the STA2X11 PCIe I/O HUB.
779 tristate "OpenCores I2C Controller"
781 If you say yes to this option, support will be included for the
782 OpenCores I2C controller. For details see
783 http://www.opencores.org/projects.cgi/web/i2c/overview
785 This driver can also be built as a module. If so, the module
786 will be called i2c-ocores.
789 tristate "OMAP I2C adapter"
790 depends on ARCH_OMAP || ARCH_K3
791 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
793 If you say yes to this option, support will be included for the
794 I2C interface on the Texas Instruments OMAP1/2 family of processors.
795 Like OMAP1510/1610/1710/5912 and OMAP242x.
796 For details see http://www.ti.com/omap.
799 tristate "Actions Semiconductor Owl I2C Controller"
800 depends on ARCH_ACTIONS || COMPILE_TEST
802 Say Y here if you want to use the I2C bus controller on
803 the Actions Semiconductor Owl SoC's.
806 tristate "PA Semi SMBus interface"
807 depends on PPC_PASEMI && PCI
809 Supports the PA Semi PWRficient on-chip SMBus interfaces.
811 config I2C_PCA_PLATFORM
812 tristate "PCA9564/PCA9665 as platform device"
816 This driver supports a memory mapped Philips PCA9564/PCA9665
817 parallel bus to I2C bus controller.
819 This driver can also be built as a module. If so, the module
820 will be called i2c-pca-platform.
823 tristate "PMC MSP I2C TWI Controller"
826 This driver supports the PMC TWI controller on MSP devices.
828 This driver can also be built as module. If so, the module
829 will be called i2c-pmcmsp.
832 tristate "I2C bus support for Philips PNX and NXP LPC targets"
833 depends on ARCH_LPC32XX
835 This driver supports the Philips IP3204 I2C IP block master and/or
838 This driver can also be built as a module. If so, the module
839 will be called i2c-pnx.
842 tristate "PKUnity v3 I2C bus support"
843 depends on UNICORE32 && ARCH_PUV3
846 This driver supports the I2C IP inside the PKUnity-v3 SoC.
847 This I2C bus controller is under AMBA/AXI bus.
849 This driver can also be built as a module. If so, the module
850 will be called i2c-puv3.
853 tristate "Intel PXA2XX I2C adapter"
854 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
856 If you have devices in the PXA I2C bus, say yes to this option.
857 This driver can also be built as a module. If so, the module
858 will be called i2c-pxa.
861 def_bool I2C_PXA && X86_32 && PCI && OF
864 bool "Intel PXA2XX I2C Slave comms support"
865 depends on I2C_PXA && !X86_32
867 Support I2C slave mode communications on the PXA I2C bus. This
868 is necessary for systems where the PXA may be a target on the
872 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
873 depends on ARCH_QCOM || COMPILE_TEST
874 depends on QCOM_GENI_SE
876 This driver supports GENI serial engine based I2C controller in
877 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
878 yes to this option, support will be included for the built-in I2C
879 interface on the Qualcomm Technologies Inc.'s SoCs.
881 This driver can also be built as a module. If so, the module
882 will be called i2c-qcom-geni.
885 tristate "Qualcomm QUP based I2C controller"
888 If you say yes to this option, support will be included for the
889 built-in I2C interface on the Qualcomm SoCs.
891 This driver can also be built as a module. If so, the module
892 will be called i2c-qup.
895 tristate "Renesas RIIC adapter"
896 depends on ARCH_RENESAS || COMPILE_TEST
898 If you say yes to this option, support will be included for the
899 Renesas RIIC I2C interface.
901 This driver can also be built as a module. If so, the module
902 will be called i2c-riic.
905 tristate "Rockchip RK3xxx I2C adapter"
906 depends on OF && COMMON_CLK
908 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
911 This driver can also be built as a module. If so, the module will
914 config HAVE_S3C2410_I2C
917 This will include I2C support for Samsung SoCs. If you want to
918 include I2C support for any machine, kindly select this in the
919 respective Kconfig file.
922 tristate "S3C2410 I2C Driver"
923 depends on HAVE_S3C2410_I2C
925 Say Y here to include support for I2C controller in the
929 tristate "Renesas SH7760 I2C Controller"
930 depends on CPU_SUBTYPE_SH7760
932 This driver supports the 2 I2C interfaces on the Renesas SH7760.
934 This driver can also be built as a module. If so, the module
935 will be called i2c-sh7760.
938 tristate "SuperH Mobile I2C Controller"
939 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
941 If you say yes to this option, support will be included for the
942 built-in I2C interface on the Renesas SH-Mobile processor.
944 This driver can also be built as a module. If so, the module
945 will be called i2c-sh_mobile.
948 tristate "Simtec Generic I2C interface"
951 If you say yes to this option, support will be included for
952 the Simtec Generic I2C interface. This driver is for the
953 simple I2C bus used on newer Simtec products for general
954 I2C, such as DDC on the Simtec BBD2016A.
956 This driver can also be built as a module. If so, the module
957 will be called i2c-simtec.
960 tristate "CSR SiRFprimaII I2C interface"
963 If you say yes to this option, support will be included for the
964 CSR SiRFprimaII I2C interface.
966 This driver can also be built as a module. If so, the module
967 will be called i2c-sirf.
970 bool "Spreadtrum I2C interface"
971 depends on I2C=y && ARCH_SPRD
973 If you say yes to this option, support will be included for the
974 Spreadtrum I2C interface.
977 tristate "STMicroelectronics SSC I2C support"
980 Enable this option to add support for STMicroelectronics SoCs
981 hardware SSC (Synchronous Serial Controller) as an I2C controller.
983 This driver can also be built as module. If so, the module
984 will be called i2c-st.
987 tristate "STMicroelectronics STM32F4 I2C support"
988 depends on ARCH_STM32 || COMPILE_TEST
990 Enable this option to add support for STM32 I2C controller embedded
993 This driver can also be built as module. If so, the module
994 will be called i2c-stm32f4.
997 tristate "STMicroelectronics STM32F7 I2C support"
998 depends on ARCH_STM32 || COMPILE_TEST
1001 Enable this option to add support for STM32 I2C controller embedded
1004 This driver can also be built as module. If so, the module
1005 will be called i2c-stm32f7.
1008 tristate "ST Microelectronics DDC I2C interface"
1009 depends on MACH_U300
1010 default y if MACH_U300
1012 If you say yes to this option, support will be included for the
1013 I2C interface from ST Microelectronics simply called "DDC I2C"
1014 supporting both I2C and DDC, used in e.g. the U300 series
1017 This driver can also be built as a module. If so, the module
1018 will be called i2c-stu300.
1020 config I2C_SUN6I_P2WI
1021 tristate "Allwinner sun6i internal P2WI controller"
1022 depends on RESET_CONTROLLER
1023 depends on MACH_SUN6I || COMPILE_TEST
1025 If you say yes to this option, support will be included for the
1026 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1028 The P2WI looks like an SMBus controller (which supports only byte
1029 accesses), except that it only supports one slave device.
1030 This interface is used to connect to specific PMIC devices (like the
1033 config I2C_SYNQUACER
1034 tristate "Socionext SynQuacer I2C controller"
1035 depends on ARCH_SYNQUACER || COMPILE_TEST
1037 Say Y here to include support for the I2C controller used in some
1038 Fujitsu and Socionext SoCs.
1040 This driver can also be built as a module. If so, the module
1041 will be called i2c-synquacer.
1044 tristate "NVIDIA Tegra internal I2C controller"
1045 depends on ARCH_TEGRA
1047 If you say yes to this option, support will be included for the
1048 I2C controller embedded in NVIDIA Tegra SOCs
1050 config I2C_TEGRA_BPMP
1051 tristate "NVIDIA Tegra BPMP I2C controller"
1052 depends on TEGRA_BPMP
1055 If you say yes to this option, support will be included for the I2C
1056 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1058 This I2C driver is a 'virtual' I2C driver. The real driver is part
1059 of the BPMP firmware, and this driver merely communicates with that
1063 tristate "UniPhier FIFO-less I2C controller"
1064 depends on ARCH_UNIPHIER || COMPILE_TEST
1066 If you say yes to this option, support will be included for
1067 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1068 or older UniPhier SoCs.
1070 config I2C_UNIPHIER_F
1071 tristate "UniPhier FIFO-builtin I2C controller"
1072 depends on ARCH_UNIPHIER || COMPILE_TEST
1074 If you say yes to this option, support will be included for
1075 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1076 PH1-Pro5, or newer UniPhier SoCs.
1078 config I2C_VERSATILE
1079 tristate "ARM Versatile/Realview I2C bus support"
1080 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1083 Say yes if you want to support the I2C serial bus on ARMs Versatile
1086 This driver can also be built as a module. If so, the module
1087 will be called i2c-versatile.
1090 tristate "Wondermedia WM8xxx SoC I2C bus support"
1091 depends on ARCH_VT8500
1093 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1096 This driver can also be built as a module. If so, the module will be
1100 tristate "Cavium OCTEON I2C bus support"
1101 depends on CAVIUM_OCTEON_SOC
1103 Say yes if you want to support the I2C serial bus on Cavium
1106 This driver can also be built as a module. If so, the module
1107 will be called i2c-octeon.
1110 tristate "Cavium ThunderX I2C bus support"
1111 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1114 Say yes if you want to support the I2C serial bus on Cavium
1117 This driver can also be built as a module. If so, the module
1118 will be called i2c-thunderx.
1121 tristate "Xilinx I2C Controller"
1122 depends on HAS_IOMEM
1124 If you say yes to this option, support will be included for the
1125 Xilinx I2C controller.
1127 This driver can also be built as a module. If so, the module
1128 will be called xilinx_i2c.
1131 tristate "Netlogic XLR and Sigma Designs I2C support"
1132 depends on CPU_XLR || ARCH_TANGO
1134 This driver enables support for the on-chip I2C interface of
1135 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1137 This driver can also be built as a module. If so, the module
1138 will be called i2c-xlr.
1141 tristate "XLP9XX I2C support"
1142 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1144 This driver enables support for the on-chip I2C interface of
1145 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1147 This driver can also be built as a module. If so, the module will
1148 be called i2c-xlp9xx.
1151 tristate "Renesas R-Car I2C Controller"
1152 depends on ARCH_RENESAS || COMPILE_TEST
1155 If you say yes to this option, support will be included for the
1156 R-Car I2C controller.
1158 This driver can also be built as a module. If so, the module
1159 will be called i2c-rcar.
1161 comment "External I2C/SMBus adapter drivers"
1163 config I2C_DIOLAN_U2C
1164 tristate "Diolan U2C-12 USB adapter"
1167 If you say yes to this option, support will be included for Diolan
1168 U2C-12, a USB to I2C interface.
1170 This driver can also be built as a module. If so, the module
1171 will be called i2c-diolan-u2c.
1174 tristate "Diolan DLN-2 USB I2C adapter"
1177 If you say yes to this option, support will be included for Diolan
1178 DLN2, a USB to I2C interface.
1180 This driver can also be built as a module. If so, the module
1181 will be called i2c-dln2.
1184 tristate "Parallel port adapter"
1189 This supports parallel port I2C adapters such as the ones made by
1190 Philips or Velleman, Analog Devices evaluation boards, and more.
1191 Basically any adapter using the parallel port as an I2C bus with
1192 no extra chipset is supported by this driver, or could be.
1194 This driver is a replacement for (and was inspired by) an older
1195 driver named i2c-philips-par. The new driver supports more devices,
1196 and makes it easier to add support for new devices.
1198 An adapter type parameter is now mandatory. Please read the file
1199 Documentation/i2c/busses/i2c-parport for details.
1201 Another driver exists, named i2c-parport-light, which doesn't depend
1202 on the parport driver. This is meant for embedded systems. Don't say
1203 Y here if you intend to say Y or M there.
1205 This support is also available as a module. If so, the module
1206 will be called i2c-parport.
1208 config I2C_PARPORT_LIGHT
1209 tristate "Parallel port adapter (light)"
1213 This supports parallel port I2C adapters such as the ones made by
1214 Philips or Velleman, Analog Devices evaluation boards, and more.
1215 Basically any adapter using the parallel port as an I2C bus with
1216 no extra chipset is supported by this driver, or could be.
1218 This driver is a light version of i2c-parport. It doesn't depend
1219 on the parport driver, and uses direct I/O access instead. This
1220 might be preferred on embedded systems where wasting memory for
1221 the clean but heavy parport handling is not an option. The
1222 drawback is a reduced portability and the impossibility to
1223 daisy-chain other parallel port devices.
1225 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1226 both is possible but both modules should not be loaded at the same
1229 This support is also available as a module. If so, the module
1230 will be called i2c-parport-light.
1232 config I2C_ROBOTFUZZ_OSIF
1233 tristate "RobotFuzz Open Source InterFace USB adapter"
1236 If you say yes to this option, support will be included for the
1237 RobotFuzz Open Source InterFace USB to I2C interface.
1239 This driver can also be built as a module. If so, the module
1240 will be called i2c-osif.
1243 tristate "TAOS evaluation module"
1246 select SERIO_SERPORT
1249 This supports TAOS evaluation modules on serial port. In order to
1250 use this driver, you will need the inputattach tool, which is part
1251 of the input-utils package.
1255 This support is also available as a module. If so, the module
1256 will be called i2c-taos-evm.
1259 tristate "Tiny-USB adapter"
1262 If you say yes to this option, support will be included for the
1263 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1264 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1266 This driver can also be built as a module. If so, the module
1267 will be called i2c-tiny-usb.
1269 config I2C_VIPERBOARD
1270 tristate "Viperboard I2C master support"
1271 depends on MFD_VIPERBOARD && USB
1273 Say yes here to access the I2C part of the Nano River
1274 Technologies Viperboard as I2C master.
1275 See viperboard API specification and Nano
1276 River Tech's viperboard.h for detailed meaning
1277 of the module parameters.
1279 comment "Other I2C/SMBus bus drivers"
1282 tristate "Acorn IOC/IOMD I2C bus support"
1283 depends on ARCH_ACORN
1287 Say yes if you want to support the I2C bus on Acorn platforms.
1289 If you don't know, say Y.
1292 tristate "Elektor ISA card"
1293 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1296 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1299 This support is also available as a module. If so, the module
1300 will be called i2c-elektor.
1303 tristate "Mellanox I2C driver"
1306 This exposes the Mellanox platform I2C busses to the linux I2C layer
1307 for X86 based systems.
1308 Controller is implemented as CPLD logic.
1310 This driver can also be built as a module. If so, the module will be
1311 called as i2c-mlxcpld.
1314 tristate "PCA9564/PCA9665 on an ISA bus"
1319 This driver supports ISA boards using the Philips PCA9564/PCA9665
1320 parallel bus to I2C bus controller.
1322 This driver can also be built as a module. If so, the module
1323 will be called i2c-pca-isa.
1325 This device is almost undetectable and using this driver on a
1326 system which doesn't have this device will result in long
1327 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1328 time). If unsure, say N.
1331 tristate "SiByte SMBus interface"
1332 depends on SIBYTE_SB1xxx_SOC
1334 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1336 config I2C_CROS_EC_TUNNEL
1337 tristate "ChromeOS EC tunnel I2C bus"
1338 depends on MFD_CROS_EC
1340 If you say yes here you get an I2C bus that will tunnel i2c commands
1341 through to the other side of the ChromeOS EC to the i2c bus
1342 connected there. This will work whatever the interface used to
1343 talk to the EC (SPI, I2C or LPC).
1345 config I2C_XGENE_SLIMPRO
1346 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1347 depends on ARCH_XGENE && MAILBOX
1349 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1350 co-processor. The I2C device access the I2C bus via the X-Gene
1351 to SLIMpro (On chip coprocessor) mailbox mechanism.
1355 tristate "Geode ACCESS.bus support"
1356 depends on X86_32 && PCI
1358 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1359 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1361 If you don't know what to do here, say N.
1363 This support is also available as a module. If so, the module
1364 will be called scx200_acb.
1367 tristate "IBM OPAL I2C driver"
1368 depends on PPC_POWERNV
1371 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1372 the driver is based on the OPAL interfaces.
1374 This driver can also be built as a module. If so, the module will be
1378 tristate "ZTE ZX2967 I2C support"
1382 Selecting this option will add ZX2967 I2C driver.
1383 This driver can also be built as a module. If so, the module will be
1387 tristate "FSI I2C driver"
1390 Driver for FSI bus attached I2C masters. These are I2C masters that
1391 are connected to the system over an FSI bus, instead of the more
1392 common PCI or MMIO interface.
1394 This driver can also be built as a module. If so, the module will be