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 || COMPILE_TEST 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_IPROC 376 tristate "Broadcom iProc I2C controller" 377 depends on ARCH_BCM_IPROC || COMPILE_TEST 378 default ARCH_BCM_IPROC 379 help 380 If you say yes to this option, support will be included for the 381 Broadcom iProc I2C controller. 382 383 If you don't know what to do here, say N. 384 385config I2C_BCM_KONA 386 tristate "BCM Kona I2C adapter" 387 depends on ARCH_BCM_MOBILE 388 default y 389 help 390 If you say yes to this option, support will be included for the 391 I2C interface on the Broadcom Kona family of processors. 392 393 If you do not need KONA I2C interface, say N. 394 395config I2C_BRCMSTB 396 tristate "BRCM Settop I2C controller" 397 depends on ARCH_BRCMSTB || COMPILE_TEST 398 default y 399 help 400 If you say yes to this option, support will be included for the 401 I2C interface on the Broadcom Settop SoCs. 402 403 If you do not need I2C interface, say N. 404 405config I2C_BLACKFIN_TWI 406 tristate "Blackfin TWI I2C support" 407 depends on BLACKFIN 408 depends on !BF561 && !BF531 && !BF532 && !BF533 409 help 410 This is the I2C bus driver for Blackfin on-chip TWI interface. 411 412 This driver can also be built as a module. If so, the module 413 will be called i2c-bfin-twi. 414 415config I2C_BLACKFIN_TWI_CLK_KHZ 416 int "Blackfin TWI I2C clock (kHz)" 417 depends on I2C_BLACKFIN_TWI 418 range 21 400 419 default 50 420 help 421 The unit of the TWI clock is kHz. 422 423config I2C_CADENCE 424 tristate "Cadence I2C Controller" 425 depends on ARCH_ZYNQ 426 help 427 Say yes here to select Cadence I2C Host Controller. This controller is 428 e.g. used by Xilinx Zynq. 429 430config I2C_CBUS_GPIO 431 tristate "CBUS I2C driver" 432 depends on GPIOLIB || COMPILE_TEST 433 help 434 Support for CBUS access using I2C API. Mostly relevant for Nokia 435 Internet Tablets (770, N800 and N810). 436 437 This driver can also be built as a module. If so, the module 438 will be called i2c-cbus-gpio. 439 440config I2C_CPM 441 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" 442 depends on CPM1 || CPM2 443 help 444 This supports the use of the I2C interface on Freescale 445 processors with CPM1 or CPM2. 446 447 This driver can also be built as a module. If so, the module 448 will be called i2c-cpm. 449 450config I2C_DAVINCI 451 tristate "DaVinci I2C driver" 452 depends on ARCH_DAVINCI || ARCH_KEYSTONE 453 help 454 Support for TI DaVinci I2C controller driver. 455 456 This driver can also be built as a module. If so, the module 457 will be called i2c-davinci. 458 459 Please note that this driver might be needed to bring up other 460 devices such as DaVinci NIC. 461 For details please see http://www.ti.com/davinci 462 463config I2C_DESIGNWARE_CORE 464 tristate 465 466config I2C_DESIGNWARE_PLATFORM 467 tristate "Synopsys DesignWare Platform" 468 select I2C_DESIGNWARE_CORE 469 depends on (ACPI && COMMON_CLK) || !ACPI 470 help 471 If you say yes to this option, support will be included for the 472 Synopsys DesignWare I2C adapter. Only master mode is supported. 473 474 This driver can also be built as a module. If so, the module 475 will be called i2c-designware-platform. 476 477config I2C_DESIGNWARE_PCI 478 tristate "Synopsys DesignWare PCI" 479 depends on PCI 480 select I2C_DESIGNWARE_CORE 481 help 482 If you say yes to this option, support will be included for the 483 Synopsys DesignWare I2C adapter. Only master mode is supported. 484 485 This driver can also be built as a module. If so, the module 486 will be called i2c-designware-pci. 487 488config I2C_DESIGNWARE_BAYTRAIL 489 bool "Intel Baytrail I2C semaphore support" 490 depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI 491 help 492 This driver enables managed host access to the PMIC I2C bus on select 493 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows 494 the host to request uninterrupted access to the PMIC's I2C bus from 495 the platform firmware controlling it. You should say Y if running on 496 a BayTrail system using the AXP288. 497 498config I2C_DIGICOLOR 499 tristate "Conexant Digicolor I2C driver" 500 depends on ARCH_DIGICOLOR 501 help 502 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver. 503 504 This driver can also be built as a module. If so, the module 505 will be called i2c-digicolor. 506 507config I2C_EFM32 508 tristate "EFM32 I2C controller" 509 depends on ARCH_EFM32 || COMPILE_TEST 510 help 511 This driver supports the i2c block found in Energy Micro's EFM32 512 SoCs. 513 514config I2C_EG20T 515 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" 516 depends on PCI && (X86_32 || COMPILE_TEST) 517 help 518 This driver is for PCH(Platform controller Hub) I2C of EG20T which 519 is an IOH(Input/Output Hub) for x86 embedded processor. 520 This driver can access PCH I2C bus device. 521 522 This driver also can be used for LAPIS Semiconductor IOH(Input/ 523 Output Hub), ML7213, ML7223 and ML7831. 524 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is 525 for MP(Media Phone) use and ML7831 IOH is for general purpose use. 526 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 527 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 528 529config I2C_EXYNOS5 530 tristate "Exynos5 high-speed I2C driver" 531 depends on ARCH_EXYNOS && OF 532 default y 533 help 534 High-speed I2C controller on Exynos5 based Samsung SoCs. 535 536config I2C_GPIO 537 tristate "GPIO-based bitbanging I2C" 538 depends on GPIOLIB || COMPILE_TEST 539 select I2C_ALGOBIT 540 help 541 This is a very simple bitbanging I2C driver utilizing the 542 arch-neutral GPIO API to control the SCL and SDA lines. 543 544config I2C_HIGHLANDER 545 tristate "Highlander FPGA SMBus interface" 546 depends on SH_HIGHLANDER 547 help 548 If you say yes to this option, support will be included for 549 the SMBus interface located in the FPGA on various Highlander 550 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL 551 FPGAs. This is wholly unrelated to the SoC I2C. 552 553 This driver can also be built as a module. If so, the module 554 will be called i2c-highlander. 555 556config I2C_IBM_IIC 557 tristate "IBM PPC 4xx on-chip I2C interface" 558 depends on 4xx 559 help 560 Say Y here if you want to use IIC peripheral found on 561 embedded IBM PPC 4xx based systems. 562 563 This driver can also be built as a module. If so, the module 564 will be called i2c-ibm_iic. 565 566config I2C_IMG 567 tristate "Imagination Technologies I2C SCB Controller" 568 depends on MIPS || METAG || COMPILE_TEST 569 help 570 Say Y here if you want to use the IMG I2C SCB controller, 571 available on the TZ1090 and other IMG SoCs. 572 573 This driver can also be built as a module. If so, the module 574 will be called i2c-img-scb. 575 576config I2C_IMX 577 tristate "IMX I2C interface" 578 depends on ARCH_MXC 579 help 580 Say Y here if you want to use the IIC bus controller on 581 the Freescale i.MX/MXC processors. 582 583 This driver can also be built as a module. If so, the module 584 will be called i2c-imx. 585 586config I2C_IOP3XX 587 tristate "Intel IOPx3xx and IXP4xx on-chip I2C interface" 588 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX || ARCH_IOP13XX 589 help 590 Say Y here if you want to use the IIC bus controller on 591 the Intel IOPx3xx I/O Processors or IXP4xx Network Processors. 592 593 This driver can also be built as a module. If so, the module 594 will be called i2c-iop3xx. 595 596config I2C_JZ4780 597 tristate "JZ4780 I2C controller interface support" 598 depends on MACH_JZ4780 || COMPILE_TEST 599 help 600 If you say yes to this option, support will be included for the 601 Ingenic JZ4780 I2C controller. 602 603 If you don't know what to do here, say N. 604 605config I2C_KEMPLD 606 tristate "Kontron COM I2C Controller" 607 depends on MFD_KEMPLD 608 help 609 This enables support for the I2C bus interface on some Kontron ETX 610 and COMexpress (ETXexpress) modules. 611 612 This driver can also be built as a module. If so, the module 613 will be called i2c-kempld. 614 615config I2C_MESON 616 tristate "Amlogic Meson I2C controller" 617 depends on ARCH_MESON 618 help 619 If you say yes to this option, support will be included for the 620 I2C interface on the Amlogic Meson family of SoCs. 621 622config I2C_MPC 623 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" 624 depends on PPC 625 help 626 If you say yes to this option, support will be included for the 627 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, 628 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. 629 630 This driver can also be built as a module. If so, the module 631 will be called i2c-mpc. 632 633config I2C_MT65XX 634 tristate "MediaTek I2C adapter" 635 depends on ARCH_MEDIATEK || COMPILE_TEST 636 help 637 This selects the MediaTek(R) Integrated Inter Circuit bus driver 638 for MT65xx and MT81xx. 639 If you want to use MediaTek(R) I2C interface, say Y or M here. 640 If unsure, say N. 641 642config I2C_MV64XXX 643 tristate "Marvell mv64xxx I2C Controller" 644 depends on MV64X60 || PLAT_ORION || ARCH_SUNXI 645 help 646 If you say yes to this option, support will be included for the 647 built-in I2C interface on the Marvell 64xxx line of host bridges. 648 This driver is also used for Allwinner SoCs I2C controllers. 649 650 This driver can also be built as a module. If so, the module 651 will be called i2c-mv64xxx. 652 653config I2C_MXS 654 tristate "Freescale i.MX28 I2C interface" 655 depends on SOC_IMX28 656 select STMP_DEVICE 657 help 658 Say Y here if you want to use the I2C bus controller on 659 the Freescale i.MX28 processors. 660 661 This driver can also be built as a module. If so, the module 662 will be called i2c-mxs. 663 664config I2C_NOMADIK 665 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" 666 depends on ARM_AMBA 667 help 668 If you say yes to this option, support will be included for the 669 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures, 670 as well as the STA2X11 PCIe I/O HUB. 671 672config I2C_OCORES 673 tristate "OpenCores I2C Controller" 674 help 675 If you say yes to this option, support will be included for the 676 OpenCores I2C controller. For details see 677 http://www.opencores.org/projects.cgi/web/i2c/overview 678 679 This driver can also be built as a module. If so, the module 680 will be called i2c-ocores. 681 682config I2C_OMAP 683 tristate "OMAP I2C adapter" 684 depends on ARCH_OMAP 685 default y if MACH_OMAP_H3 || MACH_OMAP_OSK 686 help 687 If you say yes to this option, support will be included for the 688 I2C interface on the Texas Instruments OMAP1/2 family of processors. 689 Like OMAP1510/1610/1710/5912 and OMAP242x. 690 For details see http://www.ti.com/omap. 691 692config I2C_PASEMI 693 tristate "PA Semi SMBus interface" 694 depends on PPC_PASEMI && PCI 695 help 696 Supports the PA Semi PWRficient on-chip SMBus interfaces. 697 698config I2C_PCA_PLATFORM 699 tristate "PCA9564/PCA9665 as platform device" 700 select I2C_ALGOPCA 701 default n 702 help 703 This driver supports a memory mapped Philips PCA9564/PCA9665 704 parallel bus to I2C bus controller. 705 706 This driver can also be built as a module. If so, the module 707 will be called i2c-pca-platform. 708 709config I2C_PMCMSP 710 tristate "PMC MSP I2C TWI Controller" 711 depends on PMC_MSP 712 help 713 This driver supports the PMC TWI controller on MSP devices. 714 715 This driver can also be built as module. If so, the module 716 will be called i2c-pmcmsp. 717 718config I2C_PNX 719 tristate "I2C bus support for Philips PNX and NXP LPC targets" 720 depends on ARCH_LPC32XX 721 help 722 This driver supports the Philips IP3204 I2C IP block master and/or 723 slave controller 724 725 This driver can also be built as a module. If so, the module 726 will be called i2c-pnx. 727 728config I2C_PUV3 729 tristate "PKUnity v3 I2C bus support" 730 depends on UNICORE32 && ARCH_PUV3 731 select I2C_ALGOBIT 732 help 733 This driver supports the I2C IP inside the PKUnity-v3 SoC. 734 This I2C bus controller is under AMBA/AXI bus. 735 736 This driver can also be built as a module. If so, the module 737 will be called i2c-puv3. 738 739config I2C_PXA 740 tristate "Intel PXA2XX I2C adapter" 741 depends on ARCH_PXA || ARCH_MMP || (X86_32 && PCI && OF) 742 help 743 If you have devices in the PXA I2C bus, say yes to this option. 744 This driver can also be built as a module. If so, the module 745 will be called i2c-pxa. 746 747config I2C_PXA_PCI 748 def_bool I2C_PXA && X86_32 && PCI && OF 749 750config I2C_PXA_SLAVE 751 bool "Intel PXA2XX I2C Slave comms support" 752 depends on I2C_PXA && !X86_32 753 help 754 Support I2C slave mode communications on the PXA I2C bus. This 755 is necessary for systems where the PXA may be a target on the 756 I2C bus. 757 758config I2C_QUP 759 tristate "Qualcomm QUP based I2C controller" 760 depends on ARCH_QCOM 761 help 762 If you say yes to this option, support will be included for the 763 built-in I2C interface on the Qualcomm SoCs. 764 765 This driver can also be built as a module. If so, the module 766 will be called i2c-qup. 767 768config I2C_RIIC 769 tristate "Renesas RIIC adapter" 770 depends on ARCH_SHMOBILE || COMPILE_TEST 771 help 772 If you say yes to this option, support will be included for the 773 Renesas RIIC I2C interface. 774 775 This driver can also be built as a module. If so, the module 776 will be called i2c-riic. 777 778config I2C_RK3X 779 tristate "Rockchip RK3xxx I2C adapter" 780 depends on OF && COMMON_CLK 781 help 782 Say Y here to include support for the I2C adapter in Rockchip RK3xxx 783 SoCs. 784 785 This driver can also be built as a module. If so, the module will 786 be called i2c-rk3x. 787 788config HAVE_S3C2410_I2C 789 bool 790 help 791 This will include I2C support for Samsung SoCs. If you want to 792 include I2C support for any machine, kindly select this in the 793 respective Kconfig file. 794 795config I2C_S3C2410 796 tristate "S3C2410 I2C Driver" 797 depends on HAVE_S3C2410_I2C 798 help 799 Say Y here to include support for I2C controller in the 800 Samsung SoCs. 801 802config I2C_SH7760 803 tristate "Renesas SH7760 I2C Controller" 804 depends on CPU_SUBTYPE_SH7760 805 help 806 This driver supports the 2 I2C interfaces on the Renesas SH7760. 807 808 This driver can also be built as a module. If so, the module 809 will be called i2c-sh7760. 810 811config I2C_SH_MOBILE 812 tristate "SuperH Mobile I2C Controller" 813 depends on HAS_DMA 814 depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST 815 help 816 If you say yes to this option, support will be included for the 817 built-in I2C interface on the Renesas SH-Mobile processor. 818 819 This driver can also be built as a module. If so, the module 820 will be called i2c-sh_mobile. 821 822config I2C_SIMTEC 823 tristate "Simtec Generic I2C interface" 824 select I2C_ALGOBIT 825 help 826 If you say yes to this option, support will be included for 827 the Simtec Generic I2C interface. This driver is for the 828 simple I2C bus used on newer Simtec products for general 829 I2C, such as DDC on the Simtec BBD2016A. 830 831 This driver can also be built as a module. If so, the module 832 will be called i2c-simtec. 833 834config I2C_SIRF 835 tristate "CSR SiRFprimaII I2C interface" 836 depends on ARCH_SIRF 837 help 838 If you say yes to this option, support will be included for the 839 CSR SiRFprimaII I2C interface. 840 841 This driver can also be built as a module. If so, the module 842 will be called i2c-sirf. 843 844config I2C_ST 845 tristate "STMicroelectronics SSC I2C support" 846 depends on ARCH_STI 847 help 848 Enable this option to add support for STMicroelectronics SoCs 849 hardware SSC (Synchronous Serial Controller) as an I2C controller. 850 851 This driver can also be built as module. If so, the module 852 will be called i2c-st. 853 854config I2C_STU300 855 tristate "ST Microelectronics DDC I2C interface" 856 depends on MACH_U300 857 default y if MACH_U300 858 help 859 If you say yes to this option, support will be included for the 860 I2C interface from ST Microelectronics simply called "DDC I2C" 861 supporting both I2C and DDC, used in e.g. the U300 series 862 mobile platforms. 863 864 This driver can also be built as a module. If so, the module 865 will be called i2c-stu300. 866 867config I2C_SUN6I_P2WI 868 tristate "Allwinner sun6i internal P2WI controller" 869 depends on RESET_CONTROLLER 870 depends on MACH_SUN6I || COMPILE_TEST 871 help 872 If you say yes to this option, support will be included for the 873 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi 874 SOCs. 875 The P2WI looks like an SMBus controller (which supports only byte 876 accesses), except that it only supports one slave device. 877 This interface is used to connect to specific PMIC devices (like the 878 AXP221). 879 880config I2C_TEGRA 881 tristate "NVIDIA Tegra internal I2C controller" 882 depends on ARCH_TEGRA 883 help 884 If you say yes to this option, support will be included for the 885 I2C controller embedded in NVIDIA Tegra SOCs 886 887config I2C_VERSATILE 888 tristate "ARM Versatile/Realview I2C bus support" 889 depends on ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS 890 select I2C_ALGOBIT 891 help 892 Say yes if you want to support the I2C serial bus on ARMs Versatile 893 range of platforms. 894 895 This driver can also be built as a module. If so, the module 896 will be called i2c-versatile. 897 898config I2C_WMT 899 tristate "Wondermedia WM8xxx SoC I2C bus support" 900 depends on ARCH_VT8500 901 help 902 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series 903 SoCs. 904 905 This driver can also be built as a module. If so, the module will be 906 called i2c-wmt. 907 908config I2C_OCTEON 909 tristate "Cavium OCTEON I2C bus support" 910 depends on CAVIUM_OCTEON_SOC 911 help 912 Say yes if you want to support the I2C serial bus on Cavium 913 OCTEON SOC. 914 915 This driver can also be built as a module. If so, the module 916 will be called i2c-octeon. 917 918config I2C_XILINX 919 tristate "Xilinx I2C Controller" 920 depends on HAS_IOMEM 921 help 922 If you say yes to this option, support will be included for the 923 Xilinx I2C controller. 924 925 This driver can also be built as a module. If so, the module 926 will be called xilinx_i2c. 927 928config I2C_XLR 929 tristate "XLR I2C support" 930 depends on CPU_XLR 931 help 932 This driver enables support for the on-chip I2C interface of 933 the Netlogic XLR/XLS MIPS processors. 934 935 This driver can also be built as a module. If so, the module 936 will be called i2c-xlr. 937 938config I2C_XLP9XX 939 tristate "XLP9XX I2C support" 940 depends on CPU_XLP || COMPILE_TEST 941 help 942 This driver enables support for the on-chip I2C interface of 943 the Broadcom XLP9xx/XLP5xx MIPS processors. 944 945 This driver can also be built as a module. If so, the module will 946 be called i2c-xlp9xx. 947 948config I2C_RCAR 949 tristate "Renesas R-Car I2C Controller" 950 depends on ARCH_SHMOBILE || COMPILE_TEST 951 select I2C_SLAVE 952 help 953 If you say yes to this option, support will be included for the 954 R-Car I2C controller. 955 956 This driver can also be built as a module. If so, the module 957 will be called i2c-rcar. 958 959comment "External I2C/SMBus adapter drivers" 960 961config I2C_DIOLAN_U2C 962 tristate "Diolan U2C-12 USB adapter" 963 depends on USB 964 help 965 If you say yes to this option, support will be included for Diolan 966 U2C-12, a USB to I2C interface. 967 968 This driver can also be built as a module. If so, the module 969 will be called i2c-diolan-u2c. 970 971config I2C_DLN2 972 tristate "Diolan DLN-2 USB I2C adapter" 973 depends on MFD_DLN2 974 help 975 If you say yes to this option, support will be included for Diolan 976 DLN2, a USB to I2C interface. 977 978 This driver can also be built as a module. If so, the module 979 will be called i2c-dln2. 980 981config I2C_PARPORT 982 tristate "Parallel port adapter" 983 depends on PARPORT 984 select I2C_ALGOBIT 985 select I2C_SMBUS 986 help 987 This supports parallel port I2C adapters such as the ones made by 988 Philips or Velleman, Analog Devices evaluation boards, and more. 989 Basically any adapter using the parallel port as an I2C bus with 990 no extra chipset is supported by this driver, or could be. 991 992 This driver is a replacement for (and was inspired by) an older 993 driver named i2c-philips-par. The new driver supports more devices, 994 and makes it easier to add support for new devices. 995 996 An adapter type parameter is now mandatory. Please read the file 997 Documentation/i2c/busses/i2c-parport for details. 998 999 Another driver exists, named i2c-parport-light, which doesn't depend 1000 on the parport driver. This is meant for embedded systems. Don't say 1001 Y here if you intend to say Y or M there. 1002 1003 This support is also available as a module. If so, the module 1004 will be called i2c-parport. 1005 1006config I2C_PARPORT_LIGHT 1007 tristate "Parallel port adapter (light)" 1008 select I2C_ALGOBIT 1009 select I2C_SMBUS 1010 help 1011 This supports parallel port I2C adapters such as the ones made by 1012 Philips or Velleman, Analog Devices evaluation boards, and more. 1013 Basically any adapter using the parallel port as an I2C bus with 1014 no extra chipset is supported by this driver, or could be. 1015 1016 This driver is a light version of i2c-parport. It doesn't depend 1017 on the parport driver, and uses direct I/O access instead. This 1018 might be preferred on embedded systems where wasting memory for 1019 the clean but heavy parport handling is not an option. The 1020 drawback is a reduced portability and the impossibility to 1021 daisy-chain other parallel port devices. 1022 1023 Don't say Y here if you said Y or M to i2c-parport. Saying M to 1024 both is possible but both modules should not be loaded at the same 1025 time. 1026 1027 This support is also available as a module. If so, the module 1028 will be called i2c-parport-light. 1029 1030config I2C_ROBOTFUZZ_OSIF 1031 tristate "RobotFuzz Open Source InterFace USB adapter" 1032 depends on USB 1033 help 1034 If you say yes to this option, support will be included for the 1035 RobotFuzz Open Source InterFace USB to I2C interface. 1036 1037 This driver can also be built as a module. If so, the module 1038 will be called i2c-osif. 1039 1040config I2C_TAOS_EVM 1041 tristate "TAOS evaluation module" 1042 depends on TTY 1043 select SERIO 1044 select SERIO_SERPORT 1045 default n 1046 help 1047 This supports TAOS evaluation modules on serial port. In order to 1048 use this driver, you will need the inputattach tool, which is part 1049 of the input-utils package. 1050 1051 If unsure, say N. 1052 1053 This support is also available as a module. If so, the module 1054 will be called i2c-taos-evm. 1055 1056config I2C_TINY_USB 1057 tristate "Tiny-USB adapter" 1058 depends on USB 1059 help 1060 If you say yes to this option, support will be included for the 1061 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See 1062 http://www.harbaum.org/till/i2c_tiny_usb for hardware details. 1063 1064 This driver can also be built as a module. If so, the module 1065 will be called i2c-tiny-usb. 1066 1067config I2C_VIPERBOARD 1068 tristate "Viperboard I2C master support" 1069 depends on MFD_VIPERBOARD && USB 1070 help 1071 Say yes here to access the I2C part of the Nano River 1072 Technologies Viperboard as I2C master. 1073 See viperboard API specification and Nano 1074 River Tech's viperboard.h for detailed meaning 1075 of the module parameters. 1076 1077comment "Other I2C/SMBus bus drivers" 1078 1079config I2C_ACORN 1080 tristate "Acorn IOC/IOMD I2C bus support" 1081 depends on ARCH_ACORN 1082 default y 1083 select I2C_ALGOBIT 1084 help 1085 Say yes if you want to support the I2C bus on Acorn platforms. 1086 1087 If you don't know, say Y. 1088 1089config I2C_ELEKTOR 1090 tristate "Elektor ISA card" 1091 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP 1092 select I2C_ALGOPCF 1093 help 1094 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own 1095 such an adapter. 1096 1097 This support is also available as a module. If so, the module 1098 will be called i2c-elektor. 1099 1100config I2C_PCA_ISA 1101 tristate "PCA9564/PCA9665 on an ISA bus" 1102 depends on ISA 1103 select I2C_ALGOPCA 1104 default n 1105 help 1106 This driver supports ISA boards using the Philips PCA9564/PCA9665 1107 parallel bus to I2C bus controller. 1108 1109 This driver can also be built as a module. If so, the module 1110 will be called i2c-pca-isa. 1111 1112 This device is almost undetectable and using this driver on a 1113 system which doesn't have this device will result in long 1114 delays when I2C/SMBus chip drivers are loaded (e.g. at boot 1115 time). If unsure, say N. 1116 1117config I2C_SIBYTE 1118 tristate "SiByte SMBus interface" 1119 depends on SIBYTE_SB1xxx_SOC 1120 help 1121 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 1122 1123config I2C_CROS_EC_TUNNEL 1124 tristate "ChromeOS EC tunnel I2C bus" 1125 depends on CROS_EC_PROTO 1126 help 1127 If you say yes here you get an I2C bus that will tunnel i2c commands 1128 through to the other side of the ChromeOS EC to the i2c bus 1129 connected there. This will work whatever the interface used to 1130 talk to the EC (SPI, I2C or LPC). 1131 1132config I2C_XGENE_SLIMPRO 1133 tristate "APM X-Gene SoC I2C SLIMpro devices support" 1134 depends on ARCH_XGENE && MAILBOX 1135 help 1136 Enable I2C bus access using the APM X-Gene SoC SLIMpro 1137 co-processor. The I2C device access the I2C bus via the X-Gene 1138 to SLIMpro (On chip coprocessor) mailbox mechanism. 1139 If unsure, say N. 1140 1141config SCx200_ACB 1142 tristate "Geode ACCESS.bus support" 1143 depends on X86_32 && PCI 1144 help 1145 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and 1146 SC1100 processors and the CS5535 and CS5536 Geode companion devices. 1147 1148 If you don't know what to do here, say N. 1149 1150 This support is also available as a module. If so, the module 1151 will be called scx200_acb. 1152 1153config I2C_OPAL 1154 tristate "IBM OPAL I2C driver" 1155 depends on PPC_POWERNV 1156 default y 1157 help 1158 This exposes the PowerNV platform i2c busses to the linux i2c layer, 1159 the driver is based on the OPAL interfaces. 1160 1161 This driver can also be built as a module. If so, the module will be 1162 called as i2c-opal. 1163 1164endmenu 1165