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)
132 This driver can also be built as a module. If so, the module
133 will be called i2c-i801.
136 tristate "Intel SCH SMBus 1.0"
140 Say Y here if you want to use SMBus controller on the Intel SCH
143 This driver can also be built as a module. If so, the module
144 will be called i2c-isch.
147 tristate "Intel iSMT SMBus Controller"
148 depends on PCI && X86
150 If you say yes to this option, support will be included for the Intel
151 iSMT SMBus host controller interface.
153 This driver can also be built as a module. If so, the module will be
157 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
160 If you say yes to this option, support will be included for the Intel
161 PIIX4 family of mainboard I2C interfaces. Specifically, the following
162 versions of the chipset are supported (note that Serverworks is part
182 Some AMD chipsets contain two PIIX4-compatible SMBus
183 controllers. This driver will attempt to use both controllers
184 on the SB700/SP5100, if they have been initialized by the BIOS.
186 This driver can also be built as a module. If so, the module
187 will be called i2c-piix4.
190 tristate "Nvidia nForce2, nForce3 and nForce4"
193 If you say yes to this option, support will be included for the Nvidia
194 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
196 This driver can also be built as a module. If so, the module
197 will be called i2c-nforce2.
199 config I2C_NFORCE2_S4985
200 tristate "SMBus multiplexing on the Tyan S4985"
201 depends on I2C_NFORCE2 && X86
203 Enabling this option will add specific SMBus support for the Tyan
204 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
205 over 4 different channels, where the various memory module EEPROMs
206 live. Saying yes here will give you access to these in addition
209 This driver can also be built as a module. If so, the module
210 will be called i2c-nforce2-s4985.
216 If you say yes to this option, support will be included for the
217 SiS5595 SMBus (a subset of I2C) interface.
219 This driver can also be built as a module. If so, the module
220 will be called i2c-sis5595.
223 tristate "SiS 630/730/964"
226 If you say yes to this option, support will be included for the
227 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
229 This driver can also be built as a module. If so, the module
230 will be called i2c-sis630.
236 If you say yes to this option, support will be included for the SiS
237 96x SMBus (a subset of I2C) interfaces. Specifically, the following
238 chipsets are supported:
247 This driver can also be built as a module. If so, the module
248 will be called i2c-sis96x.
251 tristate "VIA VT82C586B"
255 If you say yes to this option, support will be included for the VIA
256 82C586B I2C interface
258 This driver can also be built as a module. If so, the module
259 will be called i2c-via.
262 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
265 If you say yes to this option, support will be included for the VIA
266 VT82C596 and later SMBus interface. Specifically, the following
267 chipsets are supported:
280 This driver can also be built as a module. If so, the module
281 will be called i2c-viapro.
285 comment "ACPI drivers"
288 tristate "SMBus Control Method Interface"
290 This driver supports the SMBus Control Method Interface. It needs the
291 BIOS to declare ACPI control methods as described in the SMBus Control
292 Method Interface specification.
294 To compile this driver as a module, choose M here:
295 the module will be called i2c-scmi.
299 comment "Mac SMBus host controller drivers"
300 depends on PPC_CHRP || PPC_PMAC
303 tristate "CHRP Apple Hydra Mac I/O I2C interface"
304 depends on PCI && PPC_CHRP
307 This supports the use of the I2C interface in the Apple Hydra Mac
308 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
311 This support is also available as a module. If so, the module
312 will be called i2c-hydra.
315 tristate "Powermac I2C interface"
319 This exposes the various PowerMac i2c interfaces to the linux i2c
320 layer and to userland. It is used by various drivers on the PowerMac
321 platform, and should generally be enabled.
323 This support is also available as a module. If so, the module
324 will be called i2c-powermac.
326 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
329 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
332 This supports the use of the I2C interface on Atmel AT91
335 A serious problem is that there is no documented way to issue
336 repeated START conditions for more than two messages, as needed
337 to support combined I2C messages. Use the i2c-gpio driver
338 unless your system can cope with this limitation.
340 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
341 don't have clock stretching in transmission mode. For that reason,
342 you can encounter underrun issues causing premature stop sendings if
343 the latency to fill the transmission register is too long. If you
344 are facing this situation, use the i2c-gpio driver.
347 tristate "Au1550/Au1200/Au1300 SMBus interface"
348 depends on MIPS_ALCHEMY
350 If you say yes to this option, support will be included for the
351 Au1550/Au1200/Au1300 SMBus interface.
353 This driver can also be built as a module. If so, the module
354 will be called i2c-au1550.
357 tristate "Axxia I2C controller"
358 depends on ARCH_AXXIA || COMPILE_TEST
361 Say yes if you want to support the I2C bus on Axxia platforms.
363 Please note that this controller is limited to transfers of maximum
364 255 bytes in length. Any attempt to to a larger transfer will return
368 tristate "Broadcom BCM2835 I2C controller"
369 depends on ARCH_BCM2835
371 If you say yes to this option, support will be included for the
372 BCM2835 I2C controller.
374 If you don't know what to do here, say N.
376 This support is also available as a module. If so, the module
377 will be called i2c-bcm2835.
380 tristate "Broadcom iProc I2C controller"
381 depends on ARCH_BCM_IPROC || COMPILE_TEST
382 default ARCH_BCM_IPROC
384 If you say yes to this option, support will be included for the
385 Broadcom iProc I2C controller.
387 If you don't know what to do here, say N.
390 tristate "BCM Kona I2C adapter"
391 depends on ARCH_BCM_MOBILE
394 If you say yes to this option, support will be included for the
395 I2C interface on the Broadcom Kona family of processors.
397 If you do not need KONA I2C interface, say N.
400 tristate "BRCM Settop/DSL I2C controller"
401 depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
405 If you say yes to this option, support will be included for the
406 I2C interface on the Broadcom Settop/DSL SoCs.
408 If you do not need I2C interface, say N.
410 config I2C_BLACKFIN_TWI
411 tristate "Blackfin TWI I2C support"
413 depends on !BF561 && !BF531 && !BF532 && !BF533
415 This is the I2C bus driver for Blackfin on-chip TWI interface.
417 This driver can also be built as a module. If so, the module
418 will be called i2c-bfin-twi.
420 config I2C_BLACKFIN_TWI_CLK_KHZ
421 int "Blackfin TWI I2C clock (kHz)"
422 depends on I2C_BLACKFIN_TWI
426 The unit of the TWI clock is kHz.
429 tristate "Cadence I2C Controller"
430 depends on ARCH_ZYNQ || ARM64
432 Say yes here to select Cadence I2C Host Controller. This controller is
433 e.g. used by Xilinx Zynq.
436 tristate "CBUS I2C driver"
437 depends on GPIOLIB || COMPILE_TEST
439 Support for CBUS access using I2C API. Mostly relevant for Nokia
440 Internet Tablets (770, N800 and N810).
442 This driver can also be built as a module. If so, the module
443 will be called i2c-cbus-gpio.
446 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
447 depends on CPM1 || CPM2
449 This supports the use of the I2C interface on Freescale
450 processors with CPM1 or CPM2.
452 This driver can also be built as a module. If so, the module
453 will be called i2c-cpm.
456 tristate "DaVinci I2C driver"
457 depends on ARCH_DAVINCI || ARCH_KEYSTONE
459 Support for TI DaVinci I2C controller driver.
461 This driver can also be built as a module. If so, the module
462 will be called i2c-davinci.
464 Please note that this driver might be needed to bring up other
465 devices such as DaVinci NIC.
466 For details please see http://www.ti.com/davinci
468 config I2C_DESIGNWARE_CORE
471 config I2C_DESIGNWARE_PLATFORM
472 tristate "Synopsys DesignWare Platform"
473 select I2C_DESIGNWARE_CORE
474 depends on (ACPI && COMMON_CLK) || !ACPI
476 If you say yes to this option, support will be included for the
477 Synopsys DesignWare I2C adapter. Only master mode is supported.
479 This driver can also be built as a module. If so, the module
480 will be called i2c-designware-platform.
482 config I2C_DESIGNWARE_PCI
483 tristate "Synopsys DesignWare PCI"
485 select I2C_DESIGNWARE_CORE
487 If you say yes to this option, support will be included for the
488 Synopsys DesignWare I2C adapter. Only master mode is supported.
490 This driver can also be built as a module. If so, the module
491 will be called i2c-designware-pci.
493 config I2C_DESIGNWARE_BAYTRAIL
494 bool "Intel Baytrail I2C semaphore support"
496 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \
497 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y)
499 This driver enables managed host access to the PMIC I2C bus on select
500 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
501 the host to request uninterrupted access to the PMIC's I2C bus from
502 the platform firmware controlling it. You should say Y if running on
503 a BayTrail system using the AXP288.
506 tristate "Conexant Digicolor I2C driver"
507 depends on ARCH_DIGICOLOR
509 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
511 This driver can also be built as a module. If so, the module
512 will be called i2c-digicolor.
515 tristate "EFM32 I2C controller"
516 depends on ARCH_EFM32 || COMPILE_TEST
518 This driver supports the i2c block found in Energy Micro's EFM32
522 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
523 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
525 This driver is for PCH(Platform controller Hub) I2C of EG20T which
526 is an IOH(Input/Output Hub) for x86 embedded processor.
527 This driver can access PCH I2C bus device.
529 This driver also can be used for LAPIS Semiconductor IOH(Input/
530 Output Hub), ML7213, ML7223 and ML7831.
531 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
532 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
533 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
534 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
537 tristate "EMMA Mobile series I2C adapter"
541 If you say yes to this option, support will be included for the
542 I2C interface on the Renesas Electronics EM/EV family of processors.
545 tristate "Exynos5 high-speed I2C driver"
546 depends on ARCH_EXYNOS && OF
549 High-speed I2C controller on Exynos5 based Samsung SoCs.
552 tristate "GPIO-based bitbanging I2C"
553 depends on GPIOLIB || COMPILE_TEST
556 This is a very simple bitbanging I2C driver utilizing the
557 arch-neutral GPIO API to control the SCL and SDA lines.
559 config I2C_HIGHLANDER
560 tristate "Highlander FPGA SMBus interface"
561 depends on SH_HIGHLANDER
563 If you say yes to this option, support will be included for
564 the SMBus interface located in the FPGA on various Highlander
565 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
566 FPGAs. This is wholly unrelated to the SoC I2C.
568 This driver can also be built as a module. If so, the module
569 will be called i2c-highlander.
572 tristate "IBM PPC 4xx on-chip I2C interface"
575 Say Y here if you want to use IIC peripheral found on
576 embedded IBM PPC 4xx based systems.
578 This driver can also be built as a module. If so, the module
579 will be called i2c-ibm_iic.
582 tristate "Imagination Technologies I2C SCB Controller"
583 depends on MIPS || METAG || COMPILE_TEST
585 Say Y here if you want to use the IMG I2C SCB controller,
586 available on the TZ1090 and other IMG SoCs.
588 This driver can also be built as a module. If so, the module
589 will be called i2c-img-scb.
592 tristate "IMX I2C interface"
593 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
595 Say Y here if you want to use the IIC bus controller on
596 the Freescale i.MX/MXC, Layerscape or ColdFire processors.
598 This driver can also be built as a module. If so, the module
599 will be called i2c-imx.
602 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
603 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
605 Say Y here if you want to use the IIC bus controller on
606 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
608 This driver can also be built as a module. If so, the module
609 will be called i2c-iop3xx.
612 tristate "JZ4780 I2C controller interface support"
613 depends on MACH_JZ4780 || COMPILE_TEST
615 If you say yes to this option, support will be included for the
616 Ingenic JZ4780 I2C controller.
618 If you don't know what to do here, say N.
621 tristate "Kontron COM I2C Controller"
622 depends on MFD_KEMPLD
624 This enables support for the I2C bus interface on some Kontron ETX
625 and COMexpress (ETXexpress) modules.
627 This driver can also be built as a module. If so, the module
628 will be called i2c-kempld.
631 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx"
632 depends on OF && (ARCH_LPC18XX || COMPILE_TEST)
634 This driver supports the I2C interface found several NXP
635 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx.
637 This driver can also be built as a module. If so, the module
638 will be called i2c-lpc2k.
641 tristate "Amlogic Meson I2C controller"
642 depends on ARCH_MESON || COMPILE_TEST
644 If you say yes to this option, support will be included for the
645 I2C interface on the Amlogic Meson family of SoCs.
648 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
651 If you say yes to this option, support will be included for the
652 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
653 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
655 This driver can also be built as a module. If so, the module
656 will be called i2c-mpc.
659 tristate "MediaTek I2C adapter"
660 depends on ARCH_MEDIATEK || COMPILE_TEST
663 This selects the MediaTek(R) Integrated Inter Circuit bus driver
664 for MT65xx and MT81xx.
665 If you want to use MediaTek(R) I2C interface, say Y or M here.
669 tristate "Marvell mv64xxx I2C Controller"
670 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU
672 If you say yes to this option, support will be included for the
673 built-in I2C interface on the Marvell 64xxx line of host bridges.
674 This driver is also used for Allwinner SoCs I2C controllers.
676 This driver can also be built as a module. If so, the module
677 will be called i2c-mv64xxx.
680 tristate "Freescale i.MX28 I2C interface"
684 Say Y here if you want to use the I2C bus controller on
685 the Freescale i.MX28 processors.
687 This driver can also be built as a module. If so, the module
688 will be called i2c-mxs.
691 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
694 If you say yes to this option, support will be included for the
695 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
696 as well as the STA2X11 PCIe I/O HUB.
699 tristate "OpenCores I2C Controller"
701 If you say yes to this option, support will be included for the
702 OpenCores I2C controller. For details see
703 http://www.opencores.org/projects.cgi/web/i2c/overview
705 This driver can also be built as a module. If so, the module
706 will be called i2c-ocores.
709 tristate "OMAP I2C adapter"
711 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
713 If you say yes to this option, support will be included for the
714 I2C interface on the Texas Instruments OMAP1/2 family of processors.
715 Like OMAP1510/1610/1710/5912 and OMAP242x.
716 For details see http://www.ti.com/omap.
719 tristate "PA Semi SMBus interface"
720 depends on PPC_PASEMI && PCI
722 Supports the PA Semi PWRficient on-chip SMBus interfaces.
724 config I2C_PCA_PLATFORM
725 tristate "PCA9564/PCA9665 as platform device"
729 This driver supports a memory mapped Philips PCA9564/PCA9665
730 parallel bus to I2C bus controller.
732 This driver can also be built as a module. If so, the module
733 will be called i2c-pca-platform.
736 tristate "PMC MSP I2C TWI Controller"
739 This driver supports the PMC TWI controller on MSP devices.
741 This driver can also be built as module. If so, the module
742 will be called i2c-pmcmsp.
745 tristate "I2C bus support for Philips PNX and NXP LPC targets"
746 depends on ARCH_LPC32XX
748 This driver supports the Philips IP3204 I2C IP block master and/or
751 This driver can also be built as a module. If so, the module
752 will be called i2c-pnx.
755 tristate "PKUnity v3 I2C bus support"
756 depends on UNICORE32 && ARCH_PUV3
759 This driver supports the I2C IP inside the PKUnity-v3 SoC.
760 This I2C bus controller is under AMBA/AXI bus.
762 This driver can also be built as a module. If so, the module
763 will be called i2c-puv3.
766 tristate "Intel PXA2XX I2C adapter"
767 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
769 If you have devices in the PXA I2C bus, say yes to this option.
770 This driver can also be built as a module. If so, the module
771 will be called i2c-pxa.
774 def_bool I2C_PXA && X86_32 && PCI && OF
777 bool "Intel PXA2XX I2C Slave comms support"
778 depends on I2C_PXA && !X86_32
780 Support I2C slave mode communications on the PXA I2C bus. This
781 is necessary for systems where the PXA may be a target on the
785 tristate "Qualcomm QUP based I2C controller"
786 depends on ARCH_QCOM || COMPILE_TEST
788 If you say yes to this option, support will be included for the
789 built-in I2C interface on the Qualcomm SoCs.
791 This driver can also be built as a module. If so, the module
792 will be called i2c-qup.
795 tristate "Renesas RIIC adapter"
796 depends on ARCH_RENESAS || COMPILE_TEST
798 If you say yes to this option, support will be included for the
799 Renesas RIIC I2C interface.
801 This driver can also be built as a module. If so, the module
802 will be called i2c-riic.
805 tristate "Rockchip RK3xxx I2C adapter"
806 depends on OF && COMMON_CLK
808 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
811 This driver can also be built as a module. If so, the module will
814 config HAVE_S3C2410_I2C
817 This will include I2C support for Samsung SoCs. If you want to
818 include I2C support for any machine, kindly select this in the
819 respective Kconfig file.
822 tristate "S3C2410 I2C Driver"
823 depends on HAVE_S3C2410_I2C
825 Say Y here to include support for I2C controller in the
829 tristate "Renesas SH7760 I2C Controller"
830 depends on CPU_SUBTYPE_SH7760
832 This driver supports the 2 I2C interfaces on the Renesas SH7760.
834 This driver can also be built as a module. If so, the module
835 will be called i2c-sh7760.
838 tristate "SuperH Mobile I2C Controller"
840 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
842 If you say yes to this option, support will be included for the
843 built-in I2C interface on the Renesas SH-Mobile processor.
845 This driver can also be built as a module. If so, the module
846 will be called i2c-sh_mobile.
849 tristate "Simtec Generic I2C interface"
852 If you say yes to this option, support will be included for
853 the Simtec Generic I2C interface. This driver is for the
854 simple I2C bus used on newer Simtec products for general
855 I2C, such as DDC on the Simtec BBD2016A.
857 This driver can also be built as a module. If so, the module
858 will be called i2c-simtec.
861 tristate "CSR SiRFprimaII I2C interface"
864 If you say yes to this option, support will be included for the
865 CSR SiRFprimaII I2C interface.
867 This driver can also be built as a module. If so, the module
868 will be called i2c-sirf.
871 tristate "STMicroelectronics SSC I2C support"
874 Enable this option to add support for STMicroelectronics SoCs
875 hardware SSC (Synchronous Serial Controller) as an I2C controller.
877 This driver can also be built as module. If so, the module
878 will be called i2c-st.
881 tristate "ST Microelectronics DDC I2C interface"
883 default y if MACH_U300
885 If you say yes to this option, support will be included for the
886 I2C interface from ST Microelectronics simply called "DDC I2C"
887 supporting both I2C and DDC, used in e.g. the U300 series
890 This driver can also be built as a module. If so, the module
891 will be called i2c-stu300.
893 config I2C_SUN6I_P2WI
894 tristate "Allwinner sun6i internal P2WI controller"
895 depends on RESET_CONTROLLER
896 depends on MACH_SUN6I || COMPILE_TEST
898 If you say yes to this option, support will be included for the
899 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
901 The P2WI looks like an SMBus controller (which supports only byte
902 accesses), except that it only supports one slave device.
903 This interface is used to connect to specific PMIC devices (like the
907 tristate "NVIDIA Tegra internal I2C controller"
908 depends on ARCH_TEGRA
910 If you say yes to this option, support will be included for the
911 I2C controller embedded in NVIDIA Tegra SOCs
914 tristate "UniPhier FIFO-less I2C controller"
915 depends on ARCH_UNIPHIER || COMPILE_TEST
917 If you say yes to this option, support will be included for
918 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8,
919 or older UniPhier SoCs.
921 config I2C_UNIPHIER_F
922 tristate "UniPhier FIFO-builtin I2C controller"
923 depends on ARCH_UNIPHIER || COMPILE_TEST
925 If you say yes to this option, support will be included for
926 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4,
927 PH1-Pro5, or newer UniPhier SoCs.
930 tristate "ARM Versatile/Realview I2C bus support"
931 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST
934 Say yes if you want to support the I2C serial bus on ARMs Versatile
937 This driver can also be built as a module. If so, the module
938 will be called i2c-versatile.
941 tristate "Wondermedia WM8xxx SoC I2C bus support"
942 depends on ARCH_VT8500
944 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
947 This driver can also be built as a module. If so, the module will be
951 tristate "Cavium OCTEON I2C bus support"
952 depends on CAVIUM_OCTEON_SOC
954 Say yes if you want to support the I2C serial bus on Cavium
957 This driver can also be built as a module. If so, the module
958 will be called i2c-octeon.
961 tristate "Cavium ThunderX I2C bus support"
962 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST)
965 Say yes if you want to support the I2C serial bus on Cavium
968 This driver can also be built as a module. If so, the module
969 will be called i2c-thunderx.
972 tristate "Xilinx I2C Controller"
975 If you say yes to this option, support will be included for the
976 Xilinx I2C controller.
978 This driver can also be built as a module. If so, the module
979 will be called xilinx_i2c.
982 tristate "Netlogic XLR and Sigma Designs I2C support"
983 depends on CPU_XLR || ARCH_TANGO
985 This driver enables support for the on-chip I2C interface of
986 the Netlogic XLR/XLS MIPS processors and Sigma Designs SOCs.
988 This driver can also be built as a module. If so, the module
989 will be called i2c-xlr.
992 tristate "XLP9XX I2C support"
993 depends on CPU_XLP || ARCH_VULCAN || COMPILE_TEST
995 This driver enables support for the on-chip I2C interface of
996 the Broadcom XLP9xx/XLP5xx MIPS and Vulcan ARM64 processors.
998 This driver can also be built as a module. If so, the module will
999 be called i2c-xlp9xx.
1002 tristate "Renesas R-Car I2C Controller"
1004 depends on ARCH_RENESAS || COMPILE_TEST
1007 If you say yes to this option, support will be included for the
1008 R-Car I2C controller.
1010 This driver can also be built as a module. If so, the module
1011 will be called i2c-rcar.
1013 comment "External I2C/SMBus adapter drivers"
1015 config I2C_DIOLAN_U2C
1016 tristate "Diolan U2C-12 USB adapter"
1019 If you say yes to this option, support will be included for Diolan
1020 U2C-12, a USB to I2C interface.
1022 This driver can also be built as a module. If so, the module
1023 will be called i2c-diolan-u2c.
1026 tristate "Diolan DLN-2 USB I2C adapter"
1029 If you say yes to this option, support will be included for Diolan
1030 DLN2, a USB to I2C interface.
1032 This driver can also be built as a module. If so, the module
1033 will be called i2c-dln2.
1036 tristate "Parallel port adapter"
1041 This supports parallel port I2C adapters such as the ones made by
1042 Philips or Velleman, Analog Devices evaluation boards, and more.
1043 Basically any adapter using the parallel port as an I2C bus with
1044 no extra chipset is supported by this driver, or could be.
1046 This driver is a replacement for (and was inspired by) an older
1047 driver named i2c-philips-par. The new driver supports more devices,
1048 and makes it easier to add support for new devices.
1050 An adapter type parameter is now mandatory. Please read the file
1051 Documentation/i2c/busses/i2c-parport for details.
1053 Another driver exists, named i2c-parport-light, which doesn't depend
1054 on the parport driver. This is meant for embedded systems. Don't say
1055 Y here if you intend to say Y or M there.
1057 This support is also available as a module. If so, the module
1058 will be called i2c-parport.
1060 config I2C_PARPORT_LIGHT
1061 tristate "Parallel port adapter (light)"
1065 This supports parallel port I2C adapters such as the ones made by
1066 Philips or Velleman, Analog Devices evaluation boards, and more.
1067 Basically any adapter using the parallel port as an I2C bus with
1068 no extra chipset is supported by this driver, or could be.
1070 This driver is a light version of i2c-parport. It doesn't depend
1071 on the parport driver, and uses direct I/O access instead. This
1072 might be preferred on embedded systems where wasting memory for
1073 the clean but heavy parport handling is not an option. The
1074 drawback is a reduced portability and the impossibility to
1075 daisy-chain other parallel port devices.
1077 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1078 both is possible but both modules should not be loaded at the same
1081 This support is also available as a module. If so, the module
1082 will be called i2c-parport-light.
1084 config I2C_ROBOTFUZZ_OSIF
1085 tristate "RobotFuzz Open Source InterFace USB adapter"
1088 If you say yes to this option, support will be included for the
1089 RobotFuzz Open Source InterFace USB to I2C interface.
1091 This driver can also be built as a module. If so, the module
1092 will be called i2c-osif.
1095 tristate "TAOS evaluation module"
1098 select SERIO_SERPORT
1101 This supports TAOS evaluation modules on serial port. In order to
1102 use this driver, you will need the inputattach tool, which is part
1103 of the input-utils package.
1107 This support is also available as a module. If so, the module
1108 will be called i2c-taos-evm.
1111 tristate "Tiny-USB adapter"
1114 If you say yes to this option, support will be included for the
1115 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1116 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1118 This driver can also be built as a module. If so, the module
1119 will be called i2c-tiny-usb.
1121 config I2C_VIPERBOARD
1122 tristate "Viperboard I2C master support"
1123 depends on MFD_VIPERBOARD && USB
1125 Say yes here to access the I2C part of the Nano River
1126 Technologies Viperboard as I2C master.
1127 See viperboard API specification and Nano
1128 River Tech's viperboard.h for detailed meaning
1129 of the module parameters.
1131 comment "Other I2C/SMBus bus drivers"
1134 tristate "Acorn IOC/IOMD I2C bus support"
1135 depends on ARCH_ACORN
1139 Say yes if you want to support the I2C bus on Acorn platforms.
1141 If you don't know, say Y.
1144 tristate "Elektor ISA card"
1145 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1148 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1151 This support is also available as a module. If so, the module
1152 will be called i2c-elektor.
1155 tristate "PCA9564/PCA9665 on an ISA bus"
1160 This driver supports ISA boards using the Philips PCA9564/PCA9665
1161 parallel bus to I2C bus controller.
1163 This driver can also be built as a module. If so, the module
1164 will be called i2c-pca-isa.
1166 This device is almost undetectable and using this driver on a
1167 system which doesn't have this device will result in long
1168 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1169 time). If unsure, say N.
1172 tristate "SiByte SMBus interface"
1173 depends on SIBYTE_SB1xxx_SOC
1175 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1177 config I2C_CROS_EC_TUNNEL
1178 tristate "ChromeOS EC tunnel I2C bus"
1179 depends on MFD_CROS_EC
1181 If you say yes here you get an I2C bus that will tunnel i2c commands
1182 through to the other side of the ChromeOS EC to the i2c bus
1183 connected there. This will work whatever the interface used to
1184 talk to the EC (SPI, I2C or LPC).
1186 config I2C_XGENE_SLIMPRO
1187 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1188 depends on ARCH_XGENE && MAILBOX
1190 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1191 co-processor. The I2C device access the I2C bus via the X-Gene
1192 to SLIMpro (On chip coprocessor) mailbox mechanism.
1196 tristate "Geode ACCESS.bus support"
1197 depends on X86_32 && PCI
1199 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1200 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1202 If you don't know what to do here, say N.
1204 This support is also available as a module. If so, the module
1205 will be called scx200_acb.
1208 tristate "IBM OPAL I2C driver"
1209 depends on PPC_POWERNV
1212 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1213 the driver is based on the OPAL interfaces.
1215 This driver can also be built as a module. If so, the module will be