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)
115 This driver can also be built as a module. If so, the module
116 will be called i2c-i801.
119 tristate "Intel SCH SMBus 1.0"
123 Say Y here if you want to use SMBus controller on the Intel SCH
126 This driver can also be built as a module. If so, the module
127 will be called i2c-isch.
130 tristate "Intel iSMT SMBus Controller"
131 depends on PCI && X86
133 If you say yes to this option, support will be included for the Intel
134 iSMT SMBus host controller interface.
136 This driver can also be built as a module. If so, the module will be
140 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
143 If you say yes to this option, support will be included for the Intel
144 PIIX4 family of mainboard I2C interfaces. Specifically, the following
145 versions of the chipset are supported (note that Serverworks is part
165 Some AMD chipsets contain two PIIX4-compatible SMBus
166 controllers. This driver will attempt to use both controllers
167 on the SB700/SP5100, if they have been initialized by the BIOS.
169 This driver can also be built as a module. If so, the module
170 will be called i2c-piix4.
173 tristate "Nvidia nForce2, nForce3 and nForce4"
176 If you say yes to this option, support will be included for the Nvidia
177 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
179 This driver can also be built as a module. If so, the module
180 will be called i2c-nforce2.
182 config I2C_NFORCE2_S4985
183 tristate "SMBus multiplexing on the Tyan S4985"
184 depends on I2C_NFORCE2 && X86
186 Enabling this option will add specific SMBus support for the Tyan
187 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
188 over 4 different channels, where the various memory module EEPROMs
189 live. Saying yes here will give you access to these in addition
192 This driver can also be built as a module. If so, the module
193 will be called i2c-nforce2-s4985.
199 If you say yes to this option, support will be included for the
200 SiS5595 SMBus (a subset of I2C) interface.
202 This driver can also be built as a module. If so, the module
203 will be called i2c-sis5595.
206 tristate "SiS 630/730/964"
209 If you say yes to this option, support will be included for the
210 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
212 This driver can also be built as a module. If so, the module
213 will be called i2c-sis630.
219 If you say yes to this option, support will be included for the SiS
220 96x SMBus (a subset of I2C) interfaces. Specifically, the following
221 chipsets are supported:
230 This driver can also be built as a module. If so, the module
231 will be called i2c-sis96x.
234 tristate "VIA VT82C586B"
238 If you say yes to this option, support will be included for the VIA
239 82C586B I2C interface
241 This driver can also be built as a module. If so, the module
242 will be called i2c-via.
245 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
248 If you say yes to this option, support will be included for the VIA
249 VT82C596 and later SMBus interface. Specifically, the following
250 chipsets are supported:
263 This driver can also be built as a module. If so, the module
264 will be called i2c-viapro.
268 comment "ACPI drivers"
271 tristate "SMBus Control Method Interface"
273 This driver supports the SMBus Control Method Interface. It needs the
274 BIOS to declare ACPI control methods as described in the SMBus Control
275 Method Interface specification.
277 To compile this driver as a module, choose M here:
278 the module will be called i2c-scmi.
282 comment "Mac SMBus host controller drivers"
283 depends on PPC_CHRP || PPC_PMAC
286 tristate "CHRP Apple Hydra Mac I/O I2C interface"
287 depends on PCI && PPC_CHRP
290 This supports the use of the I2C interface in the Apple Hydra Mac
291 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
294 This support is also available as a module. If so, the module
295 will be called i2c-hydra.
298 tristate "Powermac I2C interface"
302 This exposes the various PowerMac i2c interfaces to the linux i2c
303 layer and to userland. It is used by various drivers on the PowerMac
304 platform, and should generally be enabled.
306 This support is also available as a module. If so, the module
307 will be called i2c-powermac.
309 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
312 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
315 This supports the use of the I2C interface on Atmel AT91
318 A serious problem is that there is no documented way to issue
319 repeated START conditions for more than two messages, as needed
320 to support combined I2C messages. Use the i2c-gpio driver
321 unless your system can cope with this limitation.
323 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
324 don't have clock stretching in transmission mode. For that reason,
325 you can encounter underrun issues causing premature stop sendings if
326 the latency to fill the transmission register is too long. If you
327 are facing this situation, use the i2c-gpio driver.
330 tristate "Au1550/Au1200/Au1300 SMBus interface"
331 depends on MIPS_ALCHEMY
333 If you say yes to this option, support will be included for the
334 Au1550/Au1200/Au1300 SMBus interface.
336 This driver can also be built as a module. If so, the module
337 will be called i2c-au1550.
340 tristate "Broadcom BCM2835 I2C controller"
341 depends on ARCH_BCM2835
343 If you say yes to this option, support will be included for the
344 BCM2835 I2C controller.
346 If you don't know what to do here, say N.
348 This support is also available as a module. If so, the module
349 will be called i2c-bcm2835.
352 tristate "BCM Kona I2C adapter"
353 depends on ARCH_BCM_MOBILE
356 If you say yes to this option, support will be included for the
357 I2C interface on the Broadcom Kona family of processors.
359 If you do not need KONA I2C inteface, say N.
361 config I2C_BLACKFIN_TWI
362 tristate "Blackfin TWI I2C support"
364 depends on !BF561 && !BF531 && !BF532 && !BF533
366 This is the I2C bus driver for Blackfin on-chip TWI interface.
368 This driver can also be built as a module. If so, the module
369 will be called i2c-bfin-twi.
371 config I2C_BLACKFIN_TWI_CLK_KHZ
372 int "Blackfin TWI I2C clock (kHz)"
373 depends on I2C_BLACKFIN_TWI
377 The unit of the TWI clock is kHz.
380 tristate "CBUS I2C driver"
383 Support for CBUS access using I2C API. Mostly relevant for Nokia
384 Internet Tablets (770, N800 and N810).
386 This driver can also be built as a module. If so, the module
387 will be called i2c-cbus-gpio.
390 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
391 depends on CPM1 || CPM2
393 This supports the use of the I2C interface on Freescale
394 processors with CPM1 or CPM2.
396 This driver can also be built as a module. If so, the module
397 will be called i2c-cpm.
400 tristate "DaVinci I2C driver"
401 depends on ARCH_DAVINCI || ARCH_KEYSTONE
403 Support for TI DaVinci I2C controller driver.
405 This driver can also be built as a module. If so, the module
406 will be called i2c-davinci.
408 Please note that this driver might be needed to bring up other
409 devices such as DaVinci NIC.
410 For details please see http://www.ti.com/davinci
412 config I2C_DESIGNWARE_CORE
415 config I2C_DESIGNWARE_PLATFORM
416 tristate "Synopsys DesignWare Platform"
417 select I2C_DESIGNWARE_CORE
419 If you say yes to this option, support will be included for the
420 Synopsys DesignWare I2C adapter. Only master mode is supported.
422 This driver can also be built as a module. If so, the module
423 will be called i2c-designware-platform.
425 config I2C_DESIGNWARE_PCI
426 tristate "Synopsys DesignWare PCI"
428 select I2C_DESIGNWARE_CORE
430 If you say yes to this option, support will be included for the
431 Synopsys DesignWare I2C adapter. Only master mode is supported.
433 This driver can also be built as a module. If so, the module
434 will be called i2c-designware-pci.
437 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
440 This driver is for PCH(Platform controller Hub) I2C of EG20T which
441 is an IOH(Input/Output Hub) for x86 embedded processor.
442 This driver can access PCH I2C bus device.
444 This driver also can be used for LAPIS Semiconductor IOH(Input/
445 Output Hub), ML7213, ML7223 and ML7831.
446 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
447 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
448 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
449 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
452 tristate "Exynos5 high-speed I2C driver"
453 depends on ARCH_EXYNOS5 && OF
455 Say Y here to include support for high-speed I2C controller in the
456 Exynos5 based Samsung SoCs.
459 tristate "GPIO-based bitbanging I2C"
463 This is a very simple bitbanging I2C driver utilizing the
464 arch-neutral GPIO API to control the SCL and SDA lines.
466 config I2C_HIGHLANDER
467 tristate "Highlander FPGA SMBus interface"
468 depends on SH_HIGHLANDER
470 If you say yes to this option, support will be included for
471 the SMBus interface located in the FPGA on various Highlander
472 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
473 FPGAs. This is wholly unrelated to the SoC I2C.
475 This driver can also be built as a module. If so, the module
476 will be called i2c-highlander.
479 tristate "IBM PPC 4xx on-chip I2C interface"
482 Say Y here if you want to use IIC peripheral found on
483 embedded IBM PPC 4xx based systems.
485 This driver can also be built as a module. If so, the module
486 will be called i2c-ibm_iic.
489 tristate "IMX I2C interface"
492 Say Y here if you want to use the IIC bus controller on
493 the Freescale i.MX/MXC processors.
495 This driver can also be built as a module. If so, the module
496 will be called i2c-imx.
499 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
500 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
502 Say Y here if you want to use the IIC bus controller on
503 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
505 This driver can also be built as a module. If so, the module
506 will be called i2c-iop3xx.
509 tristate "Kontron COM I2C Controller"
510 depends on MFD_KEMPLD
512 This enables support for the I2C bus interface on some Kontron ETX
513 and COMexpress (ETXexpress) modules.
515 This driver can also be built as a module. If so, the module
516 will be called i2c-kempld.
519 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
522 If you say yes to this option, support will be included for the
523 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
524 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
526 This driver can also be built as a module. If so, the module
527 will be called i2c-mpc.
530 tristate "Marvell mv64xxx I2C Controller"
531 depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI)
533 If you say yes to this option, support will be included for the
534 built-in I2C interface on the Marvell 64xxx line of host bridges.
535 This driver is also used for Allwinner SoCs I2C controllers.
537 This driver can also be built as a module. If so, the module
538 will be called i2c-mv64xxx.
541 tristate "Freescale i.MX28 I2C interface"
545 Say Y here if you want to use the I2C bus controller on
546 the Freescale i.MX28 processors.
548 This driver can also be built as a module. If so, the module
549 will be called i2c-mxs.
552 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
555 If you say yes to this option, support will be included for the
556 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
557 as well as the STA2X11 PCIe I/O HUB.
560 tristate "NUC900 I2C Driver"
561 depends on ARCH_W90X900
563 Say Y here to include support for I2C controller in the
564 Winbond/Nuvoton NUC900 based System-on-Chip devices.
567 tristate "OpenCores I2C Controller"
569 If you say yes to this option, support will be included for the
570 OpenCores I2C controller. For details see
571 http://www.opencores.org/projects.cgi/web/i2c/overview
573 This driver can also be built as a module. If so, the module
574 will be called i2c-ocores.
577 tristate "OMAP I2C adapter"
579 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
581 If you say yes to this option, support will be included for the
582 I2C interface on the Texas Instruments OMAP1/2 family of processors.
583 Like OMAP1510/1610/1710/5912 and OMAP242x.
584 For details see http://www.ti.com/omap.
587 tristate "PA Semi SMBus interface"
588 depends on PPC_PASEMI && PCI
590 Supports the PA Semi PWRficient on-chip SMBus interfaces.
592 config I2C_PCA_PLATFORM
593 tristate "PCA9564/PCA9665 as platform device"
597 This driver supports a memory mapped Philips PCA9564/PCA9665
598 parallel bus to I2C bus controller.
600 This driver can also be built as a module. If so, the module
601 will be called i2c-pca-platform.
604 tristate "PMC MSP I2C TWI Controller"
607 This driver supports the PMC TWI controller on MSP devices.
609 This driver can also be built as module. If so, the module
610 will be called i2c-pmcmsp.
613 tristate "I2C bus support for Philips PNX and NXP LPC targets"
614 depends on ARCH_LPC32XX
616 This driver supports the Philips IP3204 I2C IP block master and/or
619 This driver can also be built as a module. If so, the module
620 will be called i2c-pnx.
623 tristate "PKUnity v3 I2C bus support"
624 depends on UNICORE32 && ARCH_PUV3
627 This driver supports the I2C IP inside the PKUnity-v3 SoC.
628 This I2C bus controller is under AMBA/AXI bus.
630 This driver can also be built as a module. If so, the module
631 will be called i2c-puv3.
634 tristate "Intel PXA2XX I2C adapter"
635 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
637 If you have devices in the PXA I2C bus, say yes to this option.
638 This driver can also be built as a module. If so, the module
639 will be called i2c-pxa.
642 def_bool I2C_PXA && X86_32 && PCI && OF
645 bool "Intel PXA2XX I2C Slave comms support"
646 depends on I2C_PXA && !X86_32
648 Support I2C slave mode communications on the PXA I2C bus. This
649 is necessary for systems where the PXA may be a target on the
653 tristate "Renesas RIIC adapter"
654 depends on ARCH_SHMOBILE || COMPILE_TEST
656 If you say yes to this option, support will be included for the
657 Renesas RIIC I2C interface.
659 This driver can also be built as a module. If so, the module
660 will be called i2c-riic.
662 config HAVE_S3C2410_I2C
665 This will include I2C support for Samsung SoCs. If you want to
666 include I2C support for any machine, kindly select this in the
667 respective Kconfig file.
670 tristate "S3C2410 I2C Driver"
671 depends on HAVE_S3C2410_I2C
673 Say Y here to include support for I2C controller in the
677 tristate "S6000 I2C support"
678 depends on XTENSA_VARIANT_S6000
680 This driver supports the on chip I2C device on the
681 S6000 xtensa processor family.
683 To compile this driver as a module, choose M here. The module
684 will be called i2c-s6000.
687 tristate "Renesas SH7760 I2C Controller"
688 depends on CPU_SUBTYPE_SH7760
690 This driver supports the 2 I2C interfaces on the Renesas SH7760.
692 This driver can also be built as a module. If so, the module
693 will be called i2c-sh7760.
696 tristate "SuperH Mobile I2C Controller"
697 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
699 If you say yes to this option, support will be included for the
700 built-in I2C interface on the Renesas SH-Mobile processor.
702 This driver can also be built as a module. If so, the module
703 will be called i2c-sh_mobile.
706 tristate "Simtec Generic I2C interface"
709 If you say yes to this option, support will be included for
710 the Simtec Generic I2C interface. This driver is for the
711 simple I2C bus used on newer Simtec products for general
712 I2C, such as DDC on the Simtec BBD2016A.
714 This driver can also be built as a module. If so, the module
715 will be called i2c-simtec.
718 tristate "CSR SiRFprimaII I2C interface"
721 If you say yes to this option, support will be included for the
722 CSR SiRFprimaII I2C interface.
724 This driver can also be built as a module. If so, the module
725 will be called i2c-sirf.
728 tristate "STMicroelectronics SSC I2C support"
731 Enable this option to add support for STMicroelectronics SoCs
732 hardware SSC (Synchronous Serial Controller) as an I2C controller.
734 This driver can also be built as module. If so, the module
735 will be called i2c-st.
738 tristate "ST Microelectronics DDC I2C interface"
740 default y if MACH_U300
742 If you say yes to this option, support will be included for the
743 I2C interface from ST Microelectronics simply called "DDC I2C"
744 supporting both I2C and DDC, used in e.g. the U300 series
747 This driver can also be built as a module. If so, the module
748 will be called i2c-stu300.
751 tristate "NVIDIA Tegra internal I2C controller"
752 depends on ARCH_TEGRA
754 If you say yes to this option, support will be included for the
755 I2C controller embedded in NVIDIA Tegra SOCs
758 tristate "ARM Versatile/Realview I2C bus support"
759 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
762 Say yes if you want to support the I2C serial bus on ARMs Versatile
765 This driver can also be built as a module. If so, the module
766 will be called i2c-versatile.
769 tristate "Wondermedia WM8xxx SoC I2C bus support"
770 depends on ARCH_VT8500
772 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
775 This driver can also be built as a module. If so, the module will be
779 tristate "Cavium OCTEON I2C bus support"
780 depends on CAVIUM_OCTEON_SOC
782 Say yes if you want to support the I2C serial bus on Cavium
785 This driver can also be built as a module. If so, the module
786 will be called i2c-octeon.
789 tristate "Xilinx I2C Controller"
792 If you say yes to this option, support will be included for the
793 Xilinx I2C controller.
795 This driver can also be built as a module. If so, the module
796 will be called xilinx_i2c.
799 tristate "XLR I2C support"
802 This driver enables support for the on-chip I2C interface of
803 the Netlogic XLR/XLS MIPS processors.
805 This driver can also be built as a module. If so, the module
806 will be called i2c-xlr.
809 tristate "Renesas R-Car I2C Controller"
810 depends on ARCH_SHMOBILE || COMPILE_TEST
812 If you say yes to this option, support will be included for the
813 R-Car I2C controller.
815 This driver can also be built as a module. If so, the module
816 will be called i2c-rcar.
818 comment "External I2C/SMBus adapter drivers"
820 config I2C_DIOLAN_U2C
821 tristate "Diolan U2C-12 USB adapter"
824 If you say yes to this option, support will be included for Diolan
825 U2C-12, a USB to I2C interface.
827 This driver can also be built as a module. If so, the module
828 will be called i2c-diolan-u2c.
831 tristate "Parallel port adapter"
836 This supports parallel port I2C adapters such as the ones made by
837 Philips or Velleman, Analog Devices evaluation boards, and more.
838 Basically any adapter using the parallel port as an I2C bus with
839 no extra chipset is supported by this driver, or could be.
841 This driver is a replacement for (and was inspired by) an older
842 driver named i2c-philips-par. The new driver supports more devices,
843 and makes it easier to add support for new devices.
845 An adapter type parameter is now mandatory. Please read the file
846 Documentation/i2c/busses/i2c-parport for details.
848 Another driver exists, named i2c-parport-light, which doesn't depend
849 on the parport driver. This is meant for embedded systems. Don't say
850 Y here if you intend to say Y or M there.
852 This support is also available as a module. If so, the module
853 will be called i2c-parport.
855 config I2C_PARPORT_LIGHT
856 tristate "Parallel port adapter (light)"
860 This supports parallel port I2C adapters such as the ones made by
861 Philips or Velleman, Analog Devices evaluation boards, and more.
862 Basically any adapter using the parallel port as an I2C bus with
863 no extra chipset is supported by this driver, or could be.
865 This driver is a light version of i2c-parport. It doesn't depend
866 on the parport driver, and uses direct I/O access instead. This
867 might be preferred on embedded systems where wasting memory for
868 the clean but heavy parport handling is not an option. The
869 drawback is a reduced portability and the impossibility to
870 daisy-chain other parallel port devices.
872 Don't say Y here if you said Y or M to i2c-parport. Saying M to
873 both is possible but both modules should not be loaded at the same
876 This support is also available as a module. If so, the module
877 will be called i2c-parport-light.
879 config I2C_ROBOTFUZZ_OSIF
880 tristate "RobotFuzz Open Source InterFace USB adapter"
883 If you say yes to this option, support will be included for the
884 RobotFuzz Open Source InterFace USB to I2C interface.
886 This driver can also be built as a module. If so, the module
887 will be called i2c-osif.
890 tristate "TAOS evaluation module"
896 This supports TAOS evaluation modules on serial port. In order to
897 use this driver, you will need the inputattach tool, which is part
898 of the input-utils package.
902 This support is also available as a module. If so, the module
903 will be called i2c-taos-evm.
906 tristate "Tiny-USB adapter"
909 If you say yes to this option, support will be included for the
910 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
911 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
913 This driver can also be built as a module. If so, the module
914 will be called i2c-tiny-usb.
916 config I2C_VIPERBOARD
917 tristate "Viperboard I2C master support"
918 depends on MFD_VIPERBOARD && USB
920 Say yes here to access the I2C part of the Nano River
921 Technologies Viperboard as I2C master.
922 See viperboard API specification and Nano
923 River Tech's viperboard.h for detailed meaning
924 of the module parameters.
926 comment "Other I2C/SMBus bus drivers"
929 tristate "Acorn IOC/IOMD I2C bus support"
930 depends on ARCH_ACORN
934 Say yes if you want to support the I2C bus on Acorn platforms.
936 If you don't know, say Y.
939 tristate "Elektor ISA card"
940 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
943 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
946 This support is also available as a module. If so, the module
947 will be called i2c-elektor.
950 tristate "PCA9564/PCA9665 on an ISA bus"
955 This driver supports ISA boards using the Philips PCA9564/PCA9665
956 parallel bus to I2C bus controller.
958 This driver can also be built as a module. If so, the module
959 will be called i2c-pca-isa.
961 This device is almost undetectable and using this driver on a
962 system which doesn't have this device will result in long
963 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
964 time). If unsure, say N.
967 tristate "SiByte SMBus interface"
968 depends on SIBYTE_SB1xxx_SOC
970 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
973 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
974 depends on SCx200_GPIO
977 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
979 If you don't know what to do here, say N.
981 This support is also available as a module. If so, the module
982 will be called scx200_i2c.
984 This driver is deprecated and will be dropped soon. Use i2c-gpio
985 (or scx200_acb) instead.
987 config SCx200_I2C_SCL
988 int "GPIO pin used for SCL"
989 depends on SCx200_I2C
992 Enter the GPIO pin number used for the SCL signal. This value can
993 also be specified with a module parameter.
995 config SCx200_I2C_SDA
996 int "GPIO pin used for SDA"
997 depends on SCx200_I2C
1000 Enter the GPIO pin number used for the SSA signal. This value can
1001 also be specified with a module parameter.
1004 tristate "Geode ACCESS.bus support"
1005 depends on X86_32 && PCI
1007 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
1008 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
1010 If you don't know what to do here, say N.
1012 This support is also available as a module. If so, the module
1013 will be called scx200_acb.