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 && EXPERIMENTAL
  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 && EXPERIMENTAL
  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 && EXPERIMENTAL
  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 && EXPERIMENTAL
  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_AU1550
  78         tristate "Au1550 SMBus interface"
  79         depends on I2C && SOC_AU1550
  80         help
  81           If you say yes to this option, support will be included for the
  82           Au1550 SMBus interface.
  83
  84           This driver can also be built as a module.  If so, the module
  85           will be called i2c-au1550.
  86
  87 config I2C_ELEKTOR
  88         tristate "Elektor ISA card"
  89         depends on I2C && ISA && BROKEN_ON_SMP
  90         select I2C_ALGOPCF
  91         help
  92           This supports the PCF8584 ISA bus I2C adapter.  Say Y if you own
  93           such an adapter.
  94
  95           This support is also available as a module.  If so, the module
  96           will be called i2c-elektor.
  97
  98 config I2C_HYDRA
  99         tristate "CHRP Apple Hydra Mac I/O I2C interface"
 100         depends on I2C && PCI && PPC_CHRP && EXPERIMENTAL
 101         select I2C_ALGOBIT
 102         help
 103           This supports the use of the I2C interface in the Apple Hydra Mac
 104           I/O chip on some CHRP machines (e.g. the LongTrail).  Say Y if you
 105           have such a machine.
 106
 107           This support is also available as a module.  If so, the module
 108           will be called i2c-hydra.
 109
 110 config I2C_I801
 111         tristate "Intel 82801 (ICH)"
 112         depends on I2C && PCI && EXPERIMENTAL
 113         help
 114           If you say yes to this option, support will be included for the Intel
 115           801 family of mainboard I2C interfaces.  Specifically, the following
 116           versions of the chipset are supported:
 117             82801AA
 118             82801AB
 119             82801BA
 120             82801CA/CAM
 121             82801DB
 122             82801EB/ER (ICH5/ICH5R)
 123             6300ESB
 124             ICH6
 125             ICH7
 126
 127           This driver can also be built as a module.  If so, the module
 128           will be called i2c-i801.
 129
 130 config I2C_I810
 131         tristate "Intel 810/815"
 132         depends on I2C && PCI && EXPERIMENTAL
 133         select I2C_ALGOBIT
 134         help
 135           If you say yes to this option, support will be included for the Intel
 136           810/815 family of mainboard I2C interfaces.  Specifically, the
 137           following versions of the chipset is supported:
 138             i810AA
 139             i810AB
 140             i810E
 141             i815
 142
 143           This driver can also be built as a module.  If so, the module
 144           will be called i2c-i810.
 145
 146 config I2C_PIIX4
 147         tristate "Intel PIIX4"
 148         depends on I2C && PCI
 149         help
 150           If you say yes to this option, support will be included for the Intel
 151           PIIX4 family of mainboard I2C interfaces.  Specifically, the following
 152           versions of the chipset are supported:
 153             Intel PIIX4
 154             Intel 440MX
 155             Serverworks OSB4
 156             Serverworks CSB5
 157             Serverworks CSB6
 158             SMSC Victory66
 159
 160           This driver can also be built as a module.  If so, the module
 161           will be called i2c-piix4.
 162
 163 config I2C_IBM_IIC
 164         tristate "IBM PPC 4xx on-chip I2C interface"
 165         depends on IBM_OCP && I2C
 166         help
 167           Say Y here if you want to use IIC peripheral found on
 168           embedded IBM PPC 4xx based systems.
 169
 170           This driver can also be built as a module.  If so, the module
 171           will be called i2c-ibm_iic.
 172
 173 config I2C_IOP3XX
 174         tristate "Intel IOP3xx and IXP4xx on-chip I2C interface"
 175         depends on (ARCH_IOP3XX || ARCH_IXP4XX) && I2C
 176         help
 177           Say Y here if you want to use the IIC bus controller on
 178           the Intel IOP3xx I/O Processors or IXP4xx Network Processors.
 179
 180           This driver can also be built as a module.  If so, the module
 181           will be called i2c-iop3xx.
 182
 183 config I2C_ISA
 184         tristate "ISA Bus support"
 185         depends on I2C && EXPERIMENTAL
 186         help
 187           If you say yes to this option, support will be included for i2c
 188           interfaces that are on the ISA bus.
 189
 190           This driver can also be built as a module.  If so, the module
 191           will be called i2c-isa.
 192
 193 config I2C_ITE
 194         tristate "ITE I2C Adapter"
 195         depends on I2C && MIPS_ITE8172
 196         select I2C_ALGOITE
 197         help
 198           This supports the ITE8172 I2C peripheral found on some MIPS
 199           systems. Say Y if you have one of these. You should also say Y for
 200           the ITE I2C driver algorithm support above.
 201
 202           This support is also available as a module.  If so, the module
 203           will be called i2c-ite.
 204
 205 config I2C_IXP4XX
 206         tristate "IXP4xx GPIO-Based I2C Interface"
 207         depends on I2C && ARCH_IXP4XX
 208         select I2C_ALGOBIT
 209         help
 210           Say Y here if you have an Intel IXP4xx(420,421,422,425) based
 211           system and are using GPIO lines for an I2C bus.
 212
 213           This support is also available as a module. If so, the module
 214           will be called i2c-ixp4xx.
 215
 216 config I2C_IXP2000
 217         tristate "IXP2000 GPIO-Based I2C Interface"
 218         depends on I2C && ARCH_IXP2000
 219         select I2C_ALGOBIT
 220         help
 221           Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based
 222           system and are using GPIO lines for an I2C bus.
 223
 224           This support is also available as a module. If so, the module
 225           will be called i2c-ixp2000.
 226
 227 config I2C_KEYWEST
 228         tristate "Powermac Keywest I2C interface"
 229         depends on I2C && PPC_PMAC
 230         help
 231           This supports the use of the I2C interface in the combo-I/O
 232           chip on recent Apple machines.  Say Y if you have such a machine.
 233
 234           This support is also available as a module.  If so, the module
 235           will be called i2c-keywest.
 236
 237 config I2C_MPC
 238         tristate "MPC107/824x/85xx/52xx"
 239         depends on I2C && PPC
 240         help
 241           If you say yes to this option, support will be included for the
 242           built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
 243           MPC85xx family processors. The driver may also work on 52xx
 244           family processors, though interrupts are known not to work.
 245
 246           This driver can also be built as a module.  If so, the module
 247           will be called i2c-mpc.
 248
 249 config I2C_NFORCE2
 250         tristate "Nvidia Nforce2"
 251         depends on I2C && PCI && EXPERIMENTAL
 252         help
 253           If you say yes to this option, support will be included for the Nvidia
 254           Nforce2 family of mainboard I2C interfaces.
 255           This driver also supports the nForce3 Pro 150 MCP.
 256
 257           This driver can also be built as a module.  If so, the module
 258           will be called i2c-nforce2.
 259
 260 config I2C_PARPORT
 261         tristate "Parallel port adapter"
 262         depends on I2C && PARPORT
 263         select I2C_ALGOBIT
 264         help
 265           This supports parallel port I2C adapters such as the ones made by
 266           Philips or Velleman, Analog Devices evaluation boards, and more.
 267           Basically any adapter using the parallel port as an I2C bus with
 268           no extra chipset is supported by this driver, or could be.
 269
 270           This driver is a replacement for (and was inspired by) an older
 271           driver named i2c-philips-par.  The new driver supports more devices,
 272           and makes it easier to add support for new devices.
 273
 274           Another driver exists, named i2c-parport-light, which doesn't depend
 275           on the parport driver.  This is meant for embedded systems. Don't say
 276           Y here if you intend to say Y or M there.
 277
 278           This support is also available as a module.  If so, the module
 279           will be called i2c-parport.
 280
 281 config I2C_PARPORT_LIGHT
 282         tristate "Parallel port adapter (light)"
 283         depends on I2C
 284         select I2C_ALGOBIT
 285         help
 286           This supports parallel port I2C adapters such as the ones made by
 287           Philips or Velleman, Analog Devices evaluation boards, and more.
 288           Basically any adapter using the parallel port as an I2C bus with
 289           no extra chipset is supported by this driver, or could be.
 290
 291           This driver is a light version of i2c-parport.  It doesn't depend
 292           on the parport driver, and uses direct I/O access instead.  This
 293           might be prefered on embedded systems where wasting memory for
 294           the clean but heavy parport handling is not an option.  The
 295           drawback is a reduced portability and the impossibility to
 296           dasiy-chain other parallel port devices.
 297
 298           Don't say Y here if you said Y or M to i2c-parport.  Saying M to
 299           both is possible but both modules should not be loaded at the same
 300           time.
 301
 302           This support is also available as a module.  If so, the module
 303           will be called i2c-parport-light.
 304
 305 config I2C_PROSAVAGE
 306         tristate "S3/VIA (Pro)Savage"
 307         depends on I2C && PCI && EXPERIMENTAL
 308         select I2C_ALGOBIT
 309         help
 310           If you say yes to this option, support will be included for the
 311           I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8
 312           graphics processors.
 313           chipsets supported:
 314             S3/VIA KM266/VT8375 aka ProSavage8
 315             S3/VIA KM133/VT8365 aka Savage4
 316
 317           This support is also available as a module.  If so, the module
 318           will be called i2c-prosavage.
 319
 320 config I2C_RPXLITE
 321         tristate "Embedded Planet RPX Lite/Classic support"
 322         depends on (RPXLITE || RPXCLASSIC) && I2C
 323         select I2C_ALGO8XX
 324
 325 config I2C_S3C2410
 326         tristate "S3C2410 I2C Driver"
 327         depends on I2C && ARCH_S3C2410
 328         help
 329           Say Y here to include support for I2C controller in the
 330           Samsung S3C2410 based System-on-Chip devices.
 331
 332 config I2C_SAVAGE4
 333         tristate "S3 Savage 4"
 334         depends on I2C && PCI && EXPERIMENTAL
 335         select I2C_ALGOBIT
 336         help
 337           If you say yes to this option, support will be included for the
 338           S3 Savage 4 I2C interface.
 339
 340           This driver can also be built as a module.  If so, the module
 341           will be called i2c-savage4.
 342
 343 config I2C_SIBYTE
 344         tristate "SiByte SMBus interface"
 345         depends on SIBYTE_SB1xxx_SOC && I2C
 346         help
 347           Supports the SiByte SOC on-chip I2C interfaces (2 channels).
 348
 349 config SCx200_I2C
 350         tristate "NatSemi SCx200 I2C using GPIO pins"
 351         depends on SCx200_GPIO && I2C
 352         select I2C_ALGOBIT
 353         help
 354           Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
 355
 356           If you don't know what to do here, say N.
 357
 358           This support is also available as a module.  If so, the module
 359           will be called scx200_i2c.
 360
 361 config SCx200_I2C_SCL
 362         int "GPIO pin used for SCL"
 363         depends on SCx200_I2C
 364         default "12"
 365         help
 366           Enter the GPIO pin number used for the SCL signal.  This value can
 367           also be specified with a module parameter.
 368
 369 config SCx200_I2C_SDA
 370         int "GPIO pin used for SDA"
 371         depends on SCx200_I2C
 372         default "13"
 373         help
 374           Enter the GPIO pin number used for the SSA signal.  This value can
 375           also be specified with a module parameter.
 376
 377 config SCx200_ACB
 378         tristate "NatSemi SCx200 ACCESS.bus"
 379         depends on I2C && PCI
 380         help
 381           Enable the use of the ACCESS.bus controllers of a SCx200 processor.
 382
 383           If you don't know what to do here, say N.
 384
 385           This support is also available as a module.  If so, the module
 386           will be called scx200_acb.
 387
 388 config I2C_SIS5595
 389         tristate "SiS 5595"
 390         depends on I2C && PCI && EXPERIMENTAL
 391         help
 392           If you say yes to this option, support will be included for the
 393           SiS5595 SMBus (a subset of I2C) interface.
 394
 395           This driver can also be built as a module.  If so, the module
 396           will be called i2c-sis5595.
 397
 398 config I2C_SIS630
 399         tristate "SiS 630/730"
 400         depends on I2C && PCI && EXPERIMENTAL
 401         help
 402           If you say yes to this option, support will be included for the
 403           SiS630 and SiS730 SMBus (a subset of I2C) interface.
 404
 405           This driver can also be built as a module.  If so, the module
 406           will be called i2c-sis630.
 407
 408 config I2C_SIS96X
 409         tristate "SiS 96x"
 410         depends on I2C && PCI && EXPERIMENTAL
 411         help
 412           If you say yes to this option, support will be included for the SiS
 413           96x SMBus (a subset of I2C) interfaces.  Specifically, the following
 414           chipsets are supported:
 415             645/961
 416             645DX/961
 417             645DX/962
 418             648/961
 419             650/961
 420             735
 421
 422           This driver can also be built as a module.  If so, the module
 423           will be called i2c-sis96x.
 424
 425 config I2C_STUB
 426         tristate "I2C/SMBus Test Stub"
 427         depends on I2C && EXPERIMENTAL && 'm'
 428         default 'n'
 429         help
 430           This module may be useful to developers of SMBus client drivers,
 431           especially for certain kinds of sensor chips.
 432
 433           If you do build this module, be sure to read the notes and warnings
 434           in <file:Documentation/i2c/i2c-stub>.
 435
 436           If you don't know what to do here, definitely say N.
 437
 438 config I2C_VIA
 439         tristate "VIA 82C586B"
 440         depends on I2C && PCI && EXPERIMENTAL
 441         select I2C_ALGOBIT
 442         help
 443           If you say yes to this option, support will be included for the VIA
 444           82C586B I2C interface
 445
 446           This driver can also be built as a module.  If so, the module
 447           will be called i2c-via.
 448
 449 config I2C_VIAPRO
 450         tristate "VIA 82C596/82C686/823x"
 451         depends on I2C && PCI && EXPERIMENTAL
 452         help
 453           If you say yes to this option, support will be included for the VIA
 454           82C596/82C686/823x I2C interfaces.  Specifically, the following
 455           chipsets are supported:
 456           82C596A/B
 457           82C686A/B
 458           8231
 459           8233
 460           8233A
 461           8235
 462           8237
 463
 464           This driver can also be built as a module.  If so, the module
 465           will be called i2c-viapro.
 466
 467 config I2C_VOODOO3
 468         tristate "Voodoo 3"
 469         depends on I2C && PCI && EXPERIMENTAL
 470         select I2C_ALGOBIT
 471         help
 472           If you say yes to this option, support will be included for the
 473           Voodoo 3 I2C interface.
 474
 475           This driver can also be built as a module.  If so, the module
 476           will be called i2c-voodoo3.
 477
 478 config I2C_PCA_ISA
 479         tristate "PCA9564 on an ISA bus"
 480         depends on I2C
 481         select I2C_ALGOPCA
 482         help
 483           This driver supports ISA boards using the Philips PCA 9564
 484           Parallel bus to I2C bus controller
 485
 486           This driver can also be built as a module.  If so, the module
 487           will be called i2c-pca-isa.
 488
 489 config I2C_MV64XXX
 490         tristate "Marvell mv64xxx I2C Controller"
 491         depends on I2C && MV64X60 && EXPERIMENTAL
 492         help
 493           If you say yes to this option, support will be included for the
 494           built-in I2C interface on the Marvell 64xxx line of host bridges.
 495
 496           This driver can also be built as a module.  If so, the module
 497           will be called i2c-mv64xxx.
 498
 499 endmenu