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