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