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.
395 config I2C_BLACKFIN_TWI
396 tristate "Blackfin TWI I2C support"
398 depends on !BF561 && !BF531 && !BF532 && !BF533
400 This is the I2C bus driver for Blackfin on-chip TWI interface.
402 This driver can also be built as a module. If so, the module
403 will be called i2c-bfin-twi.
405 config I2C_BLACKFIN_TWI_CLK_KHZ
406 int "Blackfin TWI I2C clock (kHz)"
407 depends on I2C_BLACKFIN_TWI
411 The unit of the TWI clock is kHz.
414 tristate "Cadence I2C Controller"
417 Say yes here to select Cadence I2C Host Controller. This controller is
418 e.g. used by Xilinx Zynq.
421 tristate "CBUS I2C driver"
424 Support for CBUS access using I2C API. Mostly relevant for Nokia
425 Internet Tablets (770, N800 and N810).
427 This driver can also be built as a module. If so, the module
428 will be called i2c-cbus-gpio.
431 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
432 depends on CPM1 || CPM2
434 This supports the use of the I2C interface on Freescale
435 processors with CPM1 or CPM2.
437 This driver can also be built as a module. If so, the module
438 will be called i2c-cpm.
441 tristate "DaVinci I2C driver"
442 depends on ARCH_DAVINCI || ARCH_KEYSTONE
444 Support for TI DaVinci I2C controller driver.
446 This driver can also be built as a module. If so, the module
447 will be called i2c-davinci.
449 Please note that this driver might be needed to bring up other
450 devices such as DaVinci NIC.
451 For details please see http://www.ti.com/davinci
453 config I2C_DESIGNWARE_CORE
456 config I2C_DESIGNWARE_PLATFORM
457 tristate "Synopsys DesignWare Platform"
458 select I2C_DESIGNWARE_CORE
459 depends on (ACPI && COMMON_CLK) || !ACPI
461 If you say yes to this option, support will be included for the
462 Synopsys DesignWare I2C adapter. Only master mode is supported.
464 This driver can also be built as a module. If so, the module
465 will be called i2c-designware-platform.
467 config I2C_DESIGNWARE_PCI
468 tristate "Synopsys DesignWare PCI"
470 select I2C_DESIGNWARE_CORE
472 If you say yes to this option, support will be included for the
473 Synopsys DesignWare I2C adapter. Only master mode is supported.
475 This driver can also be built as a module. If so, the module
476 will be called i2c-designware-pci.
478 config I2C_DESIGNWARE_BAYTRAIL
479 bool "Intel Baytrail I2C semaphore support"
480 depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
482 This driver enables managed host access to the PMIC I2C bus on select
483 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows
484 the host to request uninterrupted access to the PMIC's I2C bus from
485 the platform firmware controlling it. You should say Y if running on
486 a BayTrail system using the AXP288.
489 tristate "EFM32 I2C controller"
490 depends on ARCH_EFM32 || COMPILE_TEST
492 This driver supports the i2c block found in Energy Micro's EFM32
496 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
497 depends on PCI && (X86_32 || COMPILE_TEST)
499 This driver is for PCH(Platform controller Hub) I2C of EG20T which
500 is an IOH(Input/Output Hub) for x86 embedded processor.
501 This driver can access PCH I2C bus device.
503 This driver also can be used for LAPIS Semiconductor IOH(Input/
504 Output Hub), ML7213, ML7223 and ML7831.
505 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
506 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
507 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
508 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
511 tristate "Exynos5 high-speed I2C driver"
512 depends on ARCH_EXYNOS && OF
515 High-speed I2C controller on Exynos5 based Samsung SoCs.
518 tristate "GPIO-based bitbanging I2C"
522 This is a very simple bitbanging I2C driver utilizing the
523 arch-neutral GPIO API to control the SCL and SDA lines.
525 config I2C_HIGHLANDER
526 tristate "Highlander FPGA SMBus interface"
527 depends on SH_HIGHLANDER
529 If you say yes to this option, support will be included for
530 the SMBus interface located in the FPGA on various Highlander
531 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
532 FPGAs. This is wholly unrelated to the SoC I2C.
534 This driver can also be built as a module. If so, the module
535 will be called i2c-highlander.
538 tristate "IBM PPC 4xx on-chip I2C interface"
541 Say Y here if you want to use IIC peripheral found on
542 embedded IBM PPC 4xx based systems.
544 This driver can also be built as a module. If so, the module
545 will be called i2c-ibm_iic.
548 tristate "Imagination Technologies I2C SCB Controller"
549 depends on MIPS || METAG || COMPILE_TEST
551 Say Y here if you want to use the IMG I2C SCB controller,
552 available on the TZ1090 and other IMG SoCs.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-img-scb.
558 tristate "IMX I2C interface"
561 Say Y here if you want to use the IIC bus controller on
562 the Freescale i.MX/MXC processors.
564 This driver can also be built as a module. If so, the module
565 will be called i2c-imx.
568 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
569 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
571 Say Y here if you want to use the IIC bus controller on
572 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
574 This driver can also be built as a module. If so, the module
575 will be called i2c-iop3xx.
578 tristate "Kontron COM I2C Controller"
579 depends on MFD_KEMPLD
581 This enables support for the I2C bus interface on some Kontron ETX
582 and COMexpress (ETXexpress) modules.
584 This driver can also be built as a module. If so, the module
585 will be called i2c-kempld.
588 tristate "Amlogic Meson I2C controller"
589 depends on ARCH_MESON
591 If you say yes to this option, support will be included for the
592 I2C interface on the Amlogic Meson family of SoCs.
595 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
598 If you say yes to this option, support will be included for the
599 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
600 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
602 This driver can also be built as a module. If so, the module
603 will be called i2c-mpc.
606 tristate "Marvell mv64xxx I2C Controller"
607 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
609 If you say yes to this option, support will be included for the
610 built-in I2C interface on the Marvell 64xxx line of host bridges.
611 This driver is also used for Allwinner SoCs I2C controllers.
613 This driver can also be built as a module. If so, the module
614 will be called i2c-mv64xxx.
617 tristate "Freescale i.MX28 I2C interface"
621 Say Y here if you want to use the I2C bus controller on
622 the Freescale i.MX28 processors.
624 This driver can also be built as a module. If so, the module
625 will be called i2c-mxs.
628 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
631 If you say yes to this option, support will be included for the
632 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
633 as well as the STA2X11 PCIe I/O HUB.
636 tristate "OpenCores I2C Controller"
638 If you say yes to this option, support will be included for the
639 OpenCores I2C controller. For details see
640 http://www.opencores.org/projects.cgi/web/i2c/overview
642 This driver can also be built as a module. If so, the module
643 will be called i2c-ocores.
646 tristate "OMAP I2C adapter"
648 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
650 If you say yes to this option, support will be included for the
651 I2C interface on the Texas Instruments OMAP1/2 family of processors.
652 Like OMAP1510/1610/1710/5912 and OMAP242x.
653 For details see http://www.ti.com/omap.
656 tristate "PA Semi SMBus interface"
657 depends on PPC_PASEMI && PCI
659 Supports the PA Semi PWRficient on-chip SMBus interfaces.
661 config I2C_PCA_PLATFORM
662 tristate "PCA9564/PCA9665 as platform device"
666 This driver supports a memory mapped Philips PCA9564/PCA9665
667 parallel bus to I2C bus controller.
669 This driver can also be built as a module. If so, the module
670 will be called i2c-pca-platform.
673 tristate "PMC MSP I2C TWI Controller"
676 This driver supports the PMC TWI controller on MSP devices.
678 This driver can also be built as module. If so, the module
679 will be called i2c-pmcmsp.
682 tristate "I2C bus support for Philips PNX and NXP LPC targets"
683 depends on ARCH_LPC32XX
685 This driver supports the Philips IP3204 I2C IP block master and/or
688 This driver can also be built as a module. If so, the module
689 will be called i2c-pnx.
692 tristate "PKUnity v3 I2C bus support"
693 depends on UNICORE32 && ARCH_PUV3
696 This driver supports the I2C IP inside the PKUnity-v3 SoC.
697 This I2C bus controller is under AMBA/AXI bus.
699 This driver can also be built as a module. If so, the module
700 will be called i2c-puv3.
703 tristate "Intel PXA2XX I2C adapter"
704 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
706 If you have devices in the PXA I2C bus, say yes to this option.
707 This driver can also be built as a module. If so, the module
708 will be called i2c-pxa.
711 def_bool I2C_PXA && X86_32 && PCI && OF
714 bool "Intel PXA2XX I2C Slave comms support"
715 depends on I2C_PXA && !X86_32
717 Support I2C slave mode communications on the PXA I2C bus. This
718 is necessary for systems where the PXA may be a target on the
722 tristate "Qualcomm QUP based I2C controller"
725 If you say yes to this option, support will be included for the
726 built-in I2C interface on the Qualcomm SoCs.
728 This driver can also be built as a module. If so, the module
729 will be called i2c-qup.
732 tristate "Renesas RIIC adapter"
733 depends on ARCH_SHMOBILE || COMPILE_TEST
735 If you say yes to this option, support will be included for the
736 Renesas RIIC I2C interface.
738 This driver can also be built as a module. If so, the module
739 will be called i2c-riic.
742 tristate "Rockchip RK3xxx I2C adapter"
743 depends on OF && COMMON_CLK
745 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
748 This driver can also be built as a module. If so, the module will
751 config HAVE_S3C2410_I2C
754 This will include I2C support for Samsung SoCs. If you want to
755 include I2C support for any machine, kindly select this in the
756 respective Kconfig file.
759 tristate "S3C2410 I2C Driver"
760 depends on HAVE_S3C2410_I2C
762 Say Y here to include support for I2C controller in the
766 tristate "Renesas SH7760 I2C Controller"
767 depends on CPU_SUBTYPE_SH7760
769 This driver supports the 2 I2C interfaces on the Renesas SH7760.
771 This driver can also be built as a module. If so, the module
772 will be called i2c-sh7760.
775 tristate "SuperH Mobile I2C Controller"
777 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
779 If you say yes to this option, support will be included for the
780 built-in I2C interface on the Renesas SH-Mobile processor.
782 This driver can also be built as a module. If so, the module
783 will be called i2c-sh_mobile.
786 tristate "Simtec Generic I2C interface"
789 If you say yes to this option, support will be included for
790 the Simtec Generic I2C interface. This driver is for the
791 simple I2C bus used on newer Simtec products for general
792 I2C, such as DDC on the Simtec BBD2016A.
794 This driver can also be built as a module. If so, the module
795 will be called i2c-simtec.
798 tristate "CSR SiRFprimaII I2C interface"
801 If you say yes to this option, support will be included for the
802 CSR SiRFprimaII I2C interface.
804 This driver can also be built as a module. If so, the module
805 will be called i2c-sirf.
808 tristate "STMicroelectronics SSC I2C support"
811 Enable this option to add support for STMicroelectronics SoCs
812 hardware SSC (Synchronous Serial Controller) as an I2C controller.
814 This driver can also be built as module. If so, the module
815 will be called i2c-st.
818 tristate "ST Microelectronics DDC I2C interface"
820 default y if MACH_U300
822 If you say yes to this option, support will be included for the
823 I2C interface from ST Microelectronics simply called "DDC I2C"
824 supporting both I2C and DDC, used in e.g. the U300 series
827 This driver can also be built as a module. If so, the module
828 will be called i2c-stu300.
830 config I2C_SUN6I_P2WI
831 tristate "Allwinner sun6i internal P2WI controller"
832 depends on RESET_CONTROLLER
833 depends on MACH_SUN6I || COMPILE_TEST
835 If you say yes to this option, support will be included for the
836 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
838 The P2WI looks like an SMBus controller (which supports only byte
839 accesses), except that it only supports one slave device.
840 This interface is used to connect to specific PMIC devices (like the
844 tristate "NVIDIA Tegra internal I2C controller"
845 depends on ARCH_TEGRA
847 If you say yes to this option, support will be included for the
848 I2C controller embedded in NVIDIA Tegra SOCs
851 tristate "ARM Versatile/Realview I2C bus support"
852 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
855 Say yes if you want to support the I2C serial bus on ARMs Versatile
858 This driver can also be built as a module. If so, the module
859 will be called i2c-versatile.
862 tristate "Wondermedia WM8xxx SoC I2C bus support"
863 depends on ARCH_VT8500
865 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
868 This driver can also be built as a module. If so, the module will be
872 tristate "Cavium OCTEON I2C bus support"
873 depends on CAVIUM_OCTEON_SOC
875 Say yes if you want to support the I2C serial bus on Cavium
878 This driver can also be built as a module. If so, the module
879 will be called i2c-octeon.
882 tristate "Xilinx I2C Controller"
885 If you say yes to this option, support will be included for the
886 Xilinx I2C controller.
888 This driver can also be built as a module. If so, the module
889 will be called xilinx_i2c.
892 tristate "XLR I2C support"
895 This driver enables support for the on-chip I2C interface of
896 the Netlogic XLR/XLS MIPS processors.
898 This driver can also be built as a module. If so, the module
899 will be called i2c-xlr.
902 tristate "Renesas R-Car I2C Controller"
903 depends on ARCH_SHMOBILE || COMPILE_TEST
906 If you say yes to this option, support will be included for the
907 R-Car I2C controller.
909 This driver can also be built as a module. If so, the module
910 will be called i2c-rcar.
912 comment "External I2C/SMBus adapter drivers"
914 config I2C_DIOLAN_U2C
915 tristate "Diolan U2C-12 USB adapter"
918 If you say yes to this option, support will be included for Diolan
919 U2C-12, a USB to I2C interface.
921 This driver can also be built as a module. If so, the module
922 will be called i2c-diolan-u2c.
925 tristate "Diolan DLN-2 USB I2C adapter"
928 If you say yes to this option, support will be included for Diolan
929 DLN2, a USB to I2C interface.
931 This driver can also be built as a module. If so, the module
932 will be called i2c-dln2.
935 tristate "Parallel port adapter"
940 This supports parallel port I2C adapters such as the ones made by
941 Philips or Velleman, Analog Devices evaluation boards, and more.
942 Basically any adapter using the parallel port as an I2C bus with
943 no extra chipset is supported by this driver, or could be.
945 This driver is a replacement for (and was inspired by) an older
946 driver named i2c-philips-par. The new driver supports more devices,
947 and makes it easier to add support for new devices.
949 An adapter type parameter is now mandatory. Please read the file
950 Documentation/i2c/busses/i2c-parport for details.
952 Another driver exists, named i2c-parport-light, which doesn't depend
953 on the parport driver. This is meant for embedded systems. Don't say
954 Y here if you intend to say Y or M there.
956 This support is also available as a module. If so, the module
957 will be called i2c-parport.
959 config I2C_PARPORT_LIGHT
960 tristate "Parallel port adapter (light)"
964 This supports parallel port I2C adapters such as the ones made by
965 Philips or Velleman, Analog Devices evaluation boards, and more.
966 Basically any adapter using the parallel port as an I2C bus with
967 no extra chipset is supported by this driver, or could be.
969 This driver is a light version of i2c-parport. It doesn't depend
970 on the parport driver, and uses direct I/O access instead. This
971 might be preferred on embedded systems where wasting memory for
972 the clean but heavy parport handling is not an option. The
973 drawback is a reduced portability and the impossibility to
974 daisy-chain other parallel port devices.
976 Don't say Y here if you said Y or M to i2c-parport. Saying M to
977 both is possible but both modules should not be loaded at the same
980 This support is also available as a module. If so, the module
981 will be called i2c-parport-light.
983 config I2C_ROBOTFUZZ_OSIF
984 tristate "RobotFuzz Open Source InterFace USB adapter"
987 If you say yes to this option, support will be included for the
988 RobotFuzz Open Source InterFace USB to I2C interface.
990 This driver can also be built as a module. If so, the module
991 will be called i2c-osif.
994 tristate "TAOS evaluation module"
1000 This supports TAOS evaluation modules on serial port. In order to
1001 use this driver, you will need the inputattach tool, which is part
1002 of the input-utils package.
1006 This support is also available as a module. If so, the module
1007 will be called i2c-taos-evm.
1010 tristate "Tiny-USB adapter"
1013 If you say yes to this option, support will be included for the
1014 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
1015 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
1017 This driver can also be built as a module. If so, the module
1018 will be called i2c-tiny-usb.
1020 config I2C_VIPERBOARD
1021 tristate "Viperboard I2C master support"
1022 depends on MFD_VIPERBOARD && USB
1024 Say yes here to access the I2C part of the Nano River
1025 Technologies Viperboard as I2C master.
1026 See viperboard API specification and Nano
1027 River Tech's viperboard.h for detailed meaning
1028 of the module parameters.
1030 comment "Other I2C/SMBus bus drivers"
1033 tristate "Acorn IOC/IOMD I2C bus support"
1034 depends on ARCH_ACORN
1038 Say yes if you want to support the I2C bus on Acorn platforms.
1040 If you don't know, say Y.
1043 tristate "Elektor ISA card"
1044 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1047 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1050 This support is also available as a module. If so, the module
1051 will be called i2c-elektor.
1054 tristate "PCA9564/PCA9665 on an ISA bus"
1059 This driver supports ISA boards using the Philips PCA9564/PCA9665
1060 parallel bus to I2C bus controller.
1062 This driver can also be built as a module. If so, the module
1063 will be called i2c-pca-isa.
1065 This device is almost undetectable and using this driver on a
1066 system which doesn't have this device will result in long
1067 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1068 time). If unsure, say N.
1071 tristate "SiByte SMBus interface"
1072 depends on SIBYTE_SB1xxx_SOC
1074 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1076 config I2C_CROS_EC_TUNNEL
1077 tristate "ChromeOS EC tunnel I2C bus"
1078 depends on MFD_CROS_EC
1080 If you say yes here you get an I2C bus that will tunnel i2c commands
1081 through to the other side of the ChromeOS EC to the i2c bus
1082 connected there. This will work whatever the interface used to
1083 talk to the EC (SPI, I2C or LPC).
1086 tristate "Geode ACCESS.bus support"
1087 depends on X86_32 && PCI
1089 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1090 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1092 If you don't know what to do here, say N.
1094 This support is also available as a module. If so, the module
1095 will be called scx200_acb.
1098 tristate "IBM OPAL I2C driver"
1099 depends on PPC_POWERNV
1102 This exposes the PowerNV platform i2c busses to the linux i2c layer,
1103 the driver is based on the OPAL interfaces.
1105 This driver can also be built as a module. If so, the module will be