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)
124 Wildcat Point-LP (PCH)
127 Sunrise Point-H (PCH)
128 Sunrise Point-LP (PCH)
138 This driver can also be built as a module. If so, the module
139 will be called i2c-i801.
142 tristate "Intel SCH SMBus 1.0"
146 Say Y here if you want to use SMBus controller on the Intel SCH
149 This driver can also be built as a module. If so, the module
150 will be called i2c-isch.
153 tristate "Intel iSMT SMBus Controller"
154 depends on PCI && X86
156 If you say yes to this option, support will be included for the Intel
157 iSMT SMBus host controller interface.
159 This driver can also be built as a module. If so, the module will be
163 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
166 If you say yes to this option, support will be included for the Intel
167 PIIX4 family of mainboard I2C interfaces. Specifically, the following
168 versions of the chipset are supported (note that Serverworks is part
188 Some AMD chipsets contain two PIIX4-compatible SMBus
189 controllers. This driver will attempt to use both controllers
190 on the SB700/SP5100, if they have been initialized by the BIOS.
192 This driver can also be built as a module. If so, the module
193 will be called i2c-piix4.
196 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
197 depends on INTEL_SOC_PMIC_CHTWC
199 If you say yes to this option, support will be included for the
200 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
201 found on some Intel Cherry Trail systems.
203 Note this controller is hooked up to a TI bq24292i charger-IC,
204 combined with a FUSB302 Type-C port-controller as such it is advised
205 to also select CONFIG_TYPEC_FUSB302=m.
208 tristate "Nvidia nForce2, nForce3 and nForce4"
211 If you say yes to this option, support will be included for the Nvidia
212 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
214 This driver can also be built as a module. If so, the module
215 will be called i2c-nforce2.
217 config I2C_NFORCE2_S4985
218 tristate "SMBus multiplexing on the Tyan S4985"
219 depends on I2C_NFORCE2 && X86
221 Enabling this option will add specific SMBus support for the Tyan
222 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
223 over 4 different channels, where the various memory module EEPROMs
224 live. Saying yes here will give you access to these in addition
227 This driver can also be built as a module. If so, the module
228 will be called i2c-nforce2-s4985.
234 If you say yes to this option, support will be included for the
235 SiS5595 SMBus (a subset of I2C) interface.
237 This driver can also be built as a module. If so, the module
238 will be called i2c-sis5595.
241 tristate "SiS 630/730/964"
244 If you say yes to this option, support will be included for the
245 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
247 This driver can also be built as a module. If so, the module
248 will be called i2c-sis630.
254 If you say yes to this option, support will be included for the SiS
255 96x SMBus (a subset of I2C) interfaces. Specifically, the following
256 chipsets are supported:
265 This driver can also be built as a module. If so, the module
266 will be called i2c-sis96x.
269 tristate "VIA VT82C586B"
273 If you say yes to this option, support will be included for the VIA
274 82C586B I2C interface
276 This driver can also be built as a module. If so, the module
277 will be called i2c-via.
280 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
283 If you say yes to this option, support will be included for the VIA
284 VT82C596 and later SMBus interface. Specifically, the following
285 chipsets are supported:
298 This driver can also be built as a module. If so, the module
299 will be called i2c-viapro.
303 comment "ACPI drivers"
306 tristate "SMBus Control Method Interface"
308 This driver supports the SMBus Control Method Interface. It needs the
309 BIOS to declare ACPI control methods as described in the SMBus Control
310 Method Interface specification.
312 To compile this driver as a module, choose M here:
313 the module will be called i2c-scmi.
317 comment "Mac SMBus host controller drivers"
318 depends on PPC_CHRP || PPC_PMAC
321 tristate "CHRP Apple Hydra Mac I/O I2C interface"
322 depends on PCI && PPC_CHRP
325 This supports the use of the I2C interface in the Apple Hydra Mac
326 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
329 This support is also available as a module. If so, the module
330 will be called i2c-hydra.
333 tristate "Powermac I2C interface"
337 This exposes the various PowerMac i2c interfaces to the linux i2c
338 layer and to userland. It is used by various drivers on the PowerMac
339 platform, and should generally be enabled.
341 This support is also available as a module. If so, the module
342 will be called i2c-powermac.
344 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
347 tristate "Altera Soft IP I2C"
348 depends on (ARCH_SOCFPGA || NIOS2) && OF
350 If you say yes to this option, support will be included for the
351 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
353 This driver can also be built as a module. If so, the module
354 will be called i2c-altera.
357 tristate "Aspeed I2C Controller"
358 depends on ARCH_ASPEED || COMPILE_TEST
360 If you say yes to this option, support will be included for the
361 Aspeed I2C controller.
363 This driver can also be built as a module. If so, the module
364 will be called i2c-aspeed.
367 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
370 This supports the use of the I2C interface on Atmel AT91
373 A serious problem is that there is no documented way to issue
374 repeated START conditions for more than two messages, as needed
375 to support combined I2C messages. Use the i2c-gpio driver
376 unless your system can cope with this limitation.
378 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
379 don't have clock stretching in transmission mode. For that reason,
380 you can encounter underrun issues causing premature stop sendings if
381 the latency to fill the transmission register is too long. If you
382 are facing this situation, use the i2c-gpio driver.
385 tristate "Au1550/Au1200/Au1300 SMBus interface"
386 depends on MIPS_ALCHEMY
388 If you say yes to this option, support will be included for the
389 Au1550/Au1200/Au1300 SMBus interface.
391 This driver can also be built as a module. If so, the module
392 will be called i2c-au1550.
395 tristate "Axxia I2C controller"
396 depends on ARCH_AXXIA || COMPILE_TEST
399 Say yes if you want to support the I2C bus on Axxia platforms.
401 Please note that this controller is limited to transfers of maximum
402 255 bytes in length. Any attempt to to a larger transfer will return
406 tristate "Broadcom BCM2835 I2C controller"
407 depends on ARCH_BCM2835
409 If you say yes to this option, support will be included for the
410 BCM2835 I2C controller.
412 If you don't know what to do here, say N.
414 This support is also available as a module. If so, the module
415 will be called i2c-bcm2835.
418 tristate "Broadcom iProc I2C controller"
419 depends on ARCH_BCM_IPROC || COMPILE_TEST
420 default ARCH_BCM_IPROC
422 If you say yes to this option, support will be included for the
423 Broadcom iProc I2C controller.
425 If you don't know what to do here, say N.
428 tristate "BCM Kona I2C adapter"
429 depends on ARCH_BCM_MOBILE
432 If you say yes to this option, support will be included for the
433 I2C interface on the Broadcom Kona family of processors.
435 If you do not need KONA I2C interface, say N.
438 tristate "BRCM Settop I2C controller"
439 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
442 If you say yes to this option, support will be included for the
443 I2C interface on the Broadcom Settop SoCs.
445 If you do not need I2C interface, say N.
448 tristate "Cadence I2C Controller"
449 depends on ARCH_ZYNQ || ARM64 || XTENSA
451 Say yes here to select Cadence I2C Host Controller. This controller is
452 e.g. used by Xilinx Zynq.
455 tristate "CBUS I2C driver"
456 depends on GPIOLIB || COMPILE_TEST
458 Support for CBUS access using I2C API. Mostly relevant for Nokia
459 Internet Tablets (770, N800 and N810).
461 This driver can also be built as a module. If so, the module
462 will be called i2c-cbus-gpio.
465 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
466 depends on CPM1 || CPM2
468 This supports the use of the I2C interface on Freescale
469 processors with CPM1 or CPM2.
471 This driver can also be built as a module. If so, the module
472 will be called i2c-cpm.
475 tristate "DaVinci I2C driver"
476 depends on ARCH_DAVINCI || ARCH_KEYSTONE
478 Support for TI DaVinci I2C controller driver.
480 This driver can also be built as a module. If so, the module
481 will be called i2c-davinci.
483 Please note that this driver might be needed to bring up other
484 devices such as DaVinci NIC.
485 For details please see http://www.ti.com/davinci
487 config I2C_DESIGNWARE_CORE
490 config I2C_DESIGNWARE_PLATFORM
491 tristate "Synopsys DesignWare Platform"
492 select I2C_DESIGNWARE_CORE
493 depends on (ACPI && COMMON_CLK) || !ACPI
495 If you say yes to this option, support will be included for the
496 Synopsys DesignWare I2C adapter.
498 This driver can also be built as a module. If so, the module
499 will be called i2c-designware-platform.
501 config I2C_DESIGNWARE_SLAVE
502 bool "Synopsys DesignWare Slave"
504 depends on I2C_DESIGNWARE_PLATFORM
506 If you say yes to this option, support will be included for the
507 Synopsys DesignWare I2C slave adapter.
509 This is not a standalone module, this module compiles together with
512 config I2C_DESIGNWARE_PCI
513 tristate "Synopsys DesignWare PCI"
515 select I2C_DESIGNWARE_CORE
517 If you say yes to this option, support will be included for the
518 Synopsys DesignWare I2C adapter. Only master mode is supported.
520 This driver can also be built as a module. If so, the module
521 will be called i2c-designware-pci.
523 config I2C_DESIGNWARE_BAYTRAIL
524 bool "Intel Baytrail I2C semaphore support"
526 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
527 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
529 This driver enables managed host access to the PMIC I2C bus on select
530 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
531 the host to request uninterrupted access to the PMIC's I2C bus from
532 the platform firmware controlling it. You should say Y if running on
533 a BayTrail system using the AXP288.
536 tristate "Conexant Digicolor I2C driver"
537 depends on ARCH_DIGICOLOR
539 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-digicolor.
545 tristate "EFM32 I2C controller"
546 depends on ARCH_EFM32 || COMPILE_TEST
548 This driver supports the i2c block found in Energy Micro's EFM32
552 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
553 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
555 This driver is for PCH(Platform controller Hub) I2C of EG20T which
556 is an IOH(Input/Output Hub) for x86 embedded processor.
557 This driver can access PCH I2C bus device.
559 This driver also can be used for LAPIS Semiconductor IOH(Input/
560 Output Hub), ML7213, ML7223 and ML7831.
561 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
562 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
563 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
564 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
567 tristate "EMMA Mobile series I2C adapter"
571 If you say yes to this option, support will be included for the
572 I2C interface on the Renesas Electronics EM/EV family of processors.
575 tristate "Exynos5 high-speed I2C driver"
576 depends on ARCH_EXYNOS && OF
579 High-speed I2C controller on Exynos5 based Samsung SoCs.
582 tristate "GPIO-based bitbanging I2C"
583 depends on GPIOLIB || COMPILE_TEST
586 This is a very simple bitbanging I2C driver utilizing the
587 arch-neutral GPIO API to control the SCL and SDA lines.
589 config I2C_GPIO_FAULT_INJECTOR
590 bool "GPIO-based fault injector"
593 This adds some functionality to the i2c-gpio driver which can inject
594 faults to an I2C bus, so another bus master can be stress-tested.
595 This is for debugging. If unsure, say 'no'.
597 config I2C_HIGHLANDER
598 tristate "Highlander FPGA SMBus interface"
599 depends on SH_HIGHLANDER
601 If you say yes to this option, support will be included for
602 the SMBus interface located in the FPGA on various Highlander
603 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
604 FPGAs. This is wholly unrelated to the SoC I2C.
606 This driver can also be built as a module. If so, the module
607 will be called i2c-highlander.
610 tristate "IBM PPC 4xx on-chip I2C interface"
613 Say Y here if you want to use IIC peripheral found on
614 embedded IBM PPC 4xx based systems.
616 This driver can also be built as a module. If so, the module
617 will be called i2c-ibm_iic.
620 tristate "Imagination Technologies I2C SCB Controller"
621 depends on MIPS || COMPILE_TEST
623 Say Y here if you want to use the IMG I2C SCB controller,
624 available on the TZ1090 and other IMG SoCs.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-img-scb.
630 tristate "IMX I2C interface"
631 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
633 Say Y here if you want to use the IIC bus controller on
634 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
636 This driver can also be built as a module. If so, the module
637 will be called i2c-imx.
640 tristate "IMX Low Power I2C interface"
641 depends on ARCH_MXC || COMPILE_TEST
643 Say Y here if you want to use the Low Power IIC bus controller
644 on the Freescale i.MX processors.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-imx-lpi2c.
650 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
651 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
653 Say Y here if you want to use the IIC bus controller on
654 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
656 This driver can also be built as a module. If so, the module
657 will be called i2c-iop3xx.
660 tristate "JZ4780 I2C controller interface support"
661 depends on MACH_JZ4780 || COMPILE_TEST
663 If you say yes to this option, support will be included for the
664 Ingenic JZ4780 I2C controller.
666 If you don't know what to do here, say N.
669 tristate "Kontron COM I2C Controller"
670 depends on MFD_KEMPLD
672 This enables support for the I2C bus interface on some Kontron ETX
673 and COMexpress (ETXexpress) modules.
675 This driver can also be built as a module. If so, the module
676 will be called i2c-kempld.
679 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
680 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
682 This driver supports the I2C interface found several NXP
683 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
685 This driver can also be built as a module. If so, the module
686 will be called i2c-lpc2k.
689 tristate "Amlogic Meson I2C controller"
690 depends on ARCH_MESON || COMPILE_TEST
692 If you say yes to this option, support will be included for the
693 I2C interface on the Amlogic Meson family of SoCs.
696 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
699 If you say yes to this option, support will be included for the
700 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
701 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
703 This driver can also be built as a module. If so, the module
704 will be called i2c-mpc.
707 tristate "MediaTek I2C adapter"
708 depends on ARCH_MEDIATEK || COMPILE_TEST
710 This selects the MediaTek(R) Integrated Inter Circuit bus driver
711 for MT65xx and MT81xx.
712 If you want to use MediaTek(R) I2C interface, say Y or M here.
716 tristate "Marvell mv64xxx I2C Controller"
717 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
719 If you say yes to this option, support will be included for the
720 built-in I2C interface on the Marvell 64xxx line of host bridges.
721 This driver is also used for Allwinner SoCs I2C controllers.
723 This driver can also be built as a module. If so, the module
724 will be called i2c-mv64xxx.
727 tristate "Freescale i.MX28 I2C interface"
731 Say Y here if you want to use the I2C bus controller on
732 the Freescale i.MX28 processors.
734 This driver can also be built as a module. If so, the module
735 will be called i2c-mxs.
738 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
741 If you say yes to this option, support will be included for the
742 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
743 as well as the STA2X11 PCIe I/O HUB.
746 tristate "OpenCores I2C Controller"
748 If you say yes to this option, support will be included for the
749 OpenCores I2C controller. For details see
750 http://www.opencores.org/projects.cgi/web/i2c/overview
752 This driver can also be built as a module. If so, the module
753 will be called i2c-ocores.
756 tristate "OMAP I2C adapter"
758 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
760 If you say yes to this option, support will be included for the
761 I2C interface on the Texas Instruments OMAP1/2 family of processors.
762 Like OMAP1510/1610/1710/5912 and OMAP242x.
763 For details see http://www.ti.com/omap.
766 tristate "PA Semi SMBus interface"
767 depends on PPC_PASEMI && PCI
769 Supports the PA Semi PWRficient on-chip SMBus interfaces.
771 config I2C_PCA_PLATFORM
772 tristate "PCA9564/PCA9665 as platform device"
776 This driver supports a memory mapped Philips PCA9564/PCA9665
777 parallel bus to I2C bus controller.
779 This driver can also be built as a module. If so, the module
780 will be called i2c-pca-platform.
783 tristate "PMC MSP I2C TWI Controller"
786 This driver supports the PMC TWI controller on MSP devices.
788 This driver can also be built as module. If so, the module
789 will be called i2c-pmcmsp.
792 tristate "I2C bus support for Philips PNX and NXP LPC targets"
793 depends on ARCH_LPC32XX
795 This driver supports the Philips IP3204 I2C IP block master and/or
798 This driver can also be built as a module. If so, the module
799 will be called i2c-pnx.
802 tristate "PKUnity v3 I2C bus support"
803 depends on UNICORE32 && ARCH_PUV3
806 This driver supports the I2C IP inside the PKUnity-v3 SoC.
807 This I2C bus controller is under AMBA/AXI bus.
809 This driver can also be built as a module. If so, the module
810 will be called i2c-puv3.
813 tristate "Intel PXA2XX I2C adapter"
814 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
816 If you have devices in the PXA I2C bus, say yes to this option.
817 This driver can also be built as a module. If so, the module
818 will be called i2c-pxa.
821 def_bool I2C_PXA && X86_32 && PCI && OF
824 bool "Intel PXA2XX I2C Slave comms support"
825 depends on I2C_PXA && !X86_32
827 Support I2C slave mode communications on the PXA I2C bus. This
828 is necessary for systems where the PXA may be a target on the
832 tristate "Qualcomm QUP based I2C controller"
835 If you say yes to this option, support will be included for the
836 built-in I2C interface on the Qualcomm SoCs.
838 This driver can also be built as a module. If so, the module
839 will be called i2c-qup.
842 tristate "Renesas RIIC adapter"
843 depends on ARCH_RENESAS || COMPILE_TEST
845 If you say yes to this option, support will be included for the
846 Renesas RIIC I2C interface.
848 This driver can also be built as a module. If so, the module
849 will be called i2c-riic.
852 tristate "Rockchip RK3xxx I2C adapter"
853 depends on OF && COMMON_CLK
855 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
858 This driver can also be built as a module. If so, the module will
861 config HAVE_S3C2410_I2C
864 This will include I2C support for Samsung SoCs. If you want to
865 include I2C support for any machine, kindly select this in the
866 respective Kconfig file.
869 tristate "S3C2410 I2C Driver"
870 depends on HAVE_S3C2410_I2C
872 Say Y here to include support for I2C controller in the
876 tristate "Renesas SH7760 I2C Controller"
877 depends on CPU_SUBTYPE_SH7760
879 This driver supports the 2 I2C interfaces on the Renesas SH7760.
881 This driver can also be built as a module. If so, the module
882 will be called i2c-sh7760.
885 tristate "SuperH Mobile I2C Controller"
886 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
888 If you say yes to this option, support will be included for the
889 built-in I2C interface on the Renesas SH-Mobile processor.
891 This driver can also be built as a module. If so, the module
892 will be called i2c-sh_mobile.
895 tristate "Simtec Generic I2C interface"
898 If you say yes to this option, support will be included for
899 the Simtec Generic I2C interface. This driver is for the
900 simple I2C bus used on newer Simtec products for general
901 I2C, such as DDC on the Simtec BBD2016A.
903 This driver can also be built as a module. If so, the module
904 will be called i2c-simtec.
907 tristate "CSR SiRFprimaII I2C interface"
910 If you say yes to this option, support will be included for the
911 CSR SiRFprimaII I2C interface.
913 This driver can also be built as a module. If so, the module
914 will be called i2c-sirf.
917 bool "Spreadtrum I2C interface"
918 depends on I2C=y && ARCH_SPRD
920 If you say yes to this option, support will be included for the
921 Spreadtrum I2C interface.
924 tristate "STMicroelectronics SSC I2C support"
927 Enable this option to add support for STMicroelectronics SoCs
928 hardware SSC (Synchronous Serial Controller) as an I2C controller.
930 This driver can also be built as module. If so, the module
931 will be called i2c-st.
934 tristate "STMicroelectronics STM32F4 I2C support"
935 depends on ARCH_STM32 || COMPILE_TEST
937 Enable this option to add support for STM32 I2C controller embedded
940 This driver can also be built as module. If so, the module
941 will be called i2c-stm32f4.
944 tristate "STMicroelectronics STM32F7 I2C support"
945 depends on ARCH_STM32 || COMPILE_TEST
947 Enable this option to add support for STM32 I2C controller embedded
950 This driver can also be built as module. If so, the module
951 will be called i2c-stm32f7.
954 tristate "ST Microelectronics DDC I2C interface"
956 default y if MACH_U300
958 If you say yes to this option, support will be included for the
959 I2C interface from ST Microelectronics simply called "DDC I2C"
960 supporting both I2C and DDC, used in e.g. the U300 series
963 This driver can also be built as a module. If so, the module
964 will be called i2c-stu300.
966 config I2C_SUN6I_P2WI
967 tristate "Allwinner sun6i internal P2WI controller"
968 depends on RESET_CONTROLLER
969 depends on MACH_SUN6I || COMPILE_TEST
971 If you say yes to this option, support will be included for the
972 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
974 The P2WI looks like an SMBus controller (which supports only byte
975 accesses), except that it only supports one slave device.
976 This interface is used to connect to specific PMIC devices (like the
980 tristate "Socionext SynQuacer I2C controller"
981 depends on ARCH_SYNQUACER || COMPILE_TEST
983 Say Y here to include support for the I2C controller used in some
984 Fujitsu and Socionext SoCs.
986 This driver can also be built as a module. If so, the module
987 will be called i2c-synquacer.
990 tristate "NVIDIA Tegra internal I2C controller"
991 depends on ARCH_TEGRA
993 If you say yes to this option, support will be included for the
994 I2C controller embedded in NVIDIA Tegra SOCs
996 config I2C_TEGRA_BPMP
997 tristate "NVIDIA Tegra BPMP I2C controller"
998 depends on TEGRA_BPMP
1001 If you say yes to this option, support will be included for the I2C
1002 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1004 This I2C driver is a 'virtual' I2C driver. The real driver is part
1005 of the BPMP firmware, and this driver merely communicates with that
1009 tristate "UniPhier FIFO-less I2C controller"
1010 depends on ARCH_UNIPHIER || COMPILE_TEST
1012 If you say yes to this option, support will be included for
1013 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1014 or older UniPhier SoCs.
1016 config I2C_UNIPHIER_F
1017 tristate "UniPhier FIFO-builtin I2C controller"
1018 depends on ARCH_UNIPHIER || COMPILE_TEST
1020 If you say yes to this option, support will be included for
1021 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1022 PH1-Pro5, or newer UniPhier SoCs.
1024 config I2C_VERSATILE
1025 tristate "ARM Versatile/Realview I2C bus support"
1026 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1029 Say yes if you want to support the I2C serial bus on ARMs Versatile
1032 This driver can also be built as a module. If so, the module
1033 will be called i2c-versatile.
1036 tristate "Wondermedia WM8xxx SoC I2C bus support"
1037 depends on ARCH_VT8500
1039 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1042 This driver can also be built as a module. If so, the module will be
1046 tristate "Cavium OCTEON I2C bus support"
1047 depends on CAVIUM_OCTEON_SOC
1049 Say yes if you want to support the I2C serial bus on Cavium
1052 This driver can also be built as a module. If so, the module
1053 will be called i2c-octeon.
1056 tristate "Cavium ThunderX I2C bus support"
1057 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1060 Say yes if you want to support the I2C serial bus on Cavium
1063 This driver can also be built as a module. If so, the module
1064 will be called i2c-thunderx.
1067 tristate "Xilinx I2C Controller"
1068 depends on HAS_IOMEM
1070 If you say yes to this option, support will be included for the
1071 Xilinx I2C controller.
1073 This driver can also be built as a module. If so, the module
1074 will be called xilinx_i2c.
1077 tristate "Netlogic XLR and Sigma Designs I2C support"
1078 depends on CPU_XLR || ARCH_TANGO
1080 This driver enables support for the on-chip I2C interface of
1081 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1083 This driver can also be built as a module. If so, the module
1084 will be called i2c-xlr.
1087 tristate "XLP9XX I2C support"
1088 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1090 This driver enables support for the on-chip I2C interface of
1091 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1093 This driver can also be built as a module. If so, the module will
1094 be called i2c-xlp9xx.
1097 tristate "Renesas R-Car I2C Controller"
1098 depends on ARCH_RENESAS || COMPILE_TEST
1101 If you say yes to this option, support will be included for the
1102 R-Car I2C controller.
1104 This driver can also be built as a module. If so, the module
1105 will be called i2c-rcar.
1107 comment "External I2C/SMBus adapter drivers"
1109 config I2C_DIOLAN_U2C
1110 tristate "Diolan U2C-12 USB adapter"
1113 If you say yes to this option, support will be included for Diolan
1114 U2C-12, a USB to I2C interface.
1116 This driver can also be built as a module. If so, the module
1117 will be called i2c-diolan-u2c.
1120 tristate "Diolan DLN-2 USB I2C adapter"
1123 If you say yes to this option, support will be included for Diolan
1124 DLN2, a USB to I2C interface.
1126 This driver can also be built as a module. If so, the module
1127 will be called i2c-dln2.
1130 tristate "Parallel port adapter"
1135 This supports parallel port I2C adapters such as the ones made by
1136 Philips or Velleman, Analog Devices evaluation boards, and more.
1137 Basically any adapter using the parallel port as an I2C bus with
1138 no extra chipset is supported by this driver, or could be.
1140 This driver is a replacement for (and was inspired by) an older
1141 driver named i2c-philips-par. The new driver supports more devices,
1142 and makes it easier to add support for new devices.
1144 An adapter type parameter is now mandatory. Please read the file
1145 Documentation/i2c/busses/i2c-parport for details.
1147 Another driver exists, named i2c-parport-light, which doesn't depend
1148 on the parport driver. This is meant for embedded systems. Don't say
1149 Y here if you intend to say Y or M there.
1151 This support is also available as a module. If so, the module
1152 will be called i2c-parport.
1154 config I2C_PARPORT_LIGHT
1155 tristate "Parallel port adapter (light)"
1159 This supports parallel port I2C adapters such as the ones made by
1160 Philips or Velleman, Analog Devices evaluation boards, and more.
1161 Basically any adapter using the parallel port as an I2C bus with
1162 no extra chipset is supported by this driver, or could be.
1164 This driver is a light version of i2c-parport. It doesn't depend
1165 on the parport driver, and uses direct I/O access instead. This
1166 might be preferred on embedded systems where wasting memory for
1167 the clean but heavy parport handling is not an option. The
1168 drawback is a reduced portability and the impossibility to
1169 daisy-chain other parallel port devices.
1171 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1172 both is possible but both modules should not be loaded at the same
1175 This support is also available as a module. If so, the module
1176 will be called i2c-parport-light.
1178 config I2C_ROBOTFUZZ_OSIF
1179 tristate "RobotFuzz Open Source InterFace USB adapter"
1182 If you say yes to this option, support will be included for the
1183 RobotFuzz Open Source InterFace USB to I2C interface.
1185 This driver can also be built as a module. If so, the module
1186 will be called i2c-osif.
1189 tristate "TAOS evaluation module"
1192 select SERIO_SERPORT
1195 This supports TAOS evaluation modules on serial port. In order to
1196 use this driver, you will need the inputattach tool, which is part
1197 of the input-utils package.
1201 This support is also available as a module. If so, the module
1202 will be called i2c-taos-evm.
1205 tristate "Tiny-USB adapter"
1208 If you say yes to this option, support will be included for the
1209 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1210 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1212 This driver can also be built as a module. If so, the module
1213 will be called i2c-tiny-usb.
1215 config I2C_VIPERBOARD
1216 tristate "Viperboard I2C master support"
1217 depends on MFD_VIPERBOARD && USB
1219 Say yes here to access the I2C part of the Nano River
1220 Technologies Viperboard as I2C master.
1221 See viperboard API specification and Nano
1222 River Tech's viperboard.h for detailed meaning
1223 of the module parameters.
1225 comment "Other I2C/SMBus bus drivers"
1228 tristate "Acorn IOC/IOMD I2C bus support"
1229 depends on ARCH_ACORN
1233 Say yes if you want to support the I2C bus on Acorn platforms.
1235 If you don't know, say Y.
1238 tristate "Elektor ISA card"
1239 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1242 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1245 This support is also available as a module. If so, the module
1246 will be called i2c-elektor.
1249 tristate "Mellanox I2C driver"
1252 This exposes the Mellanox platform I2C busses to the linux I2C layer
1253 for X86 based systems.
1254 Controller is implemented as CPLD logic.
1256 This driver can also be built as a module. If so, the module will be
1257 called as i2c-mlxcpld.
1260 tristate "PCA9564/PCA9665 on an ISA bus"
1265 This driver supports ISA boards using the Philips PCA9564/PCA9665
1266 parallel bus to I2C bus controller.
1268 This driver can also be built as a module. If so, the module
1269 will be called i2c-pca-isa.
1271 This device is almost undetectable and using this driver on a
1272 system which doesn't have this device will result in long
1273 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1274 time). If unsure, say N.
1277 tristate "SiByte SMBus interface"
1278 depends on SIBYTE_SB1xxx_SOC
1280 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1282 config I2C_CROS_EC_TUNNEL
1283 tristate "ChromeOS EC tunnel I2C bus"
1284 depends on MFD_CROS_EC
1286 If you say yes here you get an I2C bus that will tunnel i2c commands
1287 through to the other side of the ChromeOS EC to the i2c bus
1288 connected there. This will work whatever the interface used to
1289 talk to the EC (SPI, I2C or LPC).
1291 config I2C_XGENE_SLIMPRO
1292 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1293 depends on ARCH_XGENE && MAILBOX
1295 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1296 co-processor. The I2C device access the I2C bus via the X-Gene
1297 to SLIMpro (On chip coprocessor) mailbox mechanism.
1301 tristate "Geode ACCESS.bus support"
1302 depends on X86_32 && PCI
1304 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1305 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1307 If you don't know what to do here, say N.
1309 This support is also available as a module. If so, the module
1310 will be called scx200_acb.
1313 tristate "IBM OPAL I2C driver"
1314 depends on PPC_POWERNV
1317 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1318 the driver is based on the OPAL interfaces.
1320 This driver can also be built as a module. If so, the module will be
1324 tristate "ZTE ZX2967 I2C support"
1328 Selecting this option will add ZX2967 I2C driver.
1329 This driver can also be built as a module. If so, the module will be