2 # Sensor device configuration
5 menu "I2C Hardware Bus support"
8 comment "PC SMBus host controller drivers"
15 If you say yes to this option, support will be included for the SMB
16 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB
17 controller is part of the 7101 device, which is an ACPI-compliant
18 Power Management Unit (PMU).
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
27 If you say yes to this option, support will be included for the SMB
28 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB
29 controller is part of the 7101 device, which is an ACPI-compliant
30 Power Management Unit (PMU).
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
39 If you say yes to this option, support will be included for the
40 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
46 tristate "AMD 756/766/768/8111 and nVidia nForce"
49 If you say yes to this option, support will be included for the AMD
50 756/766/768 mainboard I2C interfaces. The driver also includes
51 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
52 the nVidia nForce I2C interface.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
57 config I2C_AMD756_S4882
58 tristate "SMBus multiplexing on the Tyan S4882"
59 depends on I2C_AMD756 && X86
61 Enabling this option will add specific SMBus support for the Tyan
62 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed
63 over 8 different channels, where the various memory module EEPROMs
64 and temperature sensors live. Saying yes here will give you access
65 to these in addition to the trunk.
67 This driver can also be built as a module. If so, the module
68 will be called i2c-amd756-s4882.
74 If you say yes to this option, support will be included for the
75 second (SMBus 2.0) AMD 8111 mainboard I2C interface.
77 This driver can also be built as a module. If so, the module
78 will be called i2c-amd8111.
81 tristate "Intel 82801 (ICH/PCH)"
83 select CHECK_SIGNATURE if X86 && DMI
85 If you say yes to this option, support will be included for the Intel
86 801 family of mainboard I2C interfaces. Specifically, the following
87 versions of the chipset are supported:
93 82801EB/ER (ICH5/ICH5R)
112 Wildcat Point-LP (PCH)
114 This driver can also be built as a module. If so, the module
115 will be called i2c-i801.
118 tristate "Intel SCH SMBus 1.0"
122 Say Y here if you want to use SMBus controller on the Intel SCH
125 This driver can also be built as a module. If so, the module
126 will be called i2c-isch.
129 tristate "Intel iSMT SMBus Controller"
130 depends on PCI && X86
132 If you say yes to this option, support will be included for the Intel
133 iSMT SMBus host controller interface.
135 This driver can also be built as a module. If so, the module will be
139 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
142 If you say yes to this option, support will be included for the Intel
143 PIIX4 family of mainboard I2C interfaces. Specifically, the following
144 versions of the chipset are supported (note that Serverworks is part
163 Some AMD chipsets contain two PIIX4-compatible SMBus
164 controllers. This driver will attempt to use both controllers
165 on the SB700/SP5100, if they have been initialized by the BIOS.
167 This driver can also be built as a module. If so, the module
168 will be called i2c-piix4.
171 tristate "Nvidia nForce2, nForce3 and nForce4"
174 If you say yes to this option, support will be included for the Nvidia
175 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
177 This driver can also be built as a module. If so, the module
178 will be called i2c-nforce2.
180 config I2C_NFORCE2_S4985
181 tristate "SMBus multiplexing on the Tyan S4985"
182 depends on I2C_NFORCE2 && X86
184 Enabling this option will add specific SMBus support for the Tyan
185 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed
186 over 4 different channels, where the various memory module EEPROMs
187 live. Saying yes here will give you access to these in addition
190 This driver can also be built as a module. If so, the module
191 will be called i2c-nforce2-s4985.
197 If you say yes to this option, support will be included for the
198 SiS5595 SMBus (a subset of I2C) interface.
200 This driver can also be built as a module. If so, the module
201 will be called i2c-sis5595.
204 tristate "SiS 630/730/964"
207 If you say yes to this option, support will be included for the
208 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface.
210 This driver can also be built as a module. If so, the module
211 will be called i2c-sis630.
217 If you say yes to this option, support will be included for the SiS
218 96x SMBus (a subset of I2C) interfaces. Specifically, the following
219 chipsets are supported:
228 This driver can also be built as a module. If so, the module
229 will be called i2c-sis96x.
232 tristate "VIA VT82C586B"
236 If you say yes to this option, support will be included for the VIA
237 82C586B I2C interface
239 This driver can also be built as a module. If so, the module
240 will be called i2c-via.
243 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900"
246 If you say yes to this option, support will be included for the VIA
247 VT82C596 and later SMBus interface. Specifically, the following
248 chipsets are supported:
261 This driver can also be built as a module. If so, the module
262 will be called i2c-viapro.
266 comment "ACPI drivers"
269 tristate "SMBus Control Method Interface"
271 This driver supports the SMBus Control Method Interface. It needs the
272 BIOS to declare ACPI control methods as described in the SMBus Control
273 Method Interface specification.
275 To compile this driver as a module, choose M here:
276 the module will be called i2c-scmi.
280 comment "Mac SMBus host controller drivers"
281 depends on PPC_CHRP || PPC_PMAC
284 tristate "CHRP Apple Hydra Mac I/O I2C interface"
285 depends on PCI && PPC_CHRP
288 This supports the use of the I2C interface in the Apple Hydra Mac
289 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you
292 This support is also available as a module. If so, the module
293 will be called i2c-hydra.
296 tristate "Powermac I2C interface"
300 This exposes the various PowerMac i2c interfaces to the linux i2c
301 layer and to userland. It is used by various drivers on the PowerMac
302 platform, and should generally be enabled.
304 This support is also available as a module. If so, the module
305 will be called i2c-powermac.
307 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
310 tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
313 This supports the use of the I2C interface on Atmel AT91
316 A serious problem is that there is no documented way to issue
317 repeated START conditions for more than two messages, as needed
318 to support combined I2C messages. Use the i2c-gpio driver
319 unless your system can cope with this limitation.
321 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices
322 don't have clock stretching in transmission mode. For that reason,
323 you can encounter underrun issues causing premature stop sendings if
324 the latency to fill the transmission register is too long. If you
325 are facing this situation, use the i2c-gpio driver.
328 tristate "Au1550/Au1200/Au1300 SMBus interface"
329 depends on MIPS_ALCHEMY
331 If you say yes to this option, support will be included for the
332 Au1550/Au1200/Au1300 SMBus interface.
334 This driver can also be built as a module. If so, the module
335 will be called i2c-au1550.
338 tristate "Broadcom BCM2835 I2C controller"
339 depends on ARCH_BCM2835
341 If you say yes to this option, support will be included for the
342 BCM2835 I2C controller.
344 If you don't know what to do here, say N.
346 This support is also available as a module. If so, the module
347 will be called i2c-bcm2835.
350 tristate "BCM Kona I2C adapter"
351 depends on ARCH_BCM_MOBILE
354 If you say yes to this option, support will be included for the
355 I2C interface on the Broadcom Kona family of processors.
357 If you do not need KONA I2C inteface, say N.
359 config I2C_BLACKFIN_TWI
360 tristate "Blackfin TWI I2C support"
362 depends on !BF561 && !BF531 && !BF532 && !BF533
364 This is the I2C bus driver for Blackfin on-chip TWI interface.
366 This driver can also be built as a module. If so, the module
367 will be called i2c-bfin-twi.
369 config I2C_BLACKFIN_TWI_CLK_KHZ
370 int "Blackfin TWI I2C clock (kHz)"
371 depends on I2C_BLACKFIN_TWI
375 The unit of the TWI clock is kHz.
378 tristate "CBUS I2C driver"
381 Support for CBUS access using I2C API. Mostly relevant for Nokia
382 Internet Tablets (770, N800 and N810).
384 This driver can also be built as a module. If so, the module
385 will be called i2c-cbus-gpio.
388 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
389 depends on (CPM1 || CPM2) && OF_I2C
391 This supports the use of the I2C interface on Freescale
392 processors with CPM1 or CPM2.
394 This driver can also be built as a module. If so, the module
395 will be called i2c-cpm.
398 tristate "DaVinci I2C driver"
399 depends on ARCH_DAVINCI || ARCH_KEYSTONE
401 Support for TI DaVinci I2C controller driver.
403 This driver can also be built as a module. If so, the module
404 will be called i2c-davinci.
406 Please note that this driver might be needed to bring up other
407 devices such as DaVinci NIC.
408 For details please see http://www.ti.com/davinci
410 config I2C_DESIGNWARE_CORE
413 config I2C_DESIGNWARE_PLATFORM
414 tristate "Synopsys DesignWare Platform"
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-platform.
424 config I2C_DESIGNWARE_PCI
425 tristate "Synopsys DesignWare PCI"
427 select I2C_DESIGNWARE_CORE
429 If you say yes to this option, support will be included for the
430 Synopsys DesignWare I2C adapter. Only master mode is supported.
432 This driver can also be built as a module. If so, the module
433 will be called i2c-designware-pci.
436 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C"
439 This driver is for PCH(Platform controller Hub) I2C of EG20T which
440 is an IOH(Input/Output Hub) for x86 embedded processor.
441 This driver can access PCH I2C bus device.
443 This driver also can be used for LAPIS Semiconductor IOH(Input/
444 Output Hub), ML7213, ML7223 and ML7831.
445 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
446 for MP(Media Phone) use and ML7831 IOH is for general purpose use.
447 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
448 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
451 tristate "Exynos5 high-speed I2C driver"
452 depends on ARCH_EXYNOS5 && OF
454 Say Y here to include support for high-speed I2C controller in the
455 Exynos5 based Samsung SoCs.
458 tristate "GPIO-based bitbanging I2C"
462 This is a very simple bitbanging I2C driver utilizing the
463 arch-neutral GPIO API to control the SCL and SDA lines.
465 config I2C_HIGHLANDER
466 tristate "Highlander FPGA SMBus interface"
467 depends on SH_HIGHLANDER
469 If you say yes to this option, support will be included for
470 the SMBus interface located in the FPGA on various Highlander
471 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL
472 FPGAs. This is wholly unrelated to the SoC I2C.
474 This driver can also be built as a module. If so, the module
475 will be called i2c-highlander.
478 tristate "IBM PPC 4xx on-chip I2C interface"
481 Say Y here if you want to use IIC peripheral found on
482 embedded IBM PPC 4xx based systems.
484 This driver can also be built as a module. If so, the module
485 will be called i2c-ibm_iic.
488 tristate "IMX I2C interface"
491 Say Y here if you want to use the IIC bus controller on
492 the Freescale i.MX/MXC processors.
494 This driver can also be built as a module. If so, the module
495 will be called i2c-imx.
498 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
499 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
501 Say Y here if you want to use the IIC bus controller on
502 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
504 This driver can also be built as a module. If so, the module
505 will be called i2c-iop3xx.
508 tristate "Kontron COM I2C Controller"
509 depends on MFD_KEMPLD
511 This enables support for the I2C bus interface on some Kontron ETX
512 and COMexpress (ETXexpress) modules.
514 This driver can also be built as a module. If so, the module
515 will be called i2c-kempld.
518 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx"
521 If you say yes to this option, support will be included for the
522 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx,
523 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors.
525 This driver can also be built as a module. If so, the module
526 will be called i2c-mpc.
529 tristate "Marvell mv64xxx I2C Controller"
530 depends on (MV64X60 || PLAT_ORION || ARCH_SUNXI)
532 If you say yes to this option, support will be included for the
533 built-in I2C interface on the Marvell 64xxx line of host bridges.
534 This driver is also used for Allwinner SoCs I2C controllers.
536 This driver can also be built as a module. If so, the module
537 will be called i2c-mv64xxx.
540 tristate "Freescale i.MX28 I2C interface"
544 Say Y here if you want to use the I2C bus controller on
545 the Freescale i.MX28 processors.
547 This driver can also be built as a module. If so, the module
548 will be called i2c-mxs.
551 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller"
554 If you say yes to this option, support will be included for the
555 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures,
556 as well as the STA2X11 PCIe I/O HUB.
559 tristate "NUC900 I2C Driver"
560 depends on ARCH_W90X900
562 Say Y here to include support for I2C controller in the
563 Winbond/Nuvoton NUC900 based System-on-Chip devices.
566 tristate "OpenCores I2C Controller"
568 If you say yes to this option, support will be included for the
569 OpenCores I2C controller. For details see
570 http://www.opencores.org/projects.cgi/web/i2c/overview
572 This driver can also be built as a module. If so, the module
573 will be called i2c-ocores.
576 tristate "OMAP I2C adapter"
578 default y if MACH_OMAP_H3 || MACH_OMAP_OSK
580 If you say yes to this option, support will be included for the
581 I2C interface on the Texas Instruments OMAP1/2 family of processors.
582 Like OMAP1510/1610/1710/5912 and OMAP242x.
583 For details see http://www.ti.com/omap.
586 tristate "PA Semi SMBus interface"
587 depends on PPC_PASEMI && PCI
589 Supports the PA Semi PWRficient on-chip SMBus interfaces.
591 config I2C_PCA_PLATFORM
592 tristate "PCA9564/PCA9665 as platform device"
596 This driver supports a memory mapped Philips PCA9564/PCA9665
597 parallel bus to I2C bus controller.
599 This driver can also be built as a module. If so, the module
600 will be called i2c-pca-platform.
603 tristate "PMC MSP I2C TWI Controller"
606 This driver supports the PMC TWI controller on MSP devices.
608 This driver can also be built as module. If so, the module
609 will be called i2c-pmcmsp.
612 tristate "I2C bus support for Philips PNX and NXP LPC targets"
613 depends on ARCH_LPC32XX
615 This driver supports the Philips IP3204 I2C IP block master and/or
618 This driver can also be built as a module. If so, the module
619 will be called i2c-pnx.
622 tristate "PKUnity v3 I2C bus support"
623 depends on UNICORE32 && ARCH_PUV3
626 This driver supports the I2C IP inside the PKUnity-v3 SoC.
627 This I2C bus controller is under AMBA/AXI bus.
629 This driver can also be built as a module. If so, the module
630 will be called i2c-puv3.
633 tristate "Intel PXA2XX I2C adapter"
634 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF)
636 If you have devices in the PXA I2C bus, say yes to this option.
637 This driver can also be built as a module. If so, the module
638 will be called i2c-pxa.
641 def_bool I2C_PXA && X86_32 && PCI && OF
644 bool "Intel PXA2XX I2C Slave comms support"
645 depends on I2C_PXA && !X86_32
647 Support I2C slave mode communications on the PXA I2C bus. This
648 is necessary for systems where the PXA may be a target on the
651 config HAVE_S3C2410_I2C
654 This will include I2C support for Samsung SoCs. If you want to
655 include I2C support for any machine, kindly select this in the
656 respective Kconfig file.
659 tristate "S3C2410 I2C Driver"
660 depends on HAVE_S3C2410_I2C
662 Say Y here to include support for I2C controller in the
666 tristate "S6000 I2C support"
667 depends on XTENSA_VARIANT_S6000
669 This driver supports the on chip I2C device on the
670 S6000 xtensa processor family.
672 To compile this driver as a module, choose M here. The module
673 will be called i2c-s6000.
676 tristate "Renesas SH7760 I2C Controller"
677 depends on CPU_SUBTYPE_SH7760
679 This driver supports the 2 I2C interfaces on the Renesas SH7760.
681 This driver can also be built as a module. If so, the module
682 will be called i2c-sh7760.
685 tristate "SuperH Mobile I2C Controller"
686 depends on SUPERH || ARM || COMPILE_TEST
688 If you say yes to this option, support will be included for the
689 built-in I2C interface on the Renesas SH-Mobile processor.
691 This driver can also be built as a module. If so, the module
692 will be called i2c-sh_mobile.
695 tristate "Simtec Generic I2C interface"
698 If you say yes to this option, support will be included for
699 the Simtec Generic I2C interface. This driver is for the
700 simple I2C bus used on newer Simtec products for general
701 I2C, such as DDC on the Simtec BBD2016A.
703 This driver can also be built as a module. If so, the module
704 will be called i2c-simtec.
707 tristate "CSR SiRFprimaII I2C interface"
710 If you say yes to this option, support will be included for the
711 CSR SiRFprimaII I2C interface.
713 This driver can also be built as a module. If so, the module
714 will be called i2c-sirf.
717 tristate "STMicroelectronics SSC I2C support"
720 Enable this option to add support for STMicroelectronics SoCs
721 hardware SSC (Synchronous Serial Controller) as an I2C controller.
723 This driver can also be built as module. If so, the module
724 will be called i2c-st.
727 tristate "ST Microelectronics DDC I2C interface"
729 default y if MACH_U300
731 If you say yes to this option, support will be included for the
732 I2C interface from ST Microelectronics simply called "DDC I2C"
733 supporting both I2C and DDC, used in e.g. the U300 series
736 This driver can also be built as a module. If so, the module
737 will be called i2c-stu300.
740 tristate "NVIDIA Tegra internal I2C controller"
741 depends on ARCH_TEGRA
743 If you say yes to this option, support will be included for the
744 I2C controller embedded in NVIDIA Tegra SOCs
747 tristate "ARM Versatile/Realview I2C bus support"
748 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS
751 Say yes if you want to support the I2C serial bus on ARMs Versatile
754 This driver can also be built as a module. If so, the module
755 will be called i2c-versatile.
758 tristate "Wondermedia WM8xxx SoC I2C bus support"
759 depends on ARCH_VT8500
761 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series
764 This driver can also be built as a module. If so, the module will be
768 tristate "Cavium OCTEON I2C bus support"
769 depends on CAVIUM_OCTEON_SOC
771 Say yes if you want to support the I2C serial bus on Cavium
774 This driver can also be built as a module. If so, the module
775 will be called i2c-octeon.
778 tristate "Xilinx I2C Controller"
781 If you say yes to this option, support will be included for the
782 Xilinx I2C controller.
784 This driver can also be built as a module. If so, the module
785 will be called xilinx_i2c.
788 tristate "XLR I2C support"
791 This driver enables support for the on-chip I2C interface of
792 the Netlogic XLR/XLS MIPS processors.
794 This driver can also be built as a module. If so, the module
795 will be called i2c-xlr.
798 tristate "Renesas R-Car I2C Controller"
799 depends on ARM || COMPILE_TEST
801 If you say yes to this option, support will be included for the
802 R-Car I2C controller.
804 This driver can also be built as a module. If so, the module
805 will be called i2c-rcar.
807 comment "External I2C/SMBus adapter drivers"
809 config I2C_DIOLAN_U2C
810 tristate "Diolan U2C-12 USB adapter"
813 If you say yes to this option, support will be included for Diolan
814 U2C-12, a USB to I2C interface.
816 This driver can also be built as a module. If so, the module
817 will be called i2c-diolan-u2c.
820 tristate "Parallel port adapter"
825 This supports parallel port I2C adapters such as the ones made by
826 Philips or Velleman, Analog Devices evaluation boards, and more.
827 Basically any adapter using the parallel port as an I2C bus with
828 no extra chipset is supported by this driver, or could be.
830 This driver is a replacement for (and was inspired by) an older
831 driver named i2c-philips-par. The new driver supports more devices,
832 and makes it easier to add support for new devices.
834 An adapter type parameter is now mandatory. Please read the file
835 Documentation/i2c/busses/i2c-parport for details.
837 Another driver exists, named i2c-parport-light, which doesn't depend
838 on the parport driver. This is meant for embedded systems. Don't say
839 Y here if you intend to say Y or M there.
841 This support is also available as a module. If so, the module
842 will be called i2c-parport.
844 config I2C_PARPORT_LIGHT
845 tristate "Parallel port adapter (light)"
849 This supports parallel port I2C adapters such as the ones made by
850 Philips or Velleman, Analog Devices evaluation boards, and more.
851 Basically any adapter using the parallel port as an I2C bus with
852 no extra chipset is supported by this driver, or could be.
854 This driver is a light version of i2c-parport. It doesn't depend
855 on the parport driver, and uses direct I/O access instead. This
856 might be preferred on embedded systems where wasting memory for
857 the clean but heavy parport handling is not an option. The
858 drawback is a reduced portability and the impossibility to
859 daisy-chain other parallel port devices.
861 Don't say Y here if you said Y or M to i2c-parport. Saying M to
862 both is possible but both modules should not be loaded at the same
865 This support is also available as a module. If so, the module
866 will be called i2c-parport-light.
869 tristate "TAOS evaluation module"
875 This supports TAOS evaluation modules on serial port. In order to
876 use this driver, you will need the inputattach tool, which is part
877 of the input-utils package.
881 This support is also available as a module. If so, the module
882 will be called i2c-taos-evm.
885 tristate "Tiny-USB adapter"
888 If you say yes to this option, support will be included for the
889 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
890 http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
892 This driver can also be built as a module. If so, the module
893 will be called i2c-tiny-usb.
895 config I2C_VIPERBOARD
896 tristate "Viperboard I2C master support"
897 depends on MFD_VIPERBOARD && USB
899 Say yes here to access the I2C part of the Nano River
900 Technologies Viperboard as I2C master.
901 See viperboard API specification and Nano
902 River Tech's viperboard.h for detailed meaning
903 of the module parameters.
905 comment "Other I2C/SMBus bus drivers"
908 tristate "Acorn IOC/IOMD I2C bus support"
909 depends on ARCH_ACORN
913 Say yes if you want to support the I2C bus on Acorn platforms.
915 If you don't know, say Y.
918 tristate "Elektor ISA card"
919 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
922 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
925 This support is also available as a module. If so, the module
926 will be called i2c-elektor.
929 tristate "PCA9564/PCA9665 on an ISA bus"
934 This driver supports ISA boards using the Philips PCA9564/PCA9665
935 parallel bus to I2C bus controller.
937 This driver can also be built as a module. If so, the module
938 will be called i2c-pca-isa.
940 This device is almost undetectable and using this driver on a
941 system which doesn't have this device will result in long
942 delays when I2C/SMBus chip drivers are loaded (e.g. at boot
943 time). If unsure, say N.
946 tristate "SiByte SMBus interface"
947 depends on SIBYTE_SB1xxx_SOC
949 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
952 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
953 depends on SCx200_GPIO
956 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
958 If you don't know what to do here, say N.
960 This support is also available as a module. If so, the module
961 will be called scx200_i2c.
963 This driver is deprecated and will be dropped soon. Use i2c-gpio
964 (or scx200_acb) instead.
966 config SCx200_I2C_SCL
967 int "GPIO pin used for SCL"
968 depends on SCx200_I2C
971 Enter the GPIO pin number used for the SCL signal. This value can
972 also be specified with a module parameter.
974 config SCx200_I2C_SDA
975 int "GPIO pin used for SDA"
976 depends on SCx200_I2C
979 Enter the GPIO pin number used for the SSA signal. This value can
980 also be specified with a module parameter.
983 tristate "Geode ACCESS.bus support"
984 depends on X86_32 && PCI
986 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
987 SC1100 processors and the CS5535 and CS5536 Geode companion devices.
989 If you don't know what to do here, say N.
991 This support is also available as a module. If so, the module
992 will be called scx200_acb.