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