1# 2# Sensor device configuration 3# 4 5menu "I2C Hardware Bus support" 6 depends on I2C 7 8config 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 20config 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 32config 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 42config 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 54config 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 67config 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 77config 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 84config 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 94config 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 105config 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 117config 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 140config 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 157config 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 165config 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 173config 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 ATI SB600 187 Serverworks OSB4 188 Serverworks CSB5 189 Serverworks CSB6 190 Serverworks HT-1000 191 SMSC Victory66 192 193 This driver can also be built as a module. If so, the module 194 will be called i2c-piix4. 195 196config I2C_IBM_IIC 197 tristate "IBM PPC 4xx on-chip I2C interface" 198 depends on IBM_OCP && I2C 199 help 200 Say Y here if you want to use IIC peripheral found on 201 embedded IBM PPC 4xx based systems. 202 203 This driver can also be built as a module. If so, the module 204 will be called i2c-ibm_iic. 205 206config I2C_IOP3XX 207 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" 208 depends on (ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX) && I2C 209 help 210 Say Y here if you want to use the IIC bus controller on 211 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. 212 213 This driver can also be built as a module. If so, the module 214 will be called i2c-iop3xx. 215 216config I2C_ISA 217 tristate 218 depends on I2C 219 220config I2C_IXP4XX 221 tristate "IXP4xx GPIO-Based I2C Interface" 222 depends on I2C && ARCH_IXP4XX 223 select I2C_ALGOBIT 224 help 225 Say Y here if you have an Intel IXP4xx(420,421,422,425) based 226 system and are using GPIO lines for an I2C bus. 227 228 This support is also available as a module. If so, the module 229 will be called i2c-ixp4xx. 230 231config I2C_IXP2000 232 tristate "IXP2000 GPIO-Based I2C Interface" 233 depends on I2C && ARCH_IXP2000 234 select I2C_ALGOBIT 235 help 236 Say Y here if you have an Intel IXP2000(2400, 2800, 2850) based 237 system and are using GPIO lines for an I2C bus. 238 239 This support is also available as a module. If so, the module 240 will be called i2c-ixp2000. 241 242config I2C_POWERMAC 243 tristate "Powermac I2C interface" 244 depends on I2C && PPC_PMAC 245 default y 246 help 247 This exposes the various PowerMac i2c interfaces to the linux i2c 248 layer and to userland. It is used by various drivers on the powemac 249 platform, thus should generally be enabled. 250 251 This support is also available as a module. If so, the module 252 will be called i2c-powermac. 253 254config I2C_MPC 255 tristate "MPC107/824x/85xx/52xx/86xx" 256 depends on I2C && PPC32 257 help 258 If you say yes to this option, support will be included for the 259 built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and 260 MPC85xx/MPC8641 family processors. The driver may also work on 52xx 261 family processors, though interrupts are known not to work. 262 263 This driver can also be built as a module. If so, the module 264 will be called i2c-mpc. 265 266config I2C_NFORCE2 267 tristate "Nvidia nForce2, nForce3 and nForce4" 268 depends on I2C && PCI 269 help 270 If you say yes to this option, support will be included for the Nvidia 271 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. 272 273 This driver can also be built as a module. If so, the module 274 will be called i2c-nforce2. 275 276config I2C_OCORES 277 tristate "OpenCores I2C Controller" 278 depends on I2C && EXPERIMENTAL 279 help 280 If you say yes to this option, support will be included for the 281 OpenCores I2C controller. For details see 282 http://www.opencores.org/projects.cgi/web/i2c/overview 283 284 This driver can also be built as a module. If so, the module 285 will be called i2c-ocores. 286 287config I2C_OMAP 288 tristate "OMAP I2C adapter" 289 depends on I2C && ARCH_OMAP 290 default y if MACH_OMAP_H3 || MACH_OMAP_OSK 291 help 292 If you say yes to this option, support will be included for the 293 I2C interface on the Texas Instruments OMAP1/2 family of processors. 294 Like OMAP1510/1610/1710/5912 and OMAP242x. 295 For details see http://www.ti.com/omap. 296 297config I2C_PARPORT 298 tristate "Parallel port adapter" 299 depends on I2C && PARPORT 300 select I2C_ALGOBIT 301 help 302 This supports parallel port I2C adapters such as the ones made by 303 Philips or Velleman, Analog Devices evaluation boards, and more. 304 Basically any adapter using the parallel port as an I2C bus with 305 no extra chipset is supported by this driver, or could be. 306 307 This driver is a replacement for (and was inspired by) an older 308 driver named i2c-philips-par. The new driver supports more devices, 309 and makes it easier to add support for new devices. 310 311 An adapter type parameter is now mandatory. Please read the file 312 Documentation/i2c/busses/i2c-parport for details. 313 314 Another driver exists, named i2c-parport-light, which doesn't depend 315 on the parport driver. This is meant for embedded systems. Don't say 316 Y here if you intend to say Y or M there. 317 318 This support is also available as a module. If so, the module 319 will be called i2c-parport. 320 321config I2C_PARPORT_LIGHT 322 tristate "Parallel port adapter (light)" 323 depends on I2C 324 select I2C_ALGOBIT 325 help 326 This supports parallel port I2C adapters such as the ones made by 327 Philips or Velleman, Analog Devices evaluation boards, and more. 328 Basically any adapter using the parallel port as an I2C bus with 329 no extra chipset is supported by this driver, or could be. 330 331 This driver is a light version of i2c-parport. It doesn't depend 332 on the parport driver, and uses direct I/O access instead. This 333 might be preferred on embedded systems where wasting memory for 334 the clean but heavy parport handling is not an option. The 335 drawback is a reduced portability and the impossibility to 336 daisy-chain other parallel port devices. 337 338 Don't say Y here if you said Y or M to i2c-parport. Saying M to 339 both is possible but both modules should not be loaded at the same 340 time. 341 342 This support is also available as a module. If so, the module 343 will be called i2c-parport-light. 344 345config I2C_PASEMI 346 tristate "PA Semi SMBus interface" 347# depends on PPC_PASEMI && I2C && PCI 348 depends on I2C && PCI 349 help 350 Supports the PA Semi PWRficient on-chip SMBus interfaces. 351 352config I2C_PROSAVAGE 353 tristate "S3/VIA (Pro)Savage" 354 depends on I2C && PCI 355 select I2C_ALGOBIT 356 help 357 If you say yes to this option, support will be included for the 358 I2C bus and DDC bus of the S3VIA embedded Savage4 and ProSavage8 359 graphics processors. 360 chipsets supported: 361 S3/VIA KM266/VT8375 aka ProSavage8 362 S3/VIA KM133/VT8365 aka Savage4 363 364 This support is also available as a module. If so, the module 365 will be called i2c-prosavage. 366 367config I2C_RPXLITE 368 tristate "Embedded Planet RPX Lite/Classic support" 369 depends on (RPXLITE || RPXCLASSIC) && I2C 370 select I2C_ALGO8XX 371 372config I2C_S3C2410 373 tristate "S3C2410 I2C Driver" 374 depends on I2C && ARCH_S3C2410 375 help 376 Say Y here to include support for I2C controller in the 377 Samsung S3C2410 based System-on-Chip devices. 378 379config I2C_SAVAGE4 380 tristate "S3 Savage 4" 381 depends on I2C && PCI && EXPERIMENTAL 382 select I2C_ALGOBIT 383 help 384 If you say yes to this option, support will be included for the 385 S3 Savage 4 I2C interface. 386 387 This driver can also be built as a module. If so, the module 388 will be called i2c-savage4. 389 390config I2C_SIBYTE 391 tristate "SiByte SMBus interface" 392 depends on SIBYTE_SB1xxx_SOC && I2C 393 help 394 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 395 396config SCx200_I2C 397 tristate "NatSemi SCx200 I2C using GPIO pins" 398 depends on SCx200_GPIO && I2C 399 select I2C_ALGOBIT 400 help 401 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. 402 403 If you don't know what to do here, say N. 404 405 This support is also available as a module. If so, the module 406 will be called scx200_i2c. 407 408config SCx200_I2C_SCL 409 int "GPIO pin used for SCL" 410 depends on SCx200_I2C 411 default "12" 412 help 413 Enter the GPIO pin number used for the SCL signal. This value can 414 also be specified with a module parameter. 415 416config SCx200_I2C_SDA 417 int "GPIO pin used for SDA" 418 depends on SCx200_I2C 419 default "13" 420 help 421 Enter the GPIO pin number used for the SSA signal. This value can 422 also be specified with a module parameter. 423 424config SCx200_ACB 425 tristate "Geode ACCESS.bus support" 426 depends on X86_32 && I2C && PCI 427 help 428 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and 429 SC1100 processors and the CS5535 and CS5536 Geode companion devices. 430 431 If you don't know what to do here, say N. 432 433 This support is also available as a module. If so, the module 434 will be called scx200_acb. 435 436config I2C_SIS5595 437 tristate "SiS 5595" 438 depends on I2C && PCI 439 help 440 If you say yes to this option, support will be included for the 441 SiS5595 SMBus (a subset of I2C) interface. 442 443 This driver can also be built as a module. If so, the module 444 will be called i2c-sis5595. 445 446config I2C_SIS630 447 tristate "SiS 630/730" 448 depends on I2C && PCI 449 help 450 If you say yes to this option, support will be included for the 451 SiS630 and SiS730 SMBus (a subset of I2C) interface. 452 453 This driver can also be built as a module. If so, the module 454 will be called i2c-sis630. 455 456config I2C_SIS96X 457 tristate "SiS 96x" 458 depends on I2C && PCI 459 help 460 If you say yes to this option, support will be included for the SiS 461 96x SMBus (a subset of I2C) interfaces. Specifically, the following 462 chipsets are supported: 463 645/961 464 645DX/961 465 645DX/962 466 648/961 467 650/961 468 735 469 745 470 471 This driver can also be built as a module. If so, the module 472 will be called i2c-sis96x. 473 474config I2C_STUB 475 tristate "I2C/SMBus Test Stub" 476 depends on I2C && EXPERIMENTAL && 'm' 477 default 'n' 478 help 479 This module may be useful to developers of SMBus client drivers, 480 especially for certain kinds of sensor chips. 481 482 If you do build this module, be sure to read the notes and warnings 483 in <file:Documentation/i2c/i2c-stub>. 484 485 If you don't know what to do here, definitely say N. 486 487config I2C_VERSATILE 488 tristate "ARM Versatile/Realview I2C bus support" 489 depends on I2C && (ARCH_VERSATILE || ARCH_REALVIEW) 490 select I2C_ALGOBIT 491 help 492 Say yes if you want to support the I2C serial bus on ARMs Versatile 493 range of platforms. 494 495 This driver can also be built as a module. If so, the module 496 will be called i2c-versatile. 497 498config I2C_ACORN 499 bool "Acorn IOC/IOMD I2C bus support" 500 depends on I2C && ARCH_ACORN 501 default y 502 select I2C_ALGOBIT 503 help 504 Say yes if you want to support the I2C bus on Acorn platforms. 505 506 If you don't know, say Y. 507 508config I2C_VIA 509 tristate "VIA 82C586B" 510 depends on I2C && PCI && EXPERIMENTAL 511 select I2C_ALGOBIT 512 help 513 If you say yes to this option, support will be included for the VIA 514 82C586B I2C interface 515 516 This driver can also be built as a module. If so, the module 517 will be called i2c-via. 518 519config I2C_VIAPRO 520 tristate "VIA VT82C596/82C686/82xx and CX700" 521 depends on I2C && PCI 522 help 523 If you say yes to this option, support will be included for the VIA 524 VT82C596 and later SMBus interface. Specifically, the following 525 chipsets are supported: 526 VT82C596A/B 527 VT82C686A/B 528 VT8231 529 VT8233/A 530 VT8235 531 VT8237R/A 532 VT8251 533 CX700 534 535 This driver can also be built as a module. If so, the module 536 will be called i2c-viapro. 537 538config I2C_VOODOO3 539 tristate "Voodoo 3" 540 depends on I2C && PCI 541 select I2C_ALGOBIT 542 help 543 If you say yes to this option, support will be included for the 544 Voodoo 3 I2C interface. 545 546 This driver can also be built as a module. If so, the module 547 will be called i2c-voodoo3. 548 549config I2C_PCA_ISA 550 tristate "PCA9564 on an ISA bus" 551 depends on I2C 552 select I2C_ALGOPCA 553 default n 554 help 555 This driver supports ISA boards using the Philips PCA 9564 556 Parallel bus to I2C bus controller 557 558 This driver can also be built as a module. If so, the module 559 will be called i2c-pca-isa. 560 561 This device is almost undetectable and using this driver on a 562 system which doesn't have this device will result in long 563 delays when I2C/SMBus chip drivers are loaded (e.g. at boot 564 time). If unsure, say N. 565 566config I2C_MV64XXX 567 tristate "Marvell mv64xxx I2C Controller" 568 depends on I2C && MV64X60 && EXPERIMENTAL 569 help 570 If you say yes to this option, support will be included for the 571 built-in I2C interface on the Marvell 64xxx line of host bridges. 572 573 This driver can also be built as a module. If so, the module 574 will be called i2c-mv64xxx. 575 576config I2C_PNX 577 tristate "I2C bus support for Philips PNX targets" 578 depends on ARCH_PNX4008 && I2C 579 help 580 This driver supports the Philips IP3204 I2C IP block master and/or 581 slave controller 582 583 This driver can also be built as a module. If so, the module 584 will be called i2c-pnx. 585 586endmenu 587