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/DSL I2C controller"
436 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
440 If you say yes to this option, support will be included for the
441 I2C interface on the Broadcom Settop/DSL SoCs.
443 If you do not need I2C interface, say N.
446 tristate "Cadence I2C Controller"
447 depends on ARCH_ZYNQ || ARM64 || XTENSA
449 Say yes here to select Cadence I2C Host Controller. This controller is
450 e.g. used by Xilinx Zynq.
453 tristate "CBUS I2C driver"
454 depends on GPIOLIB || COMPILE_TEST
456 Support for CBUS access using I2C API. Mostly relevant for Nokia
457 Internet Tablets (770, N800 and N810).
459 This driver can also be built as a module. If so, the module
460 will be called i2c-cbus-gpio.
463 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
464 depends on CPM1 || CPM2
466 This supports the use of the I2C interface on Freescale
467 processors with CPM1 or CPM2.
469 This driver can also be built as a module. If so, the module
470 will be called i2c-cpm.
473 tristate "DaVinci I2C driver"
474 depends on ARCH_DAVINCI || ARCH_KEYSTONE
476 Support for TI DaVinci I2C controller driver.
478 This driver can also be built as a module. If so, the module
479 will be called i2c-davinci.
481 Please note that this driver might be needed to bring up other
482 devices such as DaVinci NIC.
483 For details please see http://www.ti.com/davinci
485 config I2C_DESIGNWARE_CORE
488 config I2C_DESIGNWARE_PLATFORM
489 tristate "Synopsys DesignWare Platform"
490 select I2C_DESIGNWARE_CORE
491 depends on (ACPI && COMMON_CLK) || !ACPI
493 If you say yes to this option, support will be included for the
494 Synopsys DesignWare I2C adapter.
496 This driver can also be built as a module. If so, the module
497 will be called i2c-designware-platform.
499 config I2C_DESIGNWARE_SLAVE
500 bool "Synopsys DesignWare Slave"
502 depends on I2C_DESIGNWARE_PLATFORM
504 If you say yes to this option, support will be included for the
505 Synopsys DesignWare I2C slave adapter.
507 This is not a standalone module, this module compiles together with
510 config I2C_DESIGNWARE_PCI
511 tristate "Synopsys DesignWare PCI"
513 select I2C_DESIGNWARE_CORE
515 If you say yes to this option, support will be included for the
516 Synopsys DesignWare I2C adapter. Only master mode is supported.
518 This driver can also be built as a module. If so, the module
519 will be called i2c-designware-pci.
521 config I2C_DESIGNWARE_BAYTRAIL
522 bool "Intel Baytrail I2C semaphore support"
524 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
525 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
527 This driver enables managed host access to the PMIC I2C bus on select
528 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
529 the host to request uninterrupted access to the PMIC's I2C bus from
530 the platform firmware controlling it. You should say Y if running on
531 a BayTrail system using the AXP288.
534 tristate "Conexant Digicolor I2C driver"
535 depends on ARCH_DIGICOLOR
537 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
539 This driver can also be built as a module. If so, the module
540 will be called i2c-digicolor.
543 tristate "EFM32 I2C controller"
544 depends on ARCH_EFM32 || COMPILE_TEST
546 This driver supports the i2c block found in Energy Micro's EFM32
550 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
551 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
553 This driver is for PCH(Platform controller Hub) I2C of EG20T which
554 is an IOH(Input/Output Hub) for x86 embedded processor.
555 This driver can access PCH I2C bus device.
557 This driver also can be used for LAPIS Semiconductor IOH(Input/
558 Output Hub), ML7213, ML7223 and ML7831.
559 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
560 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
561 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
562 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
565 tristate "EMMA Mobile series I2C adapter"
569 If you say yes to this option, support will be included for the
570 I2C interface on the Renesas Electronics EM/EV family of processors.
573 tristate "Exynos5 high-speed I2C driver"
574 depends on ARCH_EXYNOS && OF
577 High-speed I2C controller on Exynos5 based Samsung SoCs.
580 tristate "GPIO-based bitbanging I2C"
581 depends on GPIOLIB || COMPILE_TEST
584 This is a very simple bitbanging I2C driver utilizing the
585 arch-neutral GPIO API to control the SCL and SDA lines.
587 config I2C_GPIO_FAULT_INJECTOR
588 bool "GPIO-based fault injector"
591 This adds some functionality to the i2c-gpio driver which can inject
592 faults to an I2C bus, so another bus master can be stress-tested.
593 This is for debugging. If unsure, say 'no'.
595 config I2C_HIGHLANDER
596 tristate "Highlander FPGA SMBus interface"
597 depends on SH_HIGHLANDER
599 If you say yes to this option, support will be included for
600 the SMBus interface located in the FPGA on various Highlander
601 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
602 FPGAs. This is wholly unrelated to the SoC I2C.
604 This driver can also be built as a module. If so, the module
605 will be called i2c-highlander.
608 tristate "IBM PPC 4xx on-chip I2C interface"
611 Say Y here if you want to use IIC peripheral found on
612 embedded IBM PPC 4xx based systems.
614 This driver can also be built as a module. If so, the module
615 will be called i2c-ibm_iic.
618 tristate "Imagination Technologies I2C SCB Controller"
619 depends on MIPS || COMPILE_TEST
621 Say Y here if you want to use the IMG I2C SCB controller,
622 available on the TZ1090 and other IMG SoCs.
624 This driver can also be built as a module. If so, the module
625 will be called i2c-img-scb.
628 tristate "IMX I2C interface"
629 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
631 Say Y here if you want to use the IIC bus controller on
632 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
634 This driver can also be built as a module. If so, the module
635 will be called i2c-imx.
638 tristate "IMX Low Power I2C interface"
639 depends on ARCH_MXC || COMPILE_TEST
641 Say Y here if you want to use the Low Power IIC bus controller
642 on the Freescale i.MX processors.
644 This driver can also be built as a module. If so, the module
645 will be called i2c-imx-lpi2c.
648 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
649 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
651 Say Y here if you want to use the IIC bus controller on
652 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
654 This driver can also be built as a module. If so, the module
655 will be called i2c-iop3xx.
658 tristate "JZ4780 I2C controller interface support"
659 depends on MACH_JZ4780 || COMPILE_TEST
661 If you say yes to this option, support will be included for the
662 Ingenic JZ4780 I2C controller.
664 If you don't know what to do here, say N.
667 tristate "Kontron COM I2C Controller"
668 depends on MFD_KEMPLD
670 This enables support for the I2C bus interface on some Kontron ETX
671 and COMexpress (ETXexpress) modules.
673 This driver can also be built as a module. If so, the module
674 will be called i2c-kempld.
677 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
678 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
680 This driver supports the I2C interface found several NXP
681 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
683 This driver can also be built as a module. If so, the module
684 will be called i2c-lpc2k.
687 tristate "Amlogic Meson I2C controller"
688 depends on ARCH_MESON || COMPILE_TEST
690 If you say yes to this option, support will be included for the
691 I2C interface on the Amlogic Meson family of SoCs.
694 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
697 If you say yes to this option, support will be included for the
698 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
699 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
701 This driver can also be built as a module. If so, the module
702 will be called i2c-mpc.
705 tristate "MediaTek I2C adapter"
706 depends on ARCH_MEDIATEK || COMPILE_TEST
708 This selects the MediaTek(R) Integrated Inter Circuit bus driver
709 for MT65xx and MT81xx.
710 If you want to use MediaTek(R) I2C interface, say Y or M here.
714 tristate "Marvell mv64xxx I2C Controller"
715 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
717 If you say yes to this option, support will be included for the
718 built-in I2C interface on the Marvell 64xxx line of host bridges.
719 This driver is also used for Allwinner SoCs I2C controllers.
721 This driver can also be built as a module. If so, the module
722 will be called i2c-mv64xxx.
725 tristate "Freescale i.MX28 I2C interface"
729 Say Y here if you want to use the I2C bus controller on
730 the Freescale i.MX28 processors.
732 This driver can also be built as a module. If so, the module
733 will be called i2c-mxs.
736 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
739 If you say yes to this option, support will be included for the
740 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
741 as well as the STA2X11 PCIe I/O HUB.
744 tristate "OpenCores I2C Controller"
746 If you say yes to this option, support will be included for the
747 OpenCores I2C controller. For details see
748 http://www.opencores.org/projects.cgi/web/i2c/overview
750 This driver can also be built as a module. If so, the module
751 will be called i2c-ocores.
754 tristate "OMAP I2C adapter"
755 depends on ARCH_OMAP || ARCH_K3
756 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
758 If you say yes to this option, support will be included for the
759 I2C interface on the Texas Instruments OMAP1/2 family of processors.
760 Like OMAP1510/1610/1710/5912 and OMAP242x.
761 For details see http://www.ti.com/omap.
764 tristate "Actions Semiconductor Owl I2C Controller"
765 depends on ARCH_ACTIONS || COMPILE_TEST
767 Say Y here if you want to use the I2C bus controller on
768 the Actions Semiconductor Owl SoC's.
771 tristate "PA Semi SMBus interface"
772 depends on PPC_PASEMI && PCI
774 Supports the PA Semi PWRficient on-chip SMBus interfaces.
776 config I2C_PCA_PLATFORM
777 tristate "PCA9564/PCA9665 as platform device"
781 This driver supports a memory mapped Philips PCA9564/PCA9665
782 parallel bus to I2C bus controller.
784 This driver can also be built as a module. If so, the module
785 will be called i2c-pca-platform.
788 tristate "PMC MSP I2C TWI Controller"
791 This driver supports the PMC TWI controller on MSP devices.
793 This driver can also be built as module. If so, the module
794 will be called i2c-pmcmsp.
797 tristate "I2C bus support for Philips PNX and NXP LPC targets"
798 depends on ARCH_LPC32XX
800 This driver supports the Philips IP3204 I2C IP block master and/or
803 This driver can also be built as a module. If so, the module
804 will be called i2c-pnx.
807 tristate "PKUnity v3 I2C bus support"
808 depends on UNICORE32 && ARCH_PUV3
811 This driver supports the I2C IP inside the PKUnity-v3 SoC.
812 This I2C bus controller is under AMBA/AXI bus.
814 This driver can also be built as a module. If so, the module
815 will be called i2c-puv3.
818 tristate "Intel PXA2XX I2C adapter"
819 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF)
821 If you have devices in the PXA I2C bus, say yes to this option.
822 This driver can also be built as a module. If so, the module
823 will be called i2c-pxa.
826 def_bool I2C_PXA && X86_32 && PCI && OF
829 bool "Intel PXA2XX I2C Slave comms support"
830 depends on I2C_PXA && !X86_32
832 Support I2C slave mode communications on the PXA I2C bus. This
833 is necessary for systems where the PXA may be a target on the
837 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller"
838 depends on ARCH_QCOM || COMPILE_TEST
839 depends on QCOM_GENI_SE
841 This driver supports GENI serial engine based I2C controller in
842 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
843 yes to this option, support will be included for the built-in I2C
844 interface on the Qualcomm Technologies Inc.'s SoCs.
846 This driver can also be built as a module. If so, the module
847 will be called i2c-qcom-geni.
850 tristate "Qualcomm QUP based I2C controller"
853 If you say yes to this option, support will be included for the
854 built-in I2C interface on the Qualcomm SoCs.
856 This driver can also be built as a module. If so, the module
857 will be called i2c-qup.
860 tristate "Renesas RIIC adapter"
861 depends on ARCH_RENESAS || COMPILE_TEST
863 If you say yes to this option, support will be included for the
864 Renesas RIIC I2C interface.
866 This driver can also be built as a module. If so, the module
867 will be called i2c-riic.
870 tristate "Rockchip RK3xxx I2C adapter"
871 depends on OF && COMMON_CLK
873 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
876 This driver can also be built as a module. If so, the module will
879 config HAVE_S3C2410_I2C
882 This will include I2C support for Samsung SoCs. If you want to
883 include I2C support for any machine, kindly select this in the
884 respective Kconfig file.
887 tristate "S3C2410 I2C Driver"
888 depends on HAVE_S3C2410_I2C
890 Say Y here to include support for I2C controller in the
894 tristate "Renesas SH7760 I2C Controller"
895 depends on CPU_SUBTYPE_SH7760
897 This driver supports the 2 I2C interfaces on the Renesas SH7760.
899 This driver can also be built as a module. If so, the module
900 will be called i2c-sh7760.
903 tristate "SuperH Mobile I2C Controller"
904 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
906 If you say yes to this option, support will be included for the
907 built-in I2C interface on the Renesas SH-Mobile processor.
909 This driver can also be built as a module. If so, the module
910 will be called i2c-sh_mobile.
913 tristate "Simtec Generic I2C interface"
916 If you say yes to this option, support will be included for
917 the Simtec Generic I2C interface. This driver is for the
918 simple I2C bus used on newer Simtec products for general
919 I2C, such as DDC on the Simtec BBD2016A.
921 This driver can also be built as a module. If so, the module
922 will be called i2c-simtec.
925 tristate "CSR SiRFprimaII I2C interface"
928 If you say yes to this option, support will be included for the
929 CSR SiRFprimaII I2C interface.
931 This driver can also be built as a module. If so, the module
932 will be called i2c-sirf.
935 bool "Spreadtrum I2C interface"
936 depends on I2C=y && ARCH_SPRD
938 If you say yes to this option, support will be included for the
939 Spreadtrum I2C interface.
942 tristate "STMicroelectronics SSC I2C support"
945 Enable this option to add support for STMicroelectronics SoCs
946 hardware SSC (Synchronous Serial Controller) as an I2C controller.
948 This driver can also be built as module. If so, the module
949 will be called i2c-st.
952 tristate "STMicroelectronics STM32F4 I2C support"
953 depends on ARCH_STM32 || COMPILE_TEST
955 Enable this option to add support for STM32 I2C controller embedded
958 This driver can also be built as module. If so, the module
959 will be called i2c-stm32f4.
962 tristate "STMicroelectronics STM32F7 I2C support"
963 depends on ARCH_STM32 || COMPILE_TEST
966 Enable this option to add support for STM32 I2C controller embedded
969 This driver can also be built as module. If so, the module
970 will be called i2c-stm32f7.
973 tristate "ST Microelectronics DDC I2C interface"
975 default y if MACH_U300
977 If you say yes to this option, support will be included for the
978 I2C interface from ST Microelectronics simply called "DDC I2C"
979 supporting both I2C and DDC, used in e.g. the U300 series
982 This driver can also be built as a module. If so, the module
983 will be called i2c-stu300.
985 config I2C_SUN6I_P2WI
986 tristate "Allwinner sun6i internal P2WI controller"
987 depends on RESET_CONTROLLER
988 depends on MACH_SUN6I || COMPILE_TEST
990 If you say yes to this option, support will be included for the
991 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
993 The P2WI looks like an SMBus controller (which supports only byte
994 accesses), except that it only supports one slave device.
995 This interface is used to connect to specific PMIC devices (like the
999 tristate "Socionext SynQuacer I2C controller"
1000 depends on ARCH_SYNQUACER || COMPILE_TEST
1002 Say Y here to include support for the I2C controller used in some
1003 Fujitsu and Socionext SoCs.
1005 This driver can also be built as a module. If so, the module
1006 will be called i2c-synquacer.
1009 tristate "NVIDIA Tegra internal I2C controller"
1010 depends on ARCH_TEGRA
1012 If you say yes to this option, support will be included for the
1013 I2C controller embedded in NVIDIA Tegra SOCs
1015 config I2C_TEGRA_BPMP
1016 tristate "NVIDIA Tegra BPMP I2C controller"
1017 depends on TEGRA_BPMP
1020 If you say yes to this option, support will be included for the I2C
1021 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1023 This I2C driver is a 'virtual' I2C driver. The real driver is part
1024 of the BPMP firmware, and this driver merely communicates with that
1028 tristate "UniPhier FIFO-less I2C controller"
1029 depends on ARCH_UNIPHIER || COMPILE_TEST
1031 If you say yes to this option, support will be included for
1032 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1033 or older UniPhier SoCs.
1035 config I2C_UNIPHIER_F
1036 tristate "UniPhier FIFO-builtin I2C controller"
1037 depends on ARCH_UNIPHIER || COMPILE_TEST
1039 If you say yes to this option, support will be included for
1040 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1041 PH1-Pro5, or newer UniPhier SoCs.
1043 config I2C_VERSATILE
1044 tristate "ARM Versatile/Realview I2C bus support"
1045 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1048 Say yes if you want to support the I2C serial bus on ARMs Versatile
1051 This driver can also be built as a module. If so, the module
1052 will be called i2c-versatile.
1055 tristate "Wondermedia WM8xxx SoC I2C bus support"
1056 depends on ARCH_VT8500
1058 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1061 This driver can also be built as a module. If so, the module will be
1065 tristate "Cavium OCTEON I2C bus support"
1066 depends on CAVIUM_OCTEON_SOC
1068 Say yes if you want to support the I2C serial bus on Cavium
1071 This driver can also be built as a module. If so, the module
1072 will be called i2c-octeon.
1075 tristate "Cavium ThunderX I2C bus support"
1076 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1079 Say yes if you want to support the I2C serial bus on Cavium
1082 This driver can also be built as a module. If so, the module
1083 will be called i2c-thunderx.
1086 tristate "Xilinx I2C Controller"
1087 depends on HAS_IOMEM
1089 If you say yes to this option, support will be included for the
1090 Xilinx I2C controller.
1092 This driver can also be built as a module. If so, the module
1093 will be called xilinx_i2c.
1096 tristate "Netlogic XLR and Sigma Designs I2C support"
1097 depends on CPU_XLR || ARCH_TANGO
1099 This driver enables support for the on-chip I2C interface of
1100 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1102 This driver can also be built as a module. If so, the module
1103 will be called i2c-xlr.
1106 tristate "XLP9XX I2C support"
1107 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1109 This driver enables support for the on-chip I2C interface of
1110 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1112 This driver can also be built as a module. If so, the module will
1113 be called i2c-xlp9xx.
1116 tristate "Renesas R-Car I2C Controller"
1117 depends on ARCH_RENESAS || COMPILE_TEST
1120 If you say yes to this option, support will be included for the
1121 R-Car I2C controller.
1123 This driver can also be built as a module. If so, the module
1124 will be called i2c-rcar.
1126 comment "External I2C/SMBus adapter drivers"
1128 config I2C_DIOLAN_U2C
1129 tristate "Diolan U2C-12 USB adapter"
1132 If you say yes to this option, support will be included for Diolan
1133 U2C-12, a USB to I2C interface.
1135 This driver can also be built as a module. If so, the module
1136 will be called i2c-diolan-u2c.
1139 tristate "Diolan DLN-2 USB I2C adapter"
1142 If you say yes to this option, support will be included for Diolan
1143 DLN2, a USB to I2C interface.
1145 This driver can also be built as a module. If so, the module
1146 will be called i2c-dln2.
1149 tristate "Parallel port adapter"
1154 This supports parallel port I2C adapters such as the ones made by
1155 Philips or Velleman, Analog Devices evaluation boards, and more.
1156 Basically any adapter using the parallel port as an I2C bus with
1157 no extra chipset is supported by this driver, or could be.
1159 This driver is a replacement for (and was inspired by) an older
1160 driver named i2c-philips-par. The new driver supports more devices,
1161 and makes it easier to add support for new devices.
1163 An adapter type parameter is now mandatory. Please read the file
1164 Documentation/i2c/busses/i2c-parport for details.
1166 Another driver exists, named i2c-parport-light, which doesn't depend
1167 on the parport driver. This is meant for embedded systems. Don't say
1168 Y here if you intend to say Y or M there.
1170 This support is also available as a module. If so, the module
1171 will be called i2c-parport.
1173 config I2C_PARPORT_LIGHT
1174 tristate "Parallel port adapter (light)"
1178 This supports parallel port I2C adapters such as the ones made by
1179 Philips or Velleman, Analog Devices evaluation boards, and more.
1180 Basically any adapter using the parallel port as an I2C bus with
1181 no extra chipset is supported by this driver, or could be.
1183 This driver is a light version of i2c-parport. It doesn't depend
1184 on the parport driver, and uses direct I/O access instead. This
1185 might be preferred on embedded systems where wasting memory for
1186 the clean but heavy parport handling is not an option. The
1187 drawback is a reduced portability and the impossibility to
1188 daisy-chain other parallel port devices.
1190 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1191 both is possible but both modules should not be loaded at the same
1194 This support is also available as a module. If so, the module
1195 will be called i2c-parport-light.
1197 config I2C_ROBOTFUZZ_OSIF
1198 tristate "RobotFuzz Open Source InterFace USB adapter"
1201 If you say yes to this option, support will be included for the
1202 RobotFuzz Open Source InterFace USB to I2C interface.
1204 This driver can also be built as a module. If so, the module
1205 will be called i2c-osif.
1208 tristate "TAOS evaluation module"
1211 select SERIO_SERPORT
1214 This supports TAOS evaluation modules on serial port. In order to
1215 use this driver, you will need the inputattach tool, which is part
1216 of the input-utils package.
1220 This support is also available as a module. If so, the module
1221 will be called i2c-taos-evm.
1224 tristate "Tiny-USB adapter"
1227 If you say yes to this option, support will be included for the
1228 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1229 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1231 This driver can also be built as a module. If so, the module
1232 will be called i2c-tiny-usb.
1234 config I2C_VIPERBOARD
1235 tristate "Viperboard I2C master support"
1236 depends on MFD_VIPERBOARD && USB
1238 Say yes here to access the I2C part of the Nano River
1239 Technologies Viperboard as I2C master.
1240 See viperboard API specification and Nano
1241 River Tech's viperboard.h for detailed meaning
1242 of the module parameters.
1244 comment "Other I2C/SMBus bus drivers"
1247 tristate "Acorn IOC/IOMD I2C bus support"
1248 depends on ARCH_ACORN
1252 Say yes if you want to support the I2C bus on Acorn platforms.
1254 If you don't know, say Y.
1257 tristate "Elektor ISA card"
1258 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1261 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1264 This support is also available as a module. If so, the module
1265 will be called i2c-elektor.
1268 tristate "Mellanox I2C driver"
1271 This exposes the Mellanox platform I2C busses to the linux I2C layer
1272 for X86 based systems.
1273 Controller is implemented as CPLD logic.
1275 This driver can also be built as a module. If so, the module will be
1276 called as i2c-mlxcpld.
1279 tristate "PCA9564/PCA9665 on an ISA bus"
1284 This driver supports ISA boards using the Philips PCA9564/PCA9665
1285 parallel bus to I2C bus controller.
1287 This driver can also be built as a module. If so, the module
1288 will be called i2c-pca-isa.
1290 This device is almost undetectable and using this driver on a
1291 system which doesn't have this device will result in long
1292 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1293 time). If unsure, say N.
1296 tristate "SiByte SMBus interface"
1297 depends on SIBYTE_SB1xxx_SOC
1299 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1301 config I2C_CROS_EC_TUNNEL
1302 tristate "ChromeOS EC tunnel I2C bus"
1303 depends on MFD_CROS_EC
1305 If you say yes here you get an I2C bus that will tunnel i2c commands
1306 through to the other side of the ChromeOS EC to the i2c bus
1307 connected there. This will work whatever the interface used to
1308 talk to the EC (SPI, I2C or LPC).
1310 config I2C_XGENE_SLIMPRO
1311 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1312 depends on ARCH_XGENE && MAILBOX
1314 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1315 co-processor. The I2C device access the I2C bus via the X-Gene
1316 to SLIMpro (On chip coprocessor) mailbox mechanism.
1320 tristate "Geode ACCESS.bus support"
1321 depends on X86_32 && PCI
1323 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1324 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1326 If you don't know what to do here, say N.
1328 This support is also available as a module. If so, the module
1329 will be called scx200_acb.
1332 tristate "IBM OPAL I2C driver"
1333 depends on PPC_POWERNV
1336 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1337 the driver is based on the OPAL interfaces.
1339 This driver can also be built as a module. If so, the module will be
1343 tristate "ZTE ZX2967 I2C support"
1347 Selecting this option will add ZX2967 I2C driver.
1348 This driver can also be built as a module. If so, the module will be
1352 tristate "FSI I2C driver"
1355 Driver for FSI bus attached I2C masters. These are I2C masters that
1356 are connected to the system over an FSI bus, instead of the more
1357 common PCI or MMIO interface.
1359 This driver can also be built as a module. If so, the module will be