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/PCH)" 81 depends on PCI 82 select CHECK_SIGNATURE if X86 && DMI 83 help 84 If you say yes to this option, support will be included for the Intel 85 801 family of mainboard I2C interfaces. Specifically, the following 86 versions of the chipset are supported: 87 82801AA 88 82801AB 89 82801BA 90 82801CA/CAM 91 82801DB 92 82801EB/ER (ICH5/ICH5R) 93 6300ESB 94 ICH6 95 ICH7 96 ESB2 97 ICH8 98 ICH9 99 EP80579 (Tolapai) 100 ICH10 101 5/3400 Series (PCH) 102 6 Series (PCH) 103 Patsburg (PCH) 104 DH89xxCC (PCH) 105 Panther Point (PCH) 106 107 This driver can also be built as a module. If so, the module 108 will be called i2c-i801. 109 110config I2C_ISCH 111 tristate "Intel SCH SMBus 1.0" 112 depends on PCI 113 select LPC_SCH 114 help 115 Say Y here if you want to use SMBus controller on the Intel SCH 116 based systems. 117 118 This driver can also be built as a module. If so, the module 119 will be called i2c-isch. 120 121config I2C_PIIX4 122 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" 123 depends on PCI 124 help 125 If you say yes to this option, support will be included for the Intel 126 PIIX4 family of mainboard I2C interfaces. Specifically, the following 127 versions of the chipset are supported (note that Serverworks is part 128 of Broadcom): 129 Intel PIIX4 130 Intel 440MX 131 ATI IXP200 132 ATI IXP300 133 ATI IXP400 134 ATI SB600 135 ATI SB700 136 ATI SB800 137 AMD Hudson-2 138 Serverworks OSB4 139 Serverworks CSB5 140 Serverworks CSB6 141 Serverworks HT-1000 142 Serverworks HT-1100 143 SMSC Victory66 144 145 This driver can also be built as a module. If so, the module 146 will be called i2c-piix4. 147 148config I2C_NFORCE2 149 tristate "Nvidia nForce2, nForce3 and nForce4" 150 depends on PCI 151 help 152 If you say yes to this option, support will be included for the Nvidia 153 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. 154 155 This driver can also be built as a module. If so, the module 156 will be called i2c-nforce2. 157 158config I2C_NFORCE2_S4985 159 tristate "SMBus multiplexing on the Tyan S4985" 160 depends on I2C_NFORCE2 && X86 && EXPERIMENTAL 161 help 162 Enabling this option will add specific SMBus support for the Tyan 163 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed 164 over 4 different channels, where the various memory module EEPROMs 165 live. Saying yes here will give you access to these in addition 166 to the trunk. 167 168 This driver can also be built as a module. If so, the module 169 will be called i2c-nforce2-s4985. 170 171config I2C_SIS5595 172 tristate "SiS 5595" 173 depends on PCI 174 help 175 If you say yes to this option, support will be included for the 176 SiS5595 SMBus (a subset of I2C) interface. 177 178 This driver can also be built as a module. If so, the module 179 will be called i2c-sis5595. 180 181config I2C_SIS630 182 tristate "SiS 630/730" 183 depends on PCI 184 help 185 If you say yes to this option, support will be included for the 186 SiS630 and SiS730 SMBus (a subset of I2C) interface. 187 188 This driver can also be built as a module. If so, the module 189 will be called i2c-sis630. 190 191config I2C_SIS96X 192 tristate "SiS 96x" 193 depends on PCI 194 help 195 If you say yes to this option, support will be included for the SiS 196 96x SMBus (a subset of I2C) interfaces. Specifically, the following 197 chipsets are supported: 198 645/961 199 645DX/961 200 645DX/962 201 648/961 202 650/961 203 735 204 745 205 206 This driver can also be built as a module. If so, the module 207 will be called i2c-sis96x. 208 209config I2C_VIA 210 tristate "VIA VT82C586B" 211 depends on PCI && EXPERIMENTAL 212 select I2C_ALGOBIT 213 help 214 If you say yes to this option, support will be included for the VIA 215 82C586B I2C interface 216 217 This driver can also be built as a module. If so, the module 218 will be called i2c-via. 219 220config I2C_VIAPRO 221 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx" 222 depends on PCI 223 help 224 If you say yes to this option, support will be included for the VIA 225 VT82C596 and later SMBus interface. Specifically, the following 226 chipsets are supported: 227 VT82C596A/B 228 VT82C686A/B 229 VT8231 230 VT8233/A 231 VT8235 232 VT8237R/A/S 233 VT8251 234 CX700 235 VX800/VX820 236 VX855/VX875 237 238 This driver can also be built as a module. If so, the module 239 will be called i2c-viapro. 240 241if ACPI 242 243comment "ACPI drivers" 244 245config I2C_SCMI 246 tristate "SMBus Control Method Interface" 247 help 248 This driver supports the SMBus Control Method Interface. It needs the 249 BIOS to declare ACPI control methods as described in the SMBus Control 250 Method Interface specification. 251 252 To compile this driver as a module, choose M here: 253 the module will be called i2c-scmi. 254 255endif # ACPI 256 257comment "Mac SMBus host controller drivers" 258 depends on PPC_CHRP || PPC_PMAC 259 260config I2C_HYDRA 261 tristate "CHRP Apple Hydra Mac I/O I2C interface" 262 depends on PCI && PPC_CHRP && EXPERIMENTAL 263 select I2C_ALGOBIT 264 help 265 This supports the use of the I2C interface in the Apple Hydra Mac 266 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you 267 have such a machine. 268 269 This support is also available as a module. If so, the module 270 will be called i2c-hydra. 271 272config I2C_POWERMAC 273 tristate "Powermac I2C interface" 274 depends on PPC_PMAC 275 default y 276 help 277 This exposes the various PowerMac i2c interfaces to the linux i2c 278 layer and to userland. It is used by various drivers on the PowerMac 279 platform, and should generally be enabled. 280 281 This support is also available as a module. If so, the module 282 will be called i2c-powermac. 283 284comment "I2C system bus drivers (mostly embedded / system-on-chip)" 285 286config I2C_AT91 287 tristate "Atmel AT91 I2C Two-Wire interface (TWI)" 288 depends on ARCH_AT91 && EXPERIMENTAL && BROKEN 289 help 290 This supports the use of the I2C interface on Atmel AT91 291 processors. 292 293 This driver is BROKEN because the controller which it uses 294 will easily trigger RX overrun and TX underrun errors. Using 295 low I2C clock rates may partially work around those issues 296 on some systems. Another serious problem is that there is no 297 documented way to issue repeated START conditions, as needed 298 to support combined I2C messages. Use the i2c-gpio driver 299 unless your system can cope with those limitations. 300 301config I2C_AU1550 302 tristate "Au1550/Au1200 SMBus interface" 303 depends on MIPS_ALCHEMY 304 help 305 If you say yes to this option, support will be included for the 306 Au1550 and Au1200 SMBus interface. 307 308 This driver can also be built as a module. If so, the module 309 will be called i2c-au1550. 310 311config I2C_BLACKFIN_TWI 312 tristate "Blackfin TWI I2C support" 313 depends on BLACKFIN 314 depends on !BF561 && !BF531 && !BF532 && !BF533 315 help 316 This is the I2C bus driver for Blackfin on-chip TWI interface. 317 318 This driver can also be built as a module. If so, the module 319 will be called i2c-bfin-twi. 320 321config I2C_BLACKFIN_TWI_CLK_KHZ 322 int "Blackfin TWI I2C clock (kHz)" 323 depends on I2C_BLACKFIN_TWI 324 range 21 400 325 default 50 326 help 327 The unit of the TWI clock is kHz. 328 329config I2C_CPM 330 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" 331 depends on (CPM1 || CPM2) && OF_I2C 332 help 333 This supports the use of the I2C interface on Freescale 334 processors with CPM1 or CPM2. 335 336 This driver can also be built as a module. If so, the module 337 will be called i2c-cpm. 338 339config I2C_DAVINCI 340 tristate "DaVinci I2C driver" 341 depends on ARCH_DAVINCI 342 help 343 Support for TI DaVinci I2C controller driver. 344 345 This driver can also be built as a module. If so, the module 346 will be called i2c-davinci. 347 348 Please note that this driver might be needed to bring up other 349 devices such as DaVinci NIC. 350 For details please see http://www.ti.com/davinci 351 352config I2C_DESIGNWARE_PLATFORM 353 tristate "Synopsys DesignWare Platfrom" 354 depends on HAVE_CLK 355 help 356 If you say yes to this option, support will be included for the 357 Synopsys DesignWare I2C adapter. Only master mode is supported. 358 359 This driver can also be built as a module. If so, the module 360 will be called i2c-designware-platform. 361 362config I2C_DESIGNWARE_PCI 363 tristate "Synopsys DesignWare PCI" 364 depends on PCI 365 help 366 If you say yes to this option, support will be included for the 367 Synopsys DesignWare I2C adapter. Only master mode is supported. 368 369 This driver can also be built as a module. If so, the module 370 will be called i2c-designware-pci. 371 372config I2C_GPIO 373 tristate "GPIO-based bitbanging I2C" 374 depends on GENERIC_GPIO 375 select I2C_ALGOBIT 376 help 377 This is a very simple bitbanging I2C driver utilizing the 378 arch-neutral GPIO API to control the SCL and SDA lines. 379 380config I2C_HIGHLANDER 381 tristate "Highlander FPGA SMBus interface" 382 depends on SH_HIGHLANDER 383 help 384 If you say yes to this option, support will be included for 385 the SMBus interface located in the FPGA on various Highlander 386 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL 387 FPGAs. This is wholly unrelated to the SoC I2C. 388 389 This driver can also be built as a module. If so, the module 390 will be called i2c-highlander. 391 392config I2C_IBM_IIC 393 tristate "IBM PPC 4xx on-chip I2C interface" 394 depends on 4xx 395 help 396 Say Y here if you want to use IIC peripheral found on 397 embedded IBM PPC 4xx based systems. 398 399 This driver can also be built as a module. If so, the module 400 will be called i2c-ibm_iic. 401 402config I2C_IMX 403 tristate "IMX I2C interface" 404 depends on ARCH_MXC 405 help 406 Say Y here if you want to use the IIC bus controller on 407 the Freescale i.MX/MXC processors. 408 409 This driver can also be built as a module. If so, the module 410 will be called i2c-imx. 411 412config I2C_INTEL_MID 413 tristate "Intel Moorestown/Medfield Platform I2C controller" 414 depends on PCI 415 help 416 Say Y here if you have an Intel Moorestown/Medfield platform I2C 417 controller. 418 419 This support is also available as a module. If so, the module 420 will be called i2c-intel-mid. 421 422config I2C_IOP3XX 423 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" 424 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX 425 help 426 Say Y here if you want to use the IIC bus controller on 427 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. 428 429 This driver can also be built as a module. If so, the module 430 will be called i2c-iop3xx. 431 432config I2C_IXP2000 433 tristate "IXP2000 GPIO-Based I2C Interface (DEPRECATED)" 434 depends on ARCH_IXP2000 435 select I2C_ALGOBIT 436 help 437 Say Y here if you have an Intel IXP2000 (2400, 2800, 2850) based 438 system and are using GPIO lines for an I2C bus. 439 440 This support is also available as a module. If so, the module 441 will be called i2c-ixp2000. 442 443 This driver is deprecated and will be dropped soon. Use i2c-gpio 444 instead. 445 446config I2C_MPC 447 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" 448 depends on PPC 449 help 450 If you say yes to this option, support will be included for the 451 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, 452 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. 453 454 This driver can also be built as a module. If so, the module 455 will be called i2c-mpc. 456 457config I2C_MV64XXX 458 tristate "Marvell mv64xxx I2C Controller" 459 depends on (MV64X60 || PLAT_ORION) && EXPERIMENTAL 460 help 461 If you say yes to this option, support will be included for the 462 built-in I2C interface on the Marvell 64xxx line of host bridges. 463 464 This driver can also be built as a module. If so, the module 465 will be called i2c-mv64xxx. 466 467config I2C_MXS 468 tristate "Freescale i.MX28 I2C interface" 469 depends on SOC_IMX28 470 help 471 Say Y here if you want to use the I2C bus controller on 472 the Freescale i.MX28 processors. 473 474 This driver can also be built as a module. If so, the module 475 will be called i2c-mxs. 476 477config I2C_NOMADIK 478 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" 479 depends on PLAT_NOMADIK 480 help 481 If you say yes to this option, support will be included for the 482 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures. 483 484config I2C_NUC900 485 tristate "NUC900 I2C Driver" 486 depends on ARCH_W90X900 487 help 488 Say Y here to include support for I2C controller in the 489 Winbond/Nuvoton NUC900 based System-on-Chip devices. 490 491config I2C_OCORES 492 tristate "OpenCores I2C Controller" 493 depends on EXPERIMENTAL 494 help 495 If you say yes to this option, support will be included for the 496 OpenCores I2C controller. For details see 497 http://www.opencores.org/projects.cgi/web/i2c/overview 498 499 This driver can also be built as a module. If so, the module 500 will be called i2c-ocores. 501 502config I2C_OMAP 503 tristate "OMAP I2C adapter" 504 depends on ARCH_OMAP 505 default y if MACH_OMAP_H3 || MACH_OMAP_OSK 506 help 507 If you say yes to this option, support will be included for the 508 I2C interface on the Texas Instruments OMAP1/2 family of processors. 509 Like OMAP1510/1610/1710/5912 and OMAP242x. 510 For details see http://www.ti.com/omap. 511 512config I2C_PASEMI 513 tristate "PA Semi SMBus interface" 514 depends on PPC_PASEMI && PCI 515 help 516 Supports the PA Semi PWRficient on-chip SMBus interfaces. 517 518config I2C_PCA_PLATFORM 519 tristate "PCA9564/PCA9665 as platform device" 520 select I2C_ALGOPCA 521 default n 522 help 523 This driver supports a memory mapped Philips PCA9564/PCA9665 524 parallel bus to I2C bus controller. 525 526 This driver can also be built as a module. If so, the module 527 will be called i2c-pca-platform. 528 529config I2C_PMCMSP 530 tristate "PMC MSP I2C TWI Controller" 531 depends on PMC_MSP 532 help 533 This driver supports the PMC TWI controller on MSP devices. 534 535 This driver can also be built as module. If so, the module 536 will be called i2c-pmcmsp. 537 538config I2C_PNX 539 tristate "I2C bus support for Philips PNX and NXP LPC targets" 540 depends on ARCH_PNX4008 || ARCH_LPC32XX 541 help 542 This driver supports the Philips IP3204 I2C IP block master and/or 543 slave controller 544 545 This driver can also be built as a module. If so, the module 546 will be called i2c-pnx. 547 548config I2C_PUV3 549 tristate "PKUnity v3 I2C bus support" 550 depends on UNICORE32 && ARCH_PUV3 551 select I2C_ALGOBIT 552 help 553 This driver supports the I2C IP inside the PKUnity-v3 SoC. 554 This I2C bus controller is under AMBA/AXI bus. 555 556 This driver can also be built as a module. If so, the module 557 will be called i2c-puv3. 558 559config I2C_PXA 560 tristate "Intel PXA2XX I2C adapter" 561 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF) 562 help 563 If you have devices in the PXA I2C bus, say yes to this option. 564 This driver can also be built as a module. If so, the module 565 will be called i2c-pxa. 566 567config I2C_PXA_PCI 568 def_bool I2C_PXA && X86_32 && PCI && OF 569 570config I2C_PXA_SLAVE 571 bool "Intel PXA2XX I2C Slave comms support" 572 depends on I2C_PXA && !X86_32 573 help 574 Support I2C slave mode communications on the PXA I2C bus. This 575 is necessary for systems where the PXA may be a target on the 576 I2C bus. 577 578config HAVE_S3C2410_I2C 579 bool 580 help 581 This will include I2C support for Samsung SoCs. If you want to 582 include I2C support for any machine, kindly select this in the 583 respective Kconfig file. 584 585config I2C_S3C2410 586 tristate "S3C2410 I2C Driver" 587 depends on HAVE_S3C2410_I2C 588 help 589 Say Y here to include support for I2C controller in the 590 Samsung SoCs. 591 592config I2C_S6000 593 tristate "S6000 I2C support" 594 depends on XTENSA_VARIANT_S6000 595 help 596 This driver supports the on chip I2C device on the 597 S6000 xtensa processor family. 598 599 To compile this driver as a module, choose M here. The module 600 will be called i2c-s6000. 601 602config I2C_SH7760 603 tristate "Renesas SH7760 I2C Controller" 604 depends on CPU_SUBTYPE_SH7760 605 help 606 This driver supports the 2 I2C interfaces on the Renesas SH7760. 607 608 This driver can also be built as a module. If so, the module 609 will be called i2c-sh7760. 610 611config I2C_SH_MOBILE 612 tristate "SuperH Mobile I2C Controller" 613 depends on SUPERH || ARCH_SHMOBILE 614 help 615 If you say yes to this option, support will be included for the 616 built-in I2C interface on the Renesas SH-Mobile processor. 617 618 This driver can also be built as a module. If so, the module 619 will be called i2c-sh_mobile. 620 621config I2C_SIMTEC 622 tristate "Simtec Generic I2C interface" 623 select I2C_ALGOBIT 624 help 625 If you say yes to this option, support will be included for 626 the Simtec Generic I2C interface. This driver is for the 627 simple I2C bus used on newer Simtec products for general 628 I2C, such as DDC on the Simtec BBD2016A. 629 630 This driver can also be built as a module. If so, the module 631 will be called i2c-simtec. 632 633config I2C_STU300 634 tristate "ST Microelectronics DDC I2C interface" 635 depends on MACH_U300 636 default y if MACH_U300 637 help 638 If you say yes to this option, support will be included for the 639 I2C interface from ST Microelectronics simply called "DDC I2C" 640 supporting both I2C and DDC, used in e.g. the U300 series 641 mobile platforms. 642 643 This driver can also be built as a module. If so, the module 644 will be called i2c-stu300. 645 646config I2C_TEGRA 647 tristate "NVIDIA Tegra internal I2C controller" 648 depends on ARCH_TEGRA 649 help 650 If you say yes to this option, support will be included for the 651 I2C controller embedded in NVIDIA Tegra SOCs 652 653config I2C_VERSATILE 654 tristate "ARM Versatile/Realview I2C bus support" 655 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS 656 select I2C_ALGOBIT 657 help 658 Say yes if you want to support the I2C serial bus on ARMs Versatile 659 range of platforms. 660 661 This driver can also be built as a module. If so, the module 662 will be called i2c-versatile. 663 664config I2C_OCTEON 665 tristate "Cavium OCTEON I2C bus support" 666 depends on CPU_CAVIUM_OCTEON 667 help 668 Say yes if you want to support the I2C serial bus on Cavium 669 OCTEON SOC. 670 671 This driver can also be built as a module. If so, the module 672 will be called i2c-octeon. 673 674config I2C_XILINX 675 tristate "Xilinx I2C Controller" 676 depends on EXPERIMENTAL && HAS_IOMEM 677 help 678 If you say yes to this option, support will be included for the 679 Xilinx I2C controller. 680 681 This driver can also be built as a module. If so, the module 682 will be called xilinx_i2c. 683 684config I2C_EG20T 685 tristate "Intel EG20T PCH / OKI SEMICONDUCTOR IOH(ML7213/ML7223)" 686 depends on PCI 687 help 688 This driver is for PCH(Platform controller Hub) I2C of EG20T which 689 is an IOH(Input/Output Hub) for x86 embedded processor. 690 This driver can access PCH I2C bus device. 691 692 This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ 693 Output Hub), ML7213 and ML7223. 694 ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is 695 for MP(Media Phone) use. 696 ML7213/ML7223 is companion chip for Intel Atom E6xx series. 697 ML7213/ML7223 is completely compatible for Intel EG20T PCH. 698 699comment "External I2C/SMBus adapter drivers" 700 701config I2C_DIOLAN_U2C 702 tristate "Diolan U2C-12 USB adapter" 703 depends on USB 704 help 705 If you say yes to this option, support will be included for Diolan 706 U2C-12, a USB to I2C interface. 707 708 This driver can also be built as a module. If so, the module 709 will be called i2c-diolan-u2c. 710 711config I2C_PARPORT 712 tristate "Parallel port adapter" 713 depends on PARPORT 714 select I2C_ALGOBIT 715 select I2C_SMBUS 716 help 717 This supports parallel port I2C adapters such as the ones made by 718 Philips or Velleman, Analog Devices evaluation boards, and more. 719 Basically any adapter using the parallel port as an I2C bus with 720 no extra chipset is supported by this driver, or could be. 721 722 This driver is a replacement for (and was inspired by) an older 723 driver named i2c-philips-par. The new driver supports more devices, 724 and makes it easier to add support for new devices. 725 726 An adapter type parameter is now mandatory. Please read the file 727 Documentation/i2c/busses/i2c-parport for details. 728 729 Another driver exists, named i2c-parport-light, which doesn't depend 730 on the parport driver. This is meant for embedded systems. Don't say 731 Y here if you intend to say Y or M there. 732 733 This support is also available as a module. If so, the module 734 will be called i2c-parport. 735 736config I2C_PARPORT_LIGHT 737 tristate "Parallel port adapter (light)" 738 select I2C_ALGOBIT 739 select I2C_SMBUS 740 help 741 This supports parallel port I2C adapters such as the ones made by 742 Philips or Velleman, Analog Devices evaluation boards, and more. 743 Basically any adapter using the parallel port as an I2C bus with 744 no extra chipset is supported by this driver, or could be. 745 746 This driver is a light version of i2c-parport. It doesn't depend 747 on the parport driver, and uses direct I/O access instead. This 748 might be preferred on embedded systems where wasting memory for 749 the clean but heavy parport handling is not an option. The 750 drawback is a reduced portability and the impossibility to 751 daisy-chain other parallel port devices. 752 753 Don't say Y here if you said Y or M to i2c-parport. Saying M to 754 both is possible but both modules should not be loaded at the same 755 time. 756 757 This support is also available as a module. If so, the module 758 will be called i2c-parport-light. 759 760config I2C_TAOS_EVM 761 tristate "TAOS evaluation module" 762 depends on EXPERIMENTAL 763 select SERIO 764 select SERIO_SERPORT 765 default n 766 help 767 This supports TAOS evaluation modules on serial port. In order to 768 use this driver, you will need the inputattach tool, which is part 769 of the input-utils package. 770 771 If unsure, say N. 772 773 This support is also available as a module. If so, the module 774 will be called i2c-taos-evm. 775 776config I2C_TINY_USB 777 tristate "Tiny-USB adapter" 778 depends on USB 779 help 780 If you say yes to this option, support will be included for the 781 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See 782 http://www.harbaum.org/till/i2c_tiny_usb for hardware details. 783 784 This driver can also be built as a module. If so, the module 785 will be called i2c-tiny-usb. 786 787comment "Other I2C/SMBus bus drivers" 788 789config I2C_ACORN 790 tristate "Acorn IOC/IOMD I2C bus support" 791 depends on ARCH_ACORN 792 default y 793 select I2C_ALGOBIT 794 help 795 Say yes if you want to support the I2C bus on Acorn platforms. 796 797 If you don't know, say Y. 798 799config I2C_ELEKTOR 800 tristate "Elektor ISA card" 801 depends on ISA && HAS_IOPORT && BROKEN_ON_SMP 802 select I2C_ALGOPCF 803 help 804 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own 805 such an adapter. 806 807 This support is also available as a module. If so, the module 808 will be called i2c-elektor. 809 810config I2C_PCA_ISA 811 tristate "PCA9564/PCA9665 on an ISA bus" 812 depends on ISA 813 select I2C_ALGOPCA 814 default n 815 help 816 This driver supports ISA boards using the Philips PCA9564/PCA9665 817 parallel bus to I2C bus controller. 818 819 This driver can also be built as a module. If so, the module 820 will be called i2c-pca-isa. 821 822 This device is almost undetectable and using this driver on a 823 system which doesn't have this device will result in long 824 delays when I2C/SMBus chip drivers are loaded (e.g. at boot 825 time). If unsure, say N. 826 827config I2C_SIBYTE 828 tristate "SiByte SMBus interface" 829 depends on SIBYTE_SB1xxx_SOC 830 help 831 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 832 833config I2C_STUB 834 tristate "I2C/SMBus Test Stub" 835 depends on EXPERIMENTAL && m 836 default 'n' 837 help 838 This module may be useful to developers of SMBus client drivers, 839 especially for certain kinds of sensor chips. 840 841 If you do build this module, be sure to read the notes and warnings 842 in <file:Documentation/i2c/i2c-stub>. 843 844 If you don't know what to do here, definitely say N. 845 846config SCx200_I2C 847 tristate "NatSemi SCx200 I2C using GPIO pins (DEPRECATED)" 848 depends on SCx200_GPIO 849 select I2C_ALGOBIT 850 help 851 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus. 852 853 If you don't know what to do here, say N. 854 855 This support is also available as a module. If so, the module 856 will be called scx200_i2c. 857 858 This driver is deprecated and will be dropped soon. Use i2c-gpio 859 (or scx200_acb) instead. 860 861config SCx200_I2C_SCL 862 int "GPIO pin used for SCL" 863 depends on SCx200_I2C 864 default "12" 865 help 866 Enter the GPIO pin number used for the SCL signal. This value can 867 also be specified with a module parameter. 868 869config SCx200_I2C_SDA 870 int "GPIO pin used for SDA" 871 depends on SCx200_I2C 872 default "13" 873 help 874 Enter the GPIO pin number used for the SSA signal. This value can 875 also be specified with a module parameter. 876 877config SCx200_ACB 878 tristate "Geode ACCESS.bus support" 879 depends on X86_32 && PCI 880 help 881 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and 882 SC1100 processors and the CS5535 and CS5536 Geode companion devices. 883 884 If you don't know what to do here, say N. 885 886 This support is also available as a module. If so, the module 887 will be called scx200_acb. 888 889endmenu 890