1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Sensor device configuration 4# 5 6menu "I2C Hardware Bus support" 7 depends on HAS_IOMEM 8 9comment "PC SMBus host controller drivers" 10 depends on PCI 11 12config I2C_CCGX_UCSI 13 tristate 14 help 15 A common module to provide an API to instantiate UCSI device 16 for Cypress CCGx Type-C controller. Individual bus drivers 17 need to select this one on demand. 18 19config I2C_ALI1535 20 tristate "ALI 1535" 21 depends on PCI && HAS_IOPORT 22 help 23 If you say yes to this option, support will be included for the SMB 24 Host controller on Acer Labs Inc. (ALI) M1535 South Bridges. The SMB 25 controller is part of the 7101 device, which is an ACPI-compliant 26 Power Management Unit (PMU). 27 28 This driver can also be built as a module. If so, the module 29 will be called i2c-ali1535. 30 31config I2C_ALI1563 32 tristate "ALI 1563" 33 depends on PCI && HAS_IOPORT 34 help 35 If you say yes to this option, support will be included for the SMB 36 Host controller on Acer Labs Inc. (ALI) M1563 South Bridges. The SMB 37 controller is part of the 7101 device, which is an ACPI-compliant 38 Power Management Unit (PMU). 39 40 This driver can also be built as a module. If so, the module 41 will be called i2c-ali1563. 42 43config I2C_ALI15X3 44 tristate "ALI 15x3" 45 depends on PCI && HAS_IOPORT 46 help 47 If you say yes to this option, support will be included for the 48 Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces. 49 50 This driver can also be built as a module. If so, the module 51 will be called i2c-ali15x3. 52 53config I2C_AMD756 54 tristate "AMD 756/766/768/8111 and nVidia nForce" 55 depends on PCI && HAS_IOPORT 56 help 57 If you say yes to this option, support will be included for the AMD 58 756/766/768 mainboard I2C interfaces. The driver also includes 59 support for the first (SMBus 1.0) I2C interface of the AMD 8111 and 60 the nVidia nForce I2C interface. 61 62 This driver can also be built as a module. If so, the module 63 will be called i2c-amd756. 64 65config I2C_AMD756_S4882 66 tristate "SMBus multiplexing on the Tyan S4882" 67 depends on I2C_AMD756 && X86 68 help 69 Enabling this option will add specific SMBus support for the Tyan 70 S4882 motherboard. On this 4-CPU board, the SMBus is multiplexed 71 over 8 different channels, where the various memory module EEPROMs 72 and temperature sensors live. Saying yes here will give you access 73 to these in addition to the trunk. 74 75 This driver can also be built as a module. If so, the module 76 will be called i2c-amd756-s4882. 77 78config I2C_AMD8111 79 tristate "AMD 8111" 80 depends on PCI && HAS_IOPORT 81 help 82 If you say yes to this option, support will be included for the 83 second (SMBus 2.0) AMD 8111 mainboard I2C interface. 84 85 This driver can also be built as a module. If so, the module 86 will be called i2c-amd8111. 87 88config I2C_AMD_MP2 89 tristate "AMD MP2 PCIe" 90 depends on PCI && ACPI 91 help 92 If you say yes to this option, support will be included for the AMD 93 MP2 PCIe I2C adapter. 94 95 This driver can also be built as modules. If so, the modules will 96 be called i2c-amd-mp2-pci and i2c-amd-mp2-plat. 97 98config I2C_HIX5HD2 99 tristate "Hix5hd2 high-speed I2C driver" 100 depends on ARCH_HISI || ARCH_HIX5HD2 || COMPILE_TEST 101 help 102 Say Y here to include support for the high-speed I2C controller 103 used in HiSilicon hix5hd2 SoCs. 104 105 This driver can also be built as a module. If so, the module 106 will be called i2c-hix5hd2. 107 108config I2C_I801 109 tristate "Intel 82801 (ICH/PCH)" 110 depends on PCI && HAS_IOPORT 111 select P2SB if X86 112 select CHECK_SIGNATURE if X86 && DMI 113 select I2C_SMBUS 114 help 115 If you say yes to this option, support will be included for the Intel 116 801 family of mainboard I2C interfaces. Specifically, the following 117 versions of the chipset are supported: 118 82801AA 119 82801AB 120 82801BA 121 82801CA/CAM 122 82801DB 123 82801EB/ER (ICH5/ICH5R) 124 6300ESB 125 ICH6 126 ICH7 127 ESB2 128 ICH8 129 ICH9 130 EP80579 (Tolapai) 131 ICH10 132 5/3400 Series (PCH) 133 6 Series (PCH) 134 Patsburg (PCH) 135 DH89xxCC (PCH) 136 Panther Point (PCH) 137 Lynx Point (PCH) 138 Avoton (SOC) 139 Wellsburg (PCH) 140 Coleto Creek (PCH) 141 Wildcat Point (PCH) 142 BayTrail (SOC) 143 Braswell (SOC) 144 Sunrise Point (PCH) 145 Kaby Lake (PCH) 146 DNV (SOC) 147 Broxton (SOC) 148 Lewisburg (PCH) 149 Gemini Lake (SOC) 150 Cannon Lake (PCH) 151 Cedar Fork (PCH) 152 Ice Lake (PCH) 153 Comet Lake (PCH) 154 Elkhart Lake (PCH) 155 Tiger Lake (PCH) 156 Jasper Lake (SOC) 157 Emmitsburg (PCH) 158 Alder Lake (PCH) 159 Raptor Lake (PCH) 160 Meteor Lake (SOC and PCH) 161 Birch Stream (SOC) 162 Arrow Lake (SOC) 163 Panther Lake (SOC) 164 165 This driver can also be built as a module. If so, the module 166 will be called i2c-i801. 167 168config I2C_I801_MUX 169 def_bool I2C_I801 170 depends on DMI && I2C_MUX_GPIO 171 depends on !(I2C_I801=y && I2C_MUX=m) 172 help 173 Optional support for multiplexed SMBUS on certain systems with 174 more than 8 memory slots. 175 176config I2C_ISCH 177 tristate "Intel SCH SMBus 1.0" 178 depends on PCI && HAS_IOPORT 179 select LPC_SCH 180 help 181 Say Y here if you want to use SMBus controller on the Intel SCH 182 based systems. 183 184 This driver can also be built as a module. If so, the module 185 will be called i2c-isch. 186 187config I2C_ISMT 188 tristate "Intel iSMT SMBus Controller" 189 depends on PCI && X86 190 help 191 If you say yes to this option, support will be included for the Intel 192 iSMT SMBus host controller interface. 193 194 This driver can also be built as a module. If so, the module will be 195 called i2c-ismt. 196 197config I2C_PIIX4 198 tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)" 199 depends on PCI && HAS_IOPORT 200 select I2C_SMBUS 201 help 202 If you say yes to this option, support will be included for the Intel 203 PIIX4 family of mainboard I2C interfaces. Specifically, the following 204 versions of the chipset are supported (note that Serverworks is part 205 of Broadcom): 206 Intel PIIX4 207 Intel 440MX 208 ATI IXP200 209 ATI IXP300 210 ATI IXP400 211 ATI SB600 212 ATI SB700/SP5100 213 ATI SB800 214 AMD Hudson-2 215 AMD ML 216 AMD CZ 217 Hygon CZ 218 Serverworks OSB4 219 Serverworks CSB5 220 Serverworks CSB6 221 Serverworks HT-1000 222 Serverworks HT-1100 223 SMSC Victory66 224 225 Some AMD chipsets contain two PIIX4-compatible SMBus 226 controllers. This driver will attempt to use both controllers 227 on the SB700/SP5100, if they have been initialized by the BIOS. 228 229 This driver can also be built as a module. If so, the module 230 will be called i2c-piix4. 231 232config I2C_CHT_WC 233 tristate "Intel Cherry Trail Whiskey Cove PMIC smbus controller" 234 depends on INTEL_SOC_PMIC_CHTWC 235 help 236 If you say yes to this option, support will be included for the 237 SMBus controller found in the Intel Cherry Trail Whiskey Cove PMIC 238 found on some Intel Cherry Trail systems. 239 240 Note this controller is hooked up to a TI bq24292i charger-IC, 241 combined with a FUSB302 Type-C port-controller as such it is advised 242 to also select CONFIG_TYPEC_FUSB302=m. 243 244config I2C_NFORCE2 245 tristate "Nvidia nForce2, nForce3 and nForce4" 246 depends on PCI && HAS_IOPORT 247 help 248 If you say yes to this option, support will be included for the Nvidia 249 nForce2, nForce3 and nForce4 families of mainboard I2C interfaces. 250 251 This driver can also be built as a module. If so, the module 252 will be called i2c-nforce2. 253 254config I2C_NFORCE2_S4985 255 tristate "SMBus multiplexing on the Tyan S4985" 256 depends on I2C_NFORCE2 && X86 257 help 258 Enabling this option will add specific SMBus support for the Tyan 259 S4985 motherboard. On this 4-CPU board, the SMBus is multiplexed 260 over 4 different channels, where the various memory module EEPROMs 261 live. Saying yes here will give you access to these in addition 262 to the trunk. 263 264 This driver can also be built as a module. If so, the module 265 will be called i2c-nforce2-s4985. 266 267config I2C_NVIDIA_GPU 268 tristate "NVIDIA GPU I2C controller" 269 depends on PCI 270 select I2C_CCGX_UCSI 271 help 272 If you say yes to this option, support will be included for the 273 NVIDIA GPU I2C controller which is used to communicate with the GPU's 274 Type-C controller. This driver can also be built as a module called 275 i2c-nvidia-gpu. 276 277config I2C_SIS5595 278 tristate "SiS 5595" 279 depends on PCI && HAS_IOPORT 280 help 281 If you say yes to this option, support will be included for the 282 SiS5595 SMBus (a subset of I2C) interface. 283 284 This driver can also be built as a module. If so, the module 285 will be called i2c-sis5595. 286 287config I2C_SIS630 288 tristate "SiS 630/730/964" 289 depends on PCI && HAS_IOPORT 290 help 291 If you say yes to this option, support will be included for the 292 SiS630, SiS730 and SiS964 SMBus (a subset of I2C) interface. 293 294 This driver can also be built as a module. If so, the module 295 will be called i2c-sis630. 296 297config I2C_SIS96X 298 tristate "SiS 96x" 299 depends on PCI && HAS_IOPORT 300 help 301 If you say yes to this option, support will be included for the SiS 302 96x SMBus (a subset of I2C) interfaces. Specifically, the following 303 chipsets are supported: 304 645/961 305 645DX/961 306 645DX/962 307 648/961 308 650/961 309 735 310 745 311 312 This driver can also be built as a module. If so, the module 313 will be called i2c-sis96x. 314 315config I2C_VIA 316 tristate "VIA VT82C586B" 317 depends on PCI && HAS_IOPORT 318 select I2C_ALGOBIT 319 help 320 If you say yes to this option, support will be included for the VIA 321 82C586B I2C interface 322 323 This driver can also be built as a module. If so, the module 324 will be called i2c-via. 325 326config I2C_VIAPRO 327 tristate "VIA VT82C596/82C686/82xx and CX700/VX8xx/VX900" 328 depends on PCI && HAS_IOPORT 329 help 330 If you say yes to this option, support will be included for the VIA 331 VT82C596 and later SMBus interface. Specifically, the following 332 chipsets are supported: 333 VT82C596A/B 334 VT82C686A/B 335 VT8231 336 VT8233/A 337 VT8235 338 VT8237R/A/S 339 VT8251 340 CX700 341 VX800/VX820 342 VX855/VX875 343 VX900 344 345 This driver can also be built as a module. If so, the module 346 will be called i2c-viapro. 347 348if ACPI 349 350config I2C_ZHAOXIN 351 tristate "Zhaoxin I2C Interface" 352 depends on PCI || COMPILE_TEST 353 help 354 If you say yes to this option, support will be included for the 355 ZHAOXIN I2C interface 356 357 This driver can also be built as a module. If so, the module 358 will be called i2c-zhaoxin. 359 360comment "ACPI drivers" 361 362config I2C_SCMI 363 tristate "SMBus Control Method Interface" 364 help 365 This driver supports the SMBus Control Method Interface. It needs the 366 BIOS to declare ACPI control methods as described in the SMBus Control 367 Method Interface specification. 368 369 To compile this driver as a module, choose M here: 370 the module will be called i2c-scmi. 371 372endif # ACPI 373 374comment "Mac SMBus host controller drivers" 375 depends on PPC_CHRP || PPC_PMAC 376 377config I2C_HYDRA 378 tristate "CHRP Apple Hydra Mac I/O I2C interface" 379 depends on PCI && PPC_CHRP 380 select I2C_ALGOBIT 381 help 382 This supports the use of the I2C interface in the Apple Hydra Mac 383 I/O chip on some CHRP machines (e.g. the LongTrail). Say Y if you 384 have such a machine. 385 386 This support is also available as a module. If so, the module 387 will be called i2c-hydra. 388 389config I2C_POWERMAC 390 tristate "Powermac I2C interface" 391 depends on PPC_PMAC 392 default y 393 help 394 This exposes the various PowerMac i2c interfaces to the linux i2c 395 layer and to userland. It is used by various drivers on the PowerMac 396 platform, and should generally be enabled. 397 398 This support is also available as a module. If so, the module 399 will be called i2c-powermac. 400 401comment "I2C system bus drivers (mostly embedded / system-on-chip)" 402 403config I2C_ALTERA 404 tristate "Altera Soft IP I2C" 405 depends on ARCH_INTEL_SOCFPGA || NIOS2 || COMPILE_TEST 406 depends on OF 407 help 408 If you say yes to this option, support will be included for the 409 Altera Soft IP I2C interfaces on SoCFPGA and Nios2 architectures. 410 411 This driver can also be built as a module. If so, the module 412 will be called i2c-altera. 413 414config I2C_ASPEED 415 tristate "Aspeed I2C Controller" 416 depends on ARCH_ASPEED || COMPILE_TEST 417 help 418 If you say yes to this option, support will be included for the 419 Aspeed I2C controller. 420 421 This driver can also be built as a module. If so, the module 422 will be called i2c-aspeed. 423 424config I2C_AT91 425 tristate "Atmel AT91 I2C Two-Wire interface (TWI)" 426 depends on ARCH_AT91 || COMPILE_TEST 427 help 428 This supports the use of the I2C interface on Atmel AT91 429 processors. 430 431 A serious problem is that there is no documented way to issue 432 repeated START conditions for more than two messages, as needed 433 to support combined I2C messages. Use the i2c-gpio driver 434 unless your system can cope with this limitation. 435 436 Caution! at91rm9200, at91sam9261, at91sam9260, at91sam9263 devices 437 don't have clock stretching in transmission mode. For that reason, 438 you can encounter underrun issues causing premature stop sendings if 439 the latency to fill the transmission register is too long. If you 440 are facing this situation, use the i2c-gpio driver. 441 442config I2C_AT91_SLAVE_EXPERIMENTAL 443 tristate "Microchip AT91 I2C experimental slave mode" 444 depends on I2C_AT91 445 select I2C_SLAVE 446 help 447 If you say yes to this option, support for the slave mode will be 448 added. Caution: do not use it for production. This feature has not 449 been tested in a heavy way, help wanted. 450 There are known bugs: 451 - It can hang, on a SAMA5D4, after several transfers. 452 - There are some mismtaches with a SAMA5D4 as slave and a SAMA5D2 as 453 master. 454 455config I2C_AU1550 456 tristate "Au1550/Au1200/Au1300 SMBus interface" 457 depends on MIPS_ALCHEMY 458 help 459 If you say yes to this option, support will be included for the 460 Au1550/Au1200/Au1300 SMBus interface. 461 462 This driver can also be built as a module. If so, the module 463 will be called i2c-au1550. 464 465config I2C_AXXIA 466 tristate "Axxia I2C controller" 467 depends on ARCH_AXXIA || COMPILE_TEST 468 default ARCH_AXXIA 469 select I2C_SLAVE 470 help 471 Say yes if you want to support the I2C bus on Axxia platforms. 472 473 Please note that this controller is limited to transfers of maximum 474 255 bytes in length. Any attempt to to a larger transfer will return 475 an error. 476 477config I2C_BCM2835 478 tristate "Broadcom BCM2835 I2C controller" 479 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST 480 depends on COMMON_CLK 481 help 482 If you say yes to this option, support will be included for the 483 BCM2835 I2C controller. 484 485 If you don't know what to do here, say N. 486 487 This support is also available as a module. If so, the module 488 will be called i2c-bcm2835. 489 490config I2C_BCM_IPROC 491 tristate "Broadcom iProc I2C controller" 492 depends on ARCH_BCM_IPROC || COMPILE_TEST 493 default ARCH_BCM_IPROC 494 select I2C_SLAVE 495 help 496 If you say yes to this option, support will be included for the 497 Broadcom iProc I2C controller. 498 499 If you don't know what to do here, say N. 500 501config I2C_BCM_KONA 502 tristate "BCM Kona I2C adapter" 503 depends on ARCH_BCM_MOBILE || COMPILE_TEST 504 default y if ARCH_BCM_MOBILE 505 help 506 If you say yes to this option, support will be included for the 507 I2C interface on the Broadcom Kona family of processors. 508 509 If you do not need KONA I2C interface, say N. 510 511config I2C_BRCMSTB 512 tristate "BRCM Settop/DSL I2C controller" 513 depends on ARCH_BCM2835 || ARCH_BCMBCA || ARCH_BRCMSTB || \ 514 BMIPS_GENERIC || COMPILE_TEST 515 default y 516 help 517 If you say yes to this option, support will be included for the 518 I2C interface on the Broadcom Settop/DSL SoCs. 519 520 If you do not need I2C interface, say N. 521 522config I2C_CADENCE 523 tristate "Cadence I2C Controller" 524 depends on ARCH_ZYNQ || ARM64 || XTENSA || RISCV || COMPILE_TEST 525 help 526 Say yes here to select Cadence I2C Host Controller. This controller is 527 e.g. used by Xilinx Zynq. 528 529config I2C_CBUS_GPIO 530 tristate "CBUS I2C driver" 531 depends on GPIOLIB || COMPILE_TEST 532 help 533 Support for CBUS access using I2C API. Mostly relevant for Nokia 534 Internet Tablets (770, N800 and N810). 535 536 This driver can also be built as a module. If so, the module 537 will be called i2c-cbus-gpio. 538 539config I2C_CPM 540 tristate "Freescale CPM1 or CPM2 (MPC8xx/826x)" 541 depends on CPM1 || CPM2 542 help 543 This supports the use of the I2C interface on Freescale 544 processors with CPM1 or CPM2. 545 546 This driver can also be built as a module. If so, the module 547 will be called i2c-cpm. 548 549config I2C_DAVINCI 550 tristate "DaVinci I2C driver" 551 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST 552 help 553 Support for TI DaVinci I2C controller driver. 554 555 This driver can also be built as a module. If so, the module 556 will be called i2c-davinci. 557 558 Please note that this driver might be needed to bring up other 559 devices such as DaVinci NIC. 560 For details please see http://www.ti.com/davinci 561 562config I2C_DESIGNWARE_CORE 563 tristate "Synopsys DesignWare I2C adapter" 564 select REGMAP 565 help 566 This option enables support for the Synopsys DesignWare I2C adapter. 567 This driver includes support for the I2C host on the Synopsys 568 Designware I2C adapter. 569 570 To compile the driver as a module, choose M here: the module will be 571 called i2c-designware-core. 572 573if I2C_DESIGNWARE_CORE 574 575config I2C_DESIGNWARE_SLAVE 576 bool "Synopsys DesignWare Slave" 577 select I2C_SLAVE 578 help 579 If you say yes to this option, support will be included for the 580 Synopsys DesignWare I2C slave adapter. 581 582config I2C_DESIGNWARE_PLATFORM 583 tristate "Synopsys DesignWare Platform driver" 584 depends on (ACPI && COMMON_CLK) || !ACPI 585 select MFD_SYSCON if MIPS_BAIKAL_T1 586 default I2C_DESIGNWARE_CORE 587 help 588 If you say yes to this option, support will be included for the 589 Synopsys DesignWare I2C adapters on the platform bus. 590 591 This driver can also be built as a module. If so, the module 592 will be called i2c-designware-platform. 593 594config I2C_DESIGNWARE_AMDPSP 595 bool "AMD PSP I2C semaphore support" 596 depends on ACPI 597 depends on CRYPTO_DEV_SP_PSP 598 depends on PCI 599 depends on I2C_DESIGNWARE_PLATFORM 600 depends on (I2C_DESIGNWARE_PLATFORM=y && CRYPTO_DEV_CCP_DD=y) || \ 601 (I2C_DESIGNWARE_PLATFORM=m && CRYPTO_DEV_CCP_DD) 602 help 603 This driver enables managed host access to the selected I2C bus shared 604 between AMD CPU and AMD PSP. 605 606 You should say Y if running on an AMD system equipped with the PSP. 607 608config I2C_DESIGNWARE_BAYTRAIL 609 bool "Intel Baytrail I2C semaphore support" 610 depends on ACPI 611 depends on I2C_DESIGNWARE_PLATFORM 612 depends on (I2C_DESIGNWARE_PLATFORM=m && IOSF_MBI) || \ 613 (I2C_DESIGNWARE_PLATFORM=y && IOSF_MBI=y) 614 help 615 This driver enables managed host access to the PMIC I2C bus on select 616 Intel BayTrail platforms using the X-Powers AXP288 PMIC. It allows 617 the host to request uninterrupted access to the PMIC's I2C bus from 618 the platform firmware controlling it. You should say Y if running on 619 a BayTrail system using the AXP288. 620 621config I2C_DESIGNWARE_PCI 622 tristate "Synopsys DesignWare PCI driver" 623 depends on PCI 624 select I2C_CCGX_UCSI 625 help 626 If you say yes to this option, support will be included for the 627 Synopsys DesignWare I2C adapters on the PCI bus. Only master mode is 628 supported. 629 630 This driver can also be built as a module. If so, the module 631 will be called i2c-designware-pci. 632 633endif 634 635config I2C_DIGICOLOR 636 tristate "Conexant Digicolor I2C driver" 637 depends on ARCH_DIGICOLOR || COMPILE_TEST 638 help 639 Support for Conexant Digicolor SoCs (CX92755) I2C controller driver. 640 641 This driver can also be built as a module. If so, the module 642 will be called i2c-digicolor. 643 644config I2C_EG20T 645 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) I2C" 646 depends on PCI && (X86_32 || MIPS || COMPILE_TEST) 647 help 648 This driver is for PCH(Platform controller Hub) I2C of EG20T which 649 is an IOH(Input/Output Hub) for x86 embedded processor. 650 This driver can access PCH I2C bus device. 651 652 This driver also can be used for LAPIS Semiconductor IOH(Input/ 653 Output Hub), ML7213, ML7223 and ML7831. 654 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is 655 for MP(Media Phone) use and ML7831 IOH is for general purpose use. 656 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 657 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 658 659config I2C_EMEV2 660 tristate "EMMA Mobile series I2C adapter" 661 depends on HAVE_CLK 662 select I2C_SLAVE 663 help 664 If you say yes to this option, support will be included for the 665 I2C interface on the Renesas Electronics EM/EV family of processors. 666 667config I2C_EXYNOS5 668 tristate "Exynos high-speed I2C driver" 669 depends on OF 670 depends on ARCH_EXYNOS || COMPILE_TEST 671 default y if ARCH_EXYNOS 672 help 673 High-speed I2C controller on Samsung Exynos5 and newer Samsung SoCs: 674 Exynos5250, Exynos5260, Exynos5410, Exynos542x, Exynos5800, 675 Exynos5433, Exynos7, Exynos850 and ExynosAutoV9. 676 Choose Y here only if you build for such Samsung SoC. 677 678config I2C_GPIO 679 tristate "GPIO-based bitbanging I2C" 680 depends on GPIOLIB || COMPILE_TEST 681 select I2C_ALGOBIT 682 help 683 This is a very simple bitbanging I2C driver utilizing the 684 arch-neutral GPIO API to control the SCL and SDA lines. 685 686config I2C_GPIO_FAULT_INJECTOR 687 bool "GPIO-based fault injector" 688 depends on I2C_GPIO 689 help 690 This adds some functionality to the i2c-gpio driver which can inject 691 faults to an I2C bus, so another bus master can be stress-tested. 692 This is for debugging. If unsure, say 'no'. 693 694config I2C_GXP 695 tristate "GXP I2C Interface" 696 depends on ARCH_HPE_GXP || COMPILE_TEST 697 help 698 This enables support for GXP I2C interface. The I2C engines can be 699 either I2C master or I2C slaves. 700 701config I2C_HIGHLANDER 702 tristate "Highlander FPGA SMBus interface" 703 depends on SH_HIGHLANDER || COMPILE_TEST 704 help 705 If you say yes to this option, support will be included for 706 the SMBus interface located in the FPGA on various Highlander 707 boards, particularly the R0P7780LC0011RL and R0P7785LC0011RL 708 FPGAs. This is wholly unrelated to the SoC I2C. 709 710 This driver can also be built as a module. If so, the module 711 will be called i2c-highlander. 712 713config I2C_HISI 714 tristate "HiSilicon I2C controller" 715 depends on ARM64 || COMPILE_TEST 716 help 717 Say Y here if you want to have Hisilicon I2C controller support 718 available on the Kunpeng Server. 719 720 This driver can also be built as a module. If so, the module 721 will be called i2c-hisi. 722 723config I2C_IBM_IIC 724 tristate "IBM PPC 4xx on-chip I2C interface" 725 depends on 4xx 726 help 727 Say Y here if you want to use IIC peripheral found on 728 embedded IBM PPC 4xx based systems. 729 730 This driver can also be built as a module. If so, the module 731 will be called i2c-ibm_iic. 732 733config I2C_IMG 734 tristate "Imagination Technologies I2C SCB Controller" 735 depends on MIPS || COMPILE_TEST 736 help 737 Say Y here if you want to use the IMG I2C SCB controller, 738 available on the TZ1090 and other IMG SoCs. 739 740 This driver can also be built as a module. If so, the module 741 will be called i2c-img-scb. 742 743config I2C_IMX 744 tristate "IMX I2C interface" 745 depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE || COMPILE_TEST 746 select I2C_SLAVE 747 help 748 Say Y here if you want to use the IIC bus controller on 749 the Freescale i.MX/MXC, Layerscape or ColdFire processors. 750 751 This driver can also be built as a module. If so, the module 752 will be called i2c-imx. 753 754config I2C_IMX_LPI2C 755 tristate "IMX Low Power I2C interface" 756 depends on ARCH_MXC || COMPILE_TEST 757 help 758 Say Y here if you want to use the Low Power IIC bus controller 759 on the Freescale i.MX processors. 760 761 This driver can also be built as a module. If so, the module 762 will be called i2c-imx-lpi2c. 763 764config I2C_IOP3XX 765 tristate "Intel IXP4xx on-chip I2C interface" 766 depends on ARCH_IXP4XX || COMPILE_TEST 767 help 768 Say Y here if you want to use the IIC bus controller on 769 the Intel IXP4xx Network Processors. 770 771 This driver can also be built as a module. If so, the module 772 will be called i2c-iop3xx. 773 774config I2C_JZ4780 775 tristate "JZ4780 I2C controller interface support" 776 depends on MIPS || COMPILE_TEST 777 help 778 If you say yes to this option, support will be included for the 779 Ingenic JZ4780 I2C controller. 780 781 If you don't know what to do here, say N. 782 783config I2C_KEBA 784 tristate "KEBA I2C controller support" 785 depends on HAS_IOMEM 786 depends on KEBA_CP500 || COMPILE_TEST 787 select AUXILIARY_BUS 788 help 789 This driver supports the I2C controller found in KEBA system FPGA 790 devices. 791 792 This driver can also be built as a module. If so, the module 793 will be called i2c-keba. 794 795config I2C_KEMPLD 796 tristate "Kontron COM I2C Controller" 797 depends on MFD_KEMPLD 798 help 799 This enables support for the I2C bus interface on some Kontron ETX 800 and COMexpress (ETXexpress) modules. 801 802 This driver can also be built as a module. If so, the module 803 will be called i2c-kempld. 804 805config I2C_LPC2K 806 tristate "I2C bus support for NXP LPC2K/LPC178x/18xx/43xx" 807 depends on OF && (ARCH_LPC18XX || COMPILE_TEST) 808 help 809 This driver supports the I2C interface found several NXP 810 devices including LPC2xxx, LPC178x/7x and LPC18xx/43xx. 811 812 This driver can also be built as a module. If so, the module 813 will be called i2c-lpc2k. 814 815config I2C_LS2X 816 tristate "Loongson LS2X I2C adapter" 817 depends on MACH_LOONGSON64 || COMPILE_TEST 818 help 819 If you say yes to this option, support will be included for the 820 I2C interface on the Loongson-2K SoCs and Loongson LS7A bridge 821 chip. 822 823 This driver can also be built as a module. If so, the module 824 will be called i2c-ls2x. 825 826config I2C_MLXBF 827 tristate "Mellanox BlueField I2C controller" 828 depends on MELLANOX_PLATFORM && ARM64 829 depends on ACPI 830 select I2C_SLAVE 831 help 832 Enabling this option will add I2C SMBus support for Mellanox BlueField 833 system. 834 835 This driver can also be built as a module. If so, the module will be 836 called i2c-mlxbf. 837 838 This driver implements an I2C SMBus host controller and enables both 839 master and slave functions. 840 841config I2C_MESON 842 tristate "Amlogic Meson I2C controller" 843 depends on ARCH_MESON || COMPILE_TEST 844 depends on COMMON_CLK 845 help 846 If you say yes to this option, support will be included for the 847 I2C interface on the Amlogic Meson family of SoCs. 848 849config I2C_MICROCHIP_CORE 850 tristate "Microchip FPGA I2C controller" 851 depends on ARCH_MICROCHIP_POLARFIRE || COMPILE_TEST 852 depends on OF 853 help 854 If you say yes to this option, support will be included for the 855 I2C interface on Microchip FPGAs. 856 857 This driver can also be built as a module. If so, the module will be 858 called i2c-microchip-core. 859 860config I2C_MPC 861 tristate "MPC107/824x/85xx/512x/52xx/83xx/86xx" 862 depends on PPC 863 help 864 If you say yes to this option, support will be included for the 865 built-in I2C interface on the MPC107, Tsi107, MPC512x, MPC52xx, 866 MPC8240, MPC8245, MPC83xx, MPC85xx and MPC8641 family processors. 867 868 This driver can also be built as a module. If so, the module 869 will be called i2c-mpc. 870 871config I2C_MT65XX 872 tristate "MediaTek I2C adapter" 873 depends on ARCH_MEDIATEK || COMPILE_TEST 874 help 875 This selects the MediaTek(R) Integrated Inter Circuit bus driver 876 for MT65xx and MT81xx. 877 If you want to use MediaTek(R) I2C interface, say Y or M here. 878 If unsure, say N. 879 880config I2C_MT7621 881 tristate "MT7621/MT7628 I2C Controller" 882 depends on (RALINK && (SOC_MT7620 || SOC_MT7621)) || ARCH_AIROHA || COMPILE_TEST 883 help 884 Say Y here to include support for I2C controller in the 885 MediaTek MT7621/MT7628 SoCs. 886 887config I2C_MV64XXX 888 tristate "Marvell mv64xxx I2C Controller" 889 depends on PLAT_ORION || ARCH_SUNXI || ARCH_MVEBU || COMPILE_TEST 890 help 891 If you say yes to this option, support will be included for the 892 built-in I2C interface on the Marvell 64xxx line of host bridges. 893 This driver is also used for Allwinner SoCs I2C controllers. 894 895 This driver can also be built as a module. If so, the module 896 will be called i2c-mv64xxx. 897 898config I2C_MXS 899 tristate "Freescale i.MX28 I2C interface" 900 depends on SOC_IMX28 || COMPILE_TEST 901 select STMP_DEVICE 902 help 903 Say Y here if you want to use the I2C bus controller on 904 the Freescale i.MX28 processors. 905 906 This driver can also be built as a module. If so, the module 907 will be called i2c-mxs. 908 909config I2C_NOMADIK 910 tristate "ST-Ericsson Nomadik/Ux500 I2C Controller" 911 depends on ARM_AMBA 912 help 913 If you say yes to this option, support will be included for the 914 I2C interface from ST-Ericsson's Nomadik and Ux500 architectures, 915 as well as the STA2X11 PCIe I/O HUB. 916 917config I2C_NPCM 918 tristate "Nuvoton I2C Controller" 919 depends on ARCH_NPCM || COMPILE_TEST 920 help 921 If you say yes to this option, support will be included for the 922 Nuvoton I2C controller, which is available on the NPCM BMC 923 controllers. 924 Driver can also support slave mode (select I2C_SLAVE). 925 926config I2C_OCORES 927 tristate "OpenCores I2C Controller" 928 help 929 If you say yes to this option, support will be included for the 930 OpenCores I2C controller. For details see 931 http://www.opencores.org/projects.cgi/web/i2c/overview 932 933 This driver can also be built as a module. If so, the module 934 will be called i2c-ocores. 935 936config I2C_OMAP 937 tristate "OMAP I2C adapter" 938 depends on ARCH_OMAP || ARCH_K3 || COMPILE_TEST 939 default MACH_OMAP_OSK 940 select MULTIPLEXER 941 help 942 If you say yes to this option, support will be included for the 943 I2C interface on the Texas Instruments OMAP1/2 family of processors. 944 Like OMAP1510/1610/1710/5912 and OMAP242x. 945 For details see http://www.ti.com/omap. 946 947config I2C_OWL 948 tristate "Actions Semiconductor Owl I2C Controller" 949 depends on ARCH_ACTIONS || COMPILE_TEST 950 help 951 Say Y here if you want to use the I2C bus controller on 952 the Actions Semiconductor Owl SoC's. 953 954config I2C_PASEMI 955 tristate "PA Semi SMBus interface" 956 depends on PPC_PASEMI && PCI 957 help 958 Supports the PA Semi PWRficient on-chip SMBus interfaces. 959 960config I2C_APPLE 961 tristate "Apple SMBus platform driver" 962 depends on !I2C_PASEMI 963 depends on ARCH_APPLE || COMPILE_TEST 964 default ARCH_APPLE 965 help 966 Say Y here if you want to use the I2C controller present on Apple 967 Silicon chips such as the M1. 968 969 This driver can also be built as a module. If so, the module 970 will be called i2c-apple. 971 972config I2C_PCA_PLATFORM 973 tristate "PCA9564/PCA9665 as platform device" 974 select I2C_ALGOPCA 975 help 976 This driver supports a memory mapped Philips PCA9564/PCA9665 977 parallel bus to I2C bus controller. 978 979 This driver can also be built as a module. If so, the module 980 will be called i2c-pca-platform. 981 982config I2C_PNX 983 tristate "I2C bus support for Philips PNX and NXP LPC targets" 984 depends on ARCH_LPC32XX || COMPILE_TEST 985 help 986 This driver supports the Philips IP3204 I2C IP block master and/or 987 slave controller 988 989 This driver can also be built as a module. If so, the module 990 will be called i2c-pnx. 991 992config I2C_PXA 993 tristate "Intel PXA2XX I2C adapter" 994 depends on ARCH_PXA || ARCH_MMP || ARCH_MVEBU || (X86_32 && PCI && OF) || COMPILE_TEST 995 help 996 If you have devices in the PXA I2C bus, say yes to this option. 997 This driver can also be built as a module. If so, the module 998 will be called i2c-pxa. 999 1000config I2C_PXA_PCI 1001 def_bool I2C_PXA && X86_32 && PCI && OF 1002 1003config I2C_PXA_SLAVE 1004 bool "Intel PXA2XX I2C Slave comms support" 1005 depends on I2C_PXA && !X86_32 1006 select I2C_SLAVE 1007 help 1008 Support I2C slave mode communications on the PXA I2C bus. This 1009 is necessary for systems where the PXA may be a target on the 1010 I2C bus. 1011 1012config I2C_QCOM_CCI 1013 tristate "Qualcomm Camera Control Interface" 1014 depends on ARCH_QCOM || COMPILE_TEST 1015 help 1016 If you say yes to this option, support will be included for the 1017 built-in camera control interface on the Qualcomm SoCs. 1018 1019 This driver can also be built as a module. If so, the module 1020 will be called i2c-qcom-cci. 1021 1022config I2C_QCOM_GENI 1023 tristate "Qualcomm Technologies Inc.'s GENI based I2C controller" 1024 depends on ARCH_QCOM || COMPILE_TEST 1025 depends on QCOM_GENI_SE 1026 help 1027 This driver supports GENI serial engine based I2C controller in 1028 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say 1029 yes to this option, support will be included for the built-in I2C 1030 interface on the Qualcomm Technologies Inc.'s SoCs. 1031 1032 This driver can also be built as a module. If so, the module 1033 will be called i2c-qcom-geni. 1034 1035config I2C_QUP 1036 tristate "Qualcomm QUP based I2C controller" 1037 depends on ARCH_QCOM || COMPILE_TEST 1038 help 1039 If you say yes to this option, support will be included for the 1040 built-in I2C interface on the Qualcomm SoCs. 1041 1042 This driver can also be built as a module. If so, the module 1043 will be called i2c-qup. 1044 1045config I2C_RIIC 1046 tristate "Renesas RIIC adapter" 1047 depends on ARCH_RENESAS || COMPILE_TEST 1048 help 1049 If you say yes to this option, support will be included for the 1050 Renesas RIIC I2C interface. 1051 1052 This driver can also be built as a module. If so, the module 1053 will be called i2c-riic. 1054 1055config I2C_RK3X 1056 tristate "Rockchip RK3xxx I2C adapter" 1057 depends on OF && COMMON_CLK 1058 help 1059 Say Y here to include support for the I2C adapter in Rockchip RK3xxx 1060 SoCs. 1061 1062 This driver can also be built as a module. If so, the module will 1063 be called i2c-rk3x. 1064 1065config I2C_RZV2M 1066 tristate "Renesas RZ/V2M adapter" 1067 depends on ARCH_RENESAS || COMPILE_TEST 1068 help 1069 If you say yes to this option, support will be included for the 1070 Renesas RZ/V2M I2C interface. 1071 1072 This driver can also be built as a module. If so, the module 1073 will be called i2c-rzv2m. 1074 1075config I2C_S3C2410 1076 tristate "S3C/Exynos I2C Driver" 1077 depends on ARCH_EXYNOS || ARCH_S3C64XX || ARCH_S5PV210 || COMPILE_TEST 1078 help 1079 Say Y here to include support for I2C controller in the 1080 Samsung SoCs (S3C, S5Pv210, Exynos). 1081 1082config I2C_SH7760 1083 tristate "Renesas SH7760 I2C Controller" 1084 depends on CPU_SUBTYPE_SH7760 1085 help 1086 This driver supports the 2 I2C interfaces on the Renesas SH7760. 1087 1088 This driver can also be built as a module. If so, the module 1089 will be called i2c-sh7760. 1090 1091config I2C_SH_MOBILE 1092 tristate "SuperH Mobile I2C Controller" 1093 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST 1094 help 1095 If you say yes to this option, support will be included for the 1096 built-in I2C interface on the Renesas SH-Mobile processor. 1097 1098 This driver can also be built as a module. If so, the module 1099 will be called i2c-sh_mobile. 1100 1101config I2C_SIMTEC 1102 tristate "Simtec Generic I2C interface" 1103 select I2C_ALGOBIT 1104 help 1105 If you say yes to this option, support will be included for 1106 the Simtec Generic I2C interface. This driver is for the 1107 simple I2C bus used on newer Simtec products for general 1108 I2C, such as DDC on the Simtec BBD2016A. 1109 1110 This driver can also be built as a module. If so, the module 1111 will be called i2c-simtec. 1112 1113config I2C_SPRD 1114 tristate "Spreadtrum I2C interface" 1115 depends on I2C=y && (ARCH_SPRD || COMPILE_TEST) 1116 depends on COMMON_CLK 1117 help 1118 If you say yes to this option, support will be included for the 1119 Spreadtrum I2C interface. 1120 1121config I2C_ST 1122 tristate "STMicroelectronics SSC I2C support" 1123 depends on ARCH_STI || COMPILE_TEST 1124 help 1125 Enable this option to add support for STMicroelectronics SoCs 1126 hardware SSC (Synchronous Serial Controller) as an I2C controller. 1127 1128 This driver can also be built as module. If so, the module 1129 will be called i2c-st. 1130 1131config I2C_STM32F4 1132 tristate "STMicroelectronics STM32F4 I2C support" 1133 depends on ARCH_STM32 || COMPILE_TEST 1134 help 1135 Enable this option to add support for STM32 I2C controller embedded 1136 in STM32F4 SoCs. 1137 1138 This driver can also be built as module. If so, the module 1139 will be called i2c-stm32f4. 1140 1141config I2C_STM32F7 1142 tristate "STMicroelectronics STM32F7 I2C support" 1143 depends on ARCH_STM32 || COMPILE_TEST 1144 select I2C_SLAVE 1145 select I2C_SMBUS 1146 help 1147 Enable this option to add support for STM32 I2C controller embedded 1148 in STM32F7 SoCs. 1149 1150 This driver can also be built as module. If so, the module 1151 will be called i2c-stm32f7. 1152 1153config I2C_SUN6I_P2WI 1154 tristate "Allwinner sun6i internal P2WI controller" 1155 depends on RESET_CONTROLLER 1156 depends on MACH_SUN6I || COMPILE_TEST 1157 help 1158 If you say yes to this option, support will be included for the 1159 P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi 1160 SOCs. 1161 The P2WI looks like an SMBus controller (which supports only byte 1162 accesses), except that it only supports one slave device. 1163 This interface is used to connect to specific PMIC devices (like the 1164 AXP221). 1165 1166config I2C_SYNQUACER 1167 tristate "Socionext SynQuacer I2C controller" 1168 depends on ARCH_SYNQUACER || COMPILE_TEST 1169 help 1170 Say Y here to include support for the I2C controller used in some 1171 Fujitsu and Socionext SoCs. 1172 1173 This driver can also be built as a module. If so, the module 1174 will be called i2c-synquacer. 1175 1176config I2C_TEGRA 1177 tristate "NVIDIA Tegra internal I2C controller" 1178 depends on ARCH_TEGRA || (COMPILE_TEST && (ARC || ARM || ARM64 || M68K || RISCV || SUPERH || SPARC)) 1179 # COMPILE_TEST needs architectures with readsX()/writesX() primitives 1180 help 1181 If you say yes to this option, support will be included for the 1182 I2C controller embedded in NVIDIA Tegra SOCs 1183 1184config I2C_TEGRA_BPMP 1185 tristate "NVIDIA Tegra BPMP I2C controller" 1186 depends on TEGRA_BPMP || COMPILE_TEST 1187 default y if TEGRA_BPMP 1188 help 1189 If you say yes to this option, support will be included for the I2C 1190 controller embedded in NVIDIA Tegra SoCs accessed via the BPMP. 1191 1192 This I2C driver is a 'virtual' I2C driver. The real driver is part 1193 of the BPMP firmware, and this driver merely communicates with that 1194 real driver. 1195 1196config I2C_UNIPHIER 1197 tristate "UniPhier FIFO-less I2C controller" 1198 depends on ARCH_UNIPHIER || COMPILE_TEST 1199 help 1200 If you say yes to this option, support will be included for 1201 the UniPhier FIFO-less I2C interface embedded in PH1-LD4, PH1-sLD8, 1202 or older UniPhier SoCs. 1203 1204config I2C_UNIPHIER_F 1205 tristate "UniPhier FIFO-builtin I2C controller" 1206 depends on ARCH_UNIPHIER || COMPILE_TEST 1207 help 1208 If you say yes to this option, support will be included for 1209 the UniPhier FIFO-builtin I2C interface embedded in PH1-Pro4, 1210 PH1-Pro5, or newer UniPhier SoCs. 1211 1212config I2C_VERSATILE 1213 tristate "ARM Versatile/Realview I2C bus support" 1214 depends on ARCH_MPS2 || ARCH_VERSATILE || ARCH_REALVIEW || ARCH_VEXPRESS || COMPILE_TEST 1215 select I2C_ALGOBIT 1216 help 1217 Say yes if you want to support the I2C serial bus on ARMs Versatile 1218 range of platforms. 1219 1220 This driver can also be built as a module. If so, the module 1221 will be called i2c-versatile. 1222 1223config I2C_WMT 1224 tristate "Wondermedia WM8xxx SoC I2C bus support" 1225 depends on ARCH_VT8500 || COMPILE_TEST 1226 help 1227 Say yes if you want to support the I2C bus on Wondermedia 8xxx-series 1228 SoCs. 1229 1230 This driver can also be built as a module. If so, the module will be 1231 called i2c-wmt. 1232 1233config I2C_OCTEON 1234 tristate "Cavium OCTEON I2C bus support" 1235 depends on CAVIUM_OCTEON_SOC 1236 help 1237 Say yes if you want to support the I2C serial bus on Cavium 1238 OCTEON SOC. 1239 1240 This driver can also be built as a module. If so, the module 1241 will be called i2c-octeon. 1242 1243config I2C_THUNDERX 1244 tristate "Cavium ThunderX I2C bus support" 1245 depends on 64BIT && PCI && (ARM64 || COMPILE_TEST) 1246 select I2C_SMBUS 1247 help 1248 Say yes if you want to support the I2C serial bus on Cavium 1249 ThunderX SOC. 1250 1251 This driver can also be built as a module. If so, the module 1252 will be called i2c-thunderx. 1253 1254config I2C_XILINX 1255 tristate "Xilinx I2C Controller" 1256 depends on HAS_IOMEM 1257 help 1258 If you say yes to this option, support will be included for the 1259 Xilinx I2C controller. 1260 1261 This driver can also be built as a module. If so, the module 1262 will be called xilinx_i2c. 1263 1264config I2C_XLP9XX 1265 tristate "Cavium ThunderX2 I2C support" 1266 depends on ARCH_THUNDER2 || COMPILE_TEST 1267 help 1268 This driver enables support for the on-chip I2C interface of 1269 the Cavium ThunderX2 processors. (Originally on Netlogic XLP SoCs.) 1270 1271 This driver can also be built as a module. If so, the module will 1272 be called i2c-xlp9xx. 1273 1274config I2C_RCAR 1275 tristate "Renesas R-Car I2C Controller" 1276 depends on ARCH_RENESAS || COMPILE_TEST 1277 select I2C_SLAVE 1278 select I2C_SMBUS 1279 select RESET_CONTROLLER if ARCH_RCAR_GEN3 || ARCH_RCAR_GEN4 1280 help 1281 If you say yes to this option, support will be included for the 1282 R-Car I2C controller. 1283 1284 This driver can also be built as a module. If so, the module 1285 will be called i2c-rcar. 1286 1287comment "External I2C/SMBus adapter drivers" 1288 1289config I2C_DIOLAN_U2C 1290 tristate "Diolan U2C-12 USB adapter" 1291 depends on USB 1292 help 1293 If you say yes to this option, support will be included for Diolan 1294 U2C-12, a USB to I2C interface. 1295 1296 This driver can also be built as a module. If so, the module 1297 will be called i2c-diolan-u2c. 1298 1299config I2C_DLN2 1300 tristate "Diolan DLN-2 USB I2C adapter" 1301 depends on MFD_DLN2 1302 help 1303 If you say yes to this option, support will be included for Diolan 1304 DLN2, a USB to I2C interface. 1305 1306 This driver can also be built as a module. If so, the module 1307 will be called i2c-dln2. 1308 1309config I2C_LJCA 1310 tristate "I2C functionality of Intel La Jolla Cove Adapter" 1311 depends on USB_LJCA 1312 default USB_LJCA 1313 help 1314 If you say yes to this option, I2C functionality support of Intel 1315 La Jolla Cove Adapter (LJCA) will be included. 1316 1317 This driver can also be built as a module. If so, the module 1318 will be called i2c-ljca. 1319 1320config I2C_CP2615 1321 tristate "Silicon Labs CP2615 USB sound card and I2C adapter" 1322 depends on USB 1323 help 1324 If you say yes to this option, support will be included for Silicon 1325 Labs CP2615's I2C interface. 1326 1327 This driver can also be built as a module. If so, the module 1328 will be called i2c-cp2615. 1329 1330config I2C_PARPORT 1331 tristate "Parallel port adapter" 1332 depends on PARPORT 1333 select I2C_ALGOBIT 1334 select I2C_SMBUS 1335 help 1336 This supports parallel port I2C adapters such as the ones made by 1337 Philips or Velleman, Analog Devices evaluation boards, and more. 1338 Basically any adapter using the parallel port as an I2C bus with 1339 no extra chipset is supported by this driver, or could be. Please 1340 read the file Documentation/i2c/busses/i2c-parport.rst for details. 1341 1342 This support is also available as a module. If so, the module 1343 will be called i2c-parport. 1344 1345config I2C_PCI1XXXX 1346 tristate "PCI1XXXX I2C Host Adapter" 1347 depends on PCI 1348 help 1349 If you say yes to this option, support will be included for 1350 Microchip PCI1XXXX's I2C interface. 1351 1352 This driver can also be built as a module. If so, the module will 1353 be called i2c-mchp-pci1xxxx. 1354 1355config I2C_ROBOTFUZZ_OSIF 1356 tristate "RobotFuzz Open Source InterFace USB adapter" 1357 depends on USB 1358 help 1359 If you say yes to this option, support will be included for the 1360 RobotFuzz Open Source InterFace USB to I2C interface. 1361 1362 This driver can also be built as a module. If so, the module 1363 will be called i2c-osif. 1364 1365config I2C_TAOS_EVM 1366 tristate "TAOS evaluation module" 1367 depends on TTY 1368 select SERIO 1369 select SERIO_SERPORT 1370 help 1371 This supports TAOS evaluation modules on serial port. In order to 1372 use this driver, you will need the inputattach tool, which is part 1373 of the input-utils package. 1374 1375 If unsure, say N. 1376 1377 This support is also available as a module. If so, the module 1378 will be called i2c-taos-evm. 1379 1380config I2C_TINY_USB 1381 tristate "Tiny-USB adapter" 1382 depends on USB 1383 help 1384 If you say yes to this option, support will be included for the 1385 i2c-tiny-usb, a simple do-it-yourself USB to I2C interface. See 1386 http://www.harbaum.org/till/i2c_tiny_usb for hardware details. 1387 1388 This driver can also be built as a module. If so, the module 1389 will be called i2c-tiny-usb. 1390 1391config I2C_VIPERBOARD 1392 tristate "Viperboard I2C master support" 1393 depends on MFD_VIPERBOARD && USB 1394 help 1395 Say yes here to access the I2C part of the Nano River 1396 Technologies Viperboard as I2C master. 1397 See viperboard API specification and Nano 1398 River Tech's viperboard.h for detailed meaning 1399 of the module parameters. 1400 1401comment "Other I2C/SMBus bus drivers" 1402 1403config I2C_ACORN 1404 tristate "Acorn IOC/IOMD I2C bus support" 1405 depends on ARCH_ACORN 1406 default y 1407 select I2C_ALGOBIT 1408 help 1409 Say yes if you want to support the I2C bus on Acorn platforms. 1410 1411 If you don't know, say Y. 1412 1413config I2C_ELEKTOR 1414 tristate "Elektor ISA card" 1415 depends on ISA && HAS_IOPORT_MAP && BROKEN_ON_SMP 1416 select I2C_ALGOPCF 1417 help 1418 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own 1419 such an adapter. 1420 1421 This support is also available as a module. If so, the module 1422 will be called i2c-elektor. 1423 1424config I2C_ICY 1425 tristate "ICY Zorro card" 1426 depends on ZORRO 1427 select I2C_ALGOPCF 1428 help 1429 This supports the PCF8584 Zorro bus I2C adapter, known as ICY. 1430 Say Y if you own such an adapter. 1431 1432 This support is also available as a module. If so, the module 1433 will be called i2c-icy. 1434 1435 If you have a 2019 edition board with an LTC2990 sensor at address 1436 0x4c, loading the module 'ltc2990' is sufficient to enable it. 1437 1438config I2C_MLXCPLD 1439 tristate "Mellanox I2C driver" 1440 depends on X86_64 || (ARM64 && ACPI) || COMPILE_TEST 1441 depends on HAS_IOPORT 1442 help 1443 This exposes the Mellanox platform I2C busses to the linux I2C layer 1444 for X86 and ARM64/ACPI based systems. 1445 Controller is implemented as CPLD logic. 1446 1447 This driver can also be built as a module. If so, the module will be 1448 called as i2c-mlxcpld. 1449 1450config I2C_PCA_ISA 1451 tristate "PCA9564/PCA9665 on an ISA bus" 1452 depends on ISA 1453 select I2C_ALGOPCA 1454 help 1455 This driver supports ISA boards using the Philips PCA9564/PCA9665 1456 parallel bus to I2C bus controller. 1457 1458 This driver can also be built as a module. If so, the module 1459 will be called i2c-pca-isa. 1460 1461 This device is almost undetectable and using this driver on a 1462 system which doesn't have this device will result in long 1463 delays when I2C/SMBus chip drivers are loaded (e.g. at boot 1464 time). If unsure, say N. 1465 1466config I2C_SIBYTE 1467 tristate "SiByte SMBus interface" 1468 depends on SIBYTE_SB1xxx_SOC 1469 help 1470 Supports the SiByte SOC on-chip I2C interfaces (2 channels). 1471 1472config I2C_CROS_EC_TUNNEL 1473 tristate "ChromeOS EC tunnel I2C bus" 1474 depends on CROS_EC 1475 help 1476 If you say yes here you get an I2C bus that will tunnel i2c commands 1477 through to the other side of the ChromeOS EC to the i2c bus 1478 connected there. This will work whatever the interface used to 1479 talk to the EC (SPI, I2C or LPC). 1480 1481config I2C_XGENE_SLIMPRO 1482 tristate "APM X-Gene SoC I2C SLIMpro devices support" 1483 depends on ARCH_XGENE && MAILBOX 1484 help 1485 Enable I2C bus access using the APM X-Gene SoC SLIMpro 1486 co-processor. The I2C device access the I2C bus via the X-Gene 1487 to SLIMpro (On chip coprocessor) mailbox mechanism. 1488 If unsure, say N. 1489 1490config SCx200_ACB 1491 tristate "Geode ACCESS.bus support" 1492 depends on X86_32 && PCI 1493 help 1494 Enable the use of the ACCESS.bus controllers on the Geode SCx200 and 1495 SC1100 processors and the CS5535 and CS5536 Geode companion devices. 1496 1497 If you don't know what to do here, say N. 1498 1499 This support is also available as a module. If so, the module 1500 will be called scx200_acb. 1501 1502config I2C_OPAL 1503 tristate "IBM OPAL I2C driver" 1504 depends on PPC_POWERNV 1505 default y 1506 help 1507 This exposes the PowerNV platform i2c busses to the linux i2c layer, 1508 the driver is based on the OPAL interfaces. 1509 1510 This driver can also be built as a module. If so, the module will be 1511 called as i2c-opal. 1512 1513config I2C_FSI 1514 tristate "FSI I2C driver" 1515 depends on FSI 1516 help 1517 Driver for FSI bus attached I2C masters. These are I2C masters that 1518 are connected to the system over an FSI bus, instead of the more 1519 common PCI or MMIO interface. 1520 1521 This driver can also be built as a module. If so, the module will be 1522 called as i2c-fsi. 1523 1524config I2C_VIRTIO 1525 tristate "Virtio I2C Adapter" 1526 select VIRTIO 1527 help 1528 If you say yes to this option, support will be included for the virtio 1529 I2C adapter driver. The hardware can be emulated by any device model 1530 software according to the virtio protocol. 1531 1532 This driver can also be built as a module. If so, the module 1533 will be called i2c-virtio. 1534 1535endmenu 1536