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)
112 Wildcat Point-LP (PCH)
114 This driver can also be built as a module. If so, the module
115 will be called i2c-i801.
118 tristate "Intel SCH SMBus 1.0"
122 Say Y here if you want to use SMBus controller on the Intel SCH
125 This driver can also be built as a module. If so, the module
126 will be called i2c-isch.
129 tristate "Intel iSMT SMBus Controller"
130 depends on PCI && X86
132 If you say yes to this option, support will be included for the Intel
133 iSMT SMBus host controller interface.
135 This driver can also be built as a module. If so, the module will be
139 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
142 If you say yes to this option, support will be included for the Intel
143 PIIX4 family of mainboard I2C interfaces. Specifically, the following
144 versions of the chipset are supported (note that Serverworks is part
163 Some AMD chipsets contain two PIIX4-compatible SMBus
164 controllers. This driver will attempt to use both controllers
165 on the SB700/SP5100, if they have been initialized by the BIOS.
167 This driver can also be built as a module. If so, the module
168 will be called i2c-piix4.
171 tristate "Nvidia nForce2, nForce3 and nForce4"
174 If you say yes to this option, support will be included for the Nvidia
175 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
177 This driver can also be built as a module. If so, the module
178 will be called i2c-nforce2.
180 config I2C_NFORCE2_S4985
181 tristate "SMBus multiplexing on the Tyan S4985"
182 depends on I2C_NFORCE2 && X86
184 Enabling this option will add specific SMBus support for the Tyan
185 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
186 over 4 different channels, where the various memory module EEPROMs
187 live. Saying yes here will give you access to these in addition
190 This driver can also be built as a module. If so, the module
191 will be called i2c-nforce2-s4985.
197 If you say yes to this option, support will be included for the
198 SiS5595 SMBus (a subset of I2C) interface.
200 This driver can also be built as a module. If so, the module
201 will be called i2c-sis5595.
204 tristate "SiS 630/730/964"
207 If you say yes to this option, support will be included for the
208 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
210 This driver can also be built as a module. If so, the module
211 will be called i2c-sis630.
217 If you say yes to this option, support will be included for the SiS
218 96x SMBus (a subset of I2C) interfaces. Specifically, the following
219 chipsets are supported:
228 This driver can also be built as a module. If so, the module
229 will be called i2c-sis96x.
232 tristate "VIA VT82C586B"
236 If you say yes to this option, support will be included for the VIA
237 82C586B I2C interface
239 This driver can also be built as a module. If so, the module
240 will be called i2c-via.
243 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
246 If you say yes to this option, support will be included for the VIA
247 VT82C596 and later SMBus interface. Specifically, the following
248 chipsets are supported:
261 This driver can also be built as a module. If so, the module
262 will be called i2c-viapro.
266 comment "ACPI drivers"
269 tristate "SMBus Control Method Interface"
271 This driver supports the SMBus Control Method Interface. It needs the
272 BIOS to declare ACPI control methods as described in the SMBus Control
273 Method Interface specification.
275 To compile this driver as a module, choose M here:
276 the module will be called i2c-scmi.
280 comment "Mac SMBus host controller drivers"
281 depends on PPC_CHRP || PPC_PMAC
284 tristate "CHRP Apple Hydra Mac I/O I2C interface"
285 depends on PCI && PPC_CHRP
288 This supports the use of the I2C interface in the Apple Hydra Mac
289 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
292 This support is also available as a module. If so, the module
293 will be called i2c-hydra.
296 tristate "Powermac I2C interface"
300 This exposes the various PowerMac i2c interfaces to the linux i2c
301 layer and to userland. It is used by various drivers on the PowerMac
302 platform, and should generally be enabled.
304 This support is also available as a module. If so, the module
305 will be called i2c-powermac.
307 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
310 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
313 This supports the use of the I2C interface on Atmel AT91
316 A serious problem is that there is no documented way to issue
317 repeated START conditions for more than two messages, as needed
318 to support combined I2C messages. Use the i2c-gpio driver
319 unless your system can cope with this limitation.
321 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
322 don't have clock stretching in transmission mode. For that reason,
323 you can encounter underrun issues causing premature stop sendings if
324 the latency to fill the transmission register is too long. If you
325 are facing this situation, use the i2c-gpio driver.
328 tristate "Au1550/Au1200/Au1300 SMBus interface"
329 depends on MIPS_ALCHEMY
331 If you say yes to this option, support will be included for the
332 Au1550/Au1200/Au1300 SMBus interface.
334 This driver can also be built as a module. If so, the module
335 will be called i2c-au1550.
338 tristate "Broadcom BCM2835 I2C controller"
339 depends on ARCH_BCM2835
341 If you say yes to this option, support will be included for the
342 BCM2835 I2C controller.
344 If you don't know what to do here, say N.
346 This support is also available as a module. If so, the module
347 will be called i2c-bcm2835.
350 tristate "BCM Kona I2C adapter"
351 depends on ARCH_BCM_MOBILE
354 If you say yes to this option, support will be included for the
355 I2C interface on the Broadcom Kona family of processors.
357 If you do not need KONA I2C inteface, say N.
359 config I2C_BLACKFIN_TWI
360 tristate "Blackfin TWI I2C support"
362 depends on !BF561 && !BF531 && !BF532 && !BF533
364 This is the I2C bus driver for Blackfin on-chip TWI interface.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-bfin-twi.
369 config I2C_BLACKFIN_TWI_CLK_KHZ
370 int "Blackfin TWI I2C clock (kHz)"
371 depends on I2C_BLACKFIN_TWI
375 The unit of the TWI clock is kHz.
378 tristate "CBUS I2C driver"
381 Support for CBUS access using I2C API. Mostly relevant for Nokia
382 Internet Tablets (770, N800 and N810).
384 This driver can also be built as a module. If so, the module
385 will be called i2c-cbus-gpio.
388 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
389 depends on (CPM1 || CPM2) && OF_I2C
391 This supports the use of the I2C interface on Freescale
392 processors with CPM1 or CPM2.
394 This driver can also be built as a module. If so, the module
395 will be called i2c-cpm.
398 tristate "DaVinci I2C driver"
399 depends on ARCH_DAVINCI || ARCH_KEYSTONE
401 Support for TI DaVinci I2C controller driver.
403 This driver can also be built as a module. If so, the module
404 will be called i2c-davinci.
406 Please note that this driver might be needed to bring up other
407 devices such as DaVinci NIC.
408 For details please see http://www.ti.com/davinci
410 config I2C_DESIGNWARE_CORE
413 config I2C_DESIGNWARE_PLATFORM
414 tristate "Synopsys DesignWare Platform"
415 select I2C_DESIGNWARE_CORE
417 If you say yes to this option, support will be included for the
418 Synopsys DesignWare I2C adapter. Only master mode is supported.
420 This driver can also be built as a module. If so, the module
421 will be called i2c-designware-platform.
423 config I2C_DESIGNWARE_PCI
424 tristate "Synopsys DesignWare PCI"
426 select I2C_DESIGNWARE_CORE
428 If you say yes to this option, support will be included for the
429 Synopsys DesignWare I2C adapter. Only master mode is supported.
431 This driver can also be built as a module. If so, the module
432 will be called i2c-designware-pci.
435 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
438 This driver is for PCH(Platform controller Hub) I2C of EG20T which
439 is an IOH(Input/Output Hub) for x86 embedded processor.
440 This driver can access PCH I2C bus device.
442 This driver also can be used for LAPIS Semiconductor IOH(Input/
443 Output Hub), ML7213, ML7223 and ML7831.
444 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
445 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
446 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
447 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
450 tristate "Exynos5 high-speed I2C driver"
451 depends on ARCH_EXYNOS5 && OF
453 Say Y here to include support for high-speed I2C controller in the
454 Exynos5 based Samsung SoCs.
457 tristate "GPIO-based bitbanging I2C"
461 This is a very simple bitbanging I2C driver utilizing the
462 arch-neutral GPIO API to control the SCL and SDA lines.
464 config I2C_HIGHLANDER
465 tristate "Highlander FPGA SMBus interface"
466 depends on SH_HIGHLANDER
468 If you say yes to this option, support will be included for
469 the SMBus interface located in the FPGA on various Highlander
470 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
471 FPGAs. This is wholly unrelated to the SoC I2C.
473 This driver can also be built as a module. If so, the module
474 will be called i2c-highlander.
477 tristate "IBM PPC 4xx on-chip I2C interface"
480 Say Y here if you want to use IIC peripheral found on
481 embedded IBM PPC 4xx based systems.
483 This driver can also be built as a module. If so, the module
484 will be called i2c-ibm_iic.
487 tristate "IMX I2C interface"
490 Say Y here if you want to use the IIC bus controller on
491 the Freescale i.MX/MXC processors.
493 This driver can also be built as a module. If so, the module
494 will be called i2c-imx.
497 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
498 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
500 Say Y here if you want to use the IIC bus controller on
501 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
503 This driver can also be built as a module. If so, the module
504 will be called i2c-iop3xx.
507 tristate "Kontron COM I2C Controller"
508 depends on MFD_KEMPLD
510 This enables support for the I2C bus interface on some Kontron ETX
511 and COMexpress (ETXexpress) modules.
513 This driver can also be built as a module. If so, the module
514 will be called i2c-kempld.
517 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
520 If you say yes to this option, support will be included for the
521 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
522 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
524 This driver can also be built as a module. If so, the module
525 will be called i2c-mpc.
528 tristate "Marvell mv64xxx I2C Controller"
529 depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI)
531 If you say yes to this option, support will be included for the
532 built-in I2C interface on the Marvell 64xxx line of host bridges.
533 This driver is also used for Allwinner SoCs I2C controllers.
535 This driver can also be built as a module. If so, the module
536 will be called i2c-mv64xxx.
539 tristate "Freescale i.MX28 I2C interface"
543 Say Y here if you want to use the I2C bus controller on
544 the Freescale i.MX28 processors.
546 This driver can also be built as a module. If so, the module
547 will be called i2c-mxs.
550 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
553 If you say yes to this option, support will be included for the
554 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
555 as well as the STA2X11 PCIe I/O HUB.
558 tristate "NUC900 I2C Driver"
559 depends on ARCH_W90X900
561 Say Y here to include support for I2C controller in the
562 Winbond/Nuvoton NUC900 based System-on-Chip devices.
565 tristate "OpenCores I2C Controller"
567 If you say yes to this option, support will be included for the
568 OpenCores I2C controller. For details see
569 http://www.opencores.org/projects.cgi/web/i2c/overview
571 This driver can also be built as a module. If so, the module
572 will be called i2c-ocores.
575 tristate "OMAP I2C adapter"
577 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
579 If you say yes to this option, support will be included for the
580 I2C interface on the Texas Instruments OMAP1/2 family of processors.
581 Like OMAP1510/1610/1710/5912 and OMAP242x.
582 For details see http://www.ti.com/omap.
585 tristate "PA Semi SMBus interface"
586 depends on PPC_PASEMI && PCI
588 Supports the PA Semi PWRficient on-chip SMBus interfaces.
590 config I2C_PCA_PLATFORM
591 tristate "PCA9564/PCA9665 as platform device"
595 This driver supports a memory mapped Philips PCA9564/PCA9665
596 parallel bus to I2C bus controller.
598 This driver can also be built as a module. If so, the module
599 will be called i2c-pca-platform.
602 tristate "PMC MSP I2C TWI Controller"
605 This driver supports the PMC TWI controller on MSP devices.
607 This driver can also be built as module. If so, the module
608 will be called i2c-pmcmsp.
611 tristate "I2C bus support for Philips PNX and NXP LPC targets"
612 depends on ARCH_LPC32XX
614 This driver supports the Philips IP3204 I2C IP block master and/or
617 This driver can also be built as a module. If so, the module
618 will be called i2c-pnx.
621 tristate "PKUnity v3 I2C bus support"
622 depends on UNICORE32 && ARCH_PUV3
625 This driver supports the I2C IP inside the PKUnity-v3 SoC.
626 This I2C bus controller is under AMBA/AXI bus.
628 This driver can also be built as a module. If so, the module
629 will be called i2c-puv3.
632 tristate "Intel PXA2XX I2C adapter"
633 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
635 If you have devices in the PXA I2C bus, say yes to this option.
636 This driver can also be built as a module. If so, the module
637 will be called i2c-pxa.
640 def_bool I2C_PXA && X86_32 && PCI && OF
643 bool "Intel PXA2XX I2C Slave comms support"
644 depends on I2C_PXA && !X86_32
646 Support I2C slave mode communications on the PXA I2C bus. This
647 is necessary for systems where the PXA may be a target on the
651 tristate "Renesas RIIC adapter"
652 depends on ARCH_SHMOBILE || COMPILE_TEST
654 If you say yes to this option, support will be included for the
655 Renesas RIIC I2C interface.
657 This driver can also be built as a module. If so, the module
658 will be called i2c-riic.
660 config HAVE_S3C2410_I2C
663 This will include I2C support for Samsung SoCs. If you want to
664 include I2C support for any machine, kindly select this in the
665 respective Kconfig file.
668 tristate "S3C2410 I2C Driver"
669 depends on HAVE_S3C2410_I2C
671 Say Y here to include support for I2C controller in the
675 tristate "S6000 I2C support"
676 depends on XTENSA_VARIANT_S6000
678 This driver supports the on chip I2C device on the
679 S6000 xtensa processor family.
681 To compile this driver as a module, choose M here. The module
682 will be called i2c-s6000.
685 tristate "Renesas SH7760 I2C Controller"
686 depends on CPU_SUBTYPE_SH7760
688 This driver supports the 2 I2C interfaces on the Renesas SH7760.
690 This driver can also be built as a module. If so, the module
691 will be called i2c-sh7760.
694 tristate "SuperH Mobile I2C Controller"
695 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
697 If you say yes to this option, support will be included for the
698 built-in I2C interface on the Renesas SH-Mobile processor.
700 This driver can also be built as a module. If so, the module
701 will be called i2c-sh_mobile.
704 tristate "Simtec Generic I2C interface"
707 If you say yes to this option, support will be included for
708 the Simtec Generic I2C interface. This driver is for the
709 simple I2C bus used on newer Simtec products for general
710 I2C, such as DDC on the Simtec BBD2016A.
712 This driver can also be built as a module. If so, the module
713 will be called i2c-simtec.
716 tristate "CSR SiRFprimaII I2C interface"
719 If you say yes to this option, support will be included for the
720 CSR SiRFprimaII I2C interface.
722 This driver can also be built as a module. If so, the module
723 will be called i2c-sirf.
726 tristate "STMicroelectronics SSC I2C support"
729 Enable this option to add support for STMicroelectronics SoCs
730 hardware SSC (Synchronous Serial Controller) as an I2C controller.
732 This driver can also be built as module. If so, the module
733 will be called i2c-st.
736 tristate "ST Microelectronics DDC I2C interface"
738 default y if MACH_U300
740 If you say yes to this option, support will be included for the
741 I2C interface from ST Microelectronics simply called "DDC I2C"
742 supporting both I2C and DDC, used in e.g. the U300 series
745 This driver can also be built as a module. If so, the module
746 will be called i2c-stu300.
749 tristate "NVIDIA Tegra internal I2C controller"
750 depends on ARCH_TEGRA
752 If you say yes to this option, support will be included for the
753 I2C controller embedded in NVIDIA Tegra SOCs
756 tristate "ARM Versatile/Realview I2C bus support"
757 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
760 Say yes if you want to support the I2C serial bus on ARMs Versatile
763 This driver can also be built as a module. If so, the module
764 will be called i2c-versatile.
767 tristate "Wondermedia WM8xxx SoC I2C bus support"
768 depends on ARCH_VT8500
770 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
773 This driver can also be built as a module. If so, the module will be
777 tristate "Cavium OCTEON I2C bus support"
778 depends on CAVIUM_OCTEON_SOC
780 Say yes if you want to support the I2C serial bus on Cavium
783 This driver can also be built as a module. If so, the module
784 will be called i2c-octeon.
787 tristate "Xilinx I2C Controller"
790 If you say yes to this option, support will be included for the
791 Xilinx I2C controller.
793 This driver can also be built as a module. If so, the module
794 will be called xilinx_i2c.
797 tristate "XLR I2C support"
800 This driver enables support for the on-chip I2C interface of
801 the Netlogic XLR/XLS MIPS processors.
803 This driver can also be built as a module. If so, the module
804 will be called i2c-xlr.
807 tristate "Renesas R-Car I2C Controller"
808 depends on ARCH_SHMOBILE || COMPILE_TEST
810 If you say yes to this option, support will be included for the
811 R-Car I2C controller.
813 This driver can also be built as a module. If so, the module
814 will be called i2c-rcar.
816 comment "External I2C/SMBus adapter drivers"
818 config I2C_DIOLAN_U2C
819 tristate "Diolan U2C-12 USB adapter"
822 If you say yes to this option, support will be included for Diolan
823 U2C-12, a USB to I2C interface.
825 This driver can also be built as a module. If so, the module
826 will be called i2c-diolan-u2c.
829 tristate "Parallel port adapter"
834 This supports parallel port I2C adapters such as the ones made by
835 Philips or Velleman, Analog Devices evaluation boards, and more.
836 Basically any adapter using the parallel port as an I2C bus with
837 no extra chipset is supported by this driver, or could be.
839 This driver is a replacement for (and was inspired by) an older
840 driver named i2c-philips-par. The new driver supports more devices,
841 and makes it easier to add support for new devices.
843 An adapter type parameter is now mandatory. Please read the file
844 Documentation/i2c/busses/i2c-parport for details.
846 Another driver exists, named i2c-parport-light, which doesn't depend
847 on the parport driver. This is meant for embedded systems. Don't say
848 Y here if you intend to say Y or M there.
850 This support is also available as a module. If so, the module
851 will be called i2c-parport.
853 config I2C_PARPORT_LIGHT
854 tristate "Parallel port adapter (light)"
858 This supports parallel port I2C adapters such as the ones made by
859 Philips or Velleman, Analog Devices evaluation boards, and more.
860 Basically any adapter using the parallel port as an I2C bus with
861 no extra chipset is supported by this driver, or could be.
863 This driver is a light version of i2c-parport. It doesn't depend
864 on the parport driver, and uses direct I/O access instead. This
865 might be preferred on embedded systems where wasting memory for
866 the clean but heavy parport handling is not an option. The
867 drawback is a reduced portability and the impossibility to
868 daisy-chain other parallel port devices.
870 Don't say Y here if you said Y or M to i2c-parport. Saying M to
871 both is possible but both modules should not be loaded at the same
874 This support is also available as a module. If so, the module
875 will be called i2c-parport-light.
877 config I2C_ROBOTFUZZ_OSIF
878 tristate "RobotFuzz Open Source InterFace USB adapter"
881 If you say yes to this option, support will be included for the
882 RobotFuzz Open Source InterFace USB to I2C interface.
884 This driver can also be built as a module. If so, the module
885 will be called i2c-osif.
888 tristate "TAOS evaluation module"
894 This supports TAOS evaluation modules on serial port. In order to
895 use this driver, you will need the inputattach tool, which is part
896 of the input-utils package.
900 This support is also available as a module. If so, the module
901 will be called i2c-taos-evm.
904 tristate "Tiny-USB adapter"
907 If you say yes to this option, support will be included for the
908 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
909 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
911 This driver can also be built as a module. If so, the module
912 will be called i2c-tiny-usb.
914 config I2C_VIPERBOARD
915 tristate "Viperboard I2C master support"
916 depends on MFD_VIPERBOARD && USB
918 Say yes here to access the I2C part of the Nano River
919 Technologies Viperboard as I2C master.
920 See viperboard API specification and Nano
921 River Tech's viperboard.h for detailed meaning
922 of the module parameters.
924 comment "Other I2C/SMBus bus drivers"
927 tristate "Acorn IOC/IOMD I2C bus support"
928 depends on ARCH_ACORN
932 Say yes if you want to support the I2C bus on Acorn platforms.
934 If you don't know, say Y.
937 tristate "Elektor ISA card"
938 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
941 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
944 This support is also available as a module. If so, the module
945 will be called i2c-elektor.
948 tristate "PCA9564/PCA9665 on an ISA bus"
953 This driver supports ISA boards using the Philips PCA9564/PCA9665
954 parallel bus to I2C bus controller.
956 This driver can also be built as a module. If so, the module
957 will be called i2c-pca-isa.
959 This device is almost undetectable and using this driver on a
960 system which doesn't have this device will result in long
961 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
962 time). If unsure, say N.
965 tristate "SiByte SMBus interface"
966 depends on SIBYTE_SB1xxx_SOC
968 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
971 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
972 depends on SCx200_GPIO
975 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
977 If you don't know what to do here, say N.
979 This support is also available as a module. If so, the module
980 will be called scx200_i2c.
982 This driver is deprecated and will be dropped soon. Use i2c-gpio
983 (or scx200_acb) instead.
985 config SCx200_I2C_SCL
986 int "GPIO pin used for SCL"
987 depends on SCx200_I2C
990 Enter the GPIO pin number used for the SCL signal. This value can
991 also be specified with a module parameter.
993 config SCx200_I2C_SDA
994 int "GPIO pin used for SDA"
995 depends on SCx200_I2C
998 Enter the GPIO pin number used for the SSA signal. This value can
999 also be specified with a module parameter.
1002 tristate "Geode ACCESS.bus support"
1003 depends on X86_32 && PCI
1005 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1006 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1008 If you don't know what to do here, say N.
1010 This support is also available as a module. If so, the module
1011 will be called scx200_acb.