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 "Intel 82801 (ICH/PCH)"
83 select CHECK_SIGNATURE if X86 && DMI
85 If you say yes to this option, support will be included for the Intel
86 801 family of mainboard I2C interfaces. Specifically, the following
87 versions of the chipset are supported:
93 82801EB/ER (ICH5/ICH5R)
113 Wildcat Point-LP (PCH)
116 This driver can also be built as a module. If so, the module
117 will be called i2c-i801.
120 tristate "Intel SCH SMBus 1.0"
124 Say Y here if you want to use SMBus controller on the Intel SCH
127 This driver can also be built as a module. If so, the module
128 will be called i2c-isch.
131 tristate "Intel iSMT SMBus Controller"
132 depends on PCI && X86
134 If you say yes to this option, support will be included for the Intel
135 iSMT SMBus host controller interface.
137 This driver can also be built as a module. If so, the module will be
141 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
144 If you say yes to this option, support will be included for the Intel
145 PIIX4 family of mainboard I2C interfaces. Specifically, the following
146 versions of the chipset are supported (note that Serverworks is part
166 Some AMD chipsets contain two PIIX4-compatible SMBus
167 controllers. This driver will attempt to use both controllers
168 on the SB700/SP5100, if they have been initialized by the BIOS.
170 This driver can also be built as a module. If so, the module
171 will be called i2c-piix4.
174 tristate "Nvidia nForce2, nForce3 and nForce4"
177 If you say yes to this option, support will be included for the Nvidia
178 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
180 This driver can also be built as a module. If so, the module
181 will be called i2c-nforce2.
183 config I2C_NFORCE2_S4985
184 tristate "SMBus multiplexing on the Tyan S4985"
185 depends on I2C_NFORCE2 && X86
187 Enabling this option will add specific SMBus support for the Tyan
188 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
189 over 4 different channels, where the various memory module EEPROMs
190 live. Saying yes here will give you access to these in addition
193 This driver can also be built as a module. If so, the module
194 will be called i2c-nforce2-s4985.
200 If you say yes to this option, support will be included for the
201 SiS5595 SMBus (a subset of I2C) interface.
203 This driver can also be built as a module. If so, the module
204 will be called i2c-sis5595.
207 tristate "SiS 630/730/964"
210 If you say yes to this option, support will be included for the
211 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
213 This driver can also be built as a module. If so, the module
214 will be called i2c-sis630.
220 If you say yes to this option, support will be included for the SiS
221 96x SMBus (a subset of I2C) interfaces. Specifically, the following
222 chipsets are supported:
231 This driver can also be built as a module. If so, the module
232 will be called i2c-sis96x.
235 tristate "VIA VT82C586B"
239 If you say yes to this option, support will be included for the VIA
240 82C586B I2C interface
242 This driver can also be built as a module. If so, the module
243 will be called i2c-via.
246 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
249 If you say yes to this option, support will be included for the VIA
250 VT82C596 and later SMBus interface. Specifically, the following
251 chipsets are supported:
264 This driver can also be built as a module. If so, the module
265 will be called i2c-viapro.
269 comment "ACPI drivers"
272 tristate "SMBus Control Method Interface"
274 This driver supports the SMBus Control Method Interface. It needs the
275 BIOS to declare ACPI control methods as described in the SMBus Control
276 Method Interface specification.
278 To compile this driver as a module, choose M here:
279 the module will be called i2c-scmi.
283 comment "Mac SMBus host controller drivers"
284 depends on PPC_CHRP || PPC_PMAC
287 tristate "CHRP Apple Hydra Mac I/O I2C interface"
288 depends on PCI && PPC_CHRP
291 This supports the use of the I2C interface in the Apple Hydra Mac
292 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
295 This support is also available as a module. If so, the module
296 will be called i2c-hydra.
299 tristate "Powermac I2C interface"
303 This exposes the various PowerMac i2c interfaces to the linux i2c
304 layer and to userland. It is used by various drivers on the PowerMac
305 platform, and should generally be enabled.
307 This support is also available as a module. If so, the module
308 will be called i2c-powermac.
310 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
313 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
316 This supports the use of the I2C interface on Atmel AT91
319 A serious problem is that there is no documented way to issue
320 repeated START conditions for more than two messages, as needed
321 to support combined I2C messages. Use the i2c-gpio driver
322 unless your system can cope with this limitation.
324 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
325 don't have clock stretching in transmission mode. For that reason,
326 you can encounter underrun issues causing premature stop sendings if
327 the latency to fill the transmission register is too long. If you
328 are facing this situation, use the i2c-gpio driver.
331 tristate "Au1550/Au1200/Au1300 SMBus interface"
332 depends on MIPS_ALCHEMY
334 If you say yes to this option, support will be included for the
335 Au1550/Au1200/Au1300 SMBus interface.
337 This driver can also be built as a module. If so, the module
338 will be called i2c-au1550.
341 tristate "Broadcom BCM2835 I2C controller"
342 depends on ARCH_BCM2835
344 If you say yes to this option, support will be included for the
345 BCM2835 I2C controller.
347 If you don't know what to do here, say N.
349 This support is also available as a module. If so, the module
350 will be called i2c-bcm2835.
353 tristate "BCM Kona I2C adapter"
354 depends on ARCH_BCM_MOBILE
357 If you say yes to this option, support will be included for the
358 I2C interface on the Broadcom Kona family of processors.
360 If you do not need KONA I2C inteface, say N.
362 config I2C_BLACKFIN_TWI
363 tristate "Blackfin TWI I2C support"
365 depends on !BF561 && !BF531 && !BF532 && !BF533
367 This is the I2C bus driver for Blackfin on-chip TWI interface.
369 This driver can also be built as a module. If so, the module
370 will be called i2c-bfin-twi.
372 config I2C_BLACKFIN_TWI_CLK_KHZ
373 int "Blackfin TWI I2C clock (kHz)"
374 depends on I2C_BLACKFIN_TWI
378 The unit of the TWI clock is kHz.
381 tristate "Cadence I2C Controller"
384 Say yes here to select Cadence I2C Host Controller. This controller is
385 e.g. used by Xilinx Zynq.
388 tristate "CBUS I2C driver"
391 Support for CBUS access using I2C API. Mostly relevant for Nokia
392 Internet Tablets (770, N800 and N810).
394 This driver can also be built as a module. If so, the module
395 will be called i2c-cbus-gpio.
398 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
399 depends on CPM1 || CPM2
401 This supports the use of the I2C interface on Freescale
402 processors with CPM1 or CPM2.
404 This driver can also be built as a module. If so, the module
405 will be called i2c-cpm.
408 tristate "DaVinci I2C driver"
409 depends on ARCH_DAVINCI || ARCH_KEYSTONE
411 Support for TI DaVinci I2C controller driver.
413 This driver can also be built as a module. If so, the module
414 will be called i2c-davinci.
416 Please note that this driver might be needed to bring up other
417 devices such as DaVinci NIC.
418 For details please see http://www.ti.com/davinci
420 config I2C_DESIGNWARE_CORE
423 config I2C_DESIGNWARE_PLATFORM
424 tristate "Synopsys DesignWare Platform"
425 select I2C_DESIGNWARE_CORE
427 If you say yes to this option, support will be included for the
428 Synopsys DesignWare I2C adapter. Only master mode is supported.
430 This driver can also be built as a module. If so, the module
431 will be called i2c-designware-platform.
433 config I2C_DESIGNWARE_PCI
434 tristate "Synopsys DesignWare PCI"
436 select I2C_DESIGNWARE_CORE
438 If you say yes to this option, support will be included for the
439 Synopsys DesignWare I2C adapter. Only master mode is supported.
441 This driver can also be built as a module. If so, the module
442 will be called i2c-designware-pci.
445 tristate "EFM32 I2C controller"
446 depends on ARCH_EFM32 || COMPILE_TEST
448 This driver supports the i2c block found in Energy Micro's EFM32
452 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
453 depends on PCI && (X86_32 || COMPILE_TEST)
455 This driver is for PCH(Platform controller Hub) I2C of EG20T which
456 is an IOH(Input/Output Hub) for x86 embedded processor.
457 This driver can access PCH I2C bus device.
459 This driver also can be used for LAPIS Semiconductor IOH(Input/
460 Output Hub), ML7213, ML7223 and ML7831.
461 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
462 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
463 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
464 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
467 tristate "Exynos5 high-speed I2C driver"
468 depends on ARCH_EXYNOS5 && OF
471 High-speed I2C controller on Exynos5 based Samsung SoCs.
474 tristate "GPIO-based bitbanging I2C"
478 This is a very simple bitbanging I2C driver utilizing the
479 arch-neutral GPIO API to control the SCL and SDA lines.
481 config I2C_HIGHLANDER
482 tristate "Highlander FPGA SMBus interface"
483 depends on SH_HIGHLANDER
485 If you say yes to this option, support will be included for
486 the SMBus interface located in the FPGA on various Highlander
487 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
488 FPGAs. This is wholly unrelated to the SoC I2C.
490 This driver can also be built as a module. If so, the module
491 will be called i2c-highlander.
494 tristate "IBM PPC 4xx on-chip I2C interface"
497 Say Y here if you want to use IIC peripheral found on
498 embedded IBM PPC 4xx based systems.
500 This driver can also be built as a module. If so, the module
501 will be called i2c-ibm_iic.
504 tristate "IMX I2C interface"
507 Say Y here if you want to use the IIC bus controller on
508 the Freescale i.MX/MXC processors.
510 This driver can also be built as a module. If so, the module
511 will be called i2c-imx.
514 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
515 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
517 Say Y here if you want to use the IIC bus controller on
518 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
520 This driver can also be built as a module. If so, the module
521 will be called i2c-iop3xx.
524 tristate "Kontron COM I2C Controller"
525 depends on MFD_KEMPLD
527 This enables support for the I2C bus interface on some Kontron ETX
528 and COMexpress (ETXexpress) modules.
530 This driver can also be built as a module. If so, the module
531 will be called i2c-kempld.
534 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
537 If you say yes to this option, support will be included for the
538 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
539 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
541 This driver can also be built as a module. If so, the module
542 will be called i2c-mpc.
545 tristate "Marvell mv64xxx I2C Controller"
546 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI
548 If you say yes to this option, support will be included for the
549 built-in I2C interface on the Marvell 64xxx line of host bridges.
550 This driver is also used for Allwinner SoCs I2C controllers.
552 This driver can also be built as a module. If so, the module
553 will be called i2c-mv64xxx.
556 tristate "Freescale i.MX28 I2C interface"
560 Say Y here if you want to use the I2C bus controller on
561 the Freescale i.MX28 processors.
563 This driver can also be built as a module. If so, the module
564 will be called i2c-mxs.
567 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
570 If you say yes to this option, support will be included for the
571 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
572 as well as the STA2X11 PCIe I/O HUB.
575 tristate "OpenCores I2C Controller"
577 If you say yes to this option, support will be included for the
578 OpenCores I2C controller. For details see
579 http://www.opencores.org/projects.cgi/web/i2c/overview
581 This driver can also be built as a module. If so, the module
582 will be called i2c-ocores.
585 tristate "OMAP I2C adapter"
587 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
589 If you say yes to this option, support will be included for the
590 I2C interface on the Texas Instruments OMAP1/2 family of processors.
591 Like OMAP1510/1610/1710/5912 and OMAP242x.
592 For details see http://www.ti.com/omap.
595 tristate "PA Semi SMBus interface"
596 depends on PPC_PASEMI && PCI
598 Supports the PA Semi PWRficient on-chip SMBus interfaces.
600 config I2C_PCA_PLATFORM
601 tristate "PCA9564/PCA9665 as platform device"
605 This driver supports a memory mapped Philips PCA9564/PCA9665
606 parallel bus to I2C bus controller.
608 This driver can also be built as a module. If so, the module
609 will be called i2c-pca-platform.
612 tristate "PMC MSP I2C TWI Controller"
615 This driver supports the PMC TWI controller on MSP devices.
617 This driver can also be built as module. If so, the module
618 will be called i2c-pmcmsp.
621 tristate "I2C bus support for Philips PNX and NXP LPC targets"
622 depends on ARCH_LPC32XX
624 This driver supports the Philips IP3204 I2C IP block master and/or
627 This driver can also be built as a module. If so, the module
628 will be called i2c-pnx.
631 tristate "PKUnity v3 I2C bus support"
632 depends on UNICORE32 && ARCH_PUV3
635 This driver supports the I2C IP inside the PKUnity-v3 SoC.
636 This I2C bus controller is under AMBA/AXI bus.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-puv3.
642 tristate "Intel PXA2XX I2C adapter"
643 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
645 If you have devices in the PXA I2C bus, say yes to this option.
646 This driver can also be built as a module. If so, the module
647 will be called i2c-pxa.
650 def_bool I2C_PXA && X86_32 && PCI && OF
653 bool "Intel PXA2XX I2C Slave comms support"
654 depends on I2C_PXA && !X86_32
656 Support I2C slave mode communications on the PXA I2C bus. This
657 is necessary for systems where the PXA may be a target on the
661 tristate "Qualcomm QUP based I2C controller"
664 If you say yes to this option, support will be included for the
665 built-in I2C interface on the Qualcomm SoCs.
667 This driver can also be built as a module. If so, the module
668 will be called i2c-qup.
671 tristate "Renesas RIIC adapter"
672 depends on ARCH_SHMOBILE || COMPILE_TEST
674 If you say yes to this option, support will be included for the
675 Renesas RIIC I2C interface.
677 This driver can also be built as a module. If so, the module
678 will be called i2c-riic.
681 tristate "Rockchip RK3xxx I2C adapter"
684 Say Y here to include support for the I2C adapter in Rockchip RK3xxx
687 This driver can also be built as a module. If so, the module will
690 config HAVE_S3C2410_I2C
693 This will include I2C support for Samsung SoCs. If you want to
694 include I2C support for any machine, kindly select this in the
695 respective Kconfig file.
698 tristate "S3C2410 I2C Driver"
699 depends on HAVE_S3C2410_I2C
701 Say Y here to include support for I2C controller in the
705 tristate "Renesas SH7760 I2C Controller"
706 depends on CPU_SUBTYPE_SH7760
708 This driver supports the 2 I2C interfaces on the Renesas SH7760.
710 This driver can also be built as a module. If so, the module
711 will be called i2c-sh7760.
714 tristate "SuperH Mobile I2C Controller"
715 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
717 If you say yes to this option, support will be included for the
718 built-in I2C interface on the Renesas SH-Mobile processor.
720 This driver can also be built as a module. If so, the module
721 will be called i2c-sh_mobile.
724 tristate "Simtec Generic I2C interface"
727 If you say yes to this option, support will be included for
728 the Simtec Generic I2C interface. This driver is for the
729 simple I2C bus used on newer Simtec products for general
730 I2C, such as DDC on the Simtec BBD2016A.
732 This driver can also be built as a module. If so, the module
733 will be called i2c-simtec.
736 tristate "CSR SiRFprimaII I2C interface"
739 If you say yes to this option, support will be included for the
740 CSR SiRFprimaII I2C interface.
742 This driver can also be built as a module. If so, the module
743 will be called i2c-sirf.
746 tristate "STMicroelectronics SSC I2C support"
749 Enable this option to add support for STMicroelectronics SoCs
750 hardware SSC (Synchronous Serial Controller) as an I2C controller.
752 This driver can also be built as module. If so, the module
753 will be called i2c-st.
756 tristate "ST Microelectronics DDC I2C interface"
758 default y if MACH_U300
760 If you say yes to this option, support will be included for the
761 I2C interface from ST Microelectronics simply called "DDC I2C"
762 supporting both I2C and DDC, used in e.g. the U300 series
765 This driver can also be built as a module. If so, the module
766 will be called i2c-stu300.
768 config I2C_SUN6I_P2WI
769 tristate "Allwinner sun6i internal P2WI controller"
770 depends on RESET_CONTROLLER
771 depends on MACH_SUN6I || COMPILE_TEST
773 If you say yes to this option, support will be included for the
774 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
776 The P2WI looks like an SMBus controller (which supports only byte
777 accesses), except that it only supports one slave device.
778 This interface is used to connect to specific PMIC devices (like the
782 tristate "NVIDIA Tegra internal I2C controller"
783 depends on ARCH_TEGRA
785 If you say yes to this option, support will be included for the
786 I2C controller embedded in NVIDIA Tegra SOCs
789 tristate "ARM Versatile/Realview I2C bus support"
790 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
793 Say yes if you want to support the I2C serial bus on ARMs Versatile
796 This driver can also be built as a module. If so, the module
797 will be called i2c-versatile.
800 tristate "Wondermedia WM8xxx SoC I2C bus support"
801 depends on ARCH_VT8500
803 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
806 This driver can also be built as a module. If so, the module will be
810 tristate "Cavium OCTEON I2C bus support"
811 depends on CAVIUM_OCTEON_SOC
813 Say yes if you want to support the I2C serial bus on Cavium
816 This driver can also be built as a module. If so, the module
817 will be called i2c-octeon.
820 tristate "Xilinx I2C Controller"
823 If you say yes to this option, support will be included for the
824 Xilinx I2C controller.
826 This driver can also be built as a module. If so, the module
827 will be called xilinx_i2c.
830 tristate "XLR I2C support"
833 This driver enables support for the on-chip I2C interface of
834 the Netlogic XLR/XLS MIPS processors.
836 This driver can also be built as a module. If so, the module
837 will be called i2c-xlr.
840 tristate "Renesas R-Car I2C Controller"
841 depends on ARCH_SHMOBILE || COMPILE_TEST
843 If you say yes to this option, support will be included for the
844 R-Car I2C controller.
846 This driver can also be built as a module. If so, the module
847 will be called i2c-rcar.
849 comment "External I2C/SMBus adapter drivers"
851 config I2C_DIOLAN_U2C
852 tristate "Diolan U2C-12 USB adapter"
855 If you say yes to this option, support will be included for Diolan
856 U2C-12, a USB to I2C interface.
858 This driver can also be built as a module. If so, the module
859 will be called i2c-diolan-u2c.
862 tristate "Parallel port adapter"
867 This supports parallel port I2C adapters such as the ones made by
868 Philips or Velleman, Analog Devices evaluation boards, and more.
869 Basically any adapter using the parallel port as an I2C bus with
870 no extra chipset is supported by this driver, or could be.
872 This driver is a replacement for (and was inspired by) an older
873 driver named i2c-philips-par. The new driver supports more devices,
874 and makes it easier to add support for new devices.
876 An adapter type parameter is now mandatory. Please read the file
877 Documentation/i2c/busses/i2c-parport for details.
879 Another driver exists, named i2c-parport-light, which doesn't depend
880 on the parport driver. This is meant for embedded systems. Don't say
881 Y here if you intend to say Y or M there.
883 This support is also available as a module. If so, the module
884 will be called i2c-parport.
886 config I2C_PARPORT_LIGHT
887 tristate "Parallel port adapter (light)"
891 This supports parallel port I2C adapters such as the ones made by
892 Philips or Velleman, Analog Devices evaluation boards, and more.
893 Basically any adapter using the parallel port as an I2C bus with
894 no extra chipset is supported by this driver, or could be.
896 This driver is a light version of i2c-parport. It doesn't depend
897 on the parport driver, and uses direct I/O access instead. This
898 might be preferred on embedded systems where wasting memory for
899 the clean but heavy parport handling is not an option. The
900 drawback is a reduced portability and the impossibility to
901 daisy-chain other parallel port devices.
903 Don't say Y here if you said Y or M to i2c-parport. Saying M to
904 both is possible but both modules should not be loaded at the same
907 This support is also available as a module. If so, the module
908 will be called i2c-parport-light.
910 config I2C_ROBOTFUZZ_OSIF
911 tristate "RobotFuzz Open Source InterFace USB adapter"
914 If you say yes to this option, support will be included for the
915 RobotFuzz Open Source InterFace USB to I2C interface.
917 This driver can also be built as a module. If so, the module
918 will be called i2c-osif.
921 tristate "TAOS evaluation module"
927 This supports TAOS evaluation modules on serial port. In order to
928 use this driver, you will need the inputattach tool, which is part
929 of the input-utils package.
933 This support is also available as a module. If so, the module
934 will be called i2c-taos-evm.
937 tristate "Tiny-USB adapter"
940 If you say yes to this option, support will be included for the
941 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
942 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
944 This driver can also be built as a module. If so, the module
945 will be called i2c-tiny-usb.
947 config I2C_VIPERBOARD
948 tristate "Viperboard I2C master support"
949 depends on MFD_VIPERBOARD && USB
951 Say yes here to access the I2C part of the Nano River
952 Technologies Viperboard as I2C master.
953 See viperboard API specification and Nano
954 River Tech's viperboard.h for detailed meaning
955 of the module parameters.
957 comment "Other I2C/SMBus bus drivers"
960 tristate "Acorn IOC/IOMD I2C bus support"
961 depends on ARCH_ACORN
965 Say yes if you want to support the I2C bus on Acorn platforms.
967 If you don't know, say Y.
970 tristate "Elektor ISA card"
971 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
974 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
977 This support is also available as a module. If so, the module
978 will be called i2c-elektor.
981 tristate "PCA9564/PCA9665 on an ISA bus"
986 This driver supports ISA boards using the Philips PCA9564/PCA9665
987 parallel bus to I2C bus controller.
989 This driver can also be built as a module. If so, the module
990 will be called i2c-pca-isa.
992 This device is almost undetectable and using this driver on a
993 system which doesn't have this device will result in long
994 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
995 time). If unsure, say N.
998 tristate "SiByte SMBus interface"
999 depends on SIBYTE_SB1xxx_SOC
1001 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
1003 config I2C_CROS_EC_TUNNEL
1004 tristate "ChromeOS EC tunnel I2C bus"
1005 depends on MFD_CROS_EC
1007 If you say yes here you get an I2C bus that will tunnel i2c commands
1008 through to the other side of the ChromeOS EC to the i2c bus
1009 connected there. This will work whatever the interface used to
1010 talk to the EC (SPI, I2C or LPC).
1013 tristate "Geode ACCESS.bus support"
1014 depends on X86_32 && PCI
1016 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1017 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1019 If you don't know what to do here, say N.
1021 This support is also available as a module. If so, the module
1022 will be called scx200_acb.