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 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 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_HIX5HD2 81 tristate "Hix5hd2 high-speed I2C driver" 82 depends on ARCH_HIX5HD2 83 help 84 Say Y here to include support for high-speed I2C controller in the 85 Hisilicon based hix5hd2 SoCs. 86 87 This driver can also be built as a module. If so, the module 88 will be called i2c-hix5hd2. 89 90config I2C_I801 91 tristate "Intel 82801 (ICH/PCH)" 92 depends on PCI 93 select CHECK_SIGNATURE if X86 && DMI 94 help 95 If you say yes to this option, support will be included for the Intel 96 801 family of mainboard I2C interfaces. Specifically, the following 97 versions of the chipset are supported: 98 82801AA 99 82801AB 100 82801BA 101 82801CA/CAM 102 82801DB 103 82801EB/ER (ICH5/ICH5R) 104 6300ESB 105 ICH6 106 ICH7 107 ESB2 108 ICH8 109 ICH9 110 EP80579 (Tolapai) 111 ICH10 112 5/3400 Series (PCH) 113 6 Series (PCH) 114 Patsburg (PCH) 115 DH89xxCC (PCH) 116 Panther Point (PCH) 117 Lynx Point (PCH) 118 Lynx Point-LP (PCH) 119 Avoton (SOC) 120 Wellsburg (PCH) 121 Coleto Creek (PCH) 122 Wildcat Point (PCH) 123 Wildcat Point-LP (PCH) 124 BayTrail (SOC) 125 Sunrise Point-H (PCH) 126 Sunrise Point-LP (PCH) 127 128 This driver can also be built as a module. If so, the module 129 will be called i2c-i801. 130 131config I2C_ISCH 132 tristate "Intel SCH SMBus 1.0" 133 depends on PCI 134 select LPC_SCH 135 help 136 Say Y here if you want to use SMBus controller on the Intel SCH 137 based systems. 138 139 This driver can also be built as a module. If so, the module 140 will be called i2c-isch. 141 142config I2C_ISMT 143 tristate "Intel iSMT SMBus Controller" 144 depends on PCI && X86 145 help 146 If you say yes to this option, support will be included for the Intel 147 iSMT SMBus host controller interface. 148 149 This driver can also be built as a module. If so, the module will be 150 called i2c-ismt. 151 152config I2C_PIIX4 153 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" 154 depends on PCI 155 help 156 If you say yes to this option, support will be included for the Intel 157 PIIX4 family of mainboard I2C interfaces. Specifically, the following 158 versions of the chipset are supported (note that Serverworks is part 159 of Broadcom): 160 Intel PIIX4 161 Intel 440MX 162 ATI IXP200 163 ATI IXP300 164 ATI IXP400 165 ATI SB600 166 ATI SB700/SP5100 167 ATI SB800 168 AMD Hudson-2 169 AMD ML 170 AMD CZ 171 Serverworks OSB4 172 Serverworks CSB5 173 Serverworks CSB6 174 Serverworks HT-1000 175 Serverworks HT-1100 176 SMSC Victory66 177 178 Some AMD chipsets contain two PIIX4-compatible SMBus 179 controllers. This driver will attempt to use both controllers 180 on the SB700/SP5100, if they have been initialized by the BIOS. 181 182 This driver can also be built as a module. If so, the module 183 will be called i2c-piix4. 184 185config I2C_NFORCE2 186 tristate "Nvidia nForce2, nForce3 and nForce4" 187 depends on PCI 188 help 189 If you say yes to this option, support will be included for the Nvidia 190 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. 191 192 This driver can also be built as a module. If so, the module 193 will be called i2c-nforce2. 194 195config I2C_NFORCE2_S4985 196 tristate "SMBus multiplexing on the Tyan S4985" 197 depends on I2C_NFORCE2 && X86 198 help 199 Enabling this option will add specific SMBus support for the Tyan 200 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed 201 over 4 different channels, where the various memory module EEPROMs 202 live. Saying yes here will give you access to these in addition 203 to the trunk. 204 205 This driver can also be built as a module. If so, the module 206 will be called i2c-nforce2-s4985. 207 208config I2C_SIS5595 209 tristate "SiS 5595" 210 depends on PCI 211 help 212 If you say yes to this option, support will be included for the 213 SiS5595 SMBus (a subset of I2C) interface. 214 215 This driver can also be built as a module. If so, the module 216 will be called i2c-sis5595. 217 218config I2C_SIS630 219 tristate "SiS 630/730/964" 220 depends on PCI 221 help 222 If you say yes to this option, support will be included for the 223 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface. 224 225 This driver can also be built as a module. If so, the module 226 will be called i2c-sis630. 227 228config I2C_SIS96X 229 tristate "SiS 96x" 230 depends on PCI 231 help 232 If you say yes to this option, support will be included for the SiS 233 96x SMBus (a subset of I2C) interfaces. Specifically, the following 234 chipsets are supported: 235 645/961 236 645DX/961 237 645DX/962 238 648/961 239 650/961 240 735 241 745 242 243 This driver can also be built as a module. If so, the module 244 will be called i2c-sis96x. 245 246config I2C_VIA 247 tristate "VIA VT82C586B" 248 depends on PCI 249 select I2C_ALGOBIT 250 help 251 If you say yes to this option, support will be included for the VIA 252 82C586B I2C interface 253 254 This driver can also be built as a module. If so, the module 255 will be called i2c-via. 256 257config I2C_VIAPRO 258 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900" 259 depends on PCI 260 help 261 If you say yes to this option, support will be included for the VIA 262 VT82C596 and later SMBus interface. Specifically, the following 263 chipsets are supported: 264 VT82C596A/B 265 VT82C686A/B 266 VT8231 267 VT8233/A 268 VT8235 269 VT8237R/A/S 270 VT8251 271 CX700 272 VX800/VX820 273 VX855/VX875 274 VX900 275 276 This driver can also be built as a module. If so, the module 277 will be called i2c-viapro. 278 279if ACPI 280 281comment "ACPI drivers" 282 283config I2C_SCMI 284 tristate "SMBus Control Method Interface" 285 help 286 This driver supports the SMBus Control Method Interface. It needs the 287 BIOS to declare ACPI control methods as described in the SMBus Control 288 Method Interface specification. 289 290 To compile this driver as a module, choose M here: 291 the module will be called i2c-scmi. 292 293endif # ACPI 294 295comment "Mac SMBus host controller drivers" 296 depends on PPC_CHRP || PPC_PMAC 297 298config I2C_HYDRA 299 tristate "CHRP Apple Hydra Mac I/O I2C interface" 300 depends on PCI && PPC_CHRP 301 select I2C_ALGOBIT 302 help 303 This supports the use of the I2C interface in the Apple Hydra Mac 304 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you 305 have such a machine. 306 307 This support is also available as a module. If so, the module 308 will be called i2c-hydra. 309 310config I2C_POWERMAC 311 tristate "Powermac I2C interface" 312 depends on PPC_PMAC 313 default y 314 help 315 This exposes the various PowerMac i2c interfaces to the linux i2c 316 layer and to userland. It is used by various drivers on the PowerMac 317 platform, and should generally be enabled. 318 319 This support is also available as a module. If so, the module 320 will be called i2c-powermac. 321 322comment "I2C system bus drivers (mostly embedded / system-on-chip)" 323 324config I2C_AT91 325 tristate "Atmel AT91 I2C Two-Wire interface (TWI)" 326 depends on ARCH_AT91 327 help 328 This supports the use of the I2C interface on Atmel AT91 329 processors. 330 331 A serious problem is that there is no documented way to issue 332 repeated START conditions for more than two messages, as needed 333 to support combined I2C messages. Use the i2c-gpio driver 334 unless your system can cope with this limitation. 335 336 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices 337 don't have clock stretching in transmission mode. For that reason, 338 you can encounter underrun issues causing premature stop sendings if 339 the latency to fill the transmission register is too long. If you 340 are facing this situation, use the i2c-gpio driver. 341 342config I2C_AU1550 343 tristate "Au1550/Au1200/Au1300 SMBus interface" 344 depends on MIPS_ALCHEMY 345 help 346 If you say yes to this option, support will be included for the 347 Au1550/Au1200/Au1300 SMBus interface. 348 349 This driver can also be built as a module. If so, the module 350 will be called i2c-au1550. 351 352config I2C_AXXIA 353 tristate "Axxia I2C controller" 354 depends on ARCH_AXXIA || COMPILE_TEST 355 default ARCH_AXXIA 356 help 357 Say yes if you want to support the I2C bus on Axxia platforms. 358 359 Please note that this controller is limited to transfers of maximum 360 255 bytes in length. Any attempt to to a larger transfer will return 361 an error. 362 363config I2C_BCM2835 364 tristate "Broadcom BCM2835 I2C controller" 365 depends on ARCH_BCM2835 366 help 367 If you say yes to this option, support will be included for the 368 BCM2835 I2C controller. 369 370 If you don't know what to do here, say N. 371 372 This support is also available as a module. If so, the module 373 will be called i2c-bcm2835. 374 375config I2C_BCM_KONA 376 tristate "BCM Kona I2C adapter" 377 depends on ARCH_BCM_MOBILE 378 default y 379 help 380 If you say yes to this option, support will be included for the 381 I2C interface on the Broadcom Kona family of processors. 382 383 If you do not need KONA I2C interface, say N. 384 385config I2C_BLACKFIN_TWI 386 tristate "Blackfin TWI I2C support" 387 depends on BLACKFIN 388 depends on !BF561 && !BF531 && !BF532 && !BF533 389 help 390 This is the I2C bus driver for Blackfin on-chip TWI interface. 391 392 This driver can also be built as a module. If so, the module 393 will be called i2c-bfin-twi. 394 395config I2C_BLACKFIN_TWI_CLK_KHZ 396 int "Blackfin TWI I2C clock (kHz)" 397 depends on I2C_BLACKFIN_TWI 398 range 21 400 399 default 50 400 help 401 The unit of the TWI clock is kHz. 402 403config I2C_CADENCE 404 tristate "Cadence I2C Controller" 405 depends on ARCH_ZYNQ 406 help 407 Say yes here to select Cadence I2C Host Controller. This controller is 408 e.g. used by Xilinx Zynq. 409 410config I2C_CBUS_GPIO 411 tristate "CBUS I2C driver" 412 depends on GPIOLIB 413 help 414 Support for CBUS access using I2C API. Mostly relevant for Nokia 415 Internet Tablets (770, N800 and N810). 416 417 This driver can also be built as a module. If so, the module 418 will be called i2c-cbus-gpio. 419 420config I2C_CPM 421 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" 422 depends on CPM1 || CPM2 423 help 424 This supports the use of the I2C interface on Freescale 425 processors with CPM1 or CPM2. 426 427 This driver can also be built as a module. If so, the module 428 will be called i2c-cpm. 429 430config I2C_DAVINCI 431 tristate "DaVinci I2C driver" 432 depends on ARCH_DAVINCI || ARCH_KEYSTONE 433 help 434 Support for TI DaVinci I2C controller driver. 435 436 This driver can also be built as a module. If so, the module 437 will be called i2c-davinci. 438 439 Please note that this driver might be needed to bring up other 440 devices such as DaVinci NIC. 441 For details please see http://www.ti.com/davinci 442 443config I2C_DESIGNWARE_CORE 444 tristate 445 446config I2C_DESIGNWARE_PLATFORM 447 tristate "Synopsys DesignWare Platform" 448 select I2C_DESIGNWARE_CORE 449 depends on (ACPI && COMMON_CLK) || !ACPI 450 help 451 If you say yes to this option, support will be included for the 452 Synopsys DesignWare I2C adapter. Only master mode is supported. 453 454 This driver can also be built as a module. If so, the module 455 will be called i2c-designware-platform. 456 457config I2C_DESIGNWARE_PCI 458 tristate "Synopsys DesignWare PCI" 459 depends on PCI 460 select I2C_DESIGNWARE_CORE 461 help 462 If you say yes to this option, support will be included for the 463 Synopsys DesignWare I2C adapter. Only master mode is supported. 464 465 This driver can also be built as a module. If so, the module 466 will be called i2c-designware-pci. 467 468config I2C_EFM32 469 tristate "EFM32 I2C controller" 470 depends on ARCH_EFM32 || COMPILE_TEST 471 help 472 This driver supports the i2c block found in Energy Micro's EFM32 473 SoCs. 474 475config I2C_EG20T 476 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" 477 depends on PCI && (X86_32 || COMPILE_TEST) 478 help 479 This driver is for PCH(Platform controller Hub) I2C of EG20T which 480 is an IOH(Input/Output Hub) for x86 embedded processor. 481 This driver can access PCH I2C bus device. 482 483 This driver also can be used for LAPIS Semiconductor IOH(Input/ 484 Output Hub), ML7213, ML7223 and ML7831. 485 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is 486 for MP(Media Phone) use and ML7831 IOH is for general purpose use. 487 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 488 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 489 490config I2C_EXYNOS5 491 tristate "Exynos5 high-speed I2C driver" 492 depends on ARCH_EXYNOS && OF 493 default y 494 help 495 High-speed I2C controller on Exynos5 based Samsung SoCs. 496 497config I2C_GPIO 498 tristate "GPIO-based bitbanging I2C" 499 depends on GPIOLIB 500 select I2C_ALGOBIT 501 help 502 This is a very simple bitbanging I2C driver utilizing the 503 arch-neutral GPIO API to control the SCL and SDA lines. 504 505config I2C_HIGHLANDER 506 tristate "Highlander FPGA SMBus interface" 507 depends on SH_HIGHLANDER 508 help 509 If you say yes to this option, support will be included for 510 the SMBus interface located in the FPGA on various Highlander 511 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL 512 FPGAs. This is wholly unrelated to the SoC I2C. 513 514 This driver can also be built as a module. If so, the module 515 will be called i2c-highlander. 516 517config I2C_IBM_IIC 518 tristate "IBM PPC 4xx on-chip I2C interface" 519 depends on 4xx 520 help 521 Say Y here if you want to use IIC peripheral found on 522 embedded IBM PPC 4xx based systems. 523 524 This driver can also be built as a module. If so, the module 525 will be called i2c-ibm_iic. 526 527config I2C_IMG 528 tristate "Imagination Technologies I2C SCB Controller" 529 depends on SOC_TZ1090 || COMPILE_TEST 530 help 531 Say Y here if you want to use the IMG I2C SCB controller, 532 available on the TZ1090 SoC. 533 534 This driver can also be built as a module. If so, the module 535 will be called i2c-img-scb. 536 537config I2C_IMX 538 tristate "IMX I2C interface" 539 depends on ARCH_MXC 540 help 541 Say Y here if you want to use the IIC bus controller on 542 the Freescale i.MX/MXC processors. 543 544 This driver can also be built as a module. If so, the module 545 will be called i2c-imx. 546 547config I2C_IOP3XX 548 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" 549 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX 550 help 551 Say Y here if you want to use the IIC bus controller on 552 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. 553 554 This driver can also be built as a module. If so, the module 555 will be called i2c-iop3xx. 556 557config I2C_KEMPLD 558 tristate "Kontron COM I2C Controller" 559 depends on MFD_KEMPLD 560 help 561 This enables support for the I2C bus interface on some Kontron ETX 562 and COMexpress (ETXexpress) modules. 563 564 This driver can also be built as a module. If so, the module 565 will be called i2c-kempld. 566 567config I2C_MESON 568 tristate "Amlogic Meson I2C controller" 569 depends on ARCH_MESON 570 help 571 If you say yes to this option, support will be included for the 572 I2C interface on the Amlogic Meson family of SoCs. 573 574config I2C_MPC 575 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" 576 depends on PPC 577 help 578 If you say yes to this option, support will be included for the 579 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, 580 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. 581 582 This driver can also be built as a module. If so, the module 583 will be called i2c-mpc. 584 585config I2C_MV64XXX 586 tristate "Marvell mv64xxx I2C Controller" 587 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI 588 help 589 If you say yes to this option, support will be included for the 590 built-in I2C interface on the Marvell 64xxx line of host bridges. 591 This driver is also used for Allwinner SoCs I2C controllers. 592 593 This driver can also be built as a module. If so, the module 594 will be called i2c-mv64xxx. 595 596config I2C_MXS 597 tristate "Freescale i.MX28 I2C interface" 598 depends on SOC_IMX28 599 select STMP_DEVICE 600 help 601 Say Y here if you want to use the I2C bus controller on 602 the Freescale i.MX28 processors. 603 604 This driver can also be built as a module. If so, the module 605 will be called i2c-mxs. 606 607config I2C_NOMADIK 608 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" 609 depends on ARM_AMBA 610 help 611 If you say yes to this option, support will be included for the 612 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures, 613 as well as the STA2X11 PCIe I/O HUB. 614 615config I2C_OCORES 616 tristate "OpenCores I2C Controller" 617 help 618 If you say yes to this option, support will be included for the 619 OpenCores I2C controller. For details see 620 http://www.opencores.org/projects.cgi/web/i2c/overview 621 622 This driver can also be built as a module. If so, the module 623 will be called i2c-ocores. 624 625config I2C_OMAP 626 tristate "OMAP I2C adapter" 627 depends on ARCH_OMAP 628 default y if MACH_OMAP_H3 || MACH_OMAP_OSK 629 help 630 If you say yes to this option, support will be included for the 631 I2C interface on the Texas Instruments OMAP1/2 family of processors. 632 Like OMAP1510/1610/1710/5912 and OMAP242x. 633 For details see http://www.ti.com/omap. 634 635config I2C_PASEMI 636 tristate "PA Semi SMBus interface" 637 depends on PPC_PASEMI && PCI 638 help 639 Supports the PA Semi PWRficient on-chip SMBus interfaces. 640 641config I2C_PCA_PLATFORM 642 tristate "PCA9564/PCA9665 as platform device" 643 select I2C_ALGOPCA 644 default n 645 help 646 This driver supports a memory mapped Philips PCA9564/PCA9665 647 parallel bus to I2C bus controller. 648 649 This driver can also be built as a module. If so, the module 650 will be called i2c-pca-platform. 651 652config I2C_PMCMSP 653 tristate "PMC MSP I2C TWI Controller" 654 depends on PMC_MSP 655 help 656 This driver supports the PMC TWI controller on MSP devices. 657 658 This driver can also be built as module. If so, the module 659 will be called i2c-pmcmsp. 660 661config I2C_PNX 662 tristate "I2C bus support for Philips PNX and NXP LPC targets" 663 depends on ARCH_LPC32XX 664 help 665 This driver supports the Philips IP3204 I2C IP block master and/or 666 slave controller 667 668 This driver can also be built as a module. If so, the module 669 will be called i2c-pnx. 670 671config I2C_PUV3 672 tristate "PKUnity v3 I2C bus support" 673 depends on UNICORE32 && ARCH_PUV3 674 select I2C_ALGOBIT 675 help 676 This driver supports the I2C IP inside the PKUnity-v3 SoC. 677 This I2C bus controller is under AMBA/AXI bus. 678 679 This driver can also be built as a module. If so, the module 680 will be called i2c-puv3. 681 682config I2C_PXA 683 tristate "Intel PXA2XX I2C adapter" 684 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF) 685 help 686 If you have devices in the PXA I2C bus, say yes to this option. 687 This driver can also be built as a module. If so, the module 688 will be called i2c-pxa. 689 690config I2C_PXA_PCI 691 def_bool I2C_PXA && X86_32 && PCI && OF 692 693config I2C_PXA_SLAVE 694 bool "Intel PXA2XX I2C Slave comms support" 695 depends on I2C_PXA && !X86_32 696 help 697 Support I2C slave mode communications on the PXA I2C bus. This 698 is necessary for systems where the PXA may be a target on the 699 I2C bus. 700 701config I2C_QUP 702 tristate "Qualcomm QUP based I2C controller" 703 depends on ARCH_QCOM 704 help 705 If you say yes to this option, support will be included for the 706 built-in I2C interface on the Qualcomm SoCs. 707 708 This driver can also be built as a module. If so, the module 709 will be called i2c-qup. 710 711config I2C_RIIC 712 tristate "Renesas RIIC adapter" 713 depends on ARCH_SHMOBILE || COMPILE_TEST 714 help 715 If you say yes to this option, support will be included for the 716 Renesas RIIC I2C interface. 717 718 This driver can also be built as a module. If so, the module 719 will be called i2c-riic. 720 721config I2C_RK3X 722 tristate "Rockchip RK3xxx I2C adapter" 723 depends on OF 724 help 725 Say Y here to include support for the I2C adapter in Rockchip RK3xxx 726 SoCs. 727 728 This driver can also be built as a module. If so, the module will 729 be called i2c-rk3x. 730 731config HAVE_S3C2410_I2C 732 bool 733 help 734 This will include I2C support for Samsung SoCs. If you want to 735 include I2C support for any machine, kindly select this in the 736 respective Kconfig file. 737 738config I2C_S3C2410 739 tristate "S3C2410 I2C Driver" 740 depends on HAVE_S3C2410_I2C 741 help 742 Say Y here to include support for I2C controller in the 743 Samsung SoCs. 744 745config I2C_SH7760 746 tristate "Renesas SH7760 I2C Controller" 747 depends on CPU_SUBTYPE_SH7760 748 help 749 This driver supports the 2 I2C interfaces on the Renesas SH7760. 750 751 This driver can also be built as a module. If so, the module 752 will be called i2c-sh7760. 753 754config I2C_SH_MOBILE 755 tristate "SuperH Mobile I2C Controller" 756 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST 757 help 758 If you say yes to this option, support will be included for the 759 built-in I2C interface on the Renesas SH-Mobile processor. 760 761 This driver can also be built as a module. If so, the module 762 will be called i2c-sh_mobile. 763 764config I2C_SIMTEC 765 tristate "Simtec Generic I2C interface" 766 select I2C_ALGOBIT 767 help 768 If you say yes to this option, support will be included for 769 the Simtec Generic I2C interface. This driver is for the 770 simple I2C bus used on newer Simtec products for general 771 I2C, such as DDC on the Simtec BBD2016A. 772 773 This driver can also be built as a module. If so, the module 774 will be called i2c-simtec. 775 776config I2C_SIRF 777 tristate "CSR SiRFprimaII I2C interface" 778 depends on ARCH_SIRF 779 help 780 If you say yes to this option, support will be included for the 781 CSR SiRFprimaII I2C interface. 782 783 This driver can also be built as a module. If so, the module 784 will be called i2c-sirf. 785 786config I2C_ST 787 tristate "STMicroelectronics SSC I2C support" 788 depends on ARCH_STI 789 help 790 Enable this option to add support for STMicroelectronics SoCs 791 hardware SSC (Synchronous Serial Controller) as an I2C controller. 792 793 This driver can also be built as module. If so, the module 794 will be called i2c-st. 795 796config I2C_STU300 797 tristate "ST Microelectronics DDC I2C interface" 798 depends on MACH_U300 799 default y if MACH_U300 800 help 801 If you say yes to this option, support will be included for the 802 I2C interface from ST Microelectronics simply called "DDC I2C" 803 supporting both I2C and DDC, used in e.g. the U300 series 804 mobile platforms. 805 806 This driver can also be built as a module. If so, the module 807 will be called i2c-stu300. 808 809config I2C_SUN6I_P2WI 810 tristate "Allwinner sun6i internal P2WI controller" 811 depends on RESET_CONTROLLER 812 depends on MACH_SUN6I || COMPILE_TEST 813 help 814 If you say yes to this option, support will be included for the 815 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi 816 SOCs. 817 The P2WI looks like an SMBus controller (which supports only byte 818 accesses), except that it only supports one slave device. 819 This interface is used to connect to specific PMIC devices (like the 820 AXP221). 821 822config I2C_TEGRA 823 tristate "NVIDIA Tegra internal I2C controller" 824 depends on ARCH_TEGRA 825 help 826 If you say yes to this option, support will be included for the 827 I2C controller embedded in NVIDIA Tegra SOCs 828 829config I2C_VERSATILE 830 tristate "ARM Versatile/Realview I2C bus support" 831 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS 832 select I2C_ALGOBIT 833 help 834 Say yes if you want to support the I2C serial bus on ARMs Versatile 835 range of platforms. 836 837 This driver can also be built as a module. If so, the module 838 will be called i2c-versatile. 839 840config I2C_WMT 841 tristate "Wondermedia WM8xxx SoC I2C bus support" 842 depends on ARCH_VT8500 843 help 844 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series 845 SoCs. 846 847 This driver can also be built as a module. If so, the module will be 848 called i2c-wmt. 849 850config I2C_OCTEON 851 tristate "Cavium OCTEON I2C bus support" 852 depends on CAVIUM_OCTEON_SOC 853 help 854 Say yes if you want to support the I2C serial bus on Cavium 855 OCTEON SOC. 856 857 This driver can also be built as a module. If so, the module 858 will be called i2c-octeon. 859 860config I2C_XILINX 861 tristate "Xilinx I2C Controller" 862 depends on HAS_IOMEM 863 help 864 If you say yes to this option, support will be included for the 865 Xilinx I2C controller. 866 867 This driver can also be built as a module. If so, the module 868 will be called xilinx_i2c. 869 870config I2C_XLR 871 tristate "XLR I2C support" 872 depends on CPU_XLR 873 help 874 This driver enables support for the on-chip I2C interface of 875 the Netlogic XLR/XLS MIPS processors. 876 877 This driver can also be built as a module. If so, the module 878 will be called i2c-xlr. 879 880config I2C_RCAR 881 tristate "Renesas R-Car I2C Controller" 882 depends on ARCH_SHMOBILE || COMPILE_TEST 883 help 884 If you say yes to this option, support will be included for the 885 R-Car I2C controller. 886 887 This driver can also be built as a module. If so, the module 888 will be called i2c-rcar. 889 890comment "External I2C/SMBus adapter drivers" 891 892config I2C_DIOLAN_U2C 893 tristate "Diolan U2C-12 USB adapter" 894 depends on USB 895 help 896 If you say yes to this option, support will be included for Diolan 897 U2C-12, a USB to I2C interface. 898 899 This driver can also be built as a module. If so, the module 900 will be called i2c-diolan-u2c. 901 902config I2C_PARPORT 903 tristate "Parallel port adapter" 904 depends on PARPORT 905 select I2C_ALGOBIT 906 select I2C_SMBUS 907 help 908 This supports parallel port I2C adapters such as the ones made by 909 Philips or Velleman, Analog Devices evaluation boards, and more. 910 Basically any adapter using the parallel port as an I2C bus with 911 no extra chipset is supported by this driver, or could be. 912 913 This driver is a replacement for (and was inspired by) an older 914 driver named i2c-philips-par. The new driver supports more devices, 915 and makes it easier to add support for new devices. 916 917 An adapter type parameter is now mandatory. Please read the file 918 Documentation/i2c/busses/i2c-parport for details. 919 920 Another driver exists, named i2c-parport-light, which doesn't depend 921 on the parport driver. This is meant for embedded systems. Don't say 922 Y here if you intend to say Y or M there. 923 924 This support is also available as a module. If so, the module 925 will be called i2c-parport. 926 927config I2C_PARPORT_LIGHT 928 tristate "Parallel port adapter (light)" 929 select I2C_ALGOBIT 930 select I2C_SMBUS 931 help 932 This supports parallel port I2C adapters such as the ones made by 933 Philips or Velleman, Analog Devices evaluation boards, and more. 934 Basically any adapter using the parallel port as an I2C bus with 935 no extra chipset is supported by this driver, or could be. 936 937 This driver is a light version of i2c-parport. It doesn't depend 938 on the parport driver, and uses direct I/O access instead. This 939 might be preferred on embedded systems where wasting memory for 940 the clean but heavy parport handling is not an option. The 941 drawback is a reduced portability and the impossibility to 942 daisy-chain other parallel port devices. 943 944 Don't say Y here if you said Y or M to i2c-parport. Saying M to 945 both is possible but both modules should not be loaded at the same 946 time. 947 948 This support is also available as a module. If so, the module 949 will be called i2c-parport-light. 950 951config I2C_ROBOTFUZZ_OSIF 952 tristate "RobotFuzz Open Source InterFace USB adapter" 953 depends on USB 954 help 955 If you say yes to this option, support will be included for the 956 RobotFuzz Open Source InterFace USB to I2C interface. 957 958 This driver can also be built as a module. If so, the module 959 will be called i2c-osif. 960 961config I2C_TAOS_EVM 962 tristate "TAOS evaluation module" 963 depends on TTY 964 select SERIO 965 select SERIO_SERPORT 966 default n 967 help 968 This supports TAOS evaluation modules on serial port. In order to 969 use this driver, you will need the inputattach tool, which is part 970 of the input-utils package. 971 972 If unsure, say N. 973 974 This support is also available as a module. If so, the module 975 will be called i2c-taos-evm. 976 977config I2C_TINY_USB 978 tristate "Tiny-USB adapter" 979 depends on USB 980 help 981 If you say yes to this option, support will be included for the 982 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See 983 http://www.harbaum.org/till/i2c_tiny_usb for hardware details. 984 985 This driver can also be built as a module. If so, the module 986 will be called i2c-tiny-usb. 987 988config I2C_VIPERBOARD 989 tristate "Viperboard I2C master support" 990 depends on MFD_VIPERBOARD && USB 991 help 992 Say yes here to access the I2C part of the Nano River 993 Technologies Viperboard as I2C master. 994 See viperboard API specification and Nano 995 River Tech's viperboard.h for detailed meaning 996 of the module parameters. 997 998comment "Other I2C/SMBus bus drivers" 999 1000config I2C_ACORN 1001 tristate "Acorn IOC/IOMD I2C bus support" 1002 depends on ARCH_ACORN 1003 default y 1004 select I2C_ALGOBIT 1005 help 1006 Say yes if you want to support the I2C bus on Acorn platforms. 1007 1008 If you don't know, say Y. 1009 1010config I2C_ELEKTOR 1011 tristate "Elektor ISA card" 1012 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP 1013 select I2C_ALGOPCF 1014 help 1015 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own 1016 such an adapter. 1017 1018 This support is also available as a module. If so, the module 1019 will be called i2c-elektor. 1020 1021config I2C_PCA_ISA 1022 tristate "PCA9564/PCA9665 on an ISA bus" 1023 depends on ISA 1024 select I2C_ALGOPCA 1025 default n 1026 help 1027 This driver supports ISA boards using the Philips PCA9564/PCA9665 1028 parallel bus to I2C bus controller. 1029 1030 This driver can also be built as a module. If so, the module 1031 will be called i2c-pca-isa. 1032 1033 This device is almost undetectable and using this driver on a 1034 system which doesn't have this device will result in long 1035 delays when I2C/SMBus chip drivers are loaded (e.g. at boot 1036 time). If unsure, say N. 1037 1038config I2C_SIBYTE 1039 tristate "SiByte SMBus interface" 1040 depends on SIBYTE_SB1xxx_SOC 1041 help 1042 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 1043 1044config I2C_CROS_EC_TUNNEL 1045 tristate "ChromeOS EC tunnel I2C bus" 1046 depends on MFD_CROS_EC 1047 help 1048 If you say yes here you get an I2C bus that will tunnel i2c commands 1049 through to the other side of the ChromeOS EC to the i2c bus 1050 connected there. This will work whatever the interface used to 1051 talk to the EC (SPI, I2C or LPC). 1052 1053config SCx200_ACB 1054 tristate "Geode ACCESS.bus support" 1055 depends on X86_32 && PCI 1056 help 1057 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and 1058 SC1100 processors and the CS5535 and CS5536 Geode companion devices. 1059 1060 If you don't know what to do here, say N. 1061 1062 This support is also available as a module. If so, the module 1063 will be called scx200_acb. 1064 1065endmenu 1066