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 "CBUS I2C driver"
384 Support for CBUS access using I2C API. Mostly relevant for Nokia
385 Internet Tablets (770, N800 and N810).
387 This driver can also be built as a module. If so, the module
388 will be called i2c-cbus-gpio.
391 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
392 depends on CPM1 || CPM2
394 This supports the use of the I2C interface on Freescale
395 processors with CPM1 or CPM2.
397 This driver can also be built as a module. If so, the module
398 will be called i2c-cpm.
401 tristate "DaVinci I2C driver"
402 depends on ARCH_DAVINCI || ARCH_KEYSTONE
404 Support for TI DaVinci I2C controller driver.
406 This driver can also be built as a module. If so, the module
407 will be called i2c-davinci.
409 Please note that this driver might be needed to bring up other
410 devices such as DaVinci NIC.
411 For details please see http://www.ti.com/davinci
413 config I2C_DESIGNWARE_CORE
416 config I2C_DESIGNWARE_PLATFORM
417 tristate "Synopsys DesignWare Platform"
418 select I2C_DESIGNWARE_CORE
420 If you say yes to this option, support will be included for the
421 Synopsys DesignWare I2C adapter. Only master mode is supported.
423 This driver can also be built as a module. If so, the module
424 will be called i2c-designware-platform.
426 config I2C_DESIGNWARE_PCI
427 tristate "Synopsys DesignWare PCI"
429 select I2C_DESIGNWARE_CORE
431 If you say yes to this option, support will be included for the
432 Synopsys DesignWare I2C adapter. Only master mode is supported.
434 This driver can also be built as a module. If so, the module
435 will be called i2c-designware-pci.
438 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
441 This driver is for PCH(Platform controller Hub) I2C of EG20T which
442 is an IOH(Input/Output Hub) for x86 embedded processor.
443 This driver can access PCH I2C bus device.
445 This driver also can be used for LAPIS Semiconductor IOH(Input/
446 Output Hub), ML7213, ML7223 and ML7831.
447 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
448 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
449 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
450 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
453 tristate "Exynos5 high-speed I2C driver"
454 depends on ARCH_EXYNOS5 && OF
456 Say Y here to include support for high-speed I2C controller in the
457 Exynos5 based Samsung SoCs.
460 tristate "GPIO-based bitbanging I2C"
464 This is a very simple bitbanging I2C driver utilizing the
465 arch-neutral GPIO API to control the SCL and SDA lines.
467 config I2C_HIGHLANDER
468 tristate "Highlander FPGA SMBus interface"
469 depends on SH_HIGHLANDER
471 If you say yes to this option, support will be included for
472 the SMBus interface located in the FPGA on various Highlander
473 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
474 FPGAs. This is wholly unrelated to the SoC I2C.
476 This driver can also be built as a module. If so, the module
477 will be called i2c-highlander.
480 tristate "IBM PPC 4xx on-chip I2C interface"
483 Say Y here if you want to use IIC peripheral found on
484 embedded IBM PPC 4xx based systems.
486 This driver can also be built as a module. If so, the module
487 will be called i2c-ibm_iic.
490 tristate "IMX I2C interface"
493 Say Y here if you want to use the IIC bus controller on
494 the Freescale i.MX/MXC processors.
496 This driver can also be built as a module. If so, the module
497 will be called i2c-imx.
500 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
501 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
503 Say Y here if you want to use the IIC bus controller on
504 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
506 This driver can also be built as a module. If so, the module
507 will be called i2c-iop3xx.
510 tristate "Kontron COM I2C Controller"
511 depends on MFD_KEMPLD
513 This enables support for the I2C bus interface on some Kontron ETX
514 and COMexpress (ETXexpress) modules.
516 This driver can also be built as a module. If so, the module
517 will be called i2c-kempld.
520 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
523 If you say yes to this option, support will be included for the
524 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
525 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
527 This driver can also be built as a module. If so, the module
528 will be called i2c-mpc.
531 tristate "Marvell mv64xxx I2C Controller"
532 depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI)
534 If you say yes to this option, support will be included for the
535 built-in I2C interface on the Marvell 64xxx line of host bridges.
536 This driver is also used for Allwinner SoCs I2C controllers.
538 This driver can also be built as a module. If so, the module
539 will be called i2c-mv64xxx.
542 tristate "Freescale i.MX28 I2C interface"
546 Say Y here if you want to use the I2C bus controller on
547 the Freescale i.MX28 processors.
549 This driver can also be built as a module. If so, the module
550 will be called i2c-mxs.
553 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
556 If you say yes to this option, support will be included for the
557 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
558 as well as the STA2X11 PCIe I/O HUB.
561 tristate "NUC900 I2C Driver"
562 depends on ARCH_W90X900
564 Say Y here to include support for I2C controller in the
565 Winbond/Nuvoton NUC900 based System-on-Chip devices.
568 tristate "OpenCores I2C Controller"
570 If you say yes to this option, support will be included for the
571 OpenCores I2C controller. For details see
572 http://www.opencores.org/projects.cgi/web/i2c/overview
574 This driver can also be built as a module. If so, the module
575 will be called i2c-ocores.
578 tristate "OMAP I2C adapter"
580 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
582 If you say yes to this option, support will be included for the
583 I2C interface on the Texas Instruments OMAP1/2 family of processors.
584 Like OMAP1510/1610/1710/5912 and OMAP242x.
585 For details see http://www.ti.com/omap.
588 tristate "PA Semi SMBus interface"
589 depends on PPC_PASEMI && PCI
591 Supports the PA Semi PWRficient on-chip SMBus interfaces.
593 config I2C_PCA_PLATFORM
594 tristate "PCA9564/PCA9665 as platform device"
598 This driver supports a memory mapped Philips PCA9564/PCA9665
599 parallel bus to I2C bus controller.
601 This driver can also be built as a module. If so, the module
602 will be called i2c-pca-platform.
605 tristate "PMC MSP I2C TWI Controller"
608 This driver supports the PMC TWI controller on MSP devices.
610 This driver can also be built as module. If so, the module
611 will be called i2c-pmcmsp.
614 tristate "I2C bus support for Philips PNX and NXP LPC targets"
615 depends on ARCH_LPC32XX
617 This driver supports the Philips IP3204 I2C IP block master and/or
620 This driver can also be built as a module. If so, the module
621 will be called i2c-pnx.
624 tristate "PKUnity v3 I2C bus support"
625 depends on UNICORE32 && ARCH_PUV3
628 This driver supports the I2C IP inside the PKUnity-v3 SoC.
629 This I2C bus controller is under AMBA/AXI bus.
631 This driver can also be built as a module. If so, the module
632 will be called i2c-puv3.
635 tristate "Intel PXA2XX I2C adapter"
636 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
638 If you have devices in the PXA I2C bus, say yes to this option.
639 This driver can also be built as a module. If so, the module
640 will be called i2c-pxa.
643 def_bool I2C_PXA && X86_32 && PCI && OF
646 bool "Intel PXA2XX I2C Slave comms support"
647 depends on I2C_PXA && !X86_32
649 Support I2C slave mode communications on the PXA I2C bus. This
650 is necessary for systems where the PXA may be a target on the
654 tristate "Renesas RIIC adapter"
655 depends on ARCH_SHMOBILE || COMPILE_TEST
657 If you say yes to this option, support will be included for the
658 Renesas RIIC I2C interface.
660 This driver can also be built as a module. If so, the module
661 will be called i2c-riic.
663 config HAVE_S3C2410_I2C
666 This will include I2C support for Samsung SoCs. If you want to
667 include I2C support for any machine, kindly select this in the
668 respective Kconfig file.
671 tristate "S3C2410 I2C Driver"
672 depends on HAVE_S3C2410_I2C
674 Say Y here to include support for I2C controller in the
678 tristate "S6000 I2C support"
679 depends on XTENSA_VARIANT_S6000
681 This driver supports the on chip I2C device on the
682 S6000 xtensa processor family.
684 To compile this driver as a module, choose M here. The module
685 will be called i2c-s6000.
688 tristate "Renesas SH7760 I2C Controller"
689 depends on CPU_SUBTYPE_SH7760
691 This driver supports the 2 I2C interfaces on the Renesas SH7760.
693 This driver can also be built as a module. If so, the module
694 will be called i2c-sh7760.
697 tristate "SuperH Mobile I2C Controller"
698 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
700 If you say yes to this option, support will be included for the
701 built-in I2C interface on the Renesas SH-Mobile processor.
703 This driver can also be built as a module. If so, the module
704 will be called i2c-sh_mobile.
707 tristate "Simtec Generic I2C interface"
710 If you say yes to this option, support will be included for
711 the Simtec Generic I2C interface. This driver is for the
712 simple I2C bus used on newer Simtec products for general
713 I2C, such as DDC on the Simtec BBD2016A.
715 This driver can also be built as a module. If so, the module
716 will be called i2c-simtec.
719 tristate "CSR SiRFprimaII I2C interface"
722 If you say yes to this option, support will be included for the
723 CSR SiRFprimaII I2C interface.
725 This driver can also be built as a module. If so, the module
726 will be called i2c-sirf.
729 tristate "STMicroelectronics SSC I2C support"
732 Enable this option to add support for STMicroelectronics SoCs
733 hardware SSC (Synchronous Serial Controller) as an I2C controller.
735 This driver can also be built as module. If so, the module
736 will be called i2c-st.
739 tristate "ST Microelectronics DDC I2C interface"
741 default y if MACH_U300
743 If you say yes to this option, support will be included for the
744 I2C interface from ST Microelectronics simply called "DDC I2C"
745 supporting both I2C and DDC, used in e.g. the U300 series
748 This driver can also be built as a module. If so, the module
749 will be called i2c-stu300.
752 tristate "NVIDIA Tegra internal I2C controller"
753 depends on ARCH_TEGRA
755 If you say yes to this option, support will be included for the
756 I2C controller embedded in NVIDIA Tegra SOCs
759 tristate "ARM Versatile/Realview I2C bus support"
760 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
763 Say yes if you want to support the I2C serial bus on ARMs Versatile
766 This driver can also be built as a module. If so, the module
767 will be called i2c-versatile.
770 tristate "Wondermedia WM8xxx SoC I2C bus support"
771 depends on ARCH_VT8500
773 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
776 This driver can also be built as a module. If so, the module will be
780 tristate "Cavium OCTEON I2C bus support"
781 depends on CAVIUM_OCTEON_SOC
783 Say yes if you want to support the I2C serial bus on Cavium
786 This driver can also be built as a module. If so, the module
787 will be called i2c-octeon.
790 tristate "Xilinx I2C Controller"
793 If you say yes to this option, support will be included for the
794 Xilinx I2C controller.
796 This driver can also be built as a module. If so, the module
797 will be called xilinx_i2c.
800 tristate "XLR I2C support"
803 This driver enables support for the on-chip I2C interface of
804 the Netlogic XLR/XLS MIPS processors.
806 This driver can also be built as a module. If so, the module
807 will be called i2c-xlr.
810 tristate "Renesas R-Car I2C Controller"
811 depends on ARCH_SHMOBILE || COMPILE_TEST
813 If you say yes to this option, support will be included for the
814 R-Car I2C controller.
816 This driver can also be built as a module. If so, the module
817 will be called i2c-rcar.
819 comment "External I2C/SMBus adapter drivers"
821 config I2C_DIOLAN_U2C
822 tristate "Diolan U2C-12 USB adapter"
825 If you say yes to this option, support will be included for Diolan
826 U2C-12, a USB to I2C interface.
828 This driver can also be built as a module. If so, the module
829 will be called i2c-diolan-u2c.
832 tristate "Parallel port adapter"
837 This supports parallel port I2C adapters such as the ones made by
838 Philips or Velleman, Analog Devices evaluation boards, and more.
839 Basically any adapter using the parallel port as an I2C bus with
840 no extra chipset is supported by this driver, or could be.
842 This driver is a replacement for (and was inspired by) an older
843 driver named i2c-philips-par. The new driver supports more devices,
844 and makes it easier to add support for new devices.
846 An adapter type parameter is now mandatory. Please read the file
847 Documentation/i2c/busses/i2c-parport for details.
849 Another driver exists, named i2c-parport-light, which doesn't depend
850 on the parport driver. This is meant for embedded systems. Don't say
851 Y here if you intend to say Y or M there.
853 This support is also available as a module. If so, the module
854 will be called i2c-parport.
856 config I2C_PARPORT_LIGHT
857 tristate "Parallel port adapter (light)"
861 This supports parallel port I2C adapters such as the ones made by
862 Philips or Velleman, Analog Devices evaluation boards, and more.
863 Basically any adapter using the parallel port as an I2C bus with
864 no extra chipset is supported by this driver, or could be.
866 This driver is a light version of i2c-parport. It doesn't depend
867 on the parport driver, and uses direct I/O access instead. This
868 might be preferred on embedded systems where wasting memory for
869 the clean but heavy parport handling is not an option. The
870 drawback is a reduced portability and the impossibility to
871 daisy-chain other parallel port devices.
873 Don't say Y here if you said Y or M to i2c-parport. Saying M to
874 both is possible but both modules should not be loaded at the same
877 This support is also available as a module. If so, the module
878 will be called i2c-parport-light.
880 config I2C_ROBOTFUZZ_OSIF
881 tristate "RobotFuzz Open Source InterFace USB adapter"
884 If you say yes to this option, support will be included for the
885 RobotFuzz Open Source InterFace USB to I2C interface.
887 This driver can also be built as a module. If so, the module
888 will be called i2c-osif.
891 tristate "TAOS evaluation module"
897 This supports TAOS evaluation modules on serial port. In order to
898 use this driver, you will need the inputattach tool, which is part
899 of the input-utils package.
903 This support is also available as a module. If so, the module
904 will be called i2c-taos-evm.
907 tristate "Tiny-USB adapter"
910 If you say yes to this option, support will be included for the
911 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
912 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
914 This driver can also be built as a module. If so, the module
915 will be called i2c-tiny-usb.
917 config I2C_VIPERBOARD
918 tristate "Viperboard I2C master support"
919 depends on MFD_VIPERBOARD && USB
921 Say yes here to access the I2C part of the Nano River
922 Technologies Viperboard as I2C master.
923 See viperboard API specification and Nano
924 River Tech's viperboard.h for detailed meaning
925 of the module parameters.
927 comment "Other I2C/SMBus bus drivers"
930 tristate "Acorn IOC/IOMD I2C bus support"
931 depends on ARCH_ACORN
935 Say yes if you want to support the I2C bus on Acorn platforms.
937 If you don't know, say Y.
940 tristate "Elektor ISA card"
941 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP
944 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
947 This support is also available as a module. If so, the module
948 will be called i2c-elektor.
951 tristate "PCA9564/PCA9665 on an ISA bus"
956 This driver supports ISA boards using the Philips PCA9564/PCA9665
957 parallel bus to I2C bus controller.
959 This driver can also be built as a module. If so, the module
960 will be called i2c-pca-isa.
962 This device is almost undetectable and using this driver on a
963 system which doesn't have this device will result in long
964 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
965 time). If unsure, say N.
968 tristate "SiByte SMBus interface"
969 depends on SIBYTE_SB1xxx_SOC
971 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
974 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
975 depends on SCx200_GPIO
978 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
980 If you don't know what to do here, say N.
982 This support is also available as a module. If so, the module
983 will be called scx200_i2c.
985 This driver is deprecated and will be dropped soon. Use i2c-gpio
986 (or scx200_acb) instead.
988 config SCx200_I2C_SCL
989 int "GPIO pin used for SCL"
990 depends on SCx200_I2C
993 Enter the GPIO pin number used for the SCL signal. This value can
994 also be specified with a module parameter.
996 config SCx200_I2C_SDA
997 int "GPIO pin used for SDA"
998 depends on SCx200_I2C
1001 Enter the GPIO pin number used for the SSA signal. This value can
1002 also be specified with a module parameter.
1005 tristate "Geode ACCESS.bus support"
1006 depends on X86_32 && PCI
1008 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1009 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1011 If you don't know what to do here, say N.
1013 This support is also available as a module. If so, the module
1014 will be called scx200_acb.