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