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"
120 depends on PCI && GENERIC_HARDIRQS
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
164 Some AMD chipsets contain two PIIX4-compatible SMBus
165 controllers. This driver will attempt to use both controllers
166 on the SB700/SP5100, if they have been initialized by the BIOS.
168 This driver can also be built as a module. If so, the module
169 will be called i2c-piix4.
172 tristate "Nvidia nForce2, nForce3 and nForce4"
175 If you say yes to this option, support will be included for the Nvidia
176 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
178 This driver can also be built as a module. If so, the module
179 will be called i2c-nforce2.
181 config I2C_NFORCE2_S4985
182 tristate "SMBus multiplexing on the Tyan S4985"
183 depends on I2C_NFORCE2 && X86
185 Enabling this option will add specific SMBus support for the Tyan
186 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
187 over 4 different channels, where the various memory module EEPROMs
188 live. Saying yes here will give you access to these in addition
191 This driver can also be built as a module. If so, the module
192 will be called i2c-nforce2-s4985.
198 If you say yes to this option, support will be included for the
199 SiS5595 SMBus (a subset of I2C) interface.
201 This driver can also be built as a module. If so, the module
202 will be called i2c-sis5595.
205 tristate "SiS 630/730/964"
208 If you say yes to this option, support will be included for the
209 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
211 This driver can also be built as a module. If so, the module
212 will be called i2c-sis630.
218 If you say yes to this option, support will be included for the SiS
219 96x SMBus (a subset of I2C) interfaces. Specifically, the following
220 chipsets are supported:
229 This driver can also be built as a module. If so, the module
230 will be called i2c-sis96x.
233 tristate "VIA VT82C586B"
237 If you say yes to this option, support will be included for the VIA
238 82C586B I2C interface
240 This driver can also be built as a module. If so, the module
241 will be called i2c-via.
244 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
247 If you say yes to this option, support will be included for the VIA
248 VT82C596 and later SMBus interface. Specifically, the following
249 chipsets are supported:
262 This driver can also be built as a module. If so, the module
263 will be called i2c-viapro.
267 comment "ACPI drivers"
270 tristate "SMBus Control Method Interface"
272 This driver supports the SMBus Control Method Interface. It needs the
273 BIOS to declare ACPI control methods as described in the SMBus Control
274 Method Interface specification.
276 To compile this driver as a module, choose M here:
277 the module will be called i2c-scmi.
281 comment "Mac SMBus host controller drivers"
282 depends on PPC_CHRP || PPC_PMAC
285 tristate "CHRP Apple Hydra Mac I/O I2C interface"
286 depends on PCI && PPC_CHRP
289 This supports the use of the I2C interface in the Apple Hydra Mac
290 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
293 This support is also available as a module. If so, the module
294 will be called i2c-hydra.
297 tristate "Powermac I2C interface"
301 This exposes the various PowerMac i2c interfaces to the linux i2c
302 layer and to userland. It is used by various drivers on the PowerMac
303 platform, and should generally be enabled.
305 This support is also available as a module. If so, the module
306 will be called i2c-powermac.
308 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
311 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
314 This supports the use of the I2C interface on Atmel AT91
317 A serious problem is that there is no documented way to issue
318 repeated START conditions for more than two messages, as needed
319 to support combined I2C messages. Use the i2c-gpio driver
320 unless your system can cope with this limitation.
322 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
323 don't have clock stretching in transmission mode. For that reason,
324 you can encounter underrun issues causing premature stop sendings if
325 the latency to fill the transmission register is too long. If you
326 are facing this situation, use the i2c-gpio driver.
329 tristate "Au1550/Au1200/Au1300 SMBus interface"
330 depends on MIPS_ALCHEMY
332 If you say yes to this option, support will be included for the
333 Au1550/Au1200/Au1300 SMBus interface.
335 This driver can also be built as a module. If so, the module
336 will be called i2c-au1550.
339 tristate "Broadcom BCM2835 I2C controller"
340 depends on ARCH_BCM2835
342 If you say yes to this option, support will be included for the
343 BCM2835 I2C controller.
345 If you don't know what to do here, say N.
347 This support is also available as a module. If so, the module
348 will be called i2c-bcm2835.
350 config I2C_BLACKFIN_TWI
351 tristate "Blackfin TWI I2C support"
353 depends on !BF561 && !BF531 && !BF532 && !BF533
355 This is the I2C bus driver for Blackfin on-chip TWI interface.
357 This driver can also be built as a module. If so, the module
358 will be called i2c-bfin-twi.
360 config I2C_BLACKFIN_TWI_CLK_KHZ
361 int "Blackfin TWI I2C clock (kHz)"
362 depends on I2C_BLACKFIN_TWI
366 The unit of the TWI clock is kHz.
369 tristate "CBUS I2C driver"
372 Support for CBUS access using I2C API. Mostly relevant for Nokia
373 Internet Tablets (770, N800 and N810).
375 This driver can also be built as a module. If so, the module
376 will be called i2c-cbus-gpio.
379 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
380 depends on (CPM1 || CPM2) && OF_I2C
382 This supports the use of the I2C interface on Freescale
383 processors with CPM1 or CPM2.
385 This driver can also be built as a module. If so, the module
386 will be called i2c-cpm.
389 tristate "DaVinci I2C driver"
390 depends on ARCH_DAVINCI
392 Support for TI DaVinci I2C controller driver.
394 This driver can also be built as a module. If so, the module
395 will be called i2c-davinci.
397 Please note that this driver might be needed to bring up other
398 devices such as DaVinci NIC.
399 For details please see http://www.ti.com/davinci
401 config I2C_DESIGNWARE_CORE
404 config I2C_DESIGNWARE_PLATFORM
405 tristate "Synopsys DesignWare Platform"
407 select I2C_DESIGNWARE_CORE
409 If you say yes to this option, support will be included for the
410 Synopsys DesignWare I2C adapter. Only master mode is supported.
412 This driver can also be built as a module. If so, the module
413 will be called i2c-designware-platform.
415 config I2C_DESIGNWARE_PCI
416 tristate "Synopsys DesignWare PCI"
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-pci.
427 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
430 This driver is for PCH(Platform controller Hub) I2C of EG20T which
431 is an IOH(Input/Output Hub) for x86 embedded processor.
432 This driver can access PCH I2C bus device.
434 This driver also can be used for LAPIS Semiconductor IOH(Input/
435 Output Hub), ML7213, ML7223 and ML7831.
436 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
437 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
438 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
439 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
442 tristate "GPIO-based bitbanging I2C"
446 This is a very simple bitbanging I2C driver utilizing the
447 arch-neutral GPIO API to control the SCL and SDA lines.
449 config I2C_HIGHLANDER
450 tristate "Highlander FPGA SMBus interface"
451 depends on SH_HIGHLANDER
453 If you say yes to this option, support will be included for
454 the SMBus interface located in the FPGA on various Highlander
455 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
456 FPGAs. This is wholly unrelated to the SoC I2C.
458 This driver can also be built as a module. If so, the module
459 will be called i2c-highlander.
462 tristate "IBM PPC 4xx on-chip I2C interface"
465 Say Y here if you want to use IIC peripheral found on
466 embedded IBM PPC 4xx based systems.
468 This driver can also be built as a module. If so, the module
469 will be called i2c-ibm_iic.
472 tristate "IMX I2C interface"
475 Say Y here if you want to use the IIC bus controller on
476 the Freescale i.MX/MXC processors.
478 This driver can also be built as a module. If so, the module
479 will be called i2c-imx.
482 tristate "Intel Moorestown/Medfield Platform I2C controller"
485 Say Y here if you have an Intel Moorestown/Medfield platform I2C
488 This support is also available as a module. If so, the module
489 will be called i2c-intel-mid.
492 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
493 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
495 Say Y here if you want to use the IIC bus controller on
496 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
498 This driver can also be built as a module. If so, the module
499 will be called i2c-iop3xx.
502 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
505 If you say yes to this option, support will be included for the
506 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
507 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
509 This driver can also be built as a module. If so, the module
510 will be called i2c-mpc.
513 tristate "Marvell mv64xxx I2C Controller"
514 depends on (MV64X60 || PLAT_ORION)
516 If you say yes to this option, support will be included for the
517 built-in I2C interface on the Marvell 64xxx line of host bridges.
519 This driver can also be built as a module. If so, the module
520 will be called i2c-mv64xxx.
523 tristate "Freescale i.MX28 I2C interface"
527 Say Y here if you want to use the I2C bus controller on
528 the Freescale i.MX28 processors.
530 This driver can also be built as a module. If so, the module
531 will be called i2c-mxs.
534 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
537 If you say yes to this option, support will be included for the
538 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
539 as well as the STA2X11 PCIe I/O HUB.
542 tristate "NUC900 I2C Driver"
543 depends on ARCH_W90X900
545 Say Y here to include support for I2C controller in the
546 Winbond/Nuvoton NUC900 based System-on-Chip devices.
549 tristate "OpenCores I2C Controller"
550 depends on GENERIC_HARDIRQS
552 If you say yes to this option, support will be included for the
553 OpenCores I2C controller. For details see
554 http://www.opencores.org/projects.cgi/web/i2c/overview
556 This driver can also be built as a module. If so, the module
557 will be called i2c-ocores.
560 tristate "OMAP I2C adapter"
562 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
564 If you say yes to this option, support will be included for the
565 I2C interface on the Texas Instruments OMAP1/2 family of processors.
566 Like OMAP1510/1610/1710/5912 and OMAP242x.
567 For details see http://www.ti.com/omap.
570 tristate "PA Semi SMBus interface"
571 depends on PPC_PASEMI && PCI
573 Supports the PA Semi PWRficient on-chip SMBus interfaces.
575 config I2C_PCA_PLATFORM
576 tristate "PCA9564/PCA9665 as platform device"
580 This driver supports a memory mapped Philips PCA9564/PCA9665
581 parallel bus to I2C bus controller.
583 This driver can also be built as a module. If so, the module
584 will be called i2c-pca-platform.
587 tristate "PMC MSP I2C TWI Controller"
590 This driver supports the PMC TWI controller on MSP devices.
592 This driver can also be built as module. If so, the module
593 will be called i2c-pmcmsp.
596 tristate "I2C bus support for Philips PNX and NXP LPC targets"
597 depends on ARCH_LPC32XX
599 This driver supports the Philips IP3204 I2C IP block master and/or
602 This driver can also be built as a module. If so, the module
603 will be called i2c-pnx.
606 tristate "PKUnity v3 I2C bus support"
607 depends on UNICORE32 && ARCH_PUV3
610 This driver supports the I2C IP inside the PKUnity-v3 SoC.
611 This I2C bus controller is under AMBA/AXI bus.
613 This driver can also be built as a module. If so, the module
614 will be called i2c-puv3.
617 tristate "Intel PXA2XX I2C adapter"
618 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
620 If you have devices in the PXA I2C bus, say yes to this option.
621 This driver can also be built as a module. If so, the module
622 will be called i2c-pxa.
625 def_bool I2C_PXA && X86_32 && PCI && OF
628 bool "Intel PXA2XX I2C Slave comms support"
629 depends on I2C_PXA && !X86_32
631 Support I2C slave mode communications on the PXA I2C bus. This
632 is necessary for systems where the PXA may be a target on the
635 config HAVE_S3C2410_I2C
638 This will include I2C support for Samsung SoCs. If you want to
639 include I2C support for any machine, kindly select this in the
640 respective Kconfig file.
643 tristate "S3C2410 I2C Driver"
644 depends on HAVE_S3C2410_I2C
646 Say Y here to include support for I2C controller in the
650 tristate "S6000 I2C support"
651 depends on XTENSA_VARIANT_S6000
653 This driver supports the on chip I2C device on the
654 S6000 xtensa processor family.
656 To compile this driver as a module, choose M here. The module
657 will be called i2c-s6000.
660 tristate "Renesas SH7760 I2C Controller"
661 depends on CPU_SUBTYPE_SH7760
663 This driver supports the 2 I2C interfaces on the Renesas SH7760.
665 This driver can also be built as a module. If so, the module
666 will be called i2c-sh7760.
669 tristate "SuperH Mobile I2C Controller"
670 depends on SUPERH || ARCH_SHMOBILE
672 If you say yes to this option, support will be included for the
673 built-in I2C interface on the Renesas SH-Mobile processor.
675 This driver can also be built as a module. If so, the module
676 will be called i2c-sh_mobile.
679 tristate "Simtec Generic I2C interface"
682 If you say yes to this option, support will be included for
683 the Simtec Generic I2C interface. This driver is for the
684 simple I2C bus used on newer Simtec products for general
685 I2C, such as DDC on the Simtec BBD2016A.
687 This driver can also be built as a module. If so, the module
688 will be called i2c-simtec.
691 tristate "CSR SiRFprimaII I2C interface"
692 depends on ARCH_PRIMA2
694 If you say yes to this option, support will be included for the
695 CSR SiRFprimaII I2C interface.
697 This driver can also be built as a module. If so, the module
698 will be called i2c-sirf.
701 tristate "ST Microelectronics DDC I2C interface"
703 default y if MACH_U300
705 If you say yes to this option, support will be included for the
706 I2C interface from ST Microelectronics simply called "DDC I2C"
707 supporting both I2C and DDC, used in e.g. the U300 series
710 This driver can also be built as a module. If so, the module
711 will be called i2c-stu300.
714 tristate "NVIDIA Tegra internal I2C controller"
715 depends on ARCH_TEGRA
717 If you say yes to this option, support will be included for the
718 I2C controller embedded in NVIDIA Tegra SOCs
721 tristate "ARM Versatile/Realview I2C bus support"
722 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
725 Say yes if you want to support the I2C serial bus on ARMs Versatile
728 This driver can also be built as a module. If so, the module
729 will be called i2c-versatile.
732 tristate "Cavium OCTEON I2C bus support"
733 depends on CPU_CAVIUM_OCTEON
735 Say yes if you want to support the I2C serial bus on Cavium
738 This driver can also be built as a module. If so, the module
739 will be called i2c-octeon.
742 tristate "Xilinx I2C Controller"
745 If you say yes to this option, support will be included for the
746 Xilinx I2C controller.
748 This driver can also be built as a module. If so, the module
749 will be called xilinx_i2c.
752 tristate "XLR I2C support"
755 This driver enables support for the on-chip I2C interface of
756 the Netlogic XLR/XLS MIPS processors.
758 This driver can also be built as a module. If so, the module
759 will be called i2c-xlr.
762 tristate "Renesas R-Car I2C Controller"
763 depends on ARCH_SHMOBILE && I2C
765 If you say yes to this option, support will be included for the
766 R-Car I2C controller.
768 This driver can also be built as a module. If so, the module
769 will be called i2c-rcar.
771 comment "External I2C/SMBus adapter drivers"
773 config I2C_DIOLAN_U2C
774 tristate "Diolan U2C-12 USB adapter"
777 If you say yes to this option, support will be included for Diolan
778 U2C-12, a USB to I2C interface.
780 This driver can also be built as a module. If so, the module
781 will be called i2c-diolan-u2c.
784 tristate "Parallel port adapter"
785 depends on PARPORT && GENERIC_HARDIRQS
789 This supports parallel port I2C adapters such as the ones made by
790 Philips or Velleman, Analog Devices evaluation boards, and more.
791 Basically any adapter using the parallel port as an I2C bus with
792 no extra chipset is supported by this driver, or could be.
794 This driver is a replacement for (and was inspired by) an older
795 driver named i2c-philips-par. The new driver supports more devices,
796 and makes it easier to add support for new devices.
798 An adapter type parameter is now mandatory. Please read the file
799 Documentation/i2c/busses/i2c-parport for details.
801 Another driver exists, named i2c-parport-light, which doesn't depend
802 on the parport driver. This is meant for embedded systems. Don't say
803 Y here if you intend to say Y or M there.
805 This support is also available as a module. If so, the module
806 will be called i2c-parport.
808 config I2C_PARPORT_LIGHT
809 tristate "Parallel port adapter (light)"
810 depends on GENERIC_HARDIRQS
814 This supports parallel port I2C adapters such as the ones made by
815 Philips or Velleman, Analog Devices evaluation boards, and more.
816 Basically any adapter using the parallel port as an I2C bus with
817 no extra chipset is supported by this driver, or could be.
819 This driver is a light version of i2c-parport. It doesn't depend
820 on the parport driver, and uses direct I/O access instead. This
821 might be preferred on embedded systems where wasting memory for
822 the clean but heavy parport handling is not an option. The
823 drawback is a reduced portability and the impossibility to
824 daisy-chain other parallel port devices.
826 Don't say Y here if you said Y or M to i2c-parport. Saying M to
827 both is possible but both modules should not be loaded at the same
830 This support is also available as a module. If so, the module
831 will be called i2c-parport-light.
834 tristate "TAOS evaluation module"
840 This supports TAOS evaluation modules on serial port. In order to
841 use this driver, you will need the inputattach tool, which is part
842 of the input-utils package.
846 This support is also available as a module. If so, the module
847 will be called i2c-taos-evm.
850 tristate "Tiny-USB adapter"
853 If you say yes to this option, support will be included for the
854 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
855 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
857 This driver can also be built as a module. If so, the module
858 will be called i2c-tiny-usb.
860 config I2C_VIPERBOARD
861 tristate "Viperboard I2C master support"
862 depends on MFD_VIPERBOARD && USB
864 Say yes here to access the I2C part of the Nano River
865 Technologies Viperboard as I2C master.
866 See viperboard API specification and Nano
867 River Tech's viperboard.h for detailed meaning
868 of the module parameters.
870 comment "Other I2C/SMBus bus drivers"
873 tristate "Acorn IOC/IOMD I2C bus support"
874 depends on ARCH_ACORN
878 Say yes if you want to support the I2C bus on Acorn platforms.
880 If you don't know, say Y.
883 tristate "Elektor ISA card"
884 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
887 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
890 This support is also available as a module. If so, the module
891 will be called i2c-elektor.
894 tristate "PCA9564/PCA9665 on an ISA bus"
899 This driver supports ISA boards using the Philips PCA9564/PCA9665
900 parallel bus to I2C bus controller.
902 This driver can also be built as a module. If so, the module
903 will be called i2c-pca-isa.
905 This device is almost undetectable and using this driver on a
906 system which doesn't have this device will result in long
907 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
908 time). If unsure, say N.
911 tristate "SiByte SMBus interface"
912 depends on SIBYTE_SB1xxx_SOC
914 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
917 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
918 depends on SCx200_GPIO
921 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
923 If you don't know what to do here, say N.
925 This support is also available as a module. If so, the module
926 will be called scx200_i2c.
928 This driver is deprecated and will be dropped soon. Use i2c-gpio
929 (or scx200_acb) instead.
931 config SCx200_I2C_SCL
932 int "GPIO pin used for SCL"
933 depends on SCx200_I2C
936 Enter the GPIO pin number used for the SCL signal. This value can
937 also be specified with a module parameter.
939 config SCx200_I2C_SDA
940 int "GPIO pin used for SDA"
941 depends on SCx200_I2C
944 Enter the GPIO pin number used for the SSA signal. This value can
945 also be specified with a module parameter.
948 tristate "Geode ACCESS.bus support"
949 depends on X86_32 && PCI
951 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
952 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
954 If you don't know what to do here, say N.
956 This support is also available as a module. If so, the module
957 will be called scx200_acb.