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