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