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)
126 Sunrise Point-H (PCH)
127 Sunrise Point-LP (PCH)
136 This driver can also be built as a module. If so, the module
137 will be called i2c-i801.
140 tristate "Intel SCH SMBus 1.0"
144 Say Y here if you want to use SMBus controller on the Intel SCH
147 This driver can also be built as a module. If so, the module
148 will be called i2c-isch.
151 tristate "Intel iSMT SMBus Controller"
152 depends on PCI && X86
154 If you say yes to this option, support will be included for the Intel
155 iSMT SMBus host controller interface.
157 This driver can also be built as a module. If so, the module will be
161 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
164 If you say yes to this option, support will be included for the Intel
165 PIIX4 family of mainboard I2C interfaces. Specifically, the following
166 versions of the chipset are supported (note that Serverworks is part
186 Some AMD chipsets contain two PIIX4-compatible SMBus
187 controllers. This driver will attempt to use both controllers
188 on the SB700/SP5100, if they have been initialized by the BIOS.
190 This driver can also be built as a module. If so, the module
191 will be called i2c-piix4.
194 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller"
195 depends on INTEL_SOC_PMIC_CHTWC
197 If you say yes to this option, support will be included for the
198 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC
199 found on some Intel Cherry Trail systems.
202 tristate "Nvidia nForce2, nForce3 and nForce4"
205 If you say yes to this option, support will be included for the Nvidia
206 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
208 This driver can also be built as a module. If so, the module
209 will be called i2c-nforce2.
211 config I2C_NFORCE2_S4985
212 tristate "SMBus multiplexing on the Tyan S4985"
213 depends on I2C_NFORCE2 && X86
215 Enabling this option will add specific SMBus support for the Tyan
216 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
217 over 4 different channels, where the various memory module EEPROMs
218 live. Saying yes here will give you access to these in addition
221 This driver can also be built as a module. If so, the module
222 will be called i2c-nforce2-s4985.
228 If you say yes to this option, support will be included for the
229 SiS5595 SMBus (a subset of I2C) interface.
231 This driver can also be built as a module. If so, the module
232 will be called i2c-sis5595.
235 tristate "SiS 630/730/964"
238 If you say yes to this option, support will be included for the
239 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
241 This driver can also be built as a module. If so, the module
242 will be called i2c-sis630.
248 If you say yes to this option, support will be included for the SiS
249 96x SMBus (a subset of I2C) interfaces. Specifically, the following
250 chipsets are supported:
259 This driver can also be built as a module. If so, the module
260 will be called i2c-sis96x.
263 tristate "VIA VT82C586B"
267 If you say yes to this option, support will be included for the VIA
268 82C586B I2C interface
270 This driver can also be built as a module. If so, the module
271 will be called i2c-via.
274 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
277 If you say yes to this option, support will be included for the VIA
278 VT82C596 and later SMBus interface. Specifically, the following
279 chipsets are supported:
292 This driver can also be built as a module. If so, the module
293 will be called i2c-viapro.
297 comment "ACPI drivers"
300 tristate "SMBus Control Method Interface"
302 This driver supports the SMBus Control Method Interface. It needs the
303 BIOS to declare ACPI control methods as described in the SMBus Control
304 Method Interface specification.
306 To compile this driver as a module, choose M here:
307 the module will be called i2c-scmi.
311 comment "Mac SMBus host controller drivers"
312 depends on PPC_CHRP || PPC_PMAC
315 tristate "CHRP Apple Hydra Mac I/O I2C interface"
316 depends on PCI && PPC_CHRP
319 This supports the use of the I2C interface in the Apple Hydra Mac
320 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
323 This support is also available as a module. If so, the module
324 will be called i2c-hydra.
327 tristate "Powermac I2C interface"
331 This exposes the various PowerMac i2c interfaces to the linux i2c
332 layer and to userland. It is used by various drivers on the PowerMac
333 platform, and should generally be enabled.
335 This support is also available as a module. If so, the module
336 will be called i2c-powermac.
338 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
341 tristate "Altera Soft IP I2C"
342 depends on (ARCH_SOCFPGA || NIOS2) && OF
344 If you say yes to this option, support will be included for the
345 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures.
347 This driver can also be built as a module. If so, the module
348 will be called i2c-altera.
351 tristate "Aspeed I2C Controller"
352 depends on ARCH_ASPEED || COMPILE_TEST
354 If you say yes to this option, support will be included for the
355 Aspeed I2C controller.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-aspeed.
361 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
364 This supports the use of the I2C interface on Atmel AT91
367 A serious problem is that there is no documented way to issue
368 repeated START conditions for more than two messages, as needed
369 to support combined I2C messages. Use the i2c-gpio driver
370 unless your system can cope with this limitation.
372 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
373 don't have clock stretching in transmission mode. For that reason,
374 you can encounter underrun issues causing premature stop sendings if
375 the latency to fill the transmission register is too long. If you
376 are facing this situation, use the i2c-gpio driver.
379 tristate "Au1550/Au1200/Au1300 SMBus interface"
380 depends on MIPS_ALCHEMY
382 If you say yes to this option, support will be included for the
383 Au1550/Au1200/Au1300 SMBus interface.
385 This driver can also be built as a module. If so, the module
386 will be called i2c-au1550.
389 tristate "Axxia I2C controller"
390 depends on ARCH_AXXIA || COMPILE_TEST
393 Say yes if you want to support the I2C bus on Axxia platforms.
395 Please note that this controller is limited to transfers of maximum
396 255 bytes in length. Any attempt to to a larger transfer will return
400 tristate "Broadcom BCM2835 I2C controller"
401 depends on ARCH_BCM2835
403 If you say yes to this option, support will be included for the
404 BCM2835 I2C controller.
406 If you don't know what to do here, say N.
408 This support is also available as a module. If so, the module
409 will be called i2c-bcm2835.
412 tristate "Broadcom iProc I2C controller"
413 depends on ARCH_BCM_IPROC || COMPILE_TEST
414 default ARCH_BCM_IPROC
416 If you say yes to this option, support will be included for the
417 Broadcom iProc I2C controller.
419 If you don't know what to do here, say N.
422 tristate "BCM Kona I2C adapter"
423 depends on ARCH_BCM_MOBILE
426 If you say yes to this option, support will be included for the
427 I2C interface on the Broadcom Kona family of processors.
429 If you do not need KONA I2C interface, say N.
432 tristate "BRCM Settop I2C controller"
433 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
436 If you say yes to this option, support will be included for the
437 I2C interface on the Broadcom Settop SoCs.
439 If you do not need I2C interface, say N.
441 config I2C_BLACKFIN_TWI
442 tristate "Blackfin TWI I2C support"
444 depends on !BF561 && !BF531 && !BF532 && !BF533
446 This is the I2C bus driver for Blackfin on-chip TWI interface.
448 This driver can also be built as a module. If so, the module
449 will be called i2c-bfin-twi.
451 config I2C_BLACKFIN_TWI_CLK_KHZ
452 int "Blackfin TWI I2C clock (kHz)"
453 depends on I2C_BLACKFIN_TWI
457 The unit of the TWI clock is kHz.
460 tristate "Cadence I2C Controller"
461 depends on ARCH_ZYNQ || ARM64 || XTENSA
463 Say yes here to select Cadence I2C Host Controller. This controller is
464 e.g. used by Xilinx Zynq.
467 tristate "CBUS I2C driver"
468 depends on GPIOLIB || COMPILE_TEST
470 Support for CBUS access using I2C API. Mostly relevant for Nokia
471 Internet Tablets (770, N800 and N810).
473 This driver can also be built as a module. If so, the module
474 will be called i2c-cbus-gpio.
477 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
478 depends on CPM1 || CPM2
480 This supports the use of the I2C interface on Freescale
481 processors with CPM1 or CPM2.
483 This driver can also be built as a module. If so, the module
484 will be called i2c-cpm.
487 tristate "DaVinci I2C driver"
488 depends on ARCH_DAVINCI || ARCH_KEYSTONE
490 Support for TI DaVinci I2C controller driver.
492 This driver can also be built as a module. If so, the module
493 will be called i2c-davinci.
495 Please note that this driver might be needed to bring up other
496 devices such as DaVinci NIC.
497 For details please see http://www.ti.com/davinci
499 config I2C_DESIGNWARE_CORE
502 config I2C_DESIGNWARE_PLATFORM
503 tristate "Synopsys DesignWare Platform"
504 select I2C_DESIGNWARE_CORE
505 depends on (ACPI && COMMON_CLK) || !ACPI
507 If you say yes to this option, support will be included for the
508 Synopsys DesignWare I2C adapter.
510 This driver can also be built as a module. If so, the module
511 will be called i2c-designware-platform.
513 config I2C_DESIGNWARE_SLAVE
514 bool "Synopsys DesignWare Slave"
516 depends on I2C_DESIGNWARE_PLATFORM
518 If you say yes to this option, support will be included for the
519 Synopsys DesignWare I2C slave adapter.
521 This is not a standalone module, this module compiles together with
524 config I2C_DESIGNWARE_PCI
525 tristate "Synopsys DesignWare PCI"
527 select I2C_DESIGNWARE_CORE
529 If you say yes to this option, support will be included for the
530 Synopsys DesignWare I2C adapter. Only master mode is supported.
532 This driver can also be built as a module. If so, the module
533 will be called i2c-designware-pci.
535 config I2C_DESIGNWARE_BAYTRAIL
536 bool "Intel Baytrail I2C semaphore support"
538 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
539 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
541 This driver enables managed host access to the PMIC I2C bus on select
542 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
543 the host to request uninterrupted access to the PMIC's I2C bus from
544 the platform firmware controlling it. You should say Y if running on
545 a BayTrail system using the AXP288.
548 tristate "Conexant Digicolor I2C driver"
549 depends on ARCH_DIGICOLOR
551 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
553 This driver can also be built as a module. If so, the module
554 will be called i2c-digicolor.
557 tristate "EFM32 I2C controller"
558 depends on ARCH_EFM32 || COMPILE_TEST
560 This driver supports the i2c block found in Energy Micro's EFM32
564 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
565 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
567 This driver is for PCH(Platform controller Hub) I2C of EG20T which
568 is an IOH(Input/Output Hub) for x86 embedded processor.
569 This driver can access PCH I2C bus device.
571 This driver also can be used for LAPIS Semiconductor IOH(Input/
572 Output Hub), ML7213, ML7223 and ML7831.
573 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
574 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
575 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
576 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
579 tristate "EMMA Mobile series I2C adapter"
583 If you say yes to this option, support will be included for the
584 I2C interface on the Renesas Electronics EM/EV family of processors.
587 tristate "Exynos5 high-speed I2C driver"
588 depends on ARCH_EXYNOS && OF
591 High-speed I2C controller on Exynos5 based Samsung SoCs.
594 tristate "GPIO-based bitbanging I2C"
595 depends on GPIOLIB || COMPILE_TEST
598 This is a very simple bitbanging I2C driver utilizing the
599 arch-neutral GPIO API to control the SCL and SDA lines.
601 config I2C_HIGHLANDER
602 tristate "Highlander FPGA SMBus interface"
603 depends on SH_HIGHLANDER
605 If you say yes to this option, support will be included for
606 the SMBus interface located in the FPGA on various Highlander
607 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
608 FPGAs. This is wholly unrelated to the SoC I2C.
610 This driver can also be built as a module. If so, the module
611 will be called i2c-highlander.
614 tristate "IBM PPC 4xx on-chip I2C interface"
617 Say Y here if you want to use IIC peripheral found on
618 embedded IBM PPC 4xx based systems.
620 This driver can also be built as a module. If so, the module
621 will be called i2c-ibm_iic.
624 tristate "Imagination Technologies I2C SCB Controller"
625 depends on MIPS || METAG || COMPILE_TEST
627 Say Y here if you want to use the IMG I2C SCB controller,
628 available on the TZ1090 and other IMG SoCs.
630 This driver can also be built as a module. If so, the module
631 will be called i2c-img-scb.
634 tristate "IMX I2C interface"
635 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
637 Say Y here if you want to use the IIC bus controller on
638 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
640 This driver can also be built as a module. If so, the module
641 will be called i2c-imx.
644 tristate "IMX Low Power I2C interface"
645 depends on ARCH_MXC || COMPILE_TEST
647 Say Y here if you want to use the Low Power IIC bus controller
648 on the Freescale i.MX processors.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-imx-lpi2c.
654 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
655 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
657 Say Y here if you want to use the IIC bus controller on
658 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
660 This driver can also be built as a module. If so, the module
661 will be called i2c-iop3xx.
664 tristate "JZ4780 I2C controller interface support"
665 depends on MACH_JZ4780 || COMPILE_TEST
667 If you say yes to this option, support will be included for the
668 Ingenic JZ4780 I2C controller.
670 If you don't know what to do here, say N.
673 tristate "Kontron COM I2C Controller"
674 depends on MFD_KEMPLD
676 This enables support for the I2C bus interface on some Kontron ETX
677 and COMexpress (ETXexpress) modules.
679 This driver can also be built as a module. If so, the module
680 will be called i2c-kempld.
683 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
684 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
686 This driver supports the I2C interface found several NXP
687 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
689 This driver can also be built as a module. If so, the module
690 will be called i2c-lpc2k.
693 tristate "Amlogic Meson I2C controller"
694 depends on ARCH_MESON || COMPILE_TEST
696 If you say yes to this option, support will be included for the
697 I2C interface on the Amlogic Meson family of SoCs.
700 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
703 If you say yes to this option, support will be included for the
704 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
705 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
707 This driver can also be built as a module. If so, the module
708 will be called i2c-mpc.
711 tristate "MediaTek I2C adapter"
712 depends on ARCH_MEDIATEK || COMPILE_TEST
715 This selects the MediaTek(R) Integrated Inter Circuit bus driver
716 for MT65xx and MT81xx.
717 If you want to use MediaTek(R) I2C interface, say Y or M here.
721 tristate "Marvell mv64xxx I2C Controller"
722 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
724 If you say yes to this option, support will be included for the
725 built-in I2C interface on the Marvell 64xxx line of host bridges.
726 This driver is also used for Allwinner SoCs I2C controllers.
728 This driver can also be built as a module. If so, the module
729 will be called i2c-mv64xxx.
732 tristate "Freescale i.MX28 I2C interface"
736 Say Y here if you want to use the I2C bus controller on
737 the Freescale i.MX28 processors.
739 This driver can also be built as a module. If so, the module
740 will be called i2c-mxs.
743 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
746 If you say yes to this option, support will be included for the
747 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
748 as well as the STA2X11 PCIe I/O HUB.
751 tristate "OpenCores I2C Controller"
753 If you say yes to this option, support will be included for the
754 OpenCores I2C controller. For details see
755 http://www.opencores.org/projects.cgi/web/i2c/overview
757 This driver can also be built as a module. If so, the module
758 will be called i2c-ocores.
761 tristate "OMAP I2C adapter"
763 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
765 If you say yes to this option, support will be included for the
766 I2C interface on the Texas Instruments OMAP1/2 family of processors.
767 Like OMAP1510/1610/1710/5912 and OMAP242x.
768 For details see http://www.ti.com/omap.
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 QUP based I2C controller"
840 If you say yes to this option, support will be included for the
841 built-in I2C interface on the Qualcomm SoCs.
843 This driver can also be built as a module. If so, the module
844 will be called i2c-qup.
847 tristate "Renesas RIIC adapter"
848 depends on ARCH_RENESAS || COMPILE_TEST
850 If you say yes to this option, support will be included for the
851 Renesas RIIC I2C interface.
853 This driver can also be built as a module. If so, the module
854 will be called i2c-riic.
857 tristate "Rockchip RK3xxx I2C adapter"
858 depends on OF && COMMON_CLK
860 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
863 This driver can also be built as a module. If so, the module will
866 config HAVE_S3C2410_I2C
869 This will include I2C support for Samsung SoCs. If you want to
870 include I2C support for any machine, kindly select this in the
871 respective Kconfig file.
874 tristate "S3C2410 I2C Driver"
875 depends on HAVE_S3C2410_I2C
877 Say Y here to include support for I2C controller in the
881 tristate "Renesas SH7760 I2C Controller"
882 depends on CPU_SUBTYPE_SH7760
884 This driver supports the 2 I2C interfaces on the Renesas SH7760.
886 This driver can also be built as a module. If so, the module
887 will be called i2c-sh7760.
890 tristate "SuperH Mobile I2C Controller"
892 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
894 If you say yes to this option, support will be included for the
895 built-in I2C interface on the Renesas SH-Mobile processor.
897 This driver can also be built as a module. If so, the module
898 will be called i2c-sh_mobile.
901 tristate "Simtec Generic I2C interface"
904 If you say yes to this option, support will be included for
905 the Simtec Generic I2C interface. This driver is for the
906 simple I2C bus used on newer Simtec products for general
907 I2C, such as DDC on the Simtec BBD2016A.
909 This driver can also be built as a module. If so, the module
910 will be called i2c-simtec.
913 tristate "CSR SiRFprimaII I2C interface"
916 If you say yes to this option, support will be included for the
917 CSR SiRFprimaII I2C interface.
919 This driver can also be built as a module. If so, the module
920 will be called i2c-sirf.
923 bool "Spreadtrum I2C interface"
924 depends on I2C=y && ARCH_SPRD
926 If you say yes to this option, support will be included for the
927 Spreadtrum I2C interface.
930 tristate "STMicroelectronics SSC I2C support"
933 Enable this option to add support for STMicroelectronics SoCs
934 hardware SSC (Synchronous Serial Controller) as an I2C controller.
936 This driver can also be built as module. If so, the module
937 will be called i2c-st.
940 tristate "STMicroelectronics STM32F4 I2C support"
941 depends on ARCH_STM32 || COMPILE_TEST
943 Enable this option to add support for STM32 I2C controller embedded
946 This driver can also be built as module. If so, the module
947 will be called i2c-stm32f4.
950 tristate "STMicroelectronics STM32F7 I2C support"
951 depends on ARCH_STM32 || COMPILE_TEST
953 Enable this option to add support for STM32 I2C controller embedded
956 This driver can also be built as module. If so, the module
957 will be called i2c-stm32f7.
960 tristate "ST Microelectronics DDC I2C interface"
962 default y if MACH_U300
964 If you say yes to this option, support will be included for the
965 I2C interface from ST Microelectronics simply called "DDC I2C"
966 supporting both I2C and DDC, used in e.g. the U300 series
969 This driver can also be built as a module. If so, the module
970 will be called i2c-stu300.
972 config I2C_SUN6I_P2WI
973 tristate "Allwinner sun6i internal P2WI controller"
974 depends on RESET_CONTROLLER
975 depends on MACH_SUN6I || COMPILE_TEST
977 If you say yes to this option, support will be included for the
978 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
980 The P2WI looks like an SMBus controller (which supports only byte
981 accesses), except that it only supports one slave device.
982 This interface is used to connect to specific PMIC devices (like the
986 tristate "NVIDIA Tegra internal I2C controller"
987 depends on ARCH_TEGRA
989 If you say yes to this option, support will be included for the
990 I2C controller embedded in NVIDIA Tegra SOCs
992 config I2C_TEGRA_BPMP
993 tristate "NVIDIA Tegra BPMP I2C controller"
994 depends on TEGRA_BPMP
997 If you say yes to this option, support will be included for the I2C
998 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP.
1000 This I2C driver is a 'virtual' I2C driver. The real driver is part
1001 of the BPMP firmware, and this driver merely communicates with that
1005 tristate "UniPhier FIFO-less I2C controller"
1006 depends on ARCH_UNIPHIER || COMPILE_TEST
1008 If you say yes to this option, support will be included for
1009 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
1010 or older UniPhier SoCs.
1012 config I2C_UNIPHIER_F
1013 tristate "UniPhier FIFO-builtin I2C controller"
1014 depends on ARCH_UNIPHIER || COMPILE_TEST
1016 If you say yes to this option, support will be included for
1017 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
1018 PH1-Pro5, or newer UniPhier SoCs.
1020 config I2C_VERSATILE
1021 tristate "ARM Versatile/Realview I2C bus support"
1022 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
1025 Say yes if you want to support the I2C serial bus on ARMs Versatile
1028 This driver can also be built as a module. If so, the module
1029 will be called i2c-versatile.
1032 tristate "Wondermedia WM8xxx SoC I2C bus support"
1033 depends on ARCH_VT8500
1035 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
1038 This driver can also be built as a module. If so, the module will be
1042 tristate "Cavium OCTEON I2C bus support"
1043 depends on CAVIUM_OCTEON_SOC
1045 Say yes if you want to support the I2C serial bus on Cavium
1048 This driver can also be built as a module. If so, the module
1049 will be called i2c-octeon.
1052 tristate "Cavium ThunderX I2C bus support"
1053 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
1056 Say yes if you want to support the I2C serial bus on Cavium
1059 This driver can also be built as a module. If so, the module
1060 will be called i2c-thunderx.
1063 tristate "Xilinx I2C Controller"
1064 depends on HAS_IOMEM
1066 If you say yes to this option, support will be included for the
1067 Xilinx I2C controller.
1069 This driver can also be built as a module. If so, the module
1070 will be called xilinx_i2c.
1073 tristate "Netlogic XLR and Sigma Designs I2C support"
1074 depends on CPU_XLR || ARCH_TANGO
1076 This driver enables support for the on-chip I2C interface of
1077 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
1079 This driver can also be built as a module. If so, the module
1080 will be called i2c-xlr.
1083 tristate "XLP9XX I2C support"
1084 depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
1086 This driver enables support for the on-chip I2C interface of
1087 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
1089 This driver can also be built as a module. If so, the module will
1090 be called i2c-xlp9xx.
1093 tristate "Renesas R-Car I2C Controller"
1095 depends on ARCH_RENESAS || COMPILE_TEST
1098 If you say yes to this option, support will be included for the
1099 R-Car I2C controller.
1101 This driver can also be built as a module. If so, the module
1102 will be called i2c-rcar.
1104 comment "External I2C/SMBus adapter drivers"
1106 config I2C_DIOLAN_U2C
1107 tristate "Diolan U2C-12 USB adapter"
1110 If you say yes to this option, support will be included for Diolan
1111 U2C-12, a USB to I2C interface.
1113 This driver can also be built as a module. If so, the module
1114 will be called i2c-diolan-u2c.
1117 tristate "Diolan DLN-2 USB I2C adapter"
1120 If you say yes to this option, support will be included for Diolan
1121 DLN2, a USB to I2C interface.
1123 This driver can also be built as a module. If so, the module
1124 will be called i2c-dln2.
1127 tristate "Parallel port adapter"
1132 This supports parallel port I2C adapters such as the ones made by
1133 Philips or Velleman, Analog Devices evaluation boards, and more.
1134 Basically any adapter using the parallel port as an I2C bus with
1135 no extra chipset is supported by this driver, or could be.
1137 This driver is a replacement for (and was inspired by) an older
1138 driver named i2c-philips-par. The new driver supports more devices,
1139 and makes it easier to add support for new devices.
1141 An adapter type parameter is now mandatory. Please read the file
1142 Documentation/i2c/busses/i2c-parport for details.
1144 Another driver exists, named i2c-parport-light, which doesn't depend
1145 on the parport driver. This is meant for embedded systems. Don't say
1146 Y here if you intend to say Y or M there.
1148 This support is also available as a module. If so, the module
1149 will be called i2c-parport.
1151 config I2C_PARPORT_LIGHT
1152 tristate "Parallel port adapter (light)"
1156 This supports parallel port I2C adapters such as the ones made by
1157 Philips or Velleman, Analog Devices evaluation boards, and more.
1158 Basically any adapter using the parallel port as an I2C bus with
1159 no extra chipset is supported by this driver, or could be.
1161 This driver is a light version of i2c-parport. It doesn't depend
1162 on the parport driver, and uses direct I/O access instead. This
1163 might be preferred on embedded systems where wasting memory for
1164 the clean but heavy parport handling is not an option. The
1165 drawback is a reduced portability and the impossibility to
1166 daisy-chain other parallel port devices.
1168 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1169 both is possible but both modules should not be loaded at the same
1172 This support is also available as a module. If so, the module
1173 will be called i2c-parport-light.
1175 config I2C_ROBOTFUZZ_OSIF
1176 tristate "RobotFuzz Open Source InterFace USB adapter"
1179 If you say yes to this option, support will be included for the
1180 RobotFuzz Open Source InterFace USB to I2C interface.
1182 This driver can also be built as a module. If so, the module
1183 will be called i2c-osif.
1186 tristate "TAOS evaluation module"
1189 select SERIO_SERPORT
1192 This supports TAOS evaluation modules on serial port. In order to
1193 use this driver, you will need the inputattach tool, which is part
1194 of the input-utils package.
1198 This support is also available as a module. If so, the module
1199 will be called i2c-taos-evm.
1202 tristate "Tiny-USB adapter"
1205 If you say yes to this option, support will be included for the
1206 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1207 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1209 This driver can also be built as a module. If so, the module
1210 will be called i2c-tiny-usb.
1212 config I2C_VIPERBOARD
1213 tristate "Viperboard I2C master support"
1214 depends on MFD_VIPERBOARD && USB
1216 Say yes here to access the I2C part of the Nano River
1217 Technologies Viperboard as I2C master.
1218 See viperboard API specification and Nano
1219 River Tech's viperboard.h for detailed meaning
1220 of the module parameters.
1222 comment "Other I2C/SMBus bus drivers"
1225 tristate "Acorn IOC/IOMD I2C bus support"
1226 depends on ARCH_ACORN
1230 Say yes if you want to support the I2C bus on Acorn platforms.
1232 If you don't know, say Y.
1235 tristate "Elektor ISA card"
1236 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1239 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1242 This support is also available as a module. If so, the module
1243 will be called i2c-elektor.
1246 tristate "Mellanox I2C driver"
1249 This exposes the Mellanox platform I2C busses to the linux I2C layer
1250 for X86 based systems.
1251 Controller is implemented as CPLD logic.
1253 This driver can also be built as a module. If so, the module will be
1254 called as i2c-mlxcpld.
1257 tristate "PCA9564/PCA9665 on an ISA bus"
1262 This driver supports ISA boards using the Philips PCA9564/PCA9665
1263 parallel bus to I2C bus controller.
1265 This driver can also be built as a module. If so, the module
1266 will be called i2c-pca-isa.
1268 This device is almost undetectable and using this driver on a
1269 system which doesn't have this device will result in long
1270 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1271 time). If unsure, say N.
1274 tristate "SiByte SMBus interface"
1275 depends on SIBYTE_SB1xxx_SOC
1277 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1279 config I2C_CROS_EC_TUNNEL
1280 tristate "ChromeOS EC tunnel I2C bus"
1281 depends on MFD_CROS_EC
1283 If you say yes here you get an I2C bus that will tunnel i2c commands
1284 through to the other side of the ChromeOS EC to the i2c bus
1285 connected there. This will work whatever the interface used to
1286 talk to the EC (SPI, I2C or LPC).
1288 config I2C_XGENE_SLIMPRO
1289 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1290 depends on ARCH_XGENE && MAILBOX
1292 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1293 co-processor. The I2C device access the I2C bus via the X-Gene
1294 to SLIMpro (On chip coprocessor) mailbox mechanism.
1298 tristate "Geode ACCESS.bus support"
1299 depends on X86_32 && PCI
1301 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1302 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1304 If you don't know what to do here, say N.
1306 This support is also available as a module. If so, the module
1307 will be called scx200_acb.
1310 tristate "IBM OPAL I2C driver"
1311 depends on PPC_POWERNV
1314 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1315 the driver is based on the OPAL interfaces.
1317 This driver can also be built as a module. If so, the module will be
1321 tristate "ZTE ZX2967 I2C support"
1325 Selecting this option will add ZX2967 I2C driver.
1326 This driver can also be built as a module. If so, the module will be