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