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_HIX5HD2 || COMPILE_TEST
84 Say Y here to include support for high-speed I2C controller in the
85 Hisilicon based 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
95 If you say yes to this option, support will be included for the Intel
96 801 family of mainboard I2C interfaces. Specifically, the following
97 versions of the chipset are supported:
103 82801EB/ER (ICH5/ICH5R)
123 Wildcat Point-LP (PCH)
125 Sunrise Point-H (PCH)
126 Sunrise Point-LP (PCH)
128 This driver can also be built as a module. If so, the module
129 will be called i2c-i801.
132 tristate "Intel SCH SMBus 1.0"
136 Say Y here if you want to use SMBus controller on the Intel SCH
139 This driver can also be built as a module. If so, the module
140 will be called i2c-isch.
143 tristate "Intel iSMT SMBus Controller"
144 depends on PCI && X86
146 If you say yes to this option, support will be included for the Intel
147 iSMT SMBus host controller interface.
149 This driver can also be built as a module. If so, the module will be
153 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
156 If you say yes to this option, support will be included for the Intel
157 PIIX4 family of mainboard I2C interfaces. Specifically, the following
158 versions of the chipset are supported (note that Serverworks is part
178 Some AMD chipsets contain two PIIX4-compatible SMBus
179 controllers. This driver will attempt to use both controllers
180 on the SB700/SP5100, if they have been initialized by the BIOS.
182 This driver can also be built as a module. If so, the module
183 will be called i2c-piix4.
186 tristate "Nvidia nForce2, nForce3 and nForce4"
189 If you say yes to this option, support will be included for the Nvidia
190 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
192 This driver can also be built as a module. If so, the module
193 will be called i2c-nforce2.
195 config I2C_NFORCE2_S4985
196 tristate "SMBus multiplexing on the Tyan S4985"
197 depends on I2C_NFORCE2 && X86
199 Enabling this option will add specific SMBus support for the Tyan
200 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
201 over 4 different channels, where the various memory module EEPROMs
202 live. Saying yes here will give you access to these in addition
205 This driver can also be built as a module. If so, the module
206 will be called i2c-nforce2-s4985.
212 If you say yes to this option, support will be included for the
213 SiS5595 SMBus (a subset of I2C) interface.
215 This driver can also be built as a module. If so, the module
216 will be called i2c-sis5595.
219 tristate "SiS 630/730/964"
222 If you say yes to this option, support will be included for the
223 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
225 This driver can also be built as a module. If so, the module
226 will be called i2c-sis630.
232 If you say yes to this option, support will be included for the SiS
233 96x SMBus (a subset of I2C) interfaces. Specifically, the following
234 chipsets are supported:
243 This driver can also be built as a module. If so, the module
244 will be called i2c-sis96x.
247 tristate "VIA VT82C586B"
251 If you say yes to this option, support will be included for the VIA
252 82C586B I2C interface
254 This driver can also be built as a module. If so, the module
255 will be called i2c-via.
258 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
261 If you say yes to this option, support will be included for the VIA
262 VT82C596 and later SMBus interface. Specifically, the following
263 chipsets are supported:
276 This driver can also be built as a module. If so, the module
277 will be called i2c-viapro.
281 comment "ACPI drivers"
284 tristate "SMBus Control Method Interface"
286 This driver supports the SMBus Control Method Interface. It needs the
287 BIOS to declare ACPI control methods as described in the SMBus Control
288 Method Interface specification.
290 To compile this driver as a module, choose M here:
291 the module will be called i2c-scmi.
295 comment "Mac SMBus host controller drivers"
296 depends on PPC_CHRP || PPC_PMAC
299 tristate "CHRP Apple Hydra Mac I/O I2C interface"
300 depends on PCI && PPC_CHRP
303 This supports the use of the I2C interface in the Apple Hydra Mac
304 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
307 This support is also available as a module. If so, the module
308 will be called i2c-hydra.
311 tristate "Powermac I2C interface"
315 This exposes the various PowerMac i2c interfaces to the linux i2c
316 layer and to userland. It is used by various drivers on the PowerMac
317 platform, and should generally be enabled.
319 This support is also available as a module. If so, the module
320 will be called i2c-powermac.
322 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
325 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
328 This supports the use of the I2C interface on Atmel AT91
331 A serious problem is that there is no documented way to issue
332 repeated START conditions for more than two messages, as needed
333 to support combined I2C messages. Use the i2c-gpio driver
334 unless your system can cope with this limitation.
336 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
337 don't have clock stretching in transmission mode. For that reason,
338 you can encounter underrun issues causing premature stop sendings if
339 the latency to fill the transmission register is too long. If you
340 are facing this situation, use the i2c-gpio driver.
343 tristate "Au1550/Au1200/Au1300 SMBus interface"
344 depends on MIPS_ALCHEMY
346 If you say yes to this option, support will be included for the
347 Au1550/Au1200/Au1300 SMBus interface.
349 This driver can also be built as a module. If so, the module
350 will be called i2c-au1550.
353 tristate "Axxia I2C controller"
354 depends on ARCH_AXXIA || COMPILE_TEST
357 Say yes if you want to support the I2C bus on Axxia platforms.
359 Please note that this controller is limited to transfers of maximum
360 255 bytes in length. Any attempt to to a larger transfer will return
364 tristate "Broadcom BCM2835 I2C controller"
365 depends on ARCH_BCM2835
367 If you say yes to this option, support will be included for the
368 BCM2835 I2C controller.
370 If you don't know what to do here, say N.
372 This support is also available as a module. If so, the module
373 will be called i2c-bcm2835.
376 tristate "Broadcom iProc I2C controller"
377 depends on ARCH_BCM_IPROC || COMPILE_TEST
378 default ARCH_BCM_IPROC
380 If you say yes to this option, support will be included for the
381 Broadcom iProc I2C controller.
383 If you don't know what to do here, say N.
386 tristate "BCM Kona I2C adapter"
387 depends on ARCH_BCM_MOBILE
390 If you say yes to this option, support will be included for the
391 I2C interface on the Broadcom Kona family of processors.
393 If you do not need KONA I2C interface, say N.
396 tristate "BRCM Settop I2C controller"
397 depends on ARCH_BRCMSTB || COMPILE_TEST
400 If you say yes to this option, support will be included for the
401 I2C interface on the Broadcom Settop SoCs.
403 If you do not need I2C interface, say N.
405 config I2C_BLACKFIN_TWI
406 tristate "Blackfin TWI I2C support"
408 depends on !BF561 && !BF531 && !BF532 && !BF533
410 This is the I2C bus driver for Blackfin on-chip TWI interface.
412 This driver can also be built as a module. If so, the module
413 will be called i2c-bfin-twi.
415 config I2C_BLACKFIN_TWI_CLK_KHZ
416 int "Blackfin TWI I2C clock (kHz)"
417 depends on I2C_BLACKFIN_TWI
421 The unit of the TWI clock is kHz.
424 tristate "Cadence I2C Controller"
427 Say yes here to select Cadence I2C Host Controller. This controller is
428 e.g. used by Xilinx Zynq.
431 tristate "CBUS I2C driver"
432 depends on GPIOLIB || COMPILE_TEST
434 Support for CBUS access using I2C API. Mostly relevant for Nokia
435 Internet Tablets (770, N800 and N810).
437 This driver can also be built as a module. If so, the module
438 will be called i2c-cbus-gpio.
441 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
442 depends on CPM1 || CPM2
444 This supports the use of the I2C interface on Freescale
445 processors with CPM1 or CPM2.
447 This driver can also be built as a module. If so, the module
448 will be called i2c-cpm.
451 tristate "DaVinci I2C driver"
452 depends on ARCH_DAVINCI || ARCH_KEYSTONE
454 Support for TI DaVinci I2C controller driver.
456 This driver can also be built as a module. If so, the module
457 will be called i2c-davinci.
459 Please note that this driver might be needed to bring up other
460 devices such as DaVinci NIC.
461 For details please see http://www.ti.com/davinci
463 config I2C_DESIGNWARE_CORE
466 config I2C_DESIGNWARE_PLATFORM
467 tristate "Synopsys DesignWare Platform"
468 select I2C_DESIGNWARE_CORE
469 depends on (ACPI && COMMON_CLK) || !ACPI
471 If you say yes to this option, support will be included for the
472 Synopsys DesignWare I2C adapter. Only master mode is supported.
474 This driver can also be built as a module. If so, the module
475 will be called i2c-designware-platform.
477 config I2C_DESIGNWARE_PCI
478 tristate "Synopsys DesignWare PCI"
480 select I2C_DESIGNWARE_CORE
482 If you say yes to this option, support will be included for the
483 Synopsys DesignWare I2C adapter. Only master mode is supported.
485 This driver can also be built as a module. If so, the module
486 will be called i2c-designware-pci.
488 config I2C_DESIGNWARE_BAYTRAIL
489 bool "Intel Baytrail I2C semaphore support"
490 depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
492 This driver enables managed host access to the PMIC I2C bus on select
493 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
494 the host to request uninterrupted access to the PMIC's I2C bus from
495 the platform firmware controlling it. You should say Y if running on
496 a BayTrail system using the AXP288.
499 tristate "Conexant Digicolor I2C driver"
500 depends on ARCH_DIGICOLOR
502 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver.
504 This driver can also be built as a module. If so, the module
505 will be called i2c-digicolor.
508 tristate "EFM32 I2C controller"
509 depends on ARCH_EFM32 || COMPILE_TEST
511 This driver supports the i2c block found in Energy Micro's EFM32
515 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
516 depends on PCI && (X86_32 || COMPILE_TEST)
518 This driver is for PCH(Platform controller Hub) I2C of EG20T which
519 is an IOH(Input/Output Hub) for x86 embedded processor.
520 This driver can access PCH I2C bus device.
522 This driver also can be used for LAPIS Semiconductor IOH(Input/
523 Output Hub), ML7213, ML7223 and ML7831.
524 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
525 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
526 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
527 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
530 tristate "Exynos5 high-speed I2C driver"
531 depends on ARCH_EXYNOS && OF
534 High-speed I2C controller on Exynos5 based Samsung SoCs.
537 tristate "GPIO-based bitbanging I2C"
538 depends on GPIOLIB || COMPILE_TEST
541 This is a very simple bitbanging I2C driver utilizing the
542 arch-neutral GPIO API to control the SCL and SDA lines.
544 config I2C_HIGHLANDER
545 tristate "Highlander FPGA SMBus interface"
546 depends on SH_HIGHLANDER
548 If you say yes to this option, support will be included for
549 the SMBus interface located in the FPGA on various Highlander
550 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
551 FPGAs. This is wholly unrelated to the SoC I2C.
553 This driver can also be built as a module. If so, the module
554 will be called i2c-highlander.
557 tristate "IBM PPC 4xx on-chip I2C interface"
560 Say Y here if you want to use IIC peripheral found on
561 embedded IBM PPC 4xx based systems.
563 This driver can also be built as a module. If so, the module
564 will be called i2c-ibm_iic.
567 tristate "Imagination Technologies I2C SCB Controller"
568 depends on MIPS || METAG || COMPILE_TEST
570 Say Y here if you want to use the IMG I2C SCB controller,
571 available on the TZ1090 and other IMG SoCs.
573 This driver can also be built as a module. If so, the module
574 will be called i2c-img-scb.
577 tristate "IMX I2C interface"
580 Say Y here if you want to use the IIC bus controller on
581 the Freescale i.MX/MXC processors.
583 This driver can also be built as a module. If so, the module
584 will be called i2c-imx.
587 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
588 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
590 Say Y here if you want to use the IIC bus controller on
591 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
593 This driver can also be built as a module. If so, the module
594 will be called i2c-iop3xx.
597 tristate "JZ4780 I2C controller interface support"
598 depends on MACH_JZ4780 || COMPILE_TEST
600 If you say yes to this option, support will be included for the
601 Ingenic JZ4780 I2C controller.
603 If you don't know what to do here, say N.
606 tristate "Kontron COM I2C Controller"
607 depends on MFD_KEMPLD
609 This enables support for the I2C bus interface on some Kontron ETX
610 and COMexpress (ETXexpress) modules.
612 This driver can also be built as a module. If so, the module
613 will be called i2c-kempld.
616 tristate "Amlogic Meson I2C controller"
617 depends on ARCH_MESON
619 If you say yes to this option, support will be included for the
620 I2C interface on the Amlogic Meson family of SoCs.
623 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
626 If you say yes to this option, support will be included for the
627 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
628 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
630 This driver can also be built as a module. If so, the module
631 will be called i2c-mpc.
634 tristate "MediaTek I2C adapter"
635 depends on ARCH_MEDIATEK || COMPILE_TEST
637 This selects the MediaTek(R) Integrated Inter Circuit bus driver
638 for MT65xx and MT81xx.
639 If you want to use MediaTek(R) I2C interface, say Y or M here.
643 tristate "Marvell mv64xxx I2C Controller"
644 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
646 If you say yes to this option, support will be included for the
647 built-in I2C interface on the Marvell 64xxx line of host bridges.
648 This driver is also used for Allwinner SoCs I2C controllers.
650 This driver can also be built as a module. If so, the module
651 will be called i2c-mv64xxx.
654 tristate "Freescale i.MX28 I2C interface"
658 Say Y here if you want to use the I2C bus controller on
659 the Freescale i.MX28 processors.
661 This driver can also be built as a module. If so, the module
662 will be called i2c-mxs.
665 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
668 If you say yes to this option, support will be included for the
669 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
670 as well as the STA2X11 PCIe I/O HUB.
673 tristate "OpenCores I2C Controller"
675 If you say yes to this option, support will be included for the
676 OpenCores I2C controller. For details see
677 http://www.opencores.org/projects.cgi/web/i2c/overview
679 This driver can also be built as a module. If so, the module
680 will be called i2c-ocores.
683 tristate "OMAP I2C adapter"
685 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
687 If you say yes to this option, support will be included for the
688 I2C interface on the Texas Instruments OMAP1/2 family of processors.
689 Like OMAP1510/1610/1710/5912 and OMAP242x.
690 For details see http://www.ti.com/omap.
693 tristate "PA Semi SMBus interface"
694 depends on PPC_PASEMI && PCI
696 Supports the PA Semi PWRficient on-chip SMBus interfaces.
698 config I2C_PCA_PLATFORM
699 tristate "PCA9564/PCA9665 as platform device"
703 This driver supports a memory mapped Philips PCA9564/PCA9665
704 parallel bus to I2C bus controller.
706 This driver can also be built as a module. If so, the module
707 will be called i2c-pca-platform.
710 tristate "PMC MSP I2C TWI Controller"
713 This driver supports the PMC TWI controller on MSP devices.
715 This driver can also be built as module. If so, the module
716 will be called i2c-pmcmsp.
719 tristate "I2C bus support for Philips PNX and NXP LPC targets"
720 depends on ARCH_LPC32XX
722 This driver supports the Philips IP3204 I2C IP block master and/or
725 This driver can also be built as a module. If so, the module
726 will be called i2c-pnx.
729 tristate "PKUnity v3 I2C bus support"
730 depends on UNICORE32 && ARCH_PUV3
733 This driver supports the I2C IP inside the PKUnity-v3 SoC.
734 This I2C bus controller is under AMBA/AXI bus.
736 This driver can also be built as a module. If so, the module
737 will be called i2c-puv3.
740 tristate "Intel PXA2XX I2C adapter"
741 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
743 If you have devices in the PXA I2C bus, say yes to this option.
744 This driver can also be built as a module. If so, the module
745 will be called i2c-pxa.
748 def_bool I2C_PXA && X86_32 && PCI && OF
751 bool "Intel PXA2XX I2C Slave comms support"
752 depends on I2C_PXA && !X86_32
754 Support I2C slave mode communications on the PXA I2C bus. This
755 is necessary for systems where the PXA may be a target on the
759 tristate "Qualcomm QUP based I2C controller"
762 If you say yes to this option, support will be included for the
763 built-in I2C interface on the Qualcomm SoCs.
765 This driver can also be built as a module. If so, the module
766 will be called i2c-qup.
769 tristate "Renesas RIIC adapter"
770 depends on ARCH_SHMOBILE || COMPILE_TEST
772 If you say yes to this option, support will be included for the
773 Renesas RIIC I2C interface.
775 This driver can also be built as a module. If so, the module
776 will be called i2c-riic.
779 tristate "Rockchip RK3xxx I2C adapter"
780 depends on OF && COMMON_CLK
782 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
785 This driver can also be built as a module. If so, the module will
788 config HAVE_S3C2410_I2C
791 This will include I2C support for Samsung SoCs. If you want to
792 include I2C support for any machine, kindly select this in the
793 respective Kconfig file.
796 tristate "S3C2410 I2C Driver"
797 depends on HAVE_S3C2410_I2C
799 Say Y here to include support for I2C controller in the
803 tristate "Renesas SH7760 I2C Controller"
804 depends on CPU_SUBTYPE_SH7760
806 This driver supports the 2 I2C interfaces on the Renesas SH7760.
808 This driver can also be built as a module. If so, the module
809 will be called i2c-sh7760.
812 tristate "SuperH Mobile I2C Controller"
814 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
816 If you say yes to this option, support will be included for the
817 built-in I2C interface on the Renesas SH-Mobile processor.
819 This driver can also be built as a module. If so, the module
820 will be called i2c-sh_mobile.
823 tristate "Simtec Generic I2C interface"
826 If you say yes to this option, support will be included for
827 the Simtec Generic I2C interface. This driver is for the
828 simple I2C bus used on newer Simtec products for general
829 I2C, such as DDC on the Simtec BBD2016A.
831 This driver can also be built as a module. If so, the module
832 will be called i2c-simtec.
835 tristate "CSR SiRFprimaII I2C interface"
838 If you say yes to this option, support will be included for the
839 CSR SiRFprimaII I2C interface.
841 This driver can also be built as a module. If so, the module
842 will be called i2c-sirf.
845 tristate "STMicroelectronics SSC I2C support"
848 Enable this option to add support for STMicroelectronics SoCs
849 hardware SSC (Synchronous Serial Controller) as an I2C controller.
851 This driver can also be built as module. If so, the module
852 will be called i2c-st.
855 tristate "ST Microelectronics DDC I2C interface"
857 default y if MACH_U300
859 If you say yes to this option, support will be included for the
860 I2C interface from ST Microelectronics simply called "DDC I2C"
861 supporting both I2C and DDC, used in e.g. the U300 series
864 This driver can also be built as a module. If so, the module
865 will be called i2c-stu300.
867 config I2C_SUN6I_P2WI
868 tristate "Allwinner sun6i internal P2WI controller"
869 depends on RESET_CONTROLLER
870 depends on MACH_SUN6I || COMPILE_TEST
872 If you say yes to this option, support will be included for the
873 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
875 The P2WI looks like an SMBus controller (which supports only byte
876 accesses), except that it only supports one slave device.
877 This interface is used to connect to specific PMIC devices (like the
881 tristate "NVIDIA Tegra internal I2C controller"
882 depends on ARCH_TEGRA
884 If you say yes to this option, support will be included for the
885 I2C controller embedded in NVIDIA Tegra SOCs
888 tristate "ARM Versatile/Realview I2C bus support"
889 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
892 Say yes if you want to support the I2C serial bus on ARMs Versatile
895 This driver can also be built as a module. If so, the module
896 will be called i2c-versatile.
899 tristate "Wondermedia WM8xxx SoC I2C bus support"
900 depends on ARCH_VT8500
902 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
905 This driver can also be built as a module. If so, the module will be
909 tristate "Cavium OCTEON I2C bus support"
910 depends on CAVIUM_OCTEON_SOC
912 Say yes if you want to support the I2C serial bus on Cavium
915 This driver can also be built as a module. If so, the module
916 will be called i2c-octeon.
919 tristate "Xilinx I2C Controller"
922 If you say yes to this option, support will be included for the
923 Xilinx I2C controller.
925 This driver can also be built as a module. If so, the module
926 will be called xilinx_i2c.
929 tristate "XLR I2C support"
932 This driver enables support for the on-chip I2C interface of
933 the Netlogic XLR/XLS MIPS processors.
935 This driver can also be built as a module. If so, the module
936 will be called i2c-xlr.
939 tristate "XLP9XX I2C support"
940 depends on CPU_XLP || COMPILE_TEST
942 This driver enables support for the on-chip I2C interface of
943 the Broadcom XLP9xx/XLP5xx MIPS processors.
945 This driver can also be built as a module. If so, the module will
946 be called i2c-xlp9xx.
949 tristate "Renesas R-Car I2C Controller"
950 depends on ARCH_SHMOBILE || COMPILE_TEST
953 If you say yes to this option, support will be included for the
954 R-Car I2C controller.
956 This driver can also be built as a module. If so, the module
957 will be called i2c-rcar.
959 comment "External I2C/SMBus adapter drivers"
961 config I2C_DIOLAN_U2C
962 tristate "Diolan U2C-12 USB adapter"
965 If you say yes to this option, support will be included for Diolan
966 U2C-12, a USB to I2C interface.
968 This driver can also be built as a module. If so, the module
969 will be called i2c-diolan-u2c.
972 tristate "Diolan DLN-2 USB I2C adapter"
975 If you say yes to this option, support will be included for Diolan
976 DLN2, a USB to I2C interface.
978 This driver can also be built as a module. If so, the module
979 will be called i2c-dln2.
982 tristate "Parallel port adapter"
987 This supports parallel port I2C adapters such as the ones made by
988 Philips or Velleman, Analog Devices evaluation boards, and more.
989 Basically any adapter using the parallel port as an I2C bus with
990 no extra chipset is supported by this driver, or could be.
992 This driver is a replacement for (and was inspired by) an older
993 driver named i2c-philips-par. The new driver supports more devices,
994 and makes it easier to add support for new devices.
996 An adapter type parameter is now mandatory. Please read the file
997 Documentation/i2c/busses/i2c-parport for details.
999 Another driver exists, named i2c-parport-light, which doesn't depend
1000 on the parport driver. This is meant for embedded systems. Don't say
1001 Y here if you intend to say Y or M there.
1003 This support is also available as a module. If so, the module
1004 will be called i2c-parport.
1006 config I2C_PARPORT_LIGHT
1007 tristate "Parallel port adapter (light)"
1011 This supports parallel port I2C adapters such as the ones made by
1012 Philips or Velleman, Analog Devices evaluation boards, and more.
1013 Basically any adapter using the parallel port as an I2C bus with
1014 no extra chipset is supported by this driver, or could be.
1016 This driver is a light version of i2c-parport. It doesn't depend
1017 on the parport driver, and uses direct I/O access instead. This
1018 might be preferred on embedded systems where wasting memory for
1019 the clean but heavy parport handling is not an option. The
1020 drawback is a reduced portability and the impossibility to
1021 daisy-chain other parallel port devices.
1023 Don't say Y here if you said Y or M to i2c-parport. Saying M to
1024 both is possible but both modules should not be loaded at the same
1027 This support is also available as a module. If so, the module
1028 will be called i2c-parport-light.
1030 config I2C_ROBOTFUZZ_OSIF
1031 tristate "RobotFuzz Open Source InterFace USB adapter"
1034 If you say yes to this option, support will be included for the
1035 RobotFuzz Open Source InterFace USB to I2C interface.
1037 This driver can also be built as a module. If so, the module
1038 will be called i2c-osif.
1041 tristate "TAOS evaluation module"
1044 select SERIO_SERPORT
1047 This supports TAOS evaluation modules on serial port. In order to
1048 use this driver, you will need the inputattach tool, which is part
1049 of the input-utils package.
1053 This support is also available as a module. If so, the module
1054 will be called i2c-taos-evm.
1057 tristate "Tiny-USB adapter"
1060 If you say yes to this option, support will be included for the
1061 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1062 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1064 This driver can also be built as a module. If so, the module
1065 will be called i2c-tiny-usb.
1067 config I2C_VIPERBOARD
1068 tristate "Viperboard I2C master support"
1069 depends on MFD_VIPERBOARD && USB
1071 Say yes here to access the I2C part of the Nano River
1072 Technologies Viperboard as I2C master.
1073 See viperboard API specification and Nano
1074 River Tech's viperboard.h for detailed meaning
1075 of the module parameters.
1077 comment "Other I2C/SMBus bus drivers"
1080 tristate "Acorn IOC/IOMD I2C bus support"
1081 depends on ARCH_ACORN
1085 Say yes if you want to support the I2C bus on Acorn platforms.
1087 If you don't know, say Y.
1090 tristate "Elektor ISA card"
1091 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1094 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1097 This support is also available as a module. If so, the module
1098 will be called i2c-elektor.
1101 tristate "PCA9564/PCA9665 on an ISA bus"
1106 This driver supports ISA boards using the Philips PCA9564/PCA9665
1107 parallel bus to I2C bus controller.
1109 This driver can also be built as a module. If so, the module
1110 will be called i2c-pca-isa.
1112 This device is almost undetectable and using this driver on a
1113 system which doesn't have this device will result in long
1114 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1115 time). If unsure, say N.
1118 tristate "SiByte SMBus interface"
1119 depends on SIBYTE_SB1xxx_SOC
1121 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1123 config I2C_CROS_EC_TUNNEL
1124 tristate "ChromeOS EC tunnel I2C bus"
1125 depends on CROS_EC_PROTO
1127 If you say yes here you get an I2C bus that will tunnel i2c commands
1128 through to the other side of the ChromeOS EC to the i2c bus
1129 connected there. This will work whatever the interface used to
1130 talk to the EC (SPI, I2C or LPC).
1132 config I2C_XGENE_SLIMPRO
1133 tristate "APM X-Gene SoC I2C SLIMpro devices support"
1134 depends on ARCH_XGENE && MAILBOX
1136 Enable I2C bus access using the APM X-Gene SoC SLIMpro
1137 co-processor. The I2C device access the I2C bus via the X-Gene
1138 to SLIMpro (On chip coprocessor) mailbox mechanism.
1142 tristate "Geode ACCESS.bus support"
1143 depends on X86_32 && PCI
1145 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1146 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1148 If you don't know what to do here, say N.
1150 This support is also available as a module. If so, the module
1151 will be called scx200_acb.
1154 tristate "IBM OPAL I2C driver"
1155 depends on PPC_POWERNV
1158 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1159 the driver is based on the OPAL interfaces.
1161 This driver can also be built as a module. If so, the module will be