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.
391 tristate "Au1550/Au1200/Au1300 SMBus interface"
392 depends on MIPS_ALCHEMY
394 If you say yes to this option, support will be included for the
395 Au1550/Au1200/Au1300 SMBus interface.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-au1550.
401 tristate "Axxia I2C controller"
402 depends on ARCH_AXXIA || COMPILE_TEST
405 Say yes if you want to support the I2C bus on Axxia platforms.
407 Please note that this controller is limited to transfers of maximum
408 255 bytes in length. Any attempt to to a larger transfer will return
412 tristate "Broadcom BCM2835 I2C controller"
413 depends on ARCH_BCM2835
415 If you say yes to this option, support will be included for the
416 BCM2835 I2C controller.
418 If you don't know what to do here, say N.
420 This support is also available as a module. If so, the module
421 will be called i2c-bcm2835.
424 tristate "Broadcom iProc I2C controller"
425 depends on ARCH_BCM_IPROC || COMPILE_TEST
426 default ARCH_BCM_IPROC
428 If you say yes to this option, support will be included for the
429 Broadcom iProc I2C controller.
431 If you don't know what to do here, say N.
434 tristate "BCM Kona I2C adapter"
435 depends on ARCH_BCM_MOBILE
438 If you say yes to this option, support will be included for the
439 I2C interface on the Broadcom Kona family of processors.
441 If you do not need KONA I2C interface, say N.
444 tristate "BRCM Settop/DSL I2C controller"
445 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
449 If you say yes to this option, support will be included for the
450 I2C interface on the Broadcom Settop/DSL SoCs.
452 If you do not need I2C interface, say N.
455 tristate "Cadence I2C Controller"
456 depends on ARCH_ZYNQ || ARM64 || XTENSA
458 Say yes here to select Cadence I2C Host Controller. This controller is
459 e.g. used by Xilinx Zynq.
462 tristate "CBUS I2C driver"
463 depends on GPIOLIB || COMPILE_TEST
465 Support for CBUS access using I2C API. Mostly relevant for Nokia
466 Internet Tablets (770, N800 and N810).
468 This driver can also be built as a module. If so, the module
469 will be called i2c-cbus-gpio.
472 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
473 depends on CPM1 || CPM2
475 This supports the use of the I2C interface on Freescale
476 processors with CPM1 or CPM2.
478 This driver can also be built as a module. If so, the module
479 will be called i2c-cpm.
482 tristate "DaVinci I2C driver"
483 depends on ARCH_DAVINCI || ARCH_KEYSTONE
485 Support for TI DaVinci I2C controller driver.
487 This driver can also be built as a module. If so, the module
488 will be called i2c-davinci.
490 Please note that this driver might be needed to bring up other
491 devices such as DaVinci NIC.
492 For details please see http://www.ti.com/davinci
494 config I2C_DESIGNWARE_CORE
497 config I2C_DESIGNWARE_PLATFORM
498 tristate "Synopsys DesignWare Platform"
499 select I2C_DESIGNWARE_CORE
500 depends on (ACPI && COMMON_CLK) || !ACPI
502 If you say yes to this option, support will be included for the
503 Synopsys DesignWare I2C adapter.
505 This driver can also be built as a module. If so, the module
506 will be called i2c-designware-platform.
508 config I2C_DESIGNWARE_SLAVE
509 bool "Synopsys DesignWare Slave"
511 depends on I2C_DESIGNWARE_PLATFORM
513 If you say yes to this option, support will be included for the
514 Synopsys DesignWare I2C slave adapter.
516 This is not a standalone module, this module compiles together with
519 config I2C_DESIGNWARE_PCI
520 tristate "Synopsys DesignWare PCI"
522 select I2C_DESIGNWARE_CORE
524 If you say yes to this option, support will be included for the
525 Synopsys DesignWare I2C adapter. Only master mode is supported.
527 This driver can also be built as a module. If so, the module
528 will be called i2c-designware-pci.
530 config I2C_DESIGNWARE_BAYTRAIL
531 bool "Intel Baytrail I2C semaphore support"
533 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
534 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
536 This driver enables managed host access to the PMIC I2C bus on select
537 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
538 the host to request uninterrupted access to the PMIC's I2C bus from
539 the platform firmware controlling it. You should say Y if running on
540 a BayTrail system using the AXP288.
543 tristate "Conexant Digicolor I2C driver"
544 depends on ARCH_DIGICOLOR
546 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
548 This driver can also be built as a module. If so, the module
549 will be called i2c-digicolor.
552 tristate "EFM32 I2C controller"
553 depends on ARCH_EFM32 || COMPILE_TEST
555 This driver supports the i2c block found in Energy Micro's EFM32
559 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
560 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
562 This driver is for PCH(Platform controller Hub) I2C of EG20T which
563 is an IOH(Input/Output Hub) for x86 embedded processor.
564 This driver can access PCH I2C bus device.
566 This driver also can be used for LAPIS Semiconductor IOH(Input/
567 Output Hub), ML7213, ML7223 and ML7831.
568 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
569 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
570 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
571 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
574 tristate "EMMA Mobile series I2C adapter"
578 If you say yes to this option, support will be included for the
579 I2C interface on the Renesas Electronics EM/EV family of processors.
582 tristate "Exynos5 high-speed I2C driver"
583 depends on ARCH_EXYNOS && OF
586 High-speed I2C controller on Exynos5 based Samsung SoCs.
589 tristate "GPIO-based bitbanging I2C"
590 depends on GPIOLIB || COMPILE_TEST
593 This is a very simple bitbanging I2C driver utilizing the
594 arch-neutral GPIO API to control the SCL and SDA lines.
596 config I2C_GPIO_FAULT_INJECTOR
597 bool "GPIO-based fault injector"
600 This adds some functionality to the i2c-gpio driver which can inject
601 faults to an I2C bus, so another bus master can be stress-tested.
602 This is for debugging. If unsure, say 'no'.
604 config I2C_HIGHLANDER
605 tristate "Highlander FPGA SMBus interface"
606 depends on SH_HIGHLANDER
608 If you say yes to this option, support will be included for
609 the SMBus interface located in the FPGA on various Highlander
610 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
611 FPGAs. This is wholly unrelated to the SoC I2C.
613 This driver can also be built as a module. If so, the module
614 will be called i2c-highlander.
617 tristate "IBM PPC 4xx on-chip I2C interface"
620 Say Y here if you want to use IIC peripheral found on
621 embedded IBM PPC 4xx based systems.
623 This driver can also be built as a module. If so, the module
624 will be called i2c-ibm_iic.
627 tristate "Imagination Technologies I2C SCB Controller"
628 depends on MIPS || COMPILE_TEST
630 Say Y here if you want to use the IMG I2C SCB controller,
631 available on the TZ1090 and other IMG SoCs.
633 This driver can also be built as a module. If so, the module
634 will be called i2c-img-scb.
637 tristate "IMX I2C interface"
638 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
640 Say Y here if you want to use the IIC bus controller on
641 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
643 This driver can also be built as a module. If so, the module
644 will be called i2c-imx.
647 tristate "IMX Low Power I2C interface"
648 depends on ARCH_MXC || COMPILE_TEST
650 Say Y here if you want to use the Low Power IIC bus controller
651 on the Freescale i.MX processors.
653 This driver can also be built as a module. If so, the module
654 will be called i2c-imx-lpi2c.
657 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
658 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
660 Say Y here if you want to use the IIC bus controller on
661 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
663 This driver can also be built as a module. If so, the module
664 will be called i2c-iop3xx.
667 tristate "JZ4780 I2C controller interface support"
668 depends on MACH_JZ4780 || COMPILE_TEST
670 If you say yes to this option, support will be included for the
671 Ingenic JZ4780 I2C controller.
673 If you don't know what to do here, say N.
676 tristate "Kontron COM I2C Controller"
677 depends on MFD_KEMPLD
679 This enables support for the I2C bus interface on some Kontron ETX
680 and COMexpress (ETXexpress) modules.
682 This driver can also be built as a module. If so, the module
683 will be called i2c-kempld.
686 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
687 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
689 This driver supports the I2C interface found several NXP
690 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
692 This driver can also be built as a module. If so, the module
693 will be called i2c-lpc2k.
696 tristate "Amlogic Meson I2C controller"
697 depends on ARCH_MESON || COMPILE_TEST
699 If you say yes to this option, support will be included for the
700 I2C interface on the Amlogic Meson family of SoCs.
703 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
706 If you say yes to this option, support will be included for the
707 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
708 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
710 This driver can also be built as a module. If so, the module
711 will be called i2c-mpc.
714 tristate "MediaTek I2C adapter"
715 depends on ARCH_MEDIATEK || COMPILE_TEST
717 This selects the MediaTek(R) Integrated Inter Circuit bus driver
718 for MT65xx and MT81xx.
719 If you want to use MediaTek(R) I2C interface, say Y or M here.
723 tristate "Marvell mv64xxx I2C Controller"
724 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
726 If you say yes to this option, support will be included for the
727 built-in I2C interface on the Marvell 64xxx line of host bridges.
728 This driver is also used for Allwinner SoCs I2C controllers.
730 This driver can also be built as a module. If so, the module
731 will be called i2c-mv64xxx.
734 tristate "Freescale i.MX28 I2C interface"
738 Say Y here if you want to use the I2C bus controller on
739 the Freescale i.MX28 processors.
741 This driver can also be built as a module. If so, the module
742 will be called i2c-mxs.
745 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
748 If you say yes to this option, support will be included for the
749 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
750 as well as the STA2X11 PCIe I/O HUB.
753 tristate "OpenCores I2C Controller"
755 If you say yes to this option, support will be included for the
756 OpenCores I2C controller. For details see
757 http://www.opencores.org/projects.cgi/web/i2c/overview
759 This driver can also be built as a module. If so, the module
760 will be called i2c-ocores.
763 tristate "OMAP I2C adapter"
764 depends on ARCH_OMAP || ARCH_K3
765 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
767 If you say yes to this option, support will be included for the
768 I2C interface on the Texas Instruments OMAP1/2 family of processors.
769 Like OMAP1510/1610/1710/5912 and OMAP242x.
770 For details see http://www.ti.com/omap.
773 tristate "Actions Semiconductor Owl I2C Controller"
774 depends on ARCH_ACTIONS || COMPILE_TEST
776 Say Y here if you want to use the I2C bus controller on
777 the Actions Semiconductor Owl SoC's.
780 tristate "PA Semi SMBus interface"
781 depends on PPC_PASEMI && PCI
783 Supports the PA Semi PWRficient on-chip SMBus interfaces.
785 config I2C_PCA_PLATFORM
786 tristate "PCA9564/PCA9665 as platform device"
790 This driver supports a memory mapped Philips PCA9564/PCA9665
791 parallel bus to I2C bus controller.
793 This driver can also be built as a module. If so, the module
794 will be called i2c-pca-platform.
797 tristate "PMC MSP I2C TWI Controller"
800 This driver supports the PMC TWI controller on MSP devices.
802 This driver can also be built as module. If so, the module
803 will be called i2c-pmcmsp.
806 tristate "I2C bus support for Philips PNX and NXP LPC targets"
807 depends on ARCH_LPC32XX
809 This driver supports the Philips IP3204 I2C IP block master and/or
812 This driver can also be built as a module. If so, the module
813 will be called i2c-pnx.
816 tristate "PKUnity v3 I2C bus support"
817 depends on UNICORE32 && ARCH_PUV3
820 This driver supports the I2C IP inside the PKUnity-v3 SoC.
821 This I2C bus controller is under AMBA/AXI bus.
823 This driver can also be built as a module. If so, the module
824 will be called i2c-puv3.
827 tristate "Intel PXA2XX I2C adapter"
828 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
830 If you have devices in the PXA I2C bus, say yes to this option.
831 This driver can also be built as a module. If so, the module
832 will be called i2c-pxa.
835 def_bool I2C_PXA && X86_32 && PCI && OF
838 bool "Intel PXA2XX I2C Slave comms support"
839 depends on I2C_PXA && !X86_32
841 Support I2C slave mode communications on the PXA I2C bus. This
842 is necessary for systems where the PXA may be a target on the
846 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
847 depends on ARCH_QCOM || COMPILE_TEST
848 depends on QCOM_GENI_SE
850 This driver supports GENI serial engine based I2C controller in
851 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
852 yes to this option, support will be included for the built-in I2C
853 interface on the Qualcomm Technologies Inc.'s SoCs.
855 This driver can also be built as a module. If so, the module
856 will be called i2c-qcom-geni.
859 tristate "Qualcomm QUP based I2C controller"
862 If you say yes to this option, support will be included for the
863 built-in I2C interface on the Qualcomm SoCs.
865 This driver can also be built as a module. If so, the module
866 will be called i2c-qup.
869 tristate "Renesas RIIC adapter"
870 depends on ARCH_RENESAS || COMPILE_TEST
872 If you say yes to this option, support will be included for the
873 Renesas RIIC I2C interface.
875 This driver can also be built as a module. If so, the module
876 will be called i2c-riic.
879 tristate "Rockchip RK3xxx I2C adapter"
880 depends on OF && COMMON_CLK
882 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
885 This driver can also be built as a module. If so, the module will
888 config HAVE_S3C2410_I2C
891 This will include I2C support for Samsung SoCs. If you want to
892 include I2C support for any machine, kindly select this in the
893 respective Kconfig file.
896 tristate "S3C2410 I2C Driver"
897 depends on HAVE_S3C2410_I2C
899 Say Y here to include support for I2C controller in the
903 tristate "Renesas SH7760 I2C Controller"
904 depends on CPU_SUBTYPE_SH7760
906 This driver supports the 2 I2C interfaces on the Renesas SH7760.
908 This driver can also be built as a module. If so, the module
909 will be called i2c-sh7760.
912 tristate "SuperH Mobile I2C Controller"
913 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
915 If you say yes to this option, support will be included for the
916 built-in I2C interface on the Renesas SH-Mobile processor.
918 This driver can also be built as a module. If so, the module
919 will be called i2c-sh_mobile.
922 tristate "Simtec Generic I2C interface"
925 If you say yes to this option, support will be included for
926 the Simtec Generic I2C interface. This driver is for the
927 simple I2C bus used on newer Simtec products for general
928 I2C, such as DDC on the Simtec BBD2016A.
930 This driver can also be built as a module. If so, the module
931 will be called i2c-simtec.
934 tristate "CSR SiRFprimaII I2C interface"
937 If you say yes to this option, support will be included for the
938 CSR SiRFprimaII I2C interface.
940 This driver can also be built as a module. If so, the module
941 will be called i2c-sirf.
944 bool "Spreadtrum I2C interface"
945 depends on I2C=y && ARCH_SPRD
947 If you say yes to this option, support will be included for the
948 Spreadtrum I2C interface.
951 tristate "STMicroelectronics SSC I2C support"
954 Enable this option to add support for STMicroelectronics SoCs
955 hardware SSC (Synchronous Serial Controller) as an I2C controller.
957 This driver can also be built as module. If so, the module
958 will be called i2c-st.
961 tristate "STMicroelectronics STM32F4 I2C support"
962 depends on ARCH_STM32 || COMPILE_TEST
964 Enable this option to add support for STM32 I2C controller embedded
967 This driver can also be built as module. If so, the module
968 will be called i2c-stm32f4.
971 tristate "STMicroelectronics STM32F7 I2C support"
972 depends on ARCH_STM32 || COMPILE_TEST
975 Enable this option to add support for STM32 I2C controller embedded
978 This driver can also be built as module. If so, the module
979 will be called i2c-stm32f7.
982 tristate "ST Microelectronics DDC I2C interface"
984 default y if MACH_U300
986 If you say yes to this option, support will be included for the
987 I2C interface from ST Microelectronics simply called "DDC I2C"
988 supporting both I2C and DDC, used in e.g. the U300 series
991 This driver can also be built as a module. If so, the module
992 will be called i2c-stu300.
994 config I2C_SUN6I_P2WI
995 tristate "Allwinner sun6i internal P2WI controller"
996 depends on RESET_CONTROLLER
997 depends on MACH_SUN6I || COMPILE_TEST
999 If you say yes to this option, support will be included for the
1000 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
1002 The P2WI looks like an SMBus controller (which supports only byte
1003 accesses), except that it only supports one slave device.
1004 This interface is used to connect to specific PMIC devices (like the
1007 config I2C_SYNQUACER
1008 tristate "Socionext SynQuacer I2C controller"
1009 depends on ARCH_SYNQUACER || COMPILE_TEST
1011 Say Y here to include support for the I2C controller used in some
1012 Fujitsu and Socionext SoCs.
1014 This driver can also be built as a module. If so, the module
1015 will be called i2c-synquacer.
1018 tristate "NVIDIA Tegra internal I2C controller"
1019 depends on ARCH_TEGRA
1021 If you say yes to this option, support will be included for the
1022 I2C controller embedded in NVIDIA Tegra SOCs
1024 config I2C_TEGRA_BPMP
1025 tristate "NVIDIA Tegra BPMP I2C controller"
1026 depends on TEGRA_BPMP
1029 If you say yes to this option, support will be included for the I2C
1030 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1032 This I2C driver is a 'virtual' I2C driver. The real driver is part
1033 of the BPMP firmware, and this driver merely communicates with that
1037 tristate "UniPhier FIFO-less I2C controller"
1038 depends on ARCH_UNIPHIER || COMPILE_TEST
1040 If you say yes to this option, support will be included for
1041 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1042 or older UniPhier SoCs.
1044 config I2C_UNIPHIER_F
1045 tristate "UniPhier FIFO-builtin I2C controller"
1046 depends on ARCH_UNIPHIER || COMPILE_TEST
1048 If you say yes to this option, support will be included for
1049 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1050 PH1-Pro5, or newer UniPhier SoCs.
1052 config I2C_VERSATILE
1053 tristate "ARM Versatile/Realview I2C bus support"
1054 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1057 Say yes if you want to support the I2C serial bus on ARMs Versatile
1060 This driver can also be built as a module. If so, the module
1061 will be called i2c-versatile.
1064 tristate "Wondermedia WM8xxx SoC I2C bus support"
1065 depends on ARCH_VT8500
1067 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1070 This driver can also be built as a module. If so, the module will be
1074 tristate "Cavium OCTEON I2C bus support"
1075 depends on CAVIUM_OCTEON_SOC
1077 Say yes if you want to support the I2C serial bus on Cavium
1080 This driver can also be built as a module. If so, the module
1081 will be called i2c-octeon.
1084 tristate "Cavium ThunderX I2C bus support"
1085 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1088 Say yes if you want to support the I2C serial bus on Cavium
1091 This driver can also be built as a module. If so, the module
1092 will be called i2c-thunderx.
1095 tristate "Xilinx I2C Controller"
1096 depends on HAS_IOMEM
1098 If you say yes to this option, support will be included for the
1099 Xilinx I2C controller.
1101 This driver can also be built as a module. If so, the module
1102 will be called xilinx_i2c.
1105 tristate "Netlogic XLR and Sigma Designs I2C support"
1106 depends on CPU_XLR || ARCH_TANGO
1108 This driver enables support for the on-chip I2C interface of
1109 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1111 This driver can also be built as a module. If so, the module
1112 will be called i2c-xlr.
1115 tristate "XLP9XX I2C support"
1116 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1118 This driver enables support for the on-chip I2C interface of
1119 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1121 This driver can also be built as a module. If so, the module will
1122 be called i2c-xlp9xx.
1125 tristate "Renesas R-Car I2C Controller"
1126 depends on ARCH_RENESAS || COMPILE_TEST
1129 If you say yes to this option, support will be included for the
1130 R-Car I2C controller.
1132 This driver can also be built as a module. If so, the module
1133 will be called i2c-rcar.
1135 comment "External I2C/SMBus adapter drivers"
1137 config I2C_DIOLAN_U2C
1138 tristate "Diolan U2C-12 USB adapter"
1141 If you say yes to this option, support will be included for Diolan
1142 U2C-12, a USB to I2C interface.
1144 This driver can also be built as a module. If so, the module
1145 will be called i2c-diolan-u2c.
1148 tristate "Diolan DLN-2 USB I2C adapter"
1151 If you say yes to this option, support will be included for Diolan
1152 DLN2, a USB to I2C interface.
1154 This driver can also be built as a module. If so, the module
1155 will be called i2c-dln2.
1158 tristate "Parallel port adapter"
1163 This supports parallel port I2C adapters such as the ones made by
1164 Philips or Velleman, Analog Devices evaluation boards, and more.
1165 Basically any adapter using the parallel port as an I2C bus with
1166 no extra chipset is supported by this driver, or could be.
1168 This driver is a replacement for (and was inspired by) an older
1169 driver named i2c-philips-par. The new driver supports more devices,
1170 and makes it easier to add support for new devices.
1172 An adapter type parameter is now mandatory. Please read the file
1173 Documentation/i2c/busses/i2c-parport for details.
1175 Another driver exists, named i2c-parport-light, which doesn't depend
1176 on the parport driver. This is meant for embedded systems. Don't say
1177 Y here if you intend to say Y or M there.
1179 This support is also available as a module. If so, the module
1180 will be called i2c-parport.
1182 config I2C_PARPORT_LIGHT
1183 tristate "Parallel port adapter (light)"
1187 This supports parallel port I2C adapters such as the ones made by
1188 Philips or Velleman, Analog Devices evaluation boards, and more.
1189 Basically any adapter using the parallel port as an I2C bus with
1190 no extra chipset is supported by this driver, or could be.
1192 This driver is a light version of i2c-parport. It doesn't depend
1193 on the parport driver, and uses direct I/O access instead. This
1194 might be preferred on embedded systems where wasting memory for
1195 the clean but heavy parport handling is not an option. The
1196 drawback is a reduced portability and the impossibility to
1197 daisy-chain other parallel port devices.
1199 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1200 both is possible but both modules should not be loaded at the same
1203 This support is also available as a module. If so, the module
1204 will be called i2c-parport-light.
1206 config I2C_ROBOTFUZZ_OSIF
1207 tristate "RobotFuzz Open Source InterFace USB adapter"
1210 If you say yes to this option, support will be included for the
1211 RobotFuzz Open Source InterFace USB to I2C interface.
1213 This driver can also be built as a module. If so, the module
1214 will be called i2c-osif.
1217 tristate "TAOS evaluation module"
1220 select SERIO_SERPORT
1223 This supports TAOS evaluation modules on serial port. In order to
1224 use this driver, you will need the inputattach tool, which is part
1225 of the input-utils package.
1229 This support is also available as a module. If so, the module
1230 will be called i2c-taos-evm.
1233 tristate "Tiny-USB adapter"
1236 If you say yes to this option, support will be included for the
1237 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1238 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1240 This driver can also be built as a module. If so, the module
1241 will be called i2c-tiny-usb.
1243 config I2C_VIPERBOARD
1244 tristate "Viperboard I2C master support"
1245 depends on MFD_VIPERBOARD && USB
1247 Say yes here to access the I2C part of the Nano River
1248 Technologies Viperboard as I2C master.
1249 See viperboard API specification and Nano
1250 River Tech's viperboard.h for detailed meaning
1251 of the module parameters.
1253 comment "Other I2C/SMBus bus drivers"
1256 tristate "Acorn IOC/IOMD I2C bus support"
1257 depends on ARCH_ACORN
1261 Say yes if you want to support the I2C bus on Acorn platforms.
1263 If you don't know, say Y.
1266 tristate "Elektor ISA card"
1267 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1270 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1273 This support is also available as a module. If so, the module
1274 will be called i2c-elektor.
1277 tristate "Mellanox I2C driver"
1280 This exposes the Mellanox platform I2C busses to the linux I2C layer
1281 for X86 based systems.
1282 Controller is implemented as CPLD logic.
1284 This driver can also be built as a module. If so, the module will be
1285 called as i2c-mlxcpld.
1288 tristate "PCA9564/PCA9665 on an ISA bus"
1293 This driver supports ISA boards using the Philips PCA9564/PCA9665
1294 parallel bus to I2C bus controller.
1296 This driver can also be built as a module. If so, the module
1297 will be called i2c-pca-isa.
1299 This device is almost undetectable and using this driver on a
1300 system which doesn't have this device will result in long
1301 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1302 time). If unsure, say N.
1305 tristate "SiByte SMBus interface"
1306 depends on SIBYTE_SB1xxx_SOC
1308 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1310 config I2C_CROS_EC_TUNNEL
1311 tristate "ChromeOS EC tunnel I2C bus"
1312 depends on MFD_CROS_EC
1314 If you say yes here you get an I2C bus that will tunnel i2c commands
1315 through to the other side of the ChromeOS EC to the i2c bus
1316 connected there. This will work whatever the interface used to
1317 talk to the EC (SPI, I2C or LPC).
1319 config I2C_XGENE_SLIMPRO
1320 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1321 depends on ARCH_XGENE && MAILBOX
1323 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1324 co-processor. The I2C device access the I2C bus via the X-Gene
1325 to SLIMpro (On chip coprocessor) mailbox mechanism.
1329 tristate "Geode ACCESS.bus support"
1330 depends on X86_32 && PCI
1332 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1333 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1335 If you don't know what to do here, say N.
1337 This support is also available as a module. If so, the module
1338 will be called scx200_acb.
1341 tristate "IBM OPAL I2C driver"
1342 depends on PPC_POWERNV
1345 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1346 the driver is based on the OPAL interfaces.
1348 This driver can also be built as a module. If so, the module will be
1352 tristate "ZTE ZX2967 I2C support"
1356 Selecting this option will add ZX2967 I2C driver.
1357 This driver can also be built as a module. If so, the module will be
1361 tristate "FSI I2C driver"
1364 Driver for FSI bus attached I2C masters. These are I2C masters that
1365 are connected to the system over an FSI bus, instead of the more
1366 common PCI or MMIO interface.
1368 This driver can also be built as a module. If so, the module will be