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