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 This driver can also be built as a module. If so, the module
114 will be called i2c-i801.
117 tristate "Intel SCH SMBus 1.0"
121 Say Y here if you want to use SMBus controller on the Intel SCH
124 This driver can also be built as a module. If so, the module
125 will be called i2c-isch.
128 tristate "Intel iSMT SMBus Controller"
129 depends on PCI && X86
131 If you say yes to this option, support will be included for the Intel
132 iSMT SMBus host controller interface.
134 This driver can also be built as a module. If so, the module will be
138 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
141 If you say yes to this option, support will be included for the Intel
142 PIIX4 family of mainboard I2C interfaces. Specifically, the following
143 versions of the chipset are supported (note that Serverworks is part
162 Some AMD chipsets contain two PIIX4-compatible SMBus
163 controllers. This driver will attempt to use both controllers
164 on the SB700/SP5100, if they have been initialized by the BIOS.
166 This driver can also be built as a module. If so, the module
167 will be called i2c-piix4.
170 tristate "Nvidia nForce2, nForce3 and nForce4"
173 If you say yes to this option, support will be included for the Nvidia
174 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
176 This driver can also be built as a module. If so, the module
177 will be called i2c-nforce2.
179 config I2C_NFORCE2_S4985
180 tristate "SMBus multiplexing on the Tyan S4985"
181 depends on I2C_NFORCE2 && X86
183 Enabling this option will add specific SMBus support for the Tyan
184 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
185 over 4 different channels, where the various memory module EEPROMs
186 live. Saying yes here will give you access to these in addition
189 This driver can also be built as a module. If so, the module
190 will be called i2c-nforce2-s4985.
196 If you say yes to this option, support will be included for the
197 SiS5595 SMBus (a subset of I2C) interface.
199 This driver can also be built as a module. If so, the module
200 will be called i2c-sis5595.
203 tristate "SiS 630/730/964"
206 If you say yes to this option, support will be included for the
207 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
209 This driver can also be built as a module. If so, the module
210 will be called i2c-sis630.
216 If you say yes to this option, support will be included for the SiS
217 96x SMBus (a subset of I2C) interfaces. Specifically, the following
218 chipsets are supported:
227 This driver can also be built as a module. If so, the module
228 will be called i2c-sis96x.
231 tristate "VIA VT82C586B"
235 If you say yes to this option, support will be included for the VIA
236 82C586B I2C interface
238 This driver can also be built as a module. If so, the module
239 will be called i2c-via.
242 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
245 If you say yes to this option, support will be included for the VIA
246 VT82C596 and later SMBus interface. Specifically, the following
247 chipsets are supported:
260 This driver can also be built as a module. If so, the module
261 will be called i2c-viapro.
265 comment "ACPI drivers"
268 tristate "SMBus Control Method Interface"
270 This driver supports the SMBus Control Method Interface. It needs the
271 BIOS to declare ACPI control methods as described in the SMBus Control
272 Method Interface specification.
274 To compile this driver as a module, choose M here:
275 the module will be called i2c-scmi.
279 comment "Mac SMBus host controller drivers"
280 depends on PPC_CHRP || PPC_PMAC
283 tristate "CHRP Apple Hydra Mac I/O I2C interface"
284 depends on PCI && PPC_CHRP
287 This supports the use of the I2C interface in the Apple Hydra Mac
288 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
291 This support is also available as a module. If so, the module
292 will be called i2c-hydra.
295 tristate "Powermac I2C interface"
299 This exposes the various PowerMac i2c interfaces to the linux i2c
300 layer and to userland. It is used by various drivers on the PowerMac
301 platform, and should generally be enabled.
303 This support is also available as a module. If so, the module
304 will be called i2c-powermac.
306 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
309 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
312 This supports the use of the I2C interface on Atmel AT91
315 A serious problem is that there is no documented way to issue
316 repeated START conditions for more than two messages, as needed
317 to support combined I2C messages. Use the i2c-gpio driver
318 unless your system can cope with this limitation.
320 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
321 don't have clock stretching in transmission mode. For that reason,
322 you can encounter underrun issues causing premature stop sendings if
323 the latency to fill the transmission register is too long. If you
324 are facing this situation, use the i2c-gpio driver.
327 tristate "Au1550/Au1200/Au1300 SMBus interface"
328 depends on MIPS_ALCHEMY
330 If you say yes to this option, support will be included for the
331 Au1550/Au1200/Au1300 SMBus interface.
333 This driver can also be built as a module. If so, the module
334 will be called i2c-au1550.
337 tristate "Broadcom BCM2835 I2C controller"
338 depends on ARCH_BCM2835
340 If you say yes to this option, support will be included for the
341 BCM2835 I2C controller.
343 If you don't know what to do here, say N.
345 This support is also available as a module. If so, the module
346 will be called i2c-bcm2835.
348 config I2C_BLACKFIN_TWI
349 tristate "Blackfin TWI I2C support"
351 depends on !BF561 && !BF531 && !BF532 && !BF533
353 This is the I2C bus driver for Blackfin on-chip TWI interface.
355 This driver can also be built as a module. If so, the module
356 will be called i2c-bfin-twi.
358 config I2C_BLACKFIN_TWI_CLK_KHZ
359 int "Blackfin TWI I2C clock (kHz)"
360 depends on I2C_BLACKFIN_TWI
364 The unit of the TWI clock is kHz.
367 tristate "CBUS I2C driver"
370 Support for CBUS access using I2C API. Mostly relevant for Nokia
371 Internet Tablets (770, N800 and N810).
373 This driver can also be built as a module. If so, the module
374 will be called i2c-cbus-gpio.
377 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
378 depends on (CPM1 || CPM2) && OF_I2C
380 This supports the use of the I2C interface on Freescale
381 processors with CPM1 or CPM2.
383 This driver can also be built as a module. If so, the module
384 will be called i2c-cpm.
387 tristate "DaVinci I2C driver"
388 depends on ARCH_DAVINCI || ARCH_KEYSTONE
390 Support for TI DaVinci I2C controller driver.
392 This driver can also be built as a module. If so, the module
393 will be called i2c-davinci.
395 Please note that this driver might be needed to bring up other
396 devices such as DaVinci NIC.
397 For details please see http://www.ti.com/davinci
399 config I2C_DESIGNWARE_CORE
402 config I2C_DESIGNWARE_PLATFORM
403 tristate "Synopsys DesignWare Platform"
405 select I2C_DESIGNWARE_CORE
407 If you say yes to this option, support will be included for the
408 Synopsys DesignWare I2C adapter. Only master mode is supported.
410 This driver can also be built as a module. If so, the module
411 will be called i2c-designware-platform.
413 config I2C_DESIGNWARE_PCI
414 tristate "Synopsys DesignWare PCI"
416 select I2C_DESIGNWARE_CORE
418 If you say yes to this option, support will be included for the
419 Synopsys DesignWare I2C adapter. Only master mode is supported.
421 This driver can also be built as a module. If so, the module
422 will be called i2c-designware-pci.
425 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
428 This driver is for PCH(Platform controller Hub) I2C of EG20T which
429 is an IOH(Input/Output Hub) for x86 embedded processor.
430 This driver can access PCH I2C bus device.
432 This driver also can be used for LAPIS Semiconductor IOH(Input/
433 Output Hub), ML7213, ML7223 and ML7831.
434 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
435 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
436 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
437 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
440 tristate "Exynos5 high-speed I2C driver"
441 depends on ARCH_EXYNOS5 && OF
443 Say Y here to include support for high-speed I2C controller in the
444 Exynos5 based Samsung SoCs.
447 tristate "GPIO-based bitbanging I2C"
451 This is a very simple bitbanging I2C driver utilizing the
452 arch-neutral GPIO API to control the SCL and SDA lines.
454 config I2C_HIGHLANDER
455 tristate "Highlander FPGA SMBus interface"
456 depends on SH_HIGHLANDER
458 If you say yes to this option, support will be included for
459 the SMBus interface located in the FPGA on various Highlander
460 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
461 FPGAs. This is wholly unrelated to the SoC I2C.
463 This driver can also be built as a module. If so, the module
464 will be called i2c-highlander.
467 tristate "IBM PPC 4xx on-chip I2C interface"
470 Say Y here if you want to use IIC peripheral found on
471 embedded IBM PPC 4xx based systems.
473 This driver can also be built as a module. If so, the module
474 will be called i2c-ibm_iic.
477 tristate "IMX I2C interface"
480 Say Y here if you want to use the IIC bus controller on
481 the Freescale i.MX/MXC processors.
483 This driver can also be built as a module. If so, the module
484 will be called i2c-imx.
487 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
488 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
490 Say Y here if you want to use the IIC bus controller on
491 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
493 This driver can also be built as a module. If so, the module
494 will be called i2c-iop3xx.
497 tristate "Kontron COM I2C Controller"
498 depends on MFD_KEMPLD
500 This enables support for the I2C bus interface on some Kontron ETX
501 and COMexpress (ETXexpress) modules.
503 This driver can also be built as a module. If so, the module
504 will be called i2c-kempld.
507 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
510 If you say yes to this option, support will be included for the
511 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
512 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
514 This driver can also be built as a module. If so, the module
515 will be called i2c-mpc.
518 tristate "Marvell mv64xxx I2C Controller"
519 depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI)
521 If you say yes to this option, support will be included for the
522 built-in I2C interface on the Marvell 64xxx line of host bridges.
523 This driver is also used for Allwinner SoCs I2C controllers.
525 This driver can also be built as a module. If so, the module
526 will be called i2c-mv64xxx.
529 tristate "Freescale i.MX28 I2C interface"
533 Say Y here if you want to use the I2C bus controller on
534 the Freescale i.MX28 processors.
536 This driver can also be built as a module. If so, the module
537 will be called i2c-mxs.
540 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
543 If you say yes to this option, support will be included for the
544 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
545 as well as the STA2X11 PCIe I/O HUB.
548 tristate "NUC900 I2C Driver"
549 depends on ARCH_W90X900
551 Say Y here to include support for I2C controller in the
552 Winbond/Nuvoton NUC900 based System-on-Chip devices.
555 tristate "OpenCores I2C Controller"
557 If you say yes to this option, support will be included for the
558 OpenCores I2C controller. For details see
559 http://www.opencores.org/projects.cgi/web/i2c/overview
561 This driver can also be built as a module. If so, the module
562 will be called i2c-ocores.
565 tristate "OMAP I2C adapter"
567 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
569 If you say yes to this option, support will be included for the
570 I2C interface on the Texas Instruments OMAP1/2 family of processors.
571 Like OMAP1510/1610/1710/5912 and OMAP242x.
572 For details see http://www.ti.com/omap.
575 tristate "PA Semi SMBus interface"
576 depends on PPC_PASEMI && PCI
578 Supports the PA Semi PWRficient on-chip SMBus interfaces.
580 config I2C_PCA_PLATFORM
581 tristate "PCA9564/PCA9665 as platform device"
585 This driver supports a memory mapped Philips PCA9564/PCA9665
586 parallel bus to I2C bus controller.
588 This driver can also be built as a module. If so, the module
589 will be called i2c-pca-platform.
592 tristate "PMC MSP I2C TWI Controller"
595 This driver supports the PMC TWI controller on MSP devices.
597 This driver can also be built as module. If so, the module
598 will be called i2c-pmcmsp.
601 tristate "I2C bus support for Philips PNX and NXP LPC targets"
602 depends on ARCH_LPC32XX
604 This driver supports the Philips IP3204 I2C IP block master and/or
607 This driver can also be built as a module. If so, the module
608 will be called i2c-pnx.
611 tristate "PKUnity v3 I2C bus support"
612 depends on UNICORE32 && ARCH_PUV3
615 This driver supports the I2C IP inside the PKUnity-v3 SoC.
616 This I2C bus controller is under AMBA/AXI bus.
618 This driver can also be built as a module. If so, the module
619 will be called i2c-puv3.
622 tristate "Intel PXA2XX I2C adapter"
623 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
625 If you have devices in the PXA I2C bus, say yes to this option.
626 This driver can also be built as a module. If so, the module
627 will be called i2c-pxa.
630 def_bool I2C_PXA && X86_32 && PCI && OF
633 bool "Intel PXA2XX I2C Slave comms support"
634 depends on I2C_PXA && !X86_32
636 Support I2C slave mode communications on the PXA I2C bus. This
637 is necessary for systems where the PXA may be a target on the
640 config HAVE_S3C2410_I2C
643 This will include I2C support for Samsung SoCs. If you want to
644 include I2C support for any machine, kindly select this in the
645 respective Kconfig file.
648 tristate "S3C2410 I2C Driver"
649 depends on HAVE_S3C2410_I2C
651 Say Y here to include support for I2C controller in the
655 tristate "S6000 I2C support"
656 depends on XTENSA_VARIANT_S6000
658 This driver supports the on chip I2C device on the
659 S6000 xtensa processor family.
661 To compile this driver as a module, choose M here. The module
662 will be called i2c-s6000.
665 tristate "Renesas SH7760 I2C Controller"
666 depends on CPU_SUBTYPE_SH7760
668 This driver supports the 2 I2C interfaces on the Renesas SH7760.
670 This driver can also be built as a module. If so, the module
671 will be called i2c-sh7760.
674 tristate "SuperH Mobile I2C Controller"
675 depends on SUPERH || ARM || COMPILE_TEST
677 If you say yes to this option, support will be included for the
678 built-in I2C interface on the Renesas SH-Mobile processor.
680 This driver can also be built as a module. If so, the module
681 will be called i2c-sh_mobile.
684 tristate "Simtec Generic I2C interface"
687 If you say yes to this option, support will be included for
688 the Simtec Generic I2C interface. This driver is for the
689 simple I2C bus used on newer Simtec products for general
690 I2C, such as DDC on the Simtec BBD2016A.
692 This driver can also be built as a module. If so, the module
693 will be called i2c-simtec.
696 tristate "CSR SiRFprimaII I2C interface"
699 If you say yes to this option, support will be included for the
700 CSR SiRFprimaII I2C interface.
702 This driver can also be built as a module. If so, the module
703 will be called i2c-sirf.
706 tristate "ST Microelectronics DDC I2C interface"
708 default y if MACH_U300
710 If you say yes to this option, support will be included for the
711 I2C interface from ST Microelectronics simply called "DDC I2C"
712 supporting both I2C and DDC, used in e.g. the U300 series
715 This driver can also be built as a module. If so, the module
716 will be called i2c-stu300.
719 tristate "NVIDIA Tegra internal I2C controller"
720 depends on ARCH_TEGRA
722 If you say yes to this option, support will be included for the
723 I2C controller embedded in NVIDIA Tegra SOCs
726 tristate "ARM Versatile/Realview I2C bus support"
727 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
730 Say yes if you want to support the I2C serial bus on ARMs Versatile
733 This driver can also be built as a module. If so, the module
734 will be called i2c-versatile.
737 tristate "Wondermedia WM8xxx SoC I2C bus support"
738 depends on ARCH_VT8500
740 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
743 This driver can also be built as a module. If so, the module will be
747 tristate "Cavium OCTEON I2C bus support"
748 depends on CAVIUM_OCTEON_SOC
750 Say yes if you want to support the I2C serial bus on Cavium
753 This driver can also be built as a module. If so, the module
754 will be called i2c-octeon.
757 tristate "Xilinx I2C Controller"
760 If you say yes to this option, support will be included for the
761 Xilinx I2C controller.
763 This driver can also be built as a module. If so, the module
764 will be called xilinx_i2c.
767 tristate "XLR I2C support"
770 This driver enables support for the on-chip I2C interface of
771 the Netlogic XLR/XLS MIPS processors.
773 This driver can also be built as a module. If so, the module
774 will be called i2c-xlr.
777 tristate "Renesas R-Car I2C Controller"
778 depends on ARM || COMPILE_TEST
780 If you say yes to this option, support will be included for the
781 R-Car I2C controller.
783 This driver can also be built as a module. If so, the module
784 will be called i2c-rcar.
786 comment "External I2C/SMBus adapter drivers"
788 config I2C_DIOLAN_U2C
789 tristate "Diolan U2C-12 USB adapter"
792 If you say yes to this option, support will be included for Diolan
793 U2C-12, a USB to I2C interface.
795 This driver can also be built as a module. If so, the module
796 will be called i2c-diolan-u2c.
799 tristate "Parallel port adapter"
804 This supports parallel port I2C adapters such as the ones made by
805 Philips or Velleman, Analog Devices evaluation boards, and more.
806 Basically any adapter using the parallel port as an I2C bus with
807 no extra chipset is supported by this driver, or could be.
809 This driver is a replacement for (and was inspired by) an older
810 driver named i2c-philips-par. The new driver supports more devices,
811 and makes it easier to add support for new devices.
813 An adapter type parameter is now mandatory. Please read the file
814 Documentation/i2c/busses/i2c-parport for details.
816 Another driver exists, named i2c-parport-light, which doesn't depend
817 on the parport driver. This is meant for embedded systems. Don't say
818 Y here if you intend to say Y or M there.
820 This support is also available as a module. If so, the module
821 will be called i2c-parport.
823 config I2C_PARPORT_LIGHT
824 tristate "Parallel port adapter (light)"
828 This supports parallel port I2C adapters such as the ones made by
829 Philips or Velleman, Analog Devices evaluation boards, and more.
830 Basically any adapter using the parallel port as an I2C bus with
831 no extra chipset is supported by this driver, or could be.
833 This driver is a light version of i2c-parport. It doesn't depend
834 on the parport driver, and uses direct I/O access instead. This
835 might be preferred on embedded systems where wasting memory for
836 the clean but heavy parport handling is not an option. The
837 drawback is a reduced portability and the impossibility to
838 daisy-chain other parallel port devices.
840 Don't say Y here if you said Y or M to i2c-parport. Saying M to
841 both is possible but both modules should not be loaded at the same
844 This support is also available as a module. If so, the module
845 will be called i2c-parport-light.
848 tristate "TAOS evaluation module"
854 This supports TAOS evaluation modules on serial port. In order to
855 use this driver, you will need the inputattach tool, which is part
856 of the input-utils package.
860 This support is also available as a module. If so, the module
861 will be called i2c-taos-evm.
864 tristate "Tiny-USB adapter"
867 If you say yes to this option, support will be included for the
868 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
869 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
871 This driver can also be built as a module. If so, the module
872 will be called i2c-tiny-usb.
874 config I2C_VIPERBOARD
875 tristate "Viperboard I2C master support"
876 depends on MFD_VIPERBOARD && USB
878 Say yes here to access the I2C part of the Nano River
879 Technologies Viperboard as I2C master.
880 See viperboard API specification and Nano
881 River Tech's viperboard.h for detailed meaning
882 of the module parameters.
884 comment "Other I2C/SMBus bus drivers"
887 tristate "Acorn IOC/IOMD I2C bus support"
888 depends on ARCH_ACORN
892 Say yes if you want to support the I2C bus on Acorn platforms.
894 If you don't know, say Y.
897 tristate "Elektor ISA card"
898 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
901 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
904 This support is also available as a module. If so, the module
905 will be called i2c-elektor.
908 tristate "PCA9564/PCA9665 on an ISA bus"
913 This driver supports ISA boards using the Philips PCA9564/PCA9665
914 parallel bus to I2C bus controller.
916 This driver can also be built as a module. If so, the module
917 will be called i2c-pca-isa.
919 This device is almost undetectable and using this driver on a
920 system which doesn't have this device will result in long
921 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
922 time). If unsure, say N.
925 tristate "SiByte SMBus interface"
926 depends on SIBYTE_SB1xxx_SOC
928 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
931 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
932 depends on SCx200_GPIO
935 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
937 If you don't know what to do here, say N.
939 This support is also available as a module. If so, the module
940 will be called scx200_i2c.
942 This driver is deprecated and will be dropped soon. Use i2c-gpio
943 (or scx200_acb) instead.
945 config SCx200_I2C_SCL
946 int "GPIO pin used for SCL"
947 depends on SCx200_I2C
950 Enter the GPIO pin number used for the SCL signal. This value can
951 also be specified with a module parameter.
953 config SCx200_I2C_SDA
954 int "GPIO pin used for SDA"
955 depends on SCx200_I2C
958 Enter the GPIO pin number used for the SSA signal. This value can
959 also be specified with a module parameter.
962 tristate "Geode ACCESS.bus support"
963 depends on X86_32 && PCI
965 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
966 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
968 If you don't know what to do here, say N.
970 This support is also available as a module. If so, the module
971 will be called scx200_acb.