drivers/i2c/busses/Kconfig

   1 #
   2 # Sensor device configuration
   3 #
   4
   5 menu "I2C Hardware Bus support"
   6         depends on I2C
   7
   8 config I2C_ALI1535
   9         tristate "ALI 1535"
  10         depends on I2C && PCI
  11         help
  12           If you say yes to this option, support will be included for the SMB
  13           Host controller on Acer Labs Inc. (ALI) M1535 South Bridges.  The SMB
  14           controller is part of the 7101 device, which is an ACPI-compliant
  15           Power Management Unit (PMU).
  16
  17           This driver can also be built as a module.  If so, the module
  18           will be called i2c-ali1535.
  19
  20 config I2C_ALI1563
  21         tristate "ALI 1563"
  22         depends on I2C && PCI && EXPERIMENTAL
  23         help
  24           If you say yes to this option, support will be included for the SMB
  25           Host controller on Acer Labs Inc. (ALI) M1563 South Bridges.  The SMB
  26           controller is part of the 7101 device, which is an ACPI-compliant
  27           Power Management Unit (PMU).
  28
  29           This driver can also be built as a module.  If so, the module
  30           will be called i2c-ali1563.
  31
  32 config I2C_ALI15X3
  33         tristate "ALI 15x3"
  34         depends on I2C && PCI
  35         help
  36           If you say yes to this option, support will be included for the
  37           Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
  38
  39           This driver can also be built as a module.  If so, the module
  40           will be called i2c-ali15x3.
  41
  42 config I2C_AMD756
  43         tristate "AMD 756/766/768/8111 and nVidia nForce"
  44         depends on I2C && PCI
  45         help
  46           If you say yes to this option, support will be included for the AMD
  47           756/766/768 mainboard I2C interfaces.  The driver also includes
  48           support for the first (SMBus 1.0) I2C interface of the AMD 8111 and
  49           the nVidia nForce I2C interface.
  50
  51           This driver can also be built as a module.  If so, the module
  52           will be called i2c-amd756.
  53
  54 config I2C_AMD756_S4882
  55         tristate "SMBus multiplexing on the Tyan S4882"
  56         depends on I2C_AMD756 && EXPERIMENTAL
  57         help
  58           Enabling this option will add specific SMBus support for the Tyan
  59           S4882 motherboard.  On this 4-CPU board, the SMBus is multiplexed
  60           over 8 different channels, where the various memory module EEPROMs
  61           and temperature sensors live.  Saying yes here will give you access
  62           to these in addition to the trunk.
  63
  64           This driver can also be built as a module.  If so, the module
  65           will be called i2c-amd756-s4882.
  66
  67 config I2C_AMD8111
  68         tristate "AMD 8111"
  69         depends on I2C && PCI
  70         help
  71           If you say yes to this option, support will be included for the
  72           second (SMBus 2.0) AMD 8111 mainboard I2C interface.
  73
  74           This driver can also be built as a module.  If so, the module
  75           will be called i2c-amd8111.
  76
  77 config I2C_AT91
  78         tristate "Atmel AT91 I2C Two-Wire interface (TWI)"
  79         depends on I2C && ARCH_AT91 && EXPERIMENTAL
  80         help
  81           This supports the use of the I2C interface on Atmel AT91
  82           processors.
  83
  84 config I2C_AU1550
  85         tristate "Au1550/Au1200 SMBus interface"
  86         depends on I2C && (SOC_AU1550 || SOC_AU1200)
  87         help
  88           If you say yes to this option, support will be included for the
  89           Au1550 and Au1200 SMBus interface.
  90
  91           This driver can also be built as a module.  If so, the module
  92           will be called i2c-au1550.
  93
  94 config I2C_ELEKTOR
  95         tristate "Elektor ISA card"
  96         depends on I2C && ISA && BROKEN_ON_SMP
  97         select I2C_ALGOPCF
  98         help
  99           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
 100           such an adapter.
 101
 102           This support is also available as a module.  If so, the module
 103           will be called i2c-elektor.
 104
 105 config I2C_HYDRA
 106         tristate "CHRP Apple Hydra Mac I/O I2C interface"
 107         depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
 108         select I2C_ALGOBIT
 109         help
 110           This supports the use of the I2C interface in the Apple Hydra Mac
 111           I/O chip on some CHRP machines (e.g. the LongTrail).  Say Y if you
 112           have such a machine.
 113
 114           This support is also available as a module.  If so, the module
 115           will be called i2c-hydra.
 116
 117 config I2C_I801
 118         tristate "Intel 82801 (ICH)"
 119         depends on I2C && PCI
 120         help
 121           If you say yes to this option, support will be included for the Intel
 122           801 family of mainboard I2C interfaces.  Specifically, the following
 123           versions of the chipset are supported:
 124             82801AA
 125             82801AB
 126             82801BA
 127             82801CA/CAM
 128             82801DB
 129             82801EB/ER (ICH5/ICH5R)
 130             6300ESB
 131             ICH6
 132             ICH7
 133             ESB2
 134             ICH8
 135             ICH9
 136
 137           This driver can also be built as a module.  If so, the module
 138           will be called i2c-i801.
 139
 140 config I2C_I810
 141         tristate "Intel 810/815"
 142         depends on I2C && PCI
 143         select I2C_ALGOBIT
 144         help
 145           If you say yes to this option, support will be included for the Intel
 146           810/815 family of mainboard I2C interfaces.  Specifically, the
 147           following versions of the chipset are supported:
 148             i810AA
 149             i810AB
 150             i810E
 151             i815
 152             i845G
 153
 154           This driver can also be built as a module.  If so, the module
 155           will be called i2c-i810.
 156
 157 config I2C_PXA
 158         tristate "Intel PXA2XX I2C adapter (EXPERIMENTAL)"
 159         depends on I2C && EXPERIMENTAL && ARCH_PXA
 160         help
 161           If you have devices in the PXA I2C bus, say yes to this option.
 162           This driver can also be built as a module.  If so, the module
 163           will be called i2c-pxa.
 164
 165 config I2C_PXA_SLAVE
 166         bool "Intel PXA2XX I2C Slave comms support"
 167         depends on I2C_PXA
 168         help
 169           Support I2C slave mode communications on the PXA I2C bus.  This
 170           is necessary for systems where the PXA may be a target on the
 171           I2C bus.
 172
 173 config I2C_PIIX4
 174         tristate "Intel PIIX4 and compatible (ATI/Serverworks/Broadcom/SMSC)"
 175         depends on I2C && PCI
 176         help
 177           If you say yes to this option, support will be included for the Intel
 178           PIIX4 family of mainboard I2C interfaces.  Specifically, the following
 179           versions of the chipset are supported (note that Serverworks is part
 180           of Broadcom):
 181             Intel PIIX4
 182             Intel 440MX
 183             ATI IXP200
 184             ATI IXP300
 185             ATI IXP400
 186             Serverworks OSB4
 187             Serverworks CSB5
 188             Serverworks CSB6
 189             Serverworks HT-1000
 190             SMSC Victory66
 191
 192           This driver can also be built as a module.  If so, the module
 193           will be called i2c-piix4.
 194
 195 config I2C_IBM_IIC
 196         tristate "IBM PPC 4xx on-chip I2C interface"
 197         depends on IBM_OCP && I2C
 198         help
 199           Say Y here if you want to use IIC peripheral found on
 200           embedded IBM PPC 4xx based systems.
 201
 202           This driver can also be built as a module.  If so, the module
 203           will be called i2c-ibm_iic.
 204
 205 config I2C_IOP3XX
 206         tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface"
 207         depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX) && I2C
 208         help
 209           Say Y here if you want to use the IIC bus controller on
 210           the Intel IOPx3xx I/O Processors or IXP4xx Network Processors.
 211
 212           This driver can also be built as a module.  If so, the module
 213           will be called i2c-iop3xx.
 214
 215 config I2C_ISA
 216         tristate
 217         depends on I2C
 218
 219 config I2C_IXP4XX
 220         tristate "IXP4xx GPIO-Based I2C Interface"
 221         depends on I2C && ARCH_IXP4XX
 222         select I2C_ALGOBIT
 223         help
 224           Say Y here if you have an Intel IXP4xx(420,421,422,425) based
 225           system and are using GPIO lines for an I2C bus.
 226
 227           This support is also available as a module. If so, the module
 228           will be called i2c-ixp4xx.
 229
 230 config I2C_IXP2000
 231         tristate "IXP2000 GPIO-Based I2C Interface"
 232         depends on I2C && ARCH_IXP2000
 233         select I2C_ALGOBIT
 234         help
 235           Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
 236           system and are using GPIO lines for an I2C bus.
 237
 238           This support is also available as a module. If so, the module
 239           will be called i2c-ixp2000.
 240
 241 config I2C_POWERMAC
 242         tristate "Powermac I2C interface"
 243         depends on I2C && PPC_PMAC
 244         default y
 245         help
 246           This exposes the various PowerMac i2c interfaces to the linux i2c
 247           layer and to userland. It is used by various drivers on the powemac
 248           platform, thus should generally be enabled.
 249
 250           This support is also available as a module.  If so, the module
 251           will be called i2c-powermac.
 252
 253 config I2C_MPC
 254         tristate "MPC107/824x/85xx/52xx/86xx"
 255         depends on I2C && PPC32
 256         help
 257           If you say yes to this option, support will be included for the
 258           built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
 259           MPC85xx/MPC8641 family processors. The driver may also work on 52xx
 260           family processors, though interrupts are known not to work.
 261
 262           This driver can also be built as a module.  If so, the module
 263           will be called i2c-mpc.
 264
 265 config I2C_NFORCE2
 266         tristate "Nvidia nForce2, nForce3 and nForce4"
 267         depends on I2C && PCI
 268         help
 269           If you say yes to this option, support will be included for the Nvidia
 270           nForce2, nForce3 and nForce4 families of mainboard I2C interfaces.
 271
 272           This driver can also be built as a module.  If so, the module
 273           will be called i2c-nforce2.
 274
 275 config I2C_OCORES
 276         tristate "OpenCores I2C Controller"
 277         depends on I2C && EXPERIMENTAL
 278         help
 279           If you say yes to this option, support will be included for the
 280           OpenCores I2C controller. For details see
 281           http://www.opencores.org/projects.cgi/web/i2c/overview
 282
 283           This driver can also be built as a module.  If so, the module
 284           will be called i2c-ocores.
 285
 286 config I2C_OMAP
 287         tristate "OMAP I2C adapter"
 288         depends on I2C && ARCH_OMAP
 289         default y if MACH_OMAP_H3 || MACH_OMAP_OSK
 290         help
 291           If you say yes to this option, support will be included for the
 292           I2C interface on the Texas Instruments OMAP1/2 family of processors.
 293           Like OMAP1510/1610/1710/5912 and OMAP242x.
 294           For details see http://www.ti.com/omap.
 295
 296 config I2C_PARPORT
 297         tristate "Parallel port adapter"
 298         depends on I2C && PARPORT
 299         select I2C_ALGOBIT
 300         help
 301           This supports parallel port I2C adapters such as the ones made by
 302           Philips or Velleman, Analog Devices evaluation boards, and more.
 303           Basically any adapter using the parallel port as an I2C bus with
 304           no extra chipset is supported by this driver, or could be.
 305
 306           This driver is a replacement for (and was inspired by) an older
 307           driver named i2c-philips-par.  The new driver supports more devices,
 308           and makes it easier to add support for new devices.
 309
 310           An adapter type parameter is now mandatory.  Please read the file
 311           Documentation/i2c/busses/i2c-parport for details.
 312
 313           Another driver exists, named i2c-parport-light, which doesn't depend
 314           on the parport driver.  This is meant for embedded systems. Don't say
 315           Y here if you intend to say Y or M there.
 316
 317           This support is also available as a module.  If so, the module
 318           will be called i2c-parport.
 319
 320 config I2C_PARPORT_LIGHT
 321         tristate "Parallel port adapter (light)"
 322         depends on I2C
 323         select I2C_ALGOBIT
 324         help
 325           This supports parallel port I2C adapters such as the ones made by
 326           Philips or Velleman, Analog Devices evaluation boards, and more.
 327           Basically any adapter using the parallel port as an I2C bus with
 328           no extra chipset is supported by this driver, or could be.
 329
 330           This driver is a light version of i2c-parport.  It doesn't depend
 331           on the parport driver, and uses direct I/O access instead.  This
 332           might be preferred on embedded systems where wasting memory for
 333           the clean but heavy parport handling is not an option.  The
 334           drawback is a reduced portability and the impossibility to
 335           daisy-chain other parallel port devices.
 336
 337           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
 338           both is possible but both modules should not be loaded at the same
 339           time.
 340
 341           This support is also available as a module.  If so, the module
 342           will be called i2c-parport-light.
 343
 344 config I2C_PROSAVAGE
 345         tristate "S3/VIA (Pro)Savage"
 346         depends on I2C && PCI
 347         select I2C_ALGOBIT
 348         help
 349           If you say yes to this option, support will be included for the
 350           I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
 351           graphics processors.
 352           chipsets supported:
 353             S3/VIA KM266/VT8375 aka ProSavage8
 354             S3/VIA KM133/VT8365 aka Savage4
 355
 356           This support is also available as a module.  If so, the module
 357           will be called i2c-prosavage.
 358
 359 config I2C_RPXLITE
 360         tristate "Embedded Planet RPX Lite/Classic support"
 361         depends on (RPXLITE || RPXCLASSIC) && I2C
 362         select I2C_ALGO8XX
 363
 364 config I2C_S3C2410
 365         tristate "S3C2410 I2C Driver"
 366         depends on I2C && ARCH_S3C2410
 367         help
 368           Say Y here to include support for I2C controller in the
 369           Samsung S3C2410 based System-on-Chip devices.
 370
 371 config I2C_SAVAGE4
 372         tristate "S3 Savage 4"
 373         depends on I2C && PCI && EXPERIMENTAL
 374         select I2C_ALGOBIT
 375         help
 376           If you say yes to this option, support will be included for the
 377           S3 Savage 4 I2C interface.
 378
 379           This driver can also be built as a module.  If so, the module
 380           will be called i2c-savage4.
 381
 382 config I2C_SIBYTE
 383         tristate "SiByte SMBus interface"
 384         depends on SIBYTE_SB1xxx_SOC && I2C
 385         help
 386           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
 387
 388 config SCx200_I2C
 389         tristate "NatSemi SCx200 I2C using GPIO pins"
 390         depends on SCx200_GPIO && I2C
 391         select I2C_ALGOBIT
 392         help
 393           Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
 394
 395           If you don't know what to do here, say N.
 396
 397           This support is also available as a module.  If so, the module
 398           will be called scx200_i2c.
 399
 400 config SCx200_I2C_SCL
 401         int "GPIO pin used for SCL"
 402         depends on SCx200_I2C
 403         default "12"
 404         help
 405           Enter the GPIO pin number used for the SCL signal.  This value can
 406           also be specified with a module parameter.
 407
 408 config SCx200_I2C_SDA
 409         int "GPIO pin used for SDA"
 410         depends on SCx200_I2C
 411         default "13"
 412         help
 413           Enter the GPIO pin number used for the SSA signal.  This value can
 414           also be specified with a module parameter.
 415
 416 config SCx200_ACB
 417         tristate "Geode ACCESS.bus support"
 418         depends on X86_32 && I2C && PCI
 419         help
 420           Enable the use of the ACCESS.bus controllers on the Geode SCx200 and
 421           SC1100 processors and the CS5535 and CS5536 Geode companion devices.
 422
 423           If you don't know what to do here, say N.
 424
 425           This support is also available as a module.  If so, the module
 426           will be called scx200_acb.
 427
 428 config I2C_SIS5595
 429         tristate "SiS 5595"
 430         depends on I2C && PCI
 431         help
 432           If you say yes to this option, support will be included for the
 433           SiS5595 SMBus (a subset of I2C) interface.
 434
 435           This driver can also be built as a module.  If so, the module
 436           will be called i2c-sis5595.
 437
 438 config I2C_SIS630
 439         tristate "SiS 630/730"
 440         depends on I2C && PCI
 441         help
 442           If you say yes to this option, support will be included for the
 443           SiS630 and SiS730 SMBus (a subset of I2C) interface.
 444
 445           This driver can also be built as a module.  If so, the module
 446           will be called i2c-sis630.
 447
 448 config I2C_SIS96X
 449         tristate "SiS 96x"
 450         depends on I2C && PCI
 451         help
 452           If you say yes to this option, support will be included for the SiS
 453           96x SMBus (a subset of I2C) interfaces.  Specifically, the following
 454           chipsets are supported:
 455             645/961
 456             645DX/961
 457             645DX/962
 458             648/961
 459             650/961
 460             735
 461             745
 462
 463           This driver can also be built as a module.  If so, the module
 464           will be called i2c-sis96x.
 465
 466 config I2C_STUB
 467         tristate "I2C/SMBus Test Stub"
 468         depends on I2C && EXPERIMENTAL && 'm'
 469         default 'n'
 470         help
 471           This module may be useful to developers of SMBus client drivers,
 472           especially for certain kinds of sensor chips.
 473
 474           If you do build this module, be sure to read the notes and warnings
 475           in <file:Documentation/i2c/i2c-stub>.
 476
 477           If you don't know what to do here, definitely say N.
 478
 479 config I2C_VERSATILE
 480         tristate "ARM Versatile/Realview I2C bus support"
 481         depends on I2C && (ARCH_VERSATILE || ARCH_REALVIEW)
 482         select I2C_ALGOBIT
 483         help
 484           Say yes if you want to support the I2C serial bus on ARMs Versatile
 485           range of platforms.
 486
 487           This driver can also be built as a module.  If so, the module
 488           will be called i2c-versatile.
 489
 490 config I2C_VIA
 491         tristate "VIA 82C586B"
 492         depends on I2C && PCI && EXPERIMENTAL
 493         select I2C_ALGOBIT
 494         help
 495           If you say yes to this option, support will be included for the VIA
 496           82C586B I2C interface
 497
 498           This driver can also be built as a module.  If so, the module
 499           will be called i2c-via.
 500
 501 config I2C_VIAPRO
 502         tristate "VIA 82C596/82C686/82xx"
 503         depends on I2C && PCI
 504         help
 505           If you say yes to this option, support will be included for the VIA
 506           82C596/82C686/82xx I2C interfaces.  Specifically, the following
 507           chipsets are supported:
 508             VT82C596A/B
 509             VT82C686A/B
 510             VT8231
 511             VT8233/A
 512             VT8235
 513             VT8237R/A
 514             VT8251
 515
 516           This driver can also be built as a module.  If so, the module
 517           will be called i2c-viapro.
 518
 519 config I2C_VOODOO3
 520         tristate "Voodoo 3"
 521         depends on I2C && PCI
 522         select I2C_ALGOBIT
 523         help
 524           If you say yes to this option, support will be included for the
 525           Voodoo 3 I2C interface.
 526
 527           This driver can also be built as a module.  If so, the module
 528           will be called i2c-voodoo3.
 529
 530 config I2C_PCA_ISA
 531         tristate "PCA9564 on an ISA bus"
 532         depends on I2C
 533         select I2C_ALGOPCA
 534         default n
 535         help
 536           This driver supports ISA boards using the Philips PCA 9564
 537           Parallel bus to I2C bus controller
 538
 539           This driver can also be built as a module.  If so, the module
 540           will be called i2c-pca-isa.
 541
 542           This device is almost undetectable and using this driver on a
 543           system which doesn't have this device will result in long
 544           delays when I2C/SMBus chip drivers are loaded (e.g. at boot
 545           time).  If unsure, say N.
 546
 547 config I2C_MV64XXX
 548         tristate "Marvell mv64xxx I2C Controller"
 549         depends on I2C && MV64X60 && EXPERIMENTAL
 550         help
 551           If you say yes to this option, support will be included for the
 552           built-in I2C interface on the Marvell 64xxx line of host bridges.
 553
 554           This driver can also be built as a module.  If so, the module
 555           will be called i2c-mv64xxx.
 556
 557 config I2C_PNX
 558         tristate "I2C bus support for Philips PNX targets"
 559         depends on ARCH_PNX4008 && I2C
 560         help
 561           This driver supports the Philips IP3204 I2C IP block master and/or
 562           slave controller
 563
 564           This driver can also be built as a module.  If so, the module
 565           will be called i2c-pnx.
 566
 567 endmenu