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