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
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 "BCM Kona I2C adapter"
377 depends on ARCH_BCM_MOBILE
380 If you say yes to this option, support will be included for the
381 I2C interface on the Broadcom Kona family of processors.
383 If you do not need KONA I2C interface, say N.
385 config I2C_BLACKFIN_TWI
386 tristate "Blackfin TWI I2C support"
388 depends on !BF561 && !BF531 && !BF532 && !BF533
390 This is the I2C bus driver for Blackfin on-chip TWI interface.
392 This driver can also be built as a module. If so, the module
393 will be called i2c-bfin-twi.
395 config I2C_BLACKFIN_TWI_CLK_KHZ
396 int "Blackfin TWI I2C clock (kHz)"
397 depends on I2C_BLACKFIN_TWI
401 The unit of the TWI clock is kHz.
404 tristate "Cadence I2C Controller"
407 Say yes here to select Cadence I2C Host Controller. This controller is
408 e.g. used by Xilinx Zynq.
411 tristate "CBUS I2C driver"
414 Support for CBUS access using I2C API. Mostly relevant for Nokia
415 Internet Tablets (770, N800 and N810).
417 This driver can also be built as a module. If so, the module
418 will be called i2c-cbus-gpio.
421 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
422 depends on CPM1 || CPM2
424 This supports the use of the I2C interface on Freescale
425 processors with CPM1 or CPM2.
427 This driver can also be built as a module. If so, the module
428 will be called i2c-cpm.
431 tristate "DaVinci I2C driver"
432 depends on ARCH_DAVINCI || ARCH_KEYSTONE
434 Support for TI DaVinci I2C controller driver.
436 This driver can also be built as a module. If so, the module
437 will be called i2c-davinci.
439 Please note that this driver might be needed to bring up other
440 devices such as DaVinci NIC.
441 For details please see http://www.ti.com/davinci
443 config I2C_DESIGNWARE_CORE
446 config I2C_DESIGNWARE_PLATFORM
447 tristate "Synopsys DesignWare Platform"
448 select I2C_DESIGNWARE_CORE
449 depends on (ACPI && COMMON_CLK) || !ACPI
451 If you say yes to this option, support will be included for the
452 Synopsys DesignWare I2C adapter. Only master mode is supported.
454 This driver can also be built as a module. If so, the module
455 will be called i2c-designware-platform.
457 config I2C_DESIGNWARE_PCI
458 tristate "Synopsys DesignWare PCI"
460 select I2C_DESIGNWARE_CORE
462 If you say yes to this option, support will be included for the
463 Synopsys DesignWare I2C adapter. Only master mode is supported.
465 This driver can also be built as a module. If so, the module
466 will be called i2c-designware-pci.
469 tristate "EFM32 I2C controller"
470 depends on ARCH_EFM32 || COMPILE_TEST
472 This driver supports the i2c block found in Energy Micro's EFM32
476 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
477 depends on PCI && (X86_32 || COMPILE_TEST)
479 This driver is for PCH(Platform controller Hub) I2C of EG20T which
480 is an IOH(Input/Output Hub) for x86 embedded processor.
481 This driver can access PCH I2C bus device.
483 This driver also can be used for LAPIS Semiconductor IOH(Input/
484 Output Hub), ML7213, ML7223 and ML7831.
485 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
486 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
487 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
488 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
491 tristate "Exynos5 high-speed I2C driver"
492 depends on ARCH_EXYNOS && OF
495 High-speed I2C controller on Exynos5 based Samsung SoCs.
498 tristate "GPIO-based bitbanging I2C"
502 This is a very simple bitbanging I2C driver utilizing the
503 arch-neutral GPIO API to control the SCL and SDA lines.
505 config I2C_HIGHLANDER
506 tristate "Highlander FPGA SMBus interface"
507 depends on SH_HIGHLANDER
509 If you say yes to this option, support will be included for
510 the SMBus interface located in the FPGA on various Highlander
511 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
512 FPGAs. This is wholly unrelated to the SoC I2C.
514 This driver can also be built as a module. If so, the module
515 will be called i2c-highlander.
518 tristate "IBM PPC 4xx on-chip I2C interface"
521 Say Y here if you want to use IIC peripheral found on
522 embedded IBM PPC 4xx based systems.
524 This driver can also be built as a module. If so, the module
525 will be called i2c-ibm_iic.
528 tristate "Imagination Technologies I2C SCB Controller"
529 depends on SOC_TZ1090 || COMPILE_TEST
531 Say Y here if you want to use the IMG I2C SCB controller,
532 available on the TZ1090 SoC.
534 This driver can also be built as a module. If so, the module
535 will be called i2c-img-scb.
538 tristate "IMX I2C interface"
541 Say Y here if you want to use the IIC bus controller on
542 the Freescale i.MX/MXC processors.
544 This driver can also be built as a module. If so, the module
545 will be called i2c-imx.
548 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
549 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
551 Say Y here if you want to use the IIC bus controller on
552 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
554 This driver can also be built as a module. If so, the module
555 will be called i2c-iop3xx.
558 tristate "Kontron COM I2C Controller"
559 depends on MFD_KEMPLD
561 This enables support for the I2C bus interface on some Kontron ETX
562 and COMexpress (ETXexpress) modules.
564 This driver can also be built as a module. If so, the module
565 will be called i2c-kempld.
568 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
571 If you say yes to this option, support will be included for the
572 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
573 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
575 This driver can also be built as a module. If so, the module
576 will be called i2c-mpc.
579 tristate "Marvell mv64xxx I2C Controller"
580 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
582 If you say yes to this option, support will be included for the
583 built-in I2C interface on the Marvell 64xxx line of host bridges.
584 This driver is also used for Allwinner SoCs I2C controllers.
586 This driver can also be built as a module. If so, the module
587 will be called i2c-mv64xxx.
590 tristate "Freescale i.MX28 I2C interface"
594 Say Y here if you want to use the I2C bus controller on
595 the Freescale i.MX28 processors.
597 This driver can also be built as a module. If so, the module
598 will be called i2c-mxs.
601 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
604 If you say yes to this option, support will be included for the
605 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
606 as well as the STA2X11 PCIe I/O HUB.
609 tristate "OpenCores I2C Controller"
611 If you say yes to this option, support will be included for the
612 OpenCores I2C controller. For details see
613 http://www.opencores.org/projects.cgi/web/i2c/overview
615 This driver can also be built as a module. If so, the module
616 will be called i2c-ocores.
619 tristate "OMAP I2C adapter"
621 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
623 If you say yes to this option, support will be included for the
624 I2C interface on the Texas Instruments OMAP1/2 family of processors.
625 Like OMAP1510/1610/1710/5912 and OMAP242x.
626 For details see http://www.ti.com/omap.
629 tristate "PA Semi SMBus interface"
630 depends on PPC_PASEMI && PCI
632 Supports the PA Semi PWRficient on-chip SMBus interfaces.
634 config I2C_PCA_PLATFORM
635 tristate "PCA9564/PCA9665 as platform device"
639 This driver supports a memory mapped Philips PCA9564/PCA9665
640 parallel bus to I2C bus controller.
642 This driver can also be built as a module. If so, the module
643 will be called i2c-pca-platform.
646 tristate "PMC MSP I2C TWI Controller"
649 This driver supports the PMC TWI controller on MSP devices.
651 This driver can also be built as module. If so, the module
652 will be called i2c-pmcmsp.
655 tristate "I2C bus support for Philips PNX and NXP LPC targets"
656 depends on ARCH_LPC32XX
658 This driver supports the Philips IP3204 I2C IP block master and/or
661 This driver can also be built as a module. If so, the module
662 will be called i2c-pnx.
665 tristate "PKUnity v3 I2C bus support"
666 depends on UNICORE32 && ARCH_PUV3
669 This driver supports the I2C IP inside the PKUnity-v3 SoC.
670 This I2C bus controller is under AMBA/AXI bus.
672 This driver can also be built as a module. If so, the module
673 will be called i2c-puv3.
676 tristate "Intel PXA2XX I2C adapter"
677 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
679 If you have devices in the PXA I2C bus, say yes to this option.
680 This driver can also be built as a module. If so, the module
681 will be called i2c-pxa.
684 def_bool I2C_PXA && X86_32 && PCI && OF
687 bool "Intel PXA2XX I2C Slave comms support"
688 depends on I2C_PXA && !X86_32
690 Support I2C slave mode communications on the PXA I2C bus. This
691 is necessary for systems where the PXA may be a target on the
695 tristate "Qualcomm QUP based I2C controller"
698 If you say yes to this option, support will be included for the
699 built-in I2C interface on the Qualcomm SoCs.
701 This driver can also be built as a module. If so, the module
702 will be called i2c-qup.
705 tristate "Renesas RIIC adapter"
706 depends on ARCH_SHMOBILE || COMPILE_TEST
708 If you say yes to this option, support will be included for the
709 Renesas RIIC I2C interface.
711 This driver can also be built as a module. If so, the module
712 will be called i2c-riic.
715 tristate "Rockchip RK3xxx I2C adapter"
718 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
721 This driver can also be built as a module. If so, the module will
724 config HAVE_S3C2410_I2C
727 This will include I2C support for Samsung SoCs. If you want to
728 include I2C support for any machine, kindly select this in the
729 respective Kconfig file.
732 tristate "S3C2410 I2C Driver"
733 depends on HAVE_S3C2410_I2C
735 Say Y here to include support for I2C controller in the
739 tristate "Renesas SH7760 I2C Controller"
740 depends on CPU_SUBTYPE_SH7760
742 This driver supports the 2 I2C interfaces on the Renesas SH7760.
744 This driver can also be built as a module. If so, the module
745 will be called i2c-sh7760.
748 tristate "SuperH Mobile I2C Controller"
749 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
751 If you say yes to this option, support will be included for the
752 built-in I2C interface on the Renesas SH-Mobile processor.
754 This driver can also be built as a module. If so, the module
755 will be called i2c-sh_mobile.
758 tristate "Simtec Generic I2C interface"
761 If you say yes to this option, support will be included for
762 the Simtec Generic I2C interface. This driver is for the
763 simple I2C bus used on newer Simtec products for general
764 I2C, such as DDC on the Simtec BBD2016A.
766 This driver can also be built as a module. If so, the module
767 will be called i2c-simtec.
770 tristate "CSR SiRFprimaII I2C interface"
773 If you say yes to this option, support will be included for the
774 CSR SiRFprimaII I2C interface.
776 This driver can also be built as a module. If so, the module
777 will be called i2c-sirf.
780 tristate "STMicroelectronics SSC I2C support"
783 Enable this option to add support for STMicroelectronics SoCs
784 hardware SSC (Synchronous Serial Controller) as an I2C controller.
786 This driver can also be built as module. If so, the module
787 will be called i2c-st.
790 tristate "ST Microelectronics DDC I2C interface"
792 default y if MACH_U300
794 If you say yes to this option, support will be included for the
795 I2C interface from ST Microelectronics simply called "DDC I2C"
796 supporting both I2C and DDC, used in e.g. the U300 series
799 This driver can also be built as a module. If so, the module
800 will be called i2c-stu300.
802 config I2C_SUN6I_P2WI
803 tristate "Allwinner sun6i internal P2WI controller"
804 depends on RESET_CONTROLLER
805 depends on MACH_SUN6I || COMPILE_TEST
807 If you say yes to this option, support will be included for the
808 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
810 The P2WI looks like an SMBus controller (which supports only byte
811 accesses), except that it only supports one slave device.
812 This interface is used to connect to specific PMIC devices (like the
816 tristate "NVIDIA Tegra internal I2C controller"
817 depends on ARCH_TEGRA
819 If you say yes to this option, support will be included for the
820 I2C controller embedded in NVIDIA Tegra SOCs
823 tristate "ARM Versatile/Realview I2C bus support"
824 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
827 Say yes if you want to support the I2C serial bus on ARMs Versatile
830 This driver can also be built as a module. If so, the module
831 will be called i2c-versatile.
834 tristate "Wondermedia WM8xxx SoC I2C bus support"
835 depends on ARCH_VT8500
837 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
840 This driver can also be built as a module. If so, the module will be
844 tristate "Cavium OCTEON I2C bus support"
845 depends on CAVIUM_OCTEON_SOC
847 Say yes if you want to support the I2C serial bus on Cavium
850 This driver can also be built as a module. If so, the module
851 will be called i2c-octeon.
854 tristate "Xilinx I2C Controller"
857 If you say yes to this option, support will be included for the
858 Xilinx I2C controller.
860 This driver can also be built as a module. If so, the module
861 will be called xilinx_i2c.
864 tristate "XLR I2C support"
867 This driver enables support for the on-chip I2C interface of
868 the Netlogic XLR/XLS MIPS processors.
870 This driver can also be built as a module. If so, the module
871 will be called i2c-xlr.
874 tristate "Renesas R-Car I2C Controller"
875 depends on ARCH_SHMOBILE || COMPILE_TEST
877 If you say yes to this option, support will be included for the
878 R-Car I2C controller.
880 This driver can also be built as a module. If so, the module
881 will be called i2c-rcar.
883 comment "External I2C/SMBus adapter drivers"
885 config I2C_DIOLAN_U2C
886 tristate "Diolan U2C-12 USB adapter"
889 If you say yes to this option, support will be included for Diolan
890 U2C-12, a USB to I2C interface.
892 This driver can also be built as a module. If so, the module
893 will be called i2c-diolan-u2c.
896 tristate "Parallel port adapter"
901 This supports parallel port I2C adapters such as the ones made by
902 Philips or Velleman, Analog Devices evaluation boards, and more.
903 Basically any adapter using the parallel port as an I2C bus with
904 no extra chipset is supported by this driver, or could be.
906 This driver is a replacement for (and was inspired by) an older
907 driver named i2c-philips-par. The new driver supports more devices,
908 and makes it easier to add support for new devices.
910 An adapter type parameter is now mandatory. Please read the file
911 Documentation/i2c/busses/i2c-parport for details.
913 Another driver exists, named i2c-parport-light, which doesn't depend
914 on the parport driver. This is meant for embedded systems. Don't say
915 Y here if you intend to say Y or M there.
917 This support is also available as a module. If so, the module
918 will be called i2c-parport.
920 config I2C_PARPORT_LIGHT
921 tristate "Parallel port adapter (light)"
925 This supports parallel port I2C adapters such as the ones made by
926 Philips or Velleman, Analog Devices evaluation boards, and more.
927 Basically any adapter using the parallel port as an I2C bus with
928 no extra chipset is supported by this driver, or could be.
930 This driver is a light version of i2c-parport. It doesn't depend
931 on the parport driver, and uses direct I/O access instead. This
932 might be preferred on embedded systems where wasting memory for
933 the clean but heavy parport handling is not an option. The
934 drawback is a reduced portability and the impossibility to
935 daisy-chain other parallel port devices.
937 Don't say Y here if you said Y or M to i2c-parport. Saying M to
938 both is possible but both modules should not be loaded at the same
941 This support is also available as a module. If so, the module
942 will be called i2c-parport-light.
944 config I2C_ROBOTFUZZ_OSIF
945 tristate "RobotFuzz Open Source InterFace USB adapter"
948 If you say yes to this option, support will be included for the
949 RobotFuzz Open Source InterFace USB to I2C interface.
951 This driver can also be built as a module. If so, the module
952 will be called i2c-osif.
955 tristate "TAOS evaluation module"
961 This supports TAOS evaluation modules on serial port. In order to
962 use this driver, you will need the inputattach tool, which is part
963 of the input-utils package.
967 This support is also available as a module. If so, the module
968 will be called i2c-taos-evm.
971 tristate "Tiny-USB adapter"
974 If you say yes to this option, support will be included for the
975 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
976 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
978 This driver can also be built as a module. If so, the module
979 will be called i2c-tiny-usb.
981 config I2C_VIPERBOARD
982 tristate "Viperboard I2C master support"
983 depends on MFD_VIPERBOARD && USB
985 Say yes here to access the I2C part of the Nano River
986 Technologies Viperboard as I2C master.
987 See viperboard API specification and Nano
988 River Tech's viperboard.h for detailed meaning
989 of the module parameters.
991 comment "Other I2C/SMBus bus drivers"
994 tristate "Acorn IOC/IOMD I2C bus support"
995 depends on ARCH_ACORN
999 Say yes if you want to support the I2C bus on Acorn platforms.
1001 If you don't know, say Y.
1004 tristate "Elektor ISA card"
1005 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
1008 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
1011 This support is also available as a module. If so, the module
1012 will be called i2c-elektor.
1015 tristate "PCA9564/PCA9665 on an ISA bus"
1020 This driver supports ISA boards using the Philips PCA9564/PCA9665
1021 parallel bus to I2C bus controller.
1023 This driver can also be built as a module. If so, the module
1024 will be called i2c-pca-isa.
1026 This device is almost undetectable and using this driver on a
1027 system which doesn't have this device will result in long
1028 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
1029 time). If unsure, say N.
1032 tristate "SiByte SMBus interface"
1033 depends on SIBYTE_SB1xxx_SOC
1035 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1037 config I2C_CROS_EC_TUNNEL
1038 tristate "ChromeOS EC tunnel I2C bus"
1039 depends on MFD_CROS_EC
1041 If you say yes here you get an I2C bus that will tunnel i2c commands
1042 through to the other side of the ChromeOS EC to the i2c bus
1043 connected there. This will work whatever the interface used to
1044 talk to the EC (SPI, I2C or LPC).
1047 tristate "Geode ACCESS.bus support"
1048 depends on X86_32 && PCI
1050 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1051 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1053 If you don't know what to do here, say N.
1055 This support is also available as a module. If so, the module
1056 will be called scx200_acb.