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.
231 If you say yes to this option, support will be included for the
232 SiS5595 SMBus (a subset of I2C) interface.
234 This driver can also be built as a module. If so, the module
235 will be called i2c-sis5595.
238 tristate "SiS 630/730/964"
241 If you say yes to this option, support will be included for the
242 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
244 This driver can also be built as a module. If so, the module
245 will be called i2c-sis630.
251 If you say yes to this option, support will be included for the SiS
252 96x SMBus (a subset of I2C) interfaces. Specifically, the following
253 chipsets are supported:
262 This driver can also be built as a module. If so, the module
263 will be called i2c-sis96x.
266 tristate "VIA VT82C586B"
270 If you say yes to this option, support will be included for the VIA
271 82C586B I2C interface
273 This driver can also be built as a module. If so, the module
274 will be called i2c-via.
277 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
280 If you say yes to this option, support will be included for the VIA
281 VT82C596 and later SMBus interface. Specifically, the following
282 chipsets are supported:
295 This driver can also be built as a module. If so, the module
296 will be called i2c-viapro.
300 comment "ACPI drivers"
303 tristate "SMBus Control Method Interface"
305 This driver supports the SMBus Control Method Interface. It needs the
306 BIOS to declare ACPI control methods as described in the SMBus Control
307 Method Interface specification.
309 To compile this driver as a module, choose M here:
310 the module will be called i2c-scmi.
314 comment "Mac SMBus host controller drivers"
315 depends on PPC_CHRP || PPC_PMAC
318 tristate "CHRP Apple Hydra Mac I/O I2C interface"
319 depends on PCI && PPC_CHRP
322 This supports the use of the I2C interface in the Apple Hydra Mac
323 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
326 This support is also available as a module. If so, the module
327 will be called i2c-hydra.
330 tristate "Powermac I2C interface"
334 This exposes the various PowerMac i2c interfaces to the linux i2c
335 layer and to userland. It is used by various drivers on the PowerMac
336 platform, and should generally be enabled.
338 This support is also available as a module. If so, the module
339 will be called i2c-powermac.
341 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
344 tristate "Altera Soft IP I2C"
345 depends on (ARCH_SOCFPGA || NIOS2) && OF
347 If you say yes to this option, support will be included for the
348 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
350 This driver can also be built as a module. If so, the module
351 will be called i2c-altera.
354 tristate "Aspeed I2C Controller"
355 depends on ARCH_ASPEED || COMPILE_TEST
357 If you say yes to this option, support will be included for the
358 Aspeed I2C controller.
360 This driver can also be built as a module. If so, the module
361 will be called i2c-aspeed.
364 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
367 This supports the use of the I2C interface on Atmel AT91
370 A serious problem is that there is no documented way to issue
371 repeated START conditions for more than two messages, as needed
372 to support combined I2C messages. Use the i2c-gpio driver
373 unless your system can cope with this limitation.
375 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
376 don't have clock stretching in transmission mode. For that reason,
377 you can encounter underrun issues causing premature stop sendings if
378 the latency to fill the transmission register is too long. If you
379 are facing this situation, use the i2c-gpio driver.
382 tristate "Au1550/Au1200/Au1300 SMBus interface"
383 depends on MIPS_ALCHEMY
385 If you say yes to this option, support will be included for the
386 Au1550/Au1200/Au1300 SMBus interface.
388 This driver can also be built as a module. If so, the module
389 will be called i2c-au1550.
392 tristate "Axxia I2C controller"
393 depends on ARCH_AXXIA || COMPILE_TEST
396 Say yes if you want to support the I2C bus on Axxia platforms.
398 Please note that this controller is limited to transfers of maximum
399 255 bytes in length. Any attempt to to a larger transfer will return
403 tristate "Broadcom BCM2835 I2C controller"
404 depends on ARCH_BCM2835
406 If you say yes to this option, support will be included for the
407 BCM2835 I2C controller.
409 If you don't know what to do here, say N.
411 This support is also available as a module. If so, the module
412 will be called i2c-bcm2835.
415 tristate "Broadcom iProc I2C controller"
416 depends on ARCH_BCM_IPROC || COMPILE_TEST
417 default ARCH_BCM_IPROC
419 If you say yes to this option, support will be included for the
420 Broadcom iProc I2C controller.
422 If you don't know what to do here, say N.
425 tristate "BCM Kona I2C adapter"
426 depends on ARCH_BCM_MOBILE
429 If you say yes to this option, support will be included for the
430 I2C interface on the Broadcom Kona family of processors.
432 If you do not need KONA I2C interface, say N.
435 tristate "BRCM Settop I2C controller"
436 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
439 If you say yes to this option, support will be included for the
440 I2C interface on the Broadcom Settop SoCs.
442 If you do not need I2C interface, say N.
445 tristate "Cadence I2C Controller"
446 depends on ARCH_ZYNQ || ARM64 || XTENSA
448 Say yes here to select Cadence I2C Host Controller. This controller is
449 e.g. used by Xilinx Zynq.
452 tristate "CBUS I2C driver"
453 depends on GPIOLIB || COMPILE_TEST
455 Support for CBUS access using I2C API. Mostly relevant for Nokia
456 Internet Tablets (770, N800 and N810).
458 This driver can also be built as a module. If so, the module
459 will be called i2c-cbus-gpio.
462 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
463 depends on CPM1 || CPM2
465 This supports the use of the I2C interface on Freescale
466 processors with CPM1 or CPM2.
468 This driver can also be built as a module. If so, the module
469 will be called i2c-cpm.
472 tristate "DaVinci I2C driver"
473 depends on ARCH_DAVINCI || ARCH_KEYSTONE
475 Support for TI DaVinci I2C controller driver.
477 This driver can also be built as a module. If so, the module
478 will be called i2c-davinci.
480 Please note that this driver might be needed to bring up other
481 devices such as DaVinci NIC.
482 For details please see http://www.ti.com/davinci
484 config I2C_DESIGNWARE_CORE
487 config I2C_DESIGNWARE_PLATFORM
488 tristate "Synopsys DesignWare Platform"
489 select I2C_DESIGNWARE_CORE
490 depends on (ACPI && COMMON_CLK) || !ACPI
492 If you say yes to this option, support will be included for the
493 Synopsys DesignWare I2C adapter.
495 This driver can also be built as a module. If so, the module
496 will be called i2c-designware-platform.
498 config I2C_DESIGNWARE_SLAVE
499 bool "Synopsys DesignWare Slave"
501 depends on I2C_DESIGNWARE_PLATFORM
503 If you say yes to this option, support will be included for the
504 Synopsys DesignWare I2C slave adapter.
506 This is not a standalone module, this module compiles together with
509 config I2C_DESIGNWARE_PCI
510 tristate "Synopsys DesignWare PCI"
512 select I2C_DESIGNWARE_CORE
514 If you say yes to this option, support will be included for the
515 Synopsys DesignWare I2C adapter. Only master mode is supported.
517 This driver can also be built as a module. If so, the module
518 will be called i2c-designware-pci.
520 config I2C_DESIGNWARE_BAYTRAIL
521 bool "Intel Baytrail I2C semaphore support"
523 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
524 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
526 This driver enables managed host access to the PMIC I2C bus on select
527 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
528 the host to request uninterrupted access to the PMIC's I2C bus from
529 the platform firmware controlling it. You should say Y if running on
530 a BayTrail system using the AXP288.
533 tristate "Conexant Digicolor I2C driver"
534 depends on ARCH_DIGICOLOR
536 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
538 This driver can also be built as a module. If so, the module
539 will be called i2c-digicolor.
542 tristate "EFM32 I2C controller"
543 depends on ARCH_EFM32 || COMPILE_TEST
545 This driver supports the i2c block found in Energy Micro's EFM32
549 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
550 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
552 This driver is for PCH(Platform controller Hub) I2C of EG20T which
553 is an IOH(Input/Output Hub) for x86 embedded processor.
554 This driver can access PCH I2C bus device.
556 This driver also can be used for LAPIS Semiconductor IOH(Input/
557 Output Hub), ML7213, ML7223 and ML7831.
558 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
559 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
560 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
561 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
564 tristate "EMMA Mobile series I2C adapter"
568 If you say yes to this option, support will be included for the
569 I2C interface on the Renesas Electronics EM/EV family of processors.
572 tristate "Exynos5 high-speed I2C driver"
573 depends on ARCH_EXYNOS && OF
576 High-speed I2C controller on Exynos5 based Samsung SoCs.
579 tristate "GPIO-based bitbanging I2C"
580 depends on GPIOLIB || COMPILE_TEST
583 This is a very simple bitbanging I2C driver utilizing the
584 arch-neutral GPIO API to control the SCL and SDA lines.
586 config I2C_GPIO_FAULT_INJECTOR
587 bool "GPIO-based fault injector"
590 This adds some functionality to the i2c-gpio driver which can inject
591 faults to an I2C bus, so another bus master can be stress-tested.
592 This is for debugging. If unsure, say 'no'.
594 config I2C_HIGHLANDER
595 tristate "Highlander FPGA SMBus interface"
596 depends on SH_HIGHLANDER
598 If you say yes to this option, support will be included for
599 the SMBus interface located in the FPGA on various Highlander
600 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
601 FPGAs. This is wholly unrelated to the SoC I2C.
603 This driver can also be built as a module. If so, the module
604 will be called i2c-highlander.
607 tristate "IBM PPC 4xx on-chip I2C interface"
610 Say Y here if you want to use IIC peripheral found on
611 embedded IBM PPC 4xx based systems.
613 This driver can also be built as a module. If so, the module
614 will be called i2c-ibm_iic.
617 tristate "Imagination Technologies I2C SCB Controller"
618 depends on MIPS || COMPILE_TEST
620 Say Y here if you want to use the IMG I2C SCB controller,
621 available on the TZ1090 and other IMG SoCs.
623 This driver can also be built as a module. If so, the module
624 will be called i2c-img-scb.
627 tristate "IMX I2C interface"
628 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
630 Say Y here if you want to use the IIC bus controller on
631 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
633 This driver can also be built as a module. If so, the module
634 will be called i2c-imx.
637 tristate "IMX Low Power I2C interface"
638 depends on ARCH_MXC || COMPILE_TEST
640 Say Y here if you want to use the Low Power IIC bus controller
641 on the Freescale i.MX processors.
643 This driver can also be built as a module. If so, the module
644 will be called i2c-imx-lpi2c.
647 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
648 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
650 Say Y here if you want to use the IIC bus controller on
651 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
653 This driver can also be built as a module. If so, the module
654 will be called i2c-iop3xx.
657 tristate "JZ4780 I2C controller interface support"
658 depends on MACH_JZ4780 || COMPILE_TEST
660 If you say yes to this option, support will be included for the
661 Ingenic JZ4780 I2C controller.
663 If you don't know what to do here, say N.
666 tristate "Kontron COM I2C Controller"
667 depends on MFD_KEMPLD
669 This enables support for the I2C bus interface on some Kontron ETX
670 and COMexpress (ETXexpress) modules.
672 This driver can also be built as a module. If so, the module
673 will be called i2c-kempld.
676 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
677 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
679 This driver supports the I2C interface found several NXP
680 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
682 This driver can also be built as a module. If so, the module
683 will be called i2c-lpc2k.
686 tristate "Amlogic Meson I2C controller"
687 depends on ARCH_MESON || COMPILE_TEST
689 If you say yes to this option, support will be included for the
690 I2C interface on the Amlogic Meson family of SoCs.
693 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
696 If you say yes to this option, support will be included for the
697 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
698 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
700 This driver can also be built as a module. If so, the module
701 will be called i2c-mpc.
704 tristate "MediaTek I2C adapter"
705 depends on ARCH_MEDIATEK || COMPILE_TEST
707 This selects the MediaTek(R) Integrated Inter Circuit bus driver
708 for MT65xx and MT81xx.
709 If you want to use MediaTek(R) I2C interface, say Y or M here.
713 tristate "Marvell mv64xxx I2C Controller"
714 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
716 If you say yes to this option, support will be included for the
717 built-in I2C interface on the Marvell 64xxx line of host bridges.
718 This driver is also used for Allwinner SoCs I2C controllers.
720 This driver can also be built as a module. If so, the module
721 will be called i2c-mv64xxx.
724 tristate "Freescale i.MX28 I2C interface"
728 Say Y here if you want to use the I2C bus controller on
729 the Freescale i.MX28 processors.
731 This driver can also be built as a module. If so, the module
732 will be called i2c-mxs.
735 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
738 If you say yes to this option, support will be included for the
739 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
740 as well as the STA2X11 PCIe I/O HUB.
743 tristate "OpenCores I2C Controller"
745 If you say yes to this option, support will be included for the
746 OpenCores I2C controller. For details see
747 http://www.opencores.org/projects.cgi/web/i2c/overview
749 This driver can also be built as a module. If so, the module
750 will be called i2c-ocores.
753 tristate "OMAP I2C adapter"
754 depends on ARCH_OMAP || ARCH_K3
755 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
757 If you say yes to this option, support will be included for the
758 I2C interface on the Texas Instruments OMAP1/2 family of processors.
759 Like OMAP1510/1610/1710/5912 and OMAP242x.
760 For details see http://www.ti.com/omap.
763 tristate "Actions Semiconductor Owl I2C Controller"
764 depends on ARCH_ACTIONS || COMPILE_TEST
766 Say Y here if you want to use the I2C bus controller on
767 the Actions Semiconductor Owl SoC's.
770 tristate "PA Semi SMBus interface"
771 depends on PPC_PASEMI && PCI
773 Supports the PA Semi PWRficient on-chip SMBus interfaces.
775 config I2C_PCA_PLATFORM
776 tristate "PCA9564/PCA9665 as platform device"
780 This driver supports a memory mapped Philips PCA9564/PCA9665
781 parallel bus to I2C bus controller.
783 This driver can also be built as a module. If so, the module
784 will be called i2c-pca-platform.
787 tristate "PMC MSP I2C TWI Controller"
790 This driver supports the PMC TWI controller on MSP devices.
792 This driver can also be built as module. If so, the module
793 will be called i2c-pmcmsp.
796 tristate "I2C bus support for Philips PNX and NXP LPC targets"
797 depends on ARCH_LPC32XX
799 This driver supports the Philips IP3204 I2C IP block master and/or
802 This driver can also be built as a module. If so, the module
803 will be called i2c-pnx.
806 tristate "PKUnity v3 I2C bus support"
807 depends on UNICORE32 && ARCH_PUV3
810 This driver supports the I2C IP inside the PKUnity-v3 SoC.
811 This I2C bus controller is under AMBA/AXI bus.
813 This driver can also be built as a module. If so, the module
814 will be called i2c-puv3.
817 tristate "Intel PXA2XX I2C adapter"
818 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
820 If you have devices in the PXA I2C bus, say yes to this option.
821 This driver can also be built as a module. If so, the module
822 will be called i2c-pxa.
825 def_bool I2C_PXA && X86_32 && PCI && OF
828 bool "Intel PXA2XX I2C Slave comms support"
829 depends on I2C_PXA && !X86_32
831 Support I2C slave mode communications on the PXA I2C bus. This
832 is necessary for systems where the PXA may be a target on the
836 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
837 depends on ARCH_QCOM || COMPILE_TEST
838 depends on QCOM_GENI_SE
840 This driver supports GENI serial engine based I2C controller in
841 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
842 yes to this option, support will be included for the built-in I2C
843 interface on the Qualcomm Technologies Inc.'s SoCs.
845 This driver can also be built as a module. If so, the module
846 will be called i2c-qcom-geni.
849 tristate "Qualcomm QUP based I2C controller"
852 If you say yes to this option, support will be included for the
853 built-in I2C interface on the Qualcomm SoCs.
855 This driver can also be built as a module. If so, the module
856 will be called i2c-qup.
859 tristate "Renesas RIIC adapter"
860 depends on ARCH_RENESAS || COMPILE_TEST
862 If you say yes to this option, support will be included for the
863 Renesas RIIC I2C interface.
865 This driver can also be built as a module. If so, the module
866 will be called i2c-riic.
869 tristate "Rockchip RK3xxx I2C adapter"
870 depends on OF && COMMON_CLK
872 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
875 This driver can also be built as a module. If so, the module will
878 config HAVE_S3C2410_I2C
881 This will include I2C support for Samsung SoCs. If you want to
882 include I2C support for any machine, kindly select this in the
883 respective Kconfig file.
886 tristate "S3C2410 I2C Driver"
887 depends on HAVE_S3C2410_I2C
889 Say Y here to include support for I2C controller in the
893 tristate "Renesas SH7760 I2C Controller"
894 depends on CPU_SUBTYPE_SH7760
896 This driver supports the 2 I2C interfaces on the Renesas SH7760.
898 This driver can also be built as a module. If so, the module
899 will be called i2c-sh7760.
902 tristate "SuperH Mobile I2C Controller"
903 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
905 If you say yes to this option, support will be included for the
906 built-in I2C interface on the Renesas SH-Mobile processor.
908 This driver can also be built as a module. If so, the module
909 will be called i2c-sh_mobile.
912 tristate "Simtec Generic I2C interface"
915 If you say yes to this option, support will be included for
916 the Simtec Generic I2C interface. This driver is for the
917 simple I2C bus used on newer Simtec products for general
918 I2C, such as DDC on the Simtec BBD2016A.
920 This driver can also be built as a module. If so, the module
921 will be called i2c-simtec.
924 tristate "CSR SiRFprimaII I2C interface"
927 If you say yes to this option, support will be included for the
928 CSR SiRFprimaII I2C interface.
930 This driver can also be built as a module. If so, the module
931 will be called i2c-sirf.
934 bool "Spreadtrum I2C interface"
935 depends on I2C=y && ARCH_SPRD
937 If you say yes to this option, support will be included for the
938 Spreadtrum I2C interface.
941 tristate "STMicroelectronics SSC I2C support"
944 Enable this option to add support for STMicroelectronics SoCs
945 hardware SSC (Synchronous Serial Controller) as an I2C controller.
947 This driver can also be built as module. If so, the module
948 will be called i2c-st.
951 tristate "STMicroelectronics STM32F4 I2C support"
952 depends on ARCH_STM32 || COMPILE_TEST
954 Enable this option to add support for STM32 I2C controller embedded
957 This driver can also be built as module. If so, the module
958 will be called i2c-stm32f4.
961 tristate "STMicroelectronics STM32F7 I2C support"
962 depends on ARCH_STM32 || COMPILE_TEST
965 Enable this option to add support for STM32 I2C controller embedded
968 This driver can also be built as module. If so, the module
969 will be called i2c-stm32f7.
972 tristate "ST Microelectronics DDC I2C interface"
974 default y if MACH_U300
976 If you say yes to this option, support will be included for the
977 I2C interface from ST Microelectronics simply called "DDC I2C"
978 supporting both I2C and DDC, used in e.g. the U300 series
981 This driver can also be built as a module. If so, the module
982 will be called i2c-stu300.
984 config I2C_SUN6I_P2WI
985 tristate "Allwinner sun6i internal P2WI controller"
986 depends on RESET_CONTROLLER
987 depends on MACH_SUN6I || COMPILE_TEST
989 If you say yes to this option, support will be included for the
990 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
992 The P2WI looks like an SMBus controller (which supports only byte
993 accesses), except that it only supports one slave device.
994 This interface is used to connect to specific PMIC devices (like the
998 tristate "Socionext SynQuacer I2C controller"
999 depends on ARCH_SYNQUACER || COMPILE_TEST
1001 Say Y here to include support for the I2C controller used in some
1002 Fujitsu and Socionext SoCs.
1004 This driver can also be built as a module. If so, the module
1005 will be called i2c-synquacer.
1008 tristate "NVIDIA Tegra internal I2C controller"
1009 depends on ARCH_TEGRA
1011 If you say yes to this option, support will be included for the
1012 I2C controller embedded in NVIDIA Tegra SOCs
1014 config I2C_TEGRA_BPMP
1015 tristate "NVIDIA Tegra BPMP I2C controller"
1016 depends on TEGRA_BPMP
1019 If you say yes to this option, support will be included for the I2C
1020 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1022 This I2C driver is a 'virtual' I2C driver. The real driver is part
1023 of the BPMP firmware, and this driver merely communicates with that
1027 tristate "UniPhier FIFO-less I2C controller"
1028 depends on ARCH_UNIPHIER || COMPILE_TEST
1030 If you say yes to this option, support will be included for
1031 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1032 or older UniPhier SoCs.
1034 config I2C_UNIPHIER_F
1035 tristate "UniPhier FIFO-builtin I2C controller"
1036 depends on ARCH_UNIPHIER || COMPILE_TEST
1038 If you say yes to this option, support will be included for
1039 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1040 PH1-Pro5, or newer UniPhier SoCs.
1042 config I2C_VERSATILE
1043 tristate "ARM Versatile/Realview I2C bus support"
1044 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1047 Say yes if you want to support the I2C serial bus on ARMs Versatile
1050 This driver can also be built as a module. If so, the module
1051 will be called i2c-versatile.
1054 tristate "Wondermedia WM8xxx SoC I2C bus support"
1055 depends on ARCH_VT8500
1057 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1060 This driver can also be built as a module. If so, the module will be
1064 tristate "Cavium OCTEON I2C bus support"
1065 depends on CAVIUM_OCTEON_SOC
1067 Say yes if you want to support the I2C serial bus on Cavium
1070 This driver can also be built as a module. If so, the module
1071 will be called i2c-octeon.
1074 tristate "Cavium ThunderX I2C bus support"
1075 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1078 Say yes if you want to support the I2C serial bus on Cavium
1081 This driver can also be built as a module. If so, the module
1082 will be called i2c-thunderx.
1085 tristate "Xilinx I2C Controller"
1086 depends on HAS_IOMEM
1088 If you say yes to this option, support will be included for the
1089 Xilinx I2C controller.
1091 This driver can also be built as a module. If so, the module
1092 will be called xilinx_i2c.
1095 tristate "Netlogic XLR and Sigma Designs I2C support"
1096 depends on CPU_XLR || ARCH_TANGO
1098 This driver enables support for the on-chip I2C interface of
1099 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1101 This driver can also be built as a module. If so, the module
1102 will be called i2c-xlr.
1105 tristate "XLP9XX I2C support"
1106 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1108 This driver enables support for the on-chip I2C interface of
1109 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1111 This driver can also be built as a module. If so, the module will
1112 be called i2c-xlp9xx.
1115 tristate "Renesas R-Car I2C Controller"
1116 depends on ARCH_RENESAS || COMPILE_TEST
1119 If you say yes to this option, support will be included for the
1120 R-Car I2C controller.
1122 This driver can also be built as a module. If so, the module
1123 will be called i2c-rcar.
1125 comment "External I2C/SMBus adapter drivers"
1127 config I2C_DIOLAN_U2C
1128 tristate "Diolan U2C-12 USB adapter"
1131 If you say yes to this option, support will be included for Diolan
1132 U2C-12, a USB to I2C interface.
1134 This driver can also be built as a module. If so, the module
1135 will be called i2c-diolan-u2c.
1138 tristate "Diolan DLN-2 USB I2C adapter"
1141 If you say yes to this option, support will be included for Diolan
1142 DLN2, a USB to I2C interface.
1144 This driver can also be built as a module. If so, the module
1145 will be called i2c-dln2.
1148 tristate "Parallel port adapter"
1153 This supports parallel port I2C adapters such as the ones made by
1154 Philips or Velleman, Analog Devices evaluation boards, and more.
1155 Basically any adapter using the parallel port as an I2C bus with
1156 no extra chipset is supported by this driver, or could be.
1158 This driver is a replacement for (and was inspired by) an older
1159 driver named i2c-philips-par. The new driver supports more devices,
1160 and makes it easier to add support for new devices.
1162 An adapter type parameter is now mandatory. Please read the file
1163 Documentation/i2c/busses/i2c-parport for details.
1165 Another driver exists, named i2c-parport-light, which doesn't depend
1166 on the parport driver. This is meant for embedded systems. Don't say
1167 Y here if you intend to say Y or M there.
1169 This support is also available as a module. If so, the module
1170 will be called i2c-parport.
1172 config I2C_PARPORT_LIGHT
1173 tristate "Parallel port adapter (light)"
1177 This supports parallel port I2C adapters such as the ones made by
1178 Philips or Velleman, Analog Devices evaluation boards, and more.
1179 Basically any adapter using the parallel port as an I2C bus with
1180 no extra chipset is supported by this driver, or could be.
1182 This driver is a light version of i2c-parport. It doesn't depend
1183 on the parport driver, and uses direct I/O access instead. This
1184 might be preferred on embedded systems where wasting memory for
1185 the clean but heavy parport handling is not an option. The
1186 drawback is a reduced portability and the impossibility to
1187 daisy-chain other parallel port devices.
1189 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1190 both is possible but both modules should not be loaded at the same
1193 This support is also available as a module. If so, the module
1194 will be called i2c-parport-light.
1196 config I2C_ROBOTFUZZ_OSIF
1197 tristate "RobotFuzz Open Source InterFace USB adapter"
1200 If you say yes to this option, support will be included for the
1201 RobotFuzz Open Source InterFace USB to I2C interface.
1203 This driver can also be built as a module. If so, the module
1204 will be called i2c-osif.
1207 tristate "TAOS evaluation module"
1210 select SERIO_SERPORT
1213 This supports TAOS evaluation modules on serial port. In order to
1214 use this driver, you will need the inputattach tool, which is part
1215 of the input-utils package.
1219 This support is also available as a module. If so, the module
1220 will be called i2c-taos-evm.
1223 tristate "Tiny-USB adapter"
1226 If you say yes to this option, support will be included for the
1227 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1228 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1230 This driver can also be built as a module. If so, the module
1231 will be called i2c-tiny-usb.
1233 config I2C_VIPERBOARD
1234 tristate "Viperboard I2C master support"
1235 depends on MFD_VIPERBOARD && USB
1237 Say yes here to access the I2C part of the Nano River
1238 Technologies Viperboard as I2C master.
1239 See viperboard API specification and Nano
1240 River Tech's viperboard.h for detailed meaning
1241 of the module parameters.
1243 comment "Other I2C/SMBus bus drivers"
1246 tristate "Acorn IOC/IOMD I2C bus support"
1247 depends on ARCH_ACORN
1251 Say yes if you want to support the I2C bus on Acorn platforms.
1253 If you don't know, say Y.
1256 tristate "Elektor ISA card"
1257 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1260 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1263 This support is also available as a module. If so, the module
1264 will be called i2c-elektor.
1267 tristate "Mellanox I2C driver"
1270 This exposes the Mellanox platform I2C busses to the linux I2C layer
1271 for X86 based systems.
1272 Controller is implemented as CPLD logic.
1274 This driver can also be built as a module. If so, the module will be
1275 called as i2c-mlxcpld.
1278 tristate "PCA9564/PCA9665 on an ISA bus"
1283 This driver supports ISA boards using the Philips PCA9564/PCA9665
1284 parallel bus to I2C bus controller.
1286 This driver can also be built as a module. If so, the module
1287 will be called i2c-pca-isa.
1289 This device is almost undetectable and using this driver on a
1290 system which doesn't have this device will result in long
1291 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1292 time). If unsure, say N.
1295 tristate "SiByte SMBus interface"
1296 depends on SIBYTE_SB1xxx_SOC
1298 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1300 config I2C_CROS_EC_TUNNEL
1301 tristate "ChromeOS EC tunnel I2C bus"
1302 depends on MFD_CROS_EC
1304 If you say yes here you get an I2C bus that will tunnel i2c commands
1305 through to the other side of the ChromeOS EC to the i2c bus
1306 connected there. This will work whatever the interface used to
1307 talk to the EC (SPI, I2C or LPC).
1309 config I2C_XGENE_SLIMPRO
1310 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1311 depends on ARCH_XGENE && MAILBOX
1313 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1314 co-processor. The I2C device access the I2C bus via the X-Gene
1315 to SLIMpro (On chip coprocessor) mailbox mechanism.
1319 tristate "Geode ACCESS.bus support"
1320 depends on X86_32 && PCI
1322 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1323 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1325 If you don't know what to do here, say N.
1327 This support is also available as a module. If so, the module
1328 will be called scx200_acb.
1331 tristate "IBM OPAL I2C driver"
1332 depends on PPC_POWERNV
1335 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1336 the driver is based on the OPAL interfaces.
1338 This driver can also be built as a module. If so, the module will be
1342 tristate "ZTE ZX2967 I2C support"
1346 Selecting this option will add ZX2967 I2C driver.
1347 This driver can also be built as a module. If so, the module will be
1351 tristate "FSI I2C driver"
1354 Driver for FSI bus attached I2C masters. These are I2C masters that
1355 are connected to the system over an FSI bus, instead of the more
1356 common PCI or MMIO interface.
1358 This driver can also be built as a module. If so, the module will be