drivers/i2c/busses/Kconfig

   1 #
   2 # Sensor device configuration
   3 #
   4
   5 menu "I2C Hardware Bus support"
   6
   7 comment "PC SMBus host controller drivers"
   8         depends on PCI
   9
  10 config I2C_ALI1535
  11         tristate "ALI 1535"
  12         depends on PCI
  13         help
  14           If you say yes to this option, support will be included for the SMB
  15           Host controller on Acer Labs Inc. (ALI) M1535 South Bridges.  The SMB
  16           controller is part of the 7101 device, which is an ACPI-compliant
  17           Power Management Unit (PMU).
  18
  19           This driver can also be built as a module.  If so, the module
  20           will be called i2c-ali1535.
  21
  22 config I2C_ALI1563
  23         tristate "ALI 1563"
  24         depends on PCI && EXPERIMENTAL
  25         help
  26           If you say yes to this option, support will be included for the SMB
  27           Host controller on Acer Labs Inc. (ALI) M1563 South Bridges.  The SMB
  28           controller is part of the 7101 device, which is an ACPI-compliant
  29           Power Management Unit (PMU).
  30
  31           This driver can also be built as a module.  If so, the module
  32           will be called i2c-ali1563.
  33
  34 config I2C_ALI15X3
  35         tristate "ALI 15x3"
  36         depends on PCI
  37         help
  38           If you say yes to this option, support will be included for the
  39           Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
  40
  41           This driver can also be built as a module.  If so, the module
  42           will be called i2c-ali15x3.
  43
  44 config I2C_AMD756
  45         tristate "AMD 756/766/768/8111 and nVidia nForce"
  46         depends on PCI
  47         help
  48           If you say yes to this option, support will be included for the AMD
  49           756/766/768 mainboard I2C interfaces.  The driver also includes
  50           support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
  51           the nVidia nForce I2C interface.
  52
  53           This driver can also be built as a module.  If so, the module
  54           will be called i2c-amd756.
  55
  56 config I2C_AMD756_S4882
  57         tristate "SMBus multiplexing on the Tyan S4882"
  58         depends on I2C_AMD756 && EXPERIMENTAL
  59         help
  60           Enabling this option will add specific SMBus support for the Tyan
  61           S4882 motherboard.  On this 4-CPU board, the SMBus is multiplexed
  62           over 8 different channels, where the various memory module EEPROMs
  63           and temperature sensors live.  Saying yes here will give you access
  64           to these in addition to the trunk.
  65
  66           This driver can also be built as a module.  If so, the module
  67           will be called i2c-amd756-s4882.
  68
  69 config I2C_AMD8111
  70         tristate "AMD 8111"
  71         depends on PCI
  72         help
  73           If you say yes to this option, support will be included for the
  74           second (SMBus 2.0) AMD 8111 mainboard I2C interface.
  75
  76           This driver can also be built as a module.  If so, the module
  77           will be called i2c-amd8111.
  78
  79 config I2C_I801
  80         tristate "Intel 82801 (ICH)"
  81         depends on PCI
  82         help
  83           If you say yes to this option, support will be included for the Intel
  84           801 family of mainboard I2C interfaces.  Specifically, the following
  85           versions of the chipset are supported:
  86             82801AA
  87             82801AB
  88             82801BA
  89             82801CA/CAM
  90             82801DB
  91             82801EB/ER (ICH5/ICH5R)
  92             6300ESB
  93             ICH6
  94             ICH7
  95             ESB2
  96             ICH8
  97             ICH9
  98             Tolapai
  99             ICH10
 100
 101           This driver can also be built as a module.  If so, the module
 102           will be called i2c-i801.
 103
 104 config I2C_ISCH
 105         tristate "Intel SCH SMBus 1.0"
 106         depends on PCI
 107         help
 108           Say Y here if you want to use SMBus controller on the Intel SCH
 109           based systems.
 110
 111           This driver can also be built as a module. If so, the module
 112           will be called i2c-isch.
 113
 114 config I2C_PIIX4
 115         tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
 116         depends on PCI
 117         help
 118           If you say yes to this option, support will be included for the Intel
 119           PIIX4 family of mainboard I2C interfaces.  Specifically, the following
 120           versions of the chipset are supported (note that Serverworks is part
 121           of Broadcom):
 122             Intel PIIX4
 123             Intel 440MX
 124             ATI IXP200
 125             ATI IXP300
 126             ATI IXP400
 127             ATI SB600
 128             ATI SB700
 129             ATI SB800
 130             Serverworks OSB4
 131             Serverworks CSB5
 132             Serverworks CSB6
 133             Serverworks HT-1000
 134             SMSC Victory66
 135
 136           This driver can also be built as a module.  If so, the module
 137           will be called i2c-piix4.
 138
 139 config I2C_NFORCE2
 140         tristate "Nvidia nForce2, nForce3 and nForce4"
 141         depends on PCI
 142         help
 143           If you say yes to this option, support will be included for the Nvidia
 144           nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
 145
 146           This driver can also be built as a module.  If so, the module
 147           will be called i2c-nforce2.
 148
 149 config I2C_NFORCE2_S4985
 150         tristate "SMBus multiplexing on the Tyan S4985"
 151         depends on I2C_NFORCE2 && EXPERIMENTAL
 152         help
 153           Enabling this option will add specific SMBus support for the Tyan
 154           S4985 motherboard.  On this 4-CPU board, the SMBus is multiplexed
 155           over 4 different channels, where the various memory module EEPROMs
 156           live.  Saying yes here will give you access to these in addition
 157           to the trunk.
 158
 159           This driver can also be built as a module.  If so, the module
 160           will be called i2c-nforce2-s4985.
 161
 162 config I2C_SIS5595
 163         tristate "SiS 5595"
 164         depends on PCI
 165         help
 166           If you say yes to this option, support will be included for the
 167           SiS5595 SMBus (a subset of I2C) interface.
 168
 169           This driver can also be built as a module.  If so, the module
 170           will be called i2c-sis5595.
 171
 172 config I2C_SIS630
 173         tristate "SiS 630/730"
 174         depends on PCI
 175         help
 176           If you say yes to this option, support will be included for the
 177           SiS630 and SiS730 SMBus (a subset of I2C) interface.
 178
 179           This driver can also be built as a module.  If so, the module
 180           will be called i2c-sis630.
 181
 182 config I2C_SIS96X
 183         tristate "SiS 96x"
 184         depends on PCI
 185         help
 186           If you say yes to this option, support will be included for the SiS
 187           96x SMBus (a subset of I2C) interfaces.  Specifically, the following
 188           chipsets are supported:
 189             645/961
 190             645DX/961
 191             645DX/962
 192             648/961
 193             650/961
 194             735
 195             745
 196
 197           This driver can also be built as a module.  If so, the module
 198           will be called i2c-sis96x.
 199
 200 config I2C_VIA
 201         tristate "VIA VT82C586B"
 202         depends on PCI && EXPERIMENTAL
 203         select I2C_ALGOBIT
 204         help
 205           If you say yes to this option, support will be included for the VIA
 206           82C586B I2C interface
 207
 208           This driver can also be built as a module.  If so, the module
 209           will be called i2c-via.
 210
 211 config I2C_VIAPRO
 212         tristate "VIA VT82C596/82C686/82xx and CX700"
 213         depends on PCI
 214         help
 215           If you say yes to this option, support will be included for the VIA
 216           VT82C596 and later SMBus interface.  Specifically, the following
 217           chipsets are supported:
 218             VT82C596A/B
 219             VT82C686A/B
 220             VT8231
 221             VT8233/A
 222             VT8235
 223             VT8237R/A/S
 224             VT8251
 225             CX700
 226
 227           This driver can also be built as a module.  If so, the module
 228           will be called i2c-viapro.
 229
 230 comment "Mac SMBus host controller drivers"
 231         depends on PPC_CHRP || PPC_PMAC
 232
 233 config I2C_HYDRA
 234         tristate "CHRP Apple Hydra Mac I/O I2C interface"
 235         depends on PCI && PPC_CHRP && EXPERIMENTAL
 236         select I2C_ALGOBIT
 237         help
 238           This supports the use of the I2C interface in the Apple Hydra Mac
 239           I/O chip on some CHRP machines (e.g. the LongTrail).  Say Y if you
 240           have such a machine.
 241
 242           This support is also available as a module.  If so, the module
 243           will be called i2c-hydra.
 244
 245 config I2C_POWERMAC
 246         tristate "Powermac I2C interface"
 247         depends on PPC_PMAC
 248         default y
 249         help
 250           This exposes the various PowerMac i2c interfaces to the linux i2c
 251           layer and to userland. It is used by various drivers on the PowerMac
 252           platform, and should generally be enabled.
 253
 254           This support is also available as a module.  If so, the module
 255           will be called i2c-powermac.
 256
 257 comment "I2C system bus drivers (mostly embedded / system-on-chip)"
 258
 259 config I2C_AT91
 260         tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
 261         depends on ARCH_AT91 && EXPERIMENTAL && BROKEN
 262         help
 263           This supports the use of the I2C interface on Atmel AT91
 264           processors.
 265
 266           This driver is BROKEN because the controller which it uses
 267           will easily trigger RX overrun and TX underrun errors.  Using
 268           low I2C clock rates may partially work around those issues
 269           on some systems.  Another serious problem is that there is no
 270           documented way to issue repeated START conditions, as needed
 271           to support combined I2C messages.  Use the i2c-gpio driver
 272           unless your system can cope with those limitations.
 273
 274 config I2C_AU1550
 275         tristate "Au1550/Au1200 SMBus interface"
 276         depends on SOC_AU1550 || SOC_AU1200
 277         help
 278           If you say yes to this option, support will be included for the
 279           Au1550 and Au1200 SMBus interface.
 280
 281           This driver can also be built as a module.  If so, the module
 282           will be called i2c-au1550.
 283
 284 config I2C_BLACKFIN_TWI
 285         tristate "Blackfin TWI I2C support"
 286         depends on BLACKFIN
 287         depends on !BF561 && !BF531 && !BF532 && !BF533
 288         help
 289           This is the I2C bus driver for Blackfin on-chip TWI interface.
 290
 291           This driver can also be built as a module.  If so, the module
 292           will be called i2c-bfin-twi.
 293
 294 config I2C_BLACKFIN_TWI_CLK_KHZ
 295         int "Blackfin TWI I2C clock (kHz)"
 296         depends on I2C_BLACKFIN_TWI
 297         range 10 400
 298         default 50
 299         help
 300           The unit of the TWI clock is kHz.
 301
 302 config I2C_CPM
 303         tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)"
 304         depends on (CPM1 || CPM2) && OF_I2C
 305         help
 306           This supports the use of the I2C interface on Freescale
 307           processors with CPM1 or CPM2.
 308
 309           This driver can also be built as a module.  If so, the module
 310           will be called i2c-cpm.
 311
 312 config I2C_DAVINCI
 313         tristate "DaVinci I2C driver"
 314         depends on ARCH_DAVINCI
 315         help
 316           Support for TI DaVinci I2C controller driver.
 317
 318           This driver can also be built as a module.  If so, the module
 319           will be called i2c-davinci.
 320
 321           Please note that this driver might be needed to bring up other
 322           devices such as DaVinci NIC.
 323           For details please see http://www.ti.com/davinci
 324
 325 config I2C_GPIO
 326         tristate "GPIO-based bitbanging I2C"
 327         depends on GENERIC_GPIO
 328         select I2C_ALGOBIT
 329         help
 330           This is a very simple bitbanging I2C driver utilizing the
 331           arch-neutral GPIO API to control the SCL and SDA lines.
 332
 333 config I2C_IBM_IIC
 334         tristate "IBM PPC 4xx on-chip I2C interface"
 335         depends on 4xx
 336         help
 337           Say Y here if you want to use IIC peripheral found on
 338           embedded IBM PPC 4xx based systems.
 339
 340           This driver can also be built as a module.  If so, the module
 341           will be called i2c-ibm_iic.
 342
 343 config I2C_IOP3XX
 344         tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
 345         depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX
 346         help
 347           Say Y here if you want to use the IIC bus controller on
 348           the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
 349
 350           This driver can also be built as a module.  If so, the module
 351           will be called i2c-iop3xx.
 352
 353 config I2C_IXP2000
 354         tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)"
 355         depends on ARCH_IXP2000
 356         select I2C_ALGOBIT
 357         help
 358           Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based
 359           system and are using GPIO lines for an I2C bus.
 360
 361           This support is also available as a module. If so, the module
 362           will be called i2c-ixp2000.
 363
 364           This driver is deprecated and will be dropped soon. Use i2c-gpio
 365           instead.
 366
 367 config I2C_MPC
 368         tristate "MPC107/824x/85xx/52xx/86xx"
 369         depends on PPC32
 370         help
 371           If you say yes to this option, support will be included for the
 372           built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
 373           MPC85xx/MPC8641 family processors. The driver may also work on 52xx
 374           family processors, though interrupts are known not to work.
 375
 376           This driver can also be built as a module.  If so, the module
 377           will be called i2c-mpc.
 378
 379 config I2C_MV64XXX
 380         tristate "Marvell mv64xxx I2C Controller"
 381         depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL
 382         help
 383           If you say yes to this option, support will be included for the
 384           built-in I2C interface on the Marvell 64xxx line of host bridges.
 385
 386           This driver can also be built as a module.  If so, the module
 387           will be called i2c-mv64xxx.
 388
 389 config I2C_OCORES
 390         tristate "OpenCores I2C Controller"
 391         depends on EXPERIMENTAL
 392         help
 393           If you say yes to this option, support will be included for the
 394           OpenCores I2C controller. For details see
 395           http://www.opencores.org/projects.cgi/web/i2c/overview
 396
 397           This driver can also be built as a module.  If so, the module
 398           will be called i2c-ocores.
 399
 400 config I2C_OMAP
 401         tristate "OMAP I2C adapter"
 402         depends on ARCH_OMAP
 403         default y if MACH_OMAP_H3 || MACH_OMAP_OSK
 404         help
 405           If you say yes to this option, support will be included for the
 406           I2C interface on the Texas Instruments OMAP1/2 family of processors.
 407           Like OMAP1510/1610/1710/5912 and OMAP242x.
 408           For details see http://www.ti.com/omap.
 409
 410 config I2C_PASEMI
 411         tristate "PA Semi SMBus interface"
 412         depends on PPC_PASEMI && PCI
 413         help
 414           Supports the PA Semi PWRficient on-chip SMBus interfaces.
 415
 416 config I2C_PNX
 417         tristate "I2C bus support for Philips PNX targets"
 418         depends on ARCH_PNX4008
 419         help
 420           This driver supports the Philips IP3204 I2C IP block master and/or
 421           slave controller
 422
 423           This driver can also be built as a module.  If so, the module
 424           will be called i2c-pnx.
 425
 426 config I2C_PXA
 427         tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
 428         depends on EXPERIMENTAL && ARCH_PXA
 429         help
 430           If you have devices in the PXA I2C bus, say yes to this option.
 431           This driver can also be built as a module.  If so, the module
 432           will be called i2c-pxa.
 433
 434 config I2C_PXA_SLAVE
 435         bool "Intel PXA2XX I2C Slave comms support"
 436         depends on I2C_PXA
 437         help
 438           Support I2C slave mode communications on the PXA I2C bus.  This
 439           is necessary for systems where the PXA may be a target on the
 440           I2C bus.
 441
 442 config I2C_S3C2410
 443         tristate "S3C2410 I2C Driver"
 444         depends on ARCH_S3C2410
 445         help
 446           Say Y here to include support for I2C controller in the
 447           Samsung S3C2410 based System-on-Chip devices.
 448
 449 config I2C_SH7760
 450         tristate "Renesas SH7760 I2C Controller"
 451         depends on CPU_SUBTYPE_SH7760
 452         help
 453           This driver supports the 2 I2C interfaces on the Renesas SH7760.
 454
 455           This driver can also be built as a module.  If so, the module
 456           will be called i2c-sh7760.
 457
 458 config I2C_SH_MOBILE
 459         tristate "SuperH Mobile I2C Controller"
 460         depends on SUPERH
 461         help
 462           If you say yes to this option, support will be included for the
 463           built-in I2C interface on the Renesas SH-Mobile processor.
 464
 465           This driver can also be built as a module.  If so, the module
 466           will be called i2c-sh_mobile.
 467
 468 config I2C_SIMTEC
 469         tristate "Simtec Generic I2C interface"
 470         select I2C_ALGOBIT
 471         help
 472           If you say yes to this option, support will be included for
 473           the Simtec Generic I2C interface. This driver is for the
 474           simple I2C bus used on newer Simtec products for general
 475           I2C, such as DDC on the Simtec BBD2016A.
 476
 477           This driver can also be built as a module. If so, the module
 478           will be called i2c-simtec.
 479
 480 config I2C_VERSATILE
 481         tristate "ARM Versatile/Realview I2C bus support"
 482         depends on ARCH_VERSATILE || ARCH_REALVIEW
 483         select I2C_ALGOBIT
 484         help
 485           Say yes if you want to support the I2C serial bus on ARMs Versatile
 486           range of platforms.
 487
 488           This driver can also be built as a module.  If so, the module
 489           will be called i2c-versatile.
 490
 491 comment "External I2C/SMBus adapter drivers"
 492
 493 config I2C_PARPORT
 494         tristate "Parallel port adapter"
 495         depends on PARPORT
 496         select I2C_ALGOBIT
 497         help
 498           This supports parallel port I2C adapters such as the ones made by
 499           Philips or Velleman, Analog Devices evaluation boards, and more.
 500           Basically any adapter using the parallel port as an I2C bus with
 501           no extra chipset is supported by this driver, or could be.
 502
 503           This driver is a replacement for (and was inspired by) an older
 504           driver named i2c-philips-par.  The new driver supports more devices,
 505           and makes it easier to add support for new devices.
 506
 507           An adapter type parameter is now mandatory.  Please read the file
 508           Documentation/i2c/busses/i2c-parport for details.
 509
 510           Another driver exists, named i2c-parport-light, which doesn't depend
 511           on the parport driver.  This is meant for embedded systems. Don't say
 512           Y here if you intend to say Y or M there.
 513
 514           This support is also available as a module.  If so, the module
 515           will be called i2c-parport.
 516
 517 config I2C_PARPORT_LIGHT
 518         tristate "Parallel port adapter (light)"
 519         select I2C_ALGOBIT
 520         help
 521           This supports parallel port I2C adapters such as the ones made by
 522           Philips or Velleman, Analog Devices evaluation boards, and more.
 523           Basically any adapter using the parallel port as an I2C bus with
 524           no extra chipset is supported by this driver, or could be.
 525
 526           This driver is a light version of i2c-parport.  It doesn't depend
 527           on the parport driver, and uses direct I/O access instead.  This
 528           might be preferred on embedded systems where wasting memory for
 529           the clean but heavy parport handling is not an option.  The
 530           drawback is a reduced portability and the impossibility to
 531           daisy-chain other parallel port devices.
 532
 533           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
 534           both is possible but both modules should not be loaded at the same
 535           time.
 536
 537           This support is also available as a module.  If so, the module
 538           will be called i2c-parport-light.
 539
 540 config I2C_TAOS_EVM
 541         tristate "TAOS evaluation module"
 542         depends on EXPERIMENTAL
 543         select SERIO
 544         select SERIO_SERPORT
 545         default n
 546         help
 547           This supports TAOS evaluation modules on serial port. In order to
 548           use this driver, you will need the inputattach tool, which is part
 549           of the input-utils package.
 550
 551           If unsure, say N.
 552
 553           This support is also available as a module.  If so, the module
 554           will be called i2c-taos-evm.
 555
 556 config I2C_TINY_USB
 557         tristate "Tiny-USB adapter"
 558         depends on USB
 559         help
 560           If you say yes to this option, support will be included for the
 561           i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See
 562           http://www.harbaum.org/till/i2c_tiny_usb for hardware details.
 563
 564           This driver can also be built as a module.  If so, the module
 565           will be called i2c-tiny-usb.
 566
 567 comment "Graphics adapter I2C/DDC channel drivers"
 568         depends on PCI
 569
 570 config I2C_VOODOO3
 571         tristate "Voodoo 3"
 572         depends on PCI
 573         select I2C_ALGOBIT
 574         help
 575           If you say yes to this option, support will be included for the
 576           Voodoo 3 I2C interface.
 577
 578           This driver can also be built as a module.  If so, the module
 579           will be called i2c-voodoo3.
 580
 581 comment "Other I2C/SMBus bus drivers"
 582
 583 config I2C_ACORN
 584         tristate "Acorn IOC/IOMD I2C bus support"
 585         depends on ARCH_ACORN
 586         default y
 587         select I2C_ALGOBIT
 588         help
 589           Say yes if you want to support the I2C bus on Acorn platforms.
 590
 591           If you don't know, say Y.
 592
 593 config I2C_ELEKTOR
 594         tristate "Elektor ISA card"
 595         depends on ISA && BROKEN_ON_SMP
 596         select I2C_ALGOPCF
 597         help
 598           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
 599           such an adapter.
 600
 601           This support is also available as a module.  If so, the module
 602           will be called i2c-elektor.
 603
 604 config I2C_PCA_ISA
 605         tristate "PCA9564 on an ISA bus"
 606         depends on ISA
 607         select I2C_ALGOPCA
 608         default n
 609         help
 610           This driver supports ISA boards using the Philips PCA9564
 611           parallel bus to I2C bus controller.
 612
 613           This driver can also be built as a module.  If so, the module
 614           will be called i2c-pca-isa.
 615
 616           This device is almost undetectable and using this driver on a
 617           system which doesn't have this device will result in long
 618           delays when I2C/SMBus chip drivers are loaded (e.g. at boot
 619           time).  If unsure, say N.
 620
 621 config I2C_PCA_PLATFORM
 622         tristate "PCA9564 as platform device"
 623         select I2C_ALGOPCA
 624         default n
 625         help
 626           This driver supports a memory mapped Philips PCA9564
 627           parallel bus to I2C bus controller.
 628
 629           This driver can also be built as a module.  If so, the module
 630           will be called i2c-pca-platform.
 631
 632 config I2C_PMCMSP
 633         tristate "PMC MSP I2C TWI Controller"
 634         depends on PMC_MSP
 635         help
 636           This driver supports the PMC TWI controller on MSP devices.
 637
 638           This driver can also be built as module. If so, the module
 639           will be called i2c-pmcmsp.
 640
 641 config I2C_SIBYTE
 642         tristate "SiByte SMBus interface"
 643         depends on SIBYTE_SB1xxx_SOC
 644         help
 645           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
 646
 647 config I2C_STUB
 648         tristate "I2C/SMBus Test Stub"
 649         depends on EXPERIMENTAL && m
 650         default 'n'
 651         help
 652           This module may be useful to developers of SMBus client drivers,
 653           especially for certain kinds of sensor chips.
 654
 655           If you do build this module, be sure to read the notes and warnings
 656           in <file:Documentation/i2c/i2c-stub>.
 657
 658           If you don't know what to do here, definitely say N.
 659
 660 config SCx200_I2C
 661         tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)"
 662         depends on SCx200_GPIO
 663         select I2C_ALGOBIT
 664         help
 665           Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
 666
 667           If you don't know what to do here, say N.
 668
 669           This support is also available as a module.  If so, the module
 670           will be called scx200_i2c.
 671
 672           This driver is deprecated and will be dropped soon. Use i2c-gpio
 673           (or scx200_acb) instead.
 674
 675 config SCx200_I2C_SCL
 676         int "GPIO pin used for SCL"
 677         depends on SCx200_I2C
 678         default "12"
 679         help
 680           Enter the GPIO pin number used for the SCL signal.  This value can
 681           also be specified with a module parameter.
 682
 683 config SCx200_I2C_SDA
 684         int "GPIO pin used for SDA"
 685         depends on SCx200_I2C
 686         default "13"
 687         help
 688           Enter the GPIO pin number used for the SSA signal.  This value can
 689           also be specified with a module parameter.
 690
 691 config SCx200_ACB
 692         tristate "Geode ACCESS.bus support"
 693         depends on X86_32 && PCI
 694         help
 695           Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
 696           SC1100 processors and the CS5535 and CS5536 Geode companion devices.
 697
 698           If you don't know what to do here, say N.
 699
 700           This support is also available as a module.  If so, the module
 701           will be called scx200_acb.
 702
 703 endmenu