1# SPDX-License-Identifier: GPL-2.0-only 2# 3# SPI driver configuration 4# 5menuconfig SPI 6 bool "SPI support" 7 depends on HAS_IOMEM 8 help 9 The "Serial Peripheral Interface" is a low level synchronous 10 protocol. Chips that support SPI can have data transfer rates 11 up to several tens of Mbit/sec. Chips are addressed with a 12 controller and a chipselect. Most SPI slaves don't support 13 dynamic device discovery; some are even write-only or read-only. 14 15 SPI is widely used by microcontrollers to talk with sensors, 16 eeprom and flash memory, codecs and various other controller 17 chips, analog to digital (and d-to-a) converters, and more. 18 MMC and SD cards can be accessed using SPI protocol; and for 19 DataFlash cards used in MMC sockets, SPI must always be used. 20 21 SPI is one of a family of similar protocols using a four wire 22 interface (select, clock, data in, data out) including Microwire 23 (half duplex), SSP, SSI, and PSP. This driver framework should 24 work with most such devices and controllers. 25 26if SPI 27 28config SPI_DEBUG 29 bool "Debug support for SPI drivers" 30 depends on DEBUG_KERNEL 31 help 32 Say "yes" to enable debug messaging (like dev_dbg and pr_debug), 33 sysfs, and debugfs support in SPI controller and protocol drivers. 34 35# 36# MASTER side ... talking to discrete SPI slave chips including microcontrollers 37# 38 39config SPI_MASTER 40# bool "SPI Master Support" 41 bool 42 default SPI 43 help 44 If your system has an master-capable SPI controller (which 45 provides the clock and chipselect), you can enable that 46 controller and the protocol drivers for the SPI slave chips 47 that are connected. 48 49if SPI_MASTER 50 51config SPI_MEM 52 bool "SPI memory extension" 53 help 54 Enable this option if you want to enable the SPI memory extension. 55 This extension is meant to simplify interaction with SPI memories 56 by providing a high-level interface to send memory-like commands. 57 58comment "SPI Master Controller Drivers" 59 60config SPI_ALTERA 61 tristate "Altera SPI Controller platform driver" 62 select SPI_ALTERA_CORE 63 select REGMAP_MMIO 64 help 65 This is the driver for the Altera SPI Controller. 66 67config SPI_ALTERA_CORE 68 tristate "Altera SPI Controller core code" if COMPILE_TEST 69 select REGMAP 70 help 71 "The core code for the Altera SPI Controller" 72 73config SPI_ALTERA_DFL 74 tristate "DFL bus driver for Altera SPI Controller" 75 depends on FPGA_DFL 76 select SPI_ALTERA_CORE 77 help 78 This is a Device Feature List (DFL) bus driver for the 79 Altera SPI master controller. The SPI master is connected 80 to a SPI slave to Avalon bridge in a Intel MAX BMC. 81 82config SPI_AMLOGIC_SPIFC_A1 83 tristate "Amlogic A1 SPIFC controller" 84 depends on ARCH_MESON || COMPILE_TEST 85 help 86 This enables master mode support for the SPIFC (SPI flash 87 controller) available in Amlogic A1 (A113L SoC). 88 89config SPI_AR934X 90 tristate "Qualcomm Atheros AR934X/QCA95XX SPI controller driver" 91 depends on ATH79 || COMPILE_TEST 92 help 93 This enables support for the SPI controller present on the 94 Qualcomm Atheros AR934X/QCA95XX SoCs. 95 96config SPI_ATH79 97 tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver" 98 depends on ATH79 || COMPILE_TEST 99 select SPI_BITBANG 100 help 101 This enables support for the SPI controller present on the 102 Atheros AR71XX/AR724X/AR913X SoCs. 103 104config SPI_ARMADA_3700 105 tristate "Marvell Armada 3700 SPI Controller" 106 depends on (ARCH_MVEBU && OF) || COMPILE_TEST 107 help 108 This enables support for the SPI controller present on the 109 Marvell Armada 3700 SoCs. 110 111config SPI_ASPEED_SMC 112 tristate "Aspeed flash controllers in SPI mode" 113 depends on ARCH_ASPEED || COMPILE_TEST 114 depends on OF 115 help 116 This enables support for the Firmware Memory controller (FMC) 117 in the Aspeed AST2600, AST2500 and AST2400 SoCs when attached 118 to SPI NOR chips, and support for the SPI flash memory 119 controller (SPI) for the host firmware. The implementation 120 only supports SPI NOR. 121 122config SPI_ATMEL 123 tristate "Atmel SPI Controller" 124 depends on ARCH_AT91 || COMPILE_TEST 125 depends on OF 126 help 127 This selects a driver for the Atmel SPI Controller, present on 128 many AT91 ARM chips. 129 130config SPI_AT91_USART 131 tristate "Atmel USART Controller SPI driver" 132 depends on (ARCH_AT91 || COMPILE_TEST) 133 depends on MFD_AT91_USART 134 help 135 This selects a driver for the AT91 USART Controller as SPI Master, 136 present on AT91 and SAMA5 SoC series. 137 138config SPI_ATMEL_QUADSPI 139 tristate "Atmel Quad SPI Controller" 140 depends on ARCH_AT91 || COMPILE_TEST 141 depends on OF && HAS_IOMEM 142 help 143 This enables support for the Quad SPI controller in master mode. 144 This driver does not support generic SPI. The implementation only 145 supports spi-mem interface. 146 147config SPI_AU1550 148 tristate "Au1550/Au1200/Au1300 SPI Controller" 149 depends on MIPS_ALCHEMY 150 select SPI_BITBANG 151 help 152 If you say yes to this option, support will be included for the 153 PSC SPI controller found on Au1550, Au1200 and Au1300 series. 154 155config SPI_AXI_SPI_ENGINE 156 tristate "Analog Devices AXI SPI Engine controller" 157 depends on HAS_IOMEM 158 help 159 This enables support for the Analog Devices AXI SPI Engine SPI controller. 160 It is part of the SPI Engine framework that is used in some Analog Devices 161 reference designs for FPGAs. 162 163config SPI_BCM2835 164 tristate "BCM2835 SPI controller" 165 depends on GPIOLIB 166 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST 167 help 168 This selects a driver for the Broadcom BCM2835 SPI master. 169 170 The BCM2835 contains two types of SPI master controller; the 171 "universal SPI master", and the regular SPI controller. This driver 172 is for the regular SPI controller. Slave mode operation is not also 173 not supported. 174 175config SPI_BCM2835AUX 176 tristate "BCM2835 SPI auxiliary controller" 177 depends on ((ARCH_BCM2835 || ARCH_BRCMSTB) && GPIOLIB) || COMPILE_TEST 178 help 179 This selects a driver for the Broadcom BCM2835 SPI aux master. 180 181 The BCM2835 contains two types of SPI master controller; the 182 "universal SPI master", and the regular SPI controller. 183 This driver is for the universal/auxiliary SPI controller. 184 185config SPI_BCM63XX 186 tristate "Broadcom BCM63xx SPI controller" 187 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST 188 help 189 Enable support for the SPI controller on the Broadcom BCM63xx SoCs. 190 191config SPI_BCM63XX_HSSPI 192 tristate "Broadcom BCM63XX HS SPI controller driver" 193 depends on BCM63XX || BMIPS_GENERIC || ARCH_BCMBCA || COMPILE_TEST 194 help 195 This enables support for the High Speed SPI controller present on 196 newer Broadcom BCM63XX SoCs. 197 198config SPI_BCM_QSPI 199 tristate "Broadcom BSPI and MSPI controller support" 200 depends on ARCH_BRCMSTB || ARCH_BCM || ARCH_BCM_IPROC || \ 201 BMIPS_GENERIC || COMPILE_TEST 202 default ARCH_BCM_IPROC 203 help 204 Enables support for the Broadcom SPI flash and MSPI controller. 205 Select this option for any one of BRCMSTB, iProc NSP and NS2 SoCs 206 based platforms. This driver works for both SPI master for SPI NOR 207 flash device as well as MSPI device. 208 209config SPI_BCMBCA_HSSPI 210 tristate "Broadcom BCMBCA HS SPI controller driver" 211 depends on ARCH_BCMBCA || COMPILE_TEST 212 help 213 This enables support for the High Speed SPI controller present on 214 newer Broadcom BCMBCA SoCs. These SoCs include an updated SPI controller 215 that adds the capability to allow the driver to control chip select 216 explicitly. 217 218config SPI_BITBANG 219 tristate "Utilities for Bitbanging SPI masters" 220 help 221 With a few GPIO pins, your system can bitbang the SPI protocol. 222 Select this to get SPI support through I/O pins (GPIO, parallel 223 port, etc). Or, some systems' SPI master controller drivers use 224 this code to manage the per-word or per-transfer accesses to the 225 hardware shift registers. 226 227 This is library code, and is automatically selected by drivers that 228 need it. You only need to select this explicitly to support driver 229 modules that aren't part of this kernel tree. 230 231config SPI_BUTTERFLY 232 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" 233 depends on PARPORT 234 select SPI_BITBANG 235 help 236 This uses a custom parallel port cable to connect to an AVR 237 Butterfly <http://www.atmel.com/products/avr/butterfly>, an 238 inexpensive battery powered microcontroller evaluation board. 239 This same cable can be used to flash new firmware. 240 241config SPI_CADENCE 242 tristate "Cadence SPI controller" 243 help 244 This selects the Cadence SPI controller master driver 245 used by Xilinx Zynq and ZynqMP. 246 247config SPI_CADENCE_QUADSPI 248 tristate "Cadence Quad SPI controller" 249 depends on OF && (ARM || ARM64 || X86 || RISCV || COMPILE_TEST) 250 help 251 Enable support for the Cadence Quad SPI Flash controller. 252 253 Cadence QSPI is a specialized controller for connecting an SPI 254 Flash over 1/2/4-bit wide bus. Enable this option if you have a 255 device with a Cadence QSPI controller and want to access the 256 Flash as an MTD device. 257 258config SPI_CADENCE_XSPI 259 tristate "Cadence XSPI controller" 260 depends on OF && HAS_IOMEM 261 depends on SPI_MEM 262 help 263 Enable support for the Cadence XSPI Flash controller. 264 265 Cadence XSPI is a specialized controller for connecting an SPI 266 Flash over up to 8-bit wide bus. Enable this option if you have a 267 device with a Cadence XSPI controller and want to access the 268 Flash as an MTD device. 269 270config SPI_CLPS711X 271 tristate "CLPS711X host SPI controller" 272 depends on ARCH_CLPS711X || COMPILE_TEST 273 help 274 This enables dedicated general purpose SPI/Microwire1-compatible 275 master mode interface (SSI1) for CLPS711X-based CPUs. 276 277config SPI_COLDFIRE_QSPI 278 tristate "Freescale Coldfire QSPI controller" 279 depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x) 280 help 281 This enables support for the Coldfire QSPI controller in master 282 mode. 283 284config SPI_CS42L43 285 tristate "Cirrus Logic CS42L43 SPI controller" 286 depends on MFD_CS42L43 && PINCTRL_CS42L43 287 help 288 This enables support for the SPI controller inside the Cirrus Logic 289 CS42L43 audio codec. 290 291config SPI_DAVINCI 292 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller" 293 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST 294 select SPI_BITBANG 295 help 296 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules. 297 298config SPI_DESIGNWARE 299 tristate "DesignWare SPI controller core support" 300 imply SPI_MEM 301 help 302 general driver for SPI controller core from DesignWare 303 304if SPI_DESIGNWARE 305 306config SPI_DW_DMA 307 bool "DMA support for DW SPI controller" 308 309config SPI_DW_PCI 310 tristate "PCI interface driver for DW SPI core" 311 depends on PCI 312 313config SPI_DW_MMIO 314 tristate "Memory-mapped io interface driver for DW SPI core" 315 depends on HAS_IOMEM 316 317config SPI_DW_BT1 318 tristate "Baikal-T1 SPI driver for DW SPI core" 319 depends on MIPS_BAIKAL_T1 || COMPILE_TEST 320 select MULTIPLEXER 321 help 322 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI 323 controllers. Two of them are pretty much normal: with IRQ, DMA, 324 FIFOs of 64 words depth, 4x CSs, but the third one as being a 325 part of the Baikal-T1 System Boot Controller has got a very 326 limited resources: no IRQ, no DMA, only a single native 327 chip-select and Tx/Rx FIFO with just 8 words depth available. 328 The later one is normally connected to an external SPI-nor flash 329 of 128Mb (in general can be of bigger size). 330 331config SPI_DW_BT1_DIRMAP 332 bool "Directly mapped Baikal-T1 Boot SPI flash support" 333 depends on SPI_DW_BT1 334 help 335 Directly mapped SPI flash memory is an interface specific to the 336 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which 337 can be used to access a peripheral memory device just by 338 reading/writing data from/to it. Note that the system APB bus 339 will stall during each IO from/to the dirmap region until the 340 operation is finished. So try not to use it concurrently with 341 time-critical tasks (like the SPI memory operations implemented 342 in this driver). 343 344endif 345 346config SPI_DLN2 347 tristate "Diolan DLN-2 USB SPI adapter" 348 depends on MFD_DLN2 349 help 350 If you say yes to this option, support will be included for Diolan 351 DLN2, a USB to SPI interface. 352 353 This driver can also be built as a module. If so, the module 354 will be called spi-dln2. 355 356config SPI_EP93XX 357 tristate "Cirrus Logic EP93xx SPI controller" 358 depends on ARCH_EP93XX || COMPILE_TEST 359 help 360 This enables using the Cirrus EP93xx SPI controller in master 361 mode. 362 363config SPI_FALCON 364 bool "Falcon SPI controller support" 365 depends on SOC_FALCON 366 help 367 The external bus unit (EBU) found on the FALC-ON SoC has SPI 368 emulation that is designed for serial flash access. This driver 369 has only been tested with m25p80 type chips. The hardware has no 370 support for other types of SPI peripherals. 371 372config SPI_FSI 373 tristate "FSI SPI driver" 374 depends on FSI 375 help 376 This enables support for the driver for FSI bus attached SPI 377 controllers. 378 379config SPI_FSL_LPSPI 380 tristate "Freescale i.MX LPSPI controller" 381 depends on ARCH_MXC || COMPILE_TEST 382 help 383 This enables Freescale i.MX LPSPI controllers in master mode. 384 385config SPI_FSL_QUADSPI 386 tristate "Freescale QSPI controller" 387 depends on ARCH_MXC || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST 388 depends on HAS_IOMEM 389 help 390 This enables support for the Quad SPI controller in master mode. 391 Up to four flash chips can be connected on two buses with two 392 chipselects each. 393 This controller does not support generic SPI messages. It only 394 supports the high-level SPI memory interface. 395 396config SPI_GXP 397 tristate "GXP SPI driver" 398 depends on ARCH_HPE || COMPILE_TEST 399 help 400 This enables support for the driver for GXP bus attached SPI 401 controllers. 402 403config SPI_HISI_KUNPENG 404 tristate "HiSilicon SPI Controller for Kunpeng SoCs" 405 depends on (ARM64 && ACPI) || COMPILE_TEST 406 help 407 This enables support for HiSilicon SPI controller found on 408 Kunpeng SoCs. 409 410 This driver can also be built as a module. If so, the module 411 will be called hisi-kunpeng-spi. 412 413config SPI_HISI_SFC_V3XX 414 tristate "HiSilicon SPI NOR Flash Controller for Hi16XX chipsets" 415 depends on (ARM64 && ACPI) || COMPILE_TEST 416 depends on HAS_IOMEM 417 help 418 This enables support for HiSilicon v3xx SPI NOR flash controller 419 found in hi16xx chipsets. 420 421config SPI_NXP_FLEXSPI 422 tristate "NXP Flex SPI controller" 423 depends on ARCH_LAYERSCAPE || ARCH_MXC || COMPILE_TEST 424 depends on HAS_IOMEM 425 help 426 This enables support for the Flex SPI controller in master mode. 427 Up to four slave devices can be connected on two buses with two 428 chipselects each. 429 This controller does not support generic SPI messages and only 430 supports the high-level SPI memory interface. 431 432config SPI_GPIO 433 tristate "GPIO-based bitbanging SPI Master" 434 depends on GPIOLIB || COMPILE_TEST 435 select SPI_BITBANG 436 help 437 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO 438 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI 439 slaves connected to a bus using this driver are configured as usual, 440 except that the spi_board_info.controller_data holds the GPIO number 441 for the chipselect used by this controller driver. 442 443 Note that this driver often won't achieve even 1 Mbit/sec speeds, 444 making it unusually slow for SPI. If your platform can inline 445 GPIO operations, you should be able to leverage that for better 446 speed with a custom version of this driver; see the source code. 447 448config SPI_IMG_SPFI 449 tristate "IMG SPFI controller" 450 depends on MIPS || COMPILE_TEST 451 help 452 This enables support for the SPFI master controller found on 453 IMG SoCs. 454 455config SPI_IMX 456 tristate "Freescale i.MX SPI controllers" 457 depends on ARCH_MXC || COMPILE_TEST 458 help 459 This enables support for the Freescale i.MX SPI controllers. 460 461config SPI_INGENIC 462 tristate "Ingenic SoCs SPI controller" 463 depends on MACH_INGENIC || COMPILE_TEST 464 help 465 This enables support for the Ingenic SoCs SPI controller. 466 467 To compile this driver as a module, choose M here: the module 468 will be called spi-ingenic. 469 470config SPI_INTEL 471 tristate 472 473config SPI_INTEL_PCI 474 tristate "Intel PCH/PCU SPI flash PCI driver" 475 depends on PCI 476 depends on X86 || COMPILE_TEST 477 depends on SPI_MEM 478 select SPI_INTEL 479 help 480 This enables PCI support for the Intel PCH/PCU SPI controller in 481 master mode. This controller is used to hold BIOS and other 482 persistent settings. Controllers present in modern Intel hardware 483 only work in hardware sequencing mode, this means that the 484 controller exposes a subset of operations that makes it safer to 485 use. Using this driver it is possible to upgrade BIOS directly 486 from Linux. 487 488 To compile this driver as a module, choose M here: the module 489 will be called spi-intel-pci. 490 491config SPI_INTEL_PLATFORM 492 tristate "Intel PCH/PCU SPI flash platform driver (DANGEROUS)" 493 depends on X86 || COMPILE_TEST 494 depends on SPI_MEM 495 select SPI_INTEL 496 help 497 This enables platform support for the Intel PCH/PCU SPI 498 controller in master mode that is used to hold BIOS and other 499 persistent settings. Most of these controllers work in 500 software sequencing mode, which means that the controller 501 exposes the low level SPI-NOR opcodes to the software. Using 502 this driver it is possible to upgrade BIOS directly from Linux. 503 504 Say N here unless you know what you are doing. Overwriting the 505 SPI flash may render the system unbootable. 506 507 To compile this driver as a module, choose M here: the module 508 will be called spi-intel-platform. 509 510config SPI_JCORE 511 tristate "J-Core SPI Master" 512 depends on OF && (SUPERH || COMPILE_TEST) 513 help 514 This enables support for the SPI master controller in the J-Core 515 synthesizable, open source SoC. 516 517config SPI_LM70_LLP 518 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 519 depends on PARPORT 520 select SPI_BITBANG 521 help 522 This driver supports the NS LM70 LLP Evaluation Board, 523 which interfaces to an LM70 temperature sensor using 524 a parallel port. 525 526config SPI_LP8841_RTC 527 tristate "ICP DAS LP-8841 SPI Controller for RTC" 528 depends on MACH_PXA27X_DT || COMPILE_TEST 529 help 530 This driver provides an SPI master device to drive Maxim 531 DS-1302 real time clock. 532 533 Say N here unless you plan to run the kernel on an ICP DAS 534 LP-8x4x industrial computer. 535 536config SPI_MPC52xx 537 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 538 depends on PPC_MPC52xx 539 help 540 This drivers supports the MPC52xx SPI controller in master SPI 541 mode. 542 543config SPI_MPC52xx_PSC 544 tristate "Freescale MPC52xx PSC SPI controller" 545 depends on PPC_MPC52xx 546 help 547 This enables using the Freescale MPC52xx Programmable Serial 548 Controller in master SPI mode. 549 550config SPI_MPC512x_PSC 551 tristate "Freescale MPC512x PSC SPI controller" 552 depends on PPC_MPC512x 553 help 554 This enables using the Freescale MPC5121 Programmable Serial 555 Controller in SPI master mode. 556 557config SPI_FSL_LIB 558 tristate 559 depends on OF 560 561config SPI_FSL_CPM 562 tristate 563 depends on FSL_SOC 564 565config SPI_FSL_SPI 566 tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller" 567 depends on OF 568 select SPI_FSL_LIB 569 select SPI_FSL_CPM if FSL_SOC 570 help 571 This enables using the Freescale SPI controllers in master mode. 572 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 573 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 574 This also enables using the Aeroflex Gaisler GRLIB SPI controller in 575 master mode. 576 577config SPI_FSL_DSPI 578 tristate "Freescale DSPI controller" 579 select REGMAP_MMIO 580 depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST 581 help 582 This enables support for the Freescale DSPI controller in master 583 mode. VF610, LS1021A and ColdFire platforms uses the controller. 584 585config SPI_FSL_ESPI 586 tristate "Freescale eSPI controller" 587 depends on FSL_SOC 588 help 589 This enables using the Freescale eSPI controllers in master mode. 590 From MPC8536, 85xx platform uses the controller, and all P10xx, 591 P20xx, P30xx,P40xx, P50xx uses this controller. 592 593config SPI_MESON_SPICC 594 tristate "Amlogic Meson SPICC controller" 595 depends on COMMON_CLK 596 depends on ARCH_MESON || COMPILE_TEST 597 help 598 This enables master mode support for the SPICC (SPI communication 599 controller) available in Amlogic Meson SoCs. 600 601config SPI_MESON_SPIFC 602 tristate "Amlogic Meson SPIFC controller" 603 depends on ARCH_MESON || COMPILE_TEST 604 select REGMAP_MMIO 605 help 606 This enables master mode support for the SPIFC (SPI flash 607 controller) available in Amlogic Meson SoCs. 608 609config SPI_MICROCHIP_CORE 610 tristate "Microchip FPGA SPI controllers" 611 depends on SPI_MASTER 612 help 613 This enables the SPI driver for Microchip FPGA SPI controllers. 614 Say Y or M here if you want to use the "hard" controllers on 615 PolarFire SoC. 616 If built as a module, it will be called spi-microchip-core. 617 618config SPI_MICROCHIP_CORE_QSPI 619 tristate "Microchip FPGA QSPI controllers" 620 depends on SPI_MASTER 621 help 622 This enables the QSPI driver for Microchip FPGA QSPI controllers. 623 Say Y or M here if you want to use the QSPI controllers on 624 PolarFire SoC. 625 If built as a module, it will be called spi-microchip-core-qspi. 626 627config SPI_MT65XX 628 tristate "MediaTek SPI controller" 629 depends on ARCH_MEDIATEK || COMPILE_TEST 630 help 631 This selects the MediaTek(R) SPI bus driver. 632 If you want to use MediaTek(R) SPI interface, 633 say Y or M here.If you are not sure, say N. 634 SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs. 635 636config SPI_MT7621 637 tristate "MediaTek MT7621 SPI Controller" 638 depends on RALINK || COMPILE_TEST 639 help 640 This selects a driver for the MediaTek MT7621 SPI Controller. 641 642config SPI_MTK_NOR 643 tristate "MediaTek SPI NOR controller" 644 depends on ARCH_MEDIATEK || COMPILE_TEST 645 help 646 This enables support for SPI NOR controller found on MediaTek 647 ARM SoCs. This is a controller specifically for SPI NOR flash. 648 It can perform generic SPI transfers up to 6 bytes via generic 649 SPI interface as well as several SPI NOR specific instructions 650 via SPI MEM interface. 651 652config SPI_MTK_SNFI 653 tristate "MediaTek SPI NAND Flash Interface" 654 depends on ARCH_MEDIATEK || COMPILE_TEST 655 depends on MTD_NAND_ECC_MEDIATEK 656 help 657 This enables support for SPI-NAND mode on the MediaTek NAND 658 Flash Interface found on MediaTek ARM SoCs. This controller 659 is implemented as a SPI-MEM controller with pipelined ECC 660 capcability. 661 662config SPI_WPCM_FIU 663 tristate "Nuvoton WPCM450 Flash Interface Unit" 664 depends on ARCH_NPCM || COMPILE_TEST 665 select REGMAP 666 help 667 This enables support got the Flash Interface Unit SPI controller 668 present in the Nuvoton WPCM450 SoC. 669 670 This driver does not support generic SPI. The implementation only 671 supports the spi-mem interface. 672 673config SPI_NPCM_FIU 674 tristate "Nuvoton NPCM FLASH Interface Unit" 675 depends on ARCH_NPCM || COMPILE_TEST 676 depends on OF && HAS_IOMEM 677 help 678 This enables support for the Flash Interface Unit SPI controller 679 in master mode. 680 This driver does not support generic SPI. The implementation only 681 supports spi-mem interface. 682 683config SPI_NPCM_PSPI 684 tristate "Nuvoton NPCM PSPI Controller" 685 depends on ARCH_NPCM || COMPILE_TEST 686 help 687 This driver provides support for Nuvoton NPCM BMC 688 Peripheral SPI controller in master mode. 689 690config SPI_LANTIQ_SSC 691 tristate "Lantiq SSC SPI controller" 692 depends on LANTIQ || X86 || COMPILE_TEST 693 help 694 This driver supports the Lantiq SSC SPI controller in master 695 mode. This controller is found on Intel (former Lantiq) SoCs like 696 the Danube, Falcon, xRX200, xRX300, Lightning Mountain. 697 698config SPI_OC_TINY 699 tristate "OpenCores tiny SPI" 700 depends on GPIOLIB || COMPILE_TEST 701 select SPI_BITBANG 702 help 703 This is the driver for OpenCores tiny SPI master controller. 704 705config SPI_OCTEON 706 tristate "Cavium OCTEON SPI controller" 707 depends on CAVIUM_OCTEON_SOC 708 help 709 SPI host driver for the hardware found on some Cavium OCTEON 710 SOCs. 711 712config SPI_OMAP_UWIRE 713 tristate "OMAP1 MicroWire" 714 depends on ARCH_OMAP1 || (ARM && COMPILE_TEST) 715 select SPI_BITBANG 716 help 717 This hooks up to the MicroWire controller on OMAP1 chips. 718 719config SPI_OMAP24XX 720 tristate "McSPI driver for OMAP" 721 depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST 722 select SG_SPLIT 723 help 724 SPI master controller for OMAP24XX and later Multichannel SPI 725 (McSPI) modules. 726 727config SPI_TI_QSPI 728 tristate "DRA7xxx QSPI controller support" 729 depends on ARCH_OMAP2PLUS || COMPILE_TEST 730 help 731 QSPI master controller for DRA7xxx used for flash devices. 732 This device supports single, dual and quad read support, while 733 it only supports single write mode. 734 735config SPI_ORION 736 tristate "Orion SPI master" 737 depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST 738 help 739 This enables using the SPI master controller on the Orion 740 and MVEBU chips. 741 742config SPI_PCI1XXXX 743 tristate "PCI1XXXX SPI Bus support" 744 depends on PCI 745 help 746 Say "yes" to Enable the SPI Bus support for the PCI1xxxx card 747 This is a PCI to SPI Bus driver 748 This driver can be built as module. If so, the module will be 749 called as spi-pci1xxxx. 750 751config SPI_PIC32 752 tristate "Microchip PIC32 series SPI" 753 depends on MACH_PIC32 || COMPILE_TEST 754 help 755 SPI driver for Microchip PIC32 SPI master controller. 756 757config SPI_PIC32_SQI 758 tristate "Microchip PIC32 Quad SPI driver" 759 depends on MACH_PIC32 || COMPILE_TEST 760 help 761 SPI driver for PIC32 Quad SPI controller. 762 763config SPI_PL022 764 tristate "ARM AMBA PL022 SSP controller" 765 depends on ARM_AMBA 766 default y if ARCH_REALVIEW 767 default y if INTEGRATOR_IMPD1 768 default y if ARCH_VERSATILE 769 help 770 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 771 controller. If you have an embedded system with an AMBA(R) 772 bus and a PL022 controller, say Y or M here. 773 774config SPI_PPC4xx 775 tristate "PPC4xx SPI Controller" 776 depends on PPC32 && 4xx 777 select SPI_BITBANG 778 help 779 This selects a driver for the PPC4xx SPI Controller. 780 781config SPI_PXA2XX 782 tristate "PXA2xx SSP SPI master" 783 depends on ARCH_PXA || ARCH_MMP || PCI || ACPI || COMPILE_TEST 784 select PXA_SSP if ARCH_PXA || ARCH_MMP 785 help 786 This enables using a PXA2xx or Sodaville SSP port as a SPI master 787 controller. The driver can be configured to use any SSP port and 788 additional documentation can be found a Documentation/spi/pxa2xx.rst. 789 790config SPI_PXA2XX_PCI 791 def_tristate SPI_PXA2XX && PCI && COMMON_CLK 792 793config SPI_ROCKCHIP 794 tristate "Rockchip SPI controller driver" 795 depends on ARCH_ROCKCHIP || COMPILE_TEST 796 help 797 This selects a driver for Rockchip SPI controller. 798 799 If you say yes to this option, support will be included for 800 RK3066, RK3188 and RK3288 families of SPI controller. 801 Rockchip SPI controller support DMA transport and PIO mode. 802 The main usecase of this controller is to use spi flash as boot 803 device. 804 805config SPI_ROCKCHIP_SFC 806 tristate "Rockchip Serial Flash Controller (SFC)" 807 depends on ARCH_ROCKCHIP || COMPILE_TEST 808 depends on HAS_IOMEM && HAS_DMA 809 help 810 This enables support for Rockchip serial flash controller. This 811 is a specialized controller used to access SPI flash on some 812 Rockchip SOCs. 813 814 ROCKCHIP SFC supports DMA and PIO modes. When DMA is not available, 815 the driver automatically falls back to PIO mode. 816 817config SPI_RB4XX 818 tristate "Mikrotik RB4XX SPI master" 819 depends on SPI_MASTER && ATH79 820 help 821 SPI controller driver for the Mikrotik RB4xx series boards. 822 823config SPI_RPCIF 824 tristate "Renesas RPC-IF SPI driver" 825 depends on RENESAS_RPCIF 826 help 827 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF. 828 829config SPI_RSPI 830 tristate "Renesas RSPI/QSPI controller" 831 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST 832 help 833 SPI driver for Renesas RSPI and QSPI blocks. 834 835config SPI_RZV2M_CSI 836 tristate "Renesas RZ/V2M CSI controller" 837 depends on ARCH_RENESAS || COMPILE_TEST 838 help 839 SPI driver for Renesas RZ/V2M Clocked Serial Interface (CSI) 840 841config SPI_QCOM_QSPI 842 tristate "QTI QSPI controller" 843 depends on ARCH_QCOM || COMPILE_TEST 844 help 845 QSPI(Quad SPI) driver for Qualcomm QSPI controller. 846 847config SPI_QUP 848 tristate "Qualcomm SPI controller with QUP interface" 849 depends on ARCH_QCOM || COMPILE_TEST 850 help 851 Qualcomm Universal Peripheral (QUP) core is an AHB slave that 852 provides a common data path (an output FIFO and an input FIFO) 853 for serial peripheral interface (SPI) mini-core. SPI in master 854 mode supports up to 50MHz, up to four chip selects, programmable 855 data path from 4 bits to 32 bits and numerous protocol variants. 856 857 This driver can also be built as a module. If so, the module 858 will be called spi_qup. 859 860config SPI_QCOM_GENI 861 tristate "Qualcomm GENI based SPI controller" 862 depends on QCOM_GENI_SE 863 help 864 This driver supports GENI serial engine based SPI controller in 865 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say 866 yes to this option, support will be included for the built-in SPI 867 interface on the Qualcomm Technologies Inc.'s SoCs. 868 869 This driver can also be built as a module. If so, the module 870 will be called spi-geni-qcom. 871 872config SPI_S3C64XX 873 tristate "Samsung S3C64XX/Exynos SoC series type SPI" 874 depends on (PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST) 875 help 876 SPI driver for Samsung S3C64XX, S5Pv210 and Exynos SoCs. 877 Choose Y/M here only if you build for such Samsung SoC. 878 879config SPI_SC18IS602 880 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge" 881 depends on I2C 882 help 883 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge. 884 885config SPI_SH_MSIOF 886 tristate "SuperH MSIOF SPI controller" 887 depends on HAVE_CLK 888 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST 889 help 890 SPI driver for SuperH and SH Mobile MSIOF blocks. 891 892config SPI_SH 893 tristate "SuperH SPI controller" 894 depends on SUPERH || COMPILE_TEST 895 help 896 SPI driver for SuperH SPI blocks. 897 898config SPI_SH_SCI 899 tristate "SuperH SCI SPI controller" 900 depends on SUPERH 901 select SPI_BITBANG 902 help 903 SPI driver for SuperH SCI blocks. 904 905config SPI_SH_HSPI 906 tristate "SuperH HSPI controller" 907 depends on ARCH_RENESAS || COMPILE_TEST 908 help 909 SPI driver for SuperH HSPI blocks. 910 911config SPI_SIFIVE 912 tristate "SiFive SPI controller" 913 depends on HAS_IOMEM 914 help 915 This exposes the SPI controller IP from SiFive. 916 917config SPI_SLAVE_MT27XX 918 tristate "MediaTek SPI slave device" 919 depends on ARCH_MEDIATEK || COMPILE_TEST 920 depends on SPI_SLAVE 921 help 922 This selects the MediaTek(R) SPI slave device driver. 923 If you want to use MediaTek(R) SPI slave interface, 924 say Y or M here.If you are not sure, say N. 925 SPI slave drivers for Mediatek MT27XX series ARM SoCs. 926 927config SPI_SN_F_OSPI 928 tristate "Socionext F_OSPI SPI flash controller" 929 depends on OF && HAS_IOMEM 930 depends on SPI_MEM 931 help 932 This enables support for the Socionext F_OSPI controller 933 for connecting an SPI Flash memory over up to 8-bit wide bus. 934 It supports indirect access mode only. 935 936config SPI_SPRD 937 tristate "Spreadtrum SPI controller" 938 depends on ARCH_SPRD || COMPILE_TEST 939 help 940 SPI driver for Spreadtrum SoCs. 941 942config SPI_SPRD_ADI 943 tristate "Spreadtrum ADI controller" 944 depends on ARCH_SPRD || COMPILE_TEST 945 depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK) 946 help 947 ADI driver based on SPI for Spreadtrum SoCs. 948 949config SPI_STM32 950 tristate "STMicroelectronics STM32 SPI controller" 951 depends on ARCH_STM32 || COMPILE_TEST 952 select SPI_SLAVE 953 help 954 SPI driver for STMicroelectronics STM32 SoCs. 955 956 STM32 SPI controller supports DMA and PIO modes. When DMA 957 is not available, the driver automatically falls back to 958 PIO mode. 959 960config SPI_STM32_QSPI 961 tristate "STMicroelectronics STM32 QUAD SPI controller" 962 depends on ARCH_STM32 || COMPILE_TEST 963 depends on OF 964 depends on SPI_MEM 965 help 966 This enables support for the Quad SPI controller in master mode. 967 This driver does not support generic SPI. The implementation only 968 supports spi-mem interface. 969 970config SPI_ST_SSC4 971 tristate "STMicroelectronics SPI SSC-based driver" 972 depends on ARCH_STI || COMPILE_TEST 973 help 974 STMicroelectronics SoCs support for SPI. If you say yes to 975 this option, support will be included for the SSC driven SPI. 976 977config SPI_SUN4I 978 tristate "Allwinner A10 SoCs SPI controller" 979 depends on ARCH_SUNXI || COMPILE_TEST 980 help 981 SPI driver for Allwinner sun4i, sun5i and sun7i SoCs 982 983config SPI_SUN6I 984 tristate "Allwinner A31 SPI controller" 985 depends on ARCH_SUNXI || COMPILE_TEST 986 depends on RESET_CONTROLLER 987 help 988 This enables using the SPI controller on the Allwinner A31 SoCs. 989 990config SPI_SUNPLUS_SP7021 991 tristate "Sunplus SP7021 SPI controller" 992 depends on SOC_SP7021 || COMPILE_TEST 993 help 994 This enables Sunplus SP7021 SPI controller driver on the SP7021 SoCs. 995 This driver can also be built as a module. If so, the module will be 996 called as spi-sunplus-sp7021. 997 998 If you have a Sunplus SP7021 platform say Y here. 999 If unsure, say N. 1000 1001config SPI_SYNQUACER 1002 tristate "Socionext's SynQuacer HighSpeed SPI controller" 1003 depends on ARCH_SYNQUACER || COMPILE_TEST 1004 help 1005 SPI driver for Socionext's High speed SPI controller which provides 1006 various operating modes for interfacing to serial peripheral devices 1007 that use the de-facto standard SPI protocol. 1008 1009 It also supports the new dual-bit and quad-bit SPI protocol. 1010 1011config SPI_MXIC 1012 tristate "Macronix MX25F0A SPI controller" 1013 depends on SPI_MASTER 1014 imply MTD_NAND_ECC_MXIC 1015 help 1016 This selects the Macronix MX25F0A SPI controller driver. 1017 1018config SPI_MXS 1019 tristate "Freescale MXS SPI controller" 1020 depends on ARCH_MXS 1021 select STMP_DEVICE 1022 help 1023 SPI driver for Freescale MXS devices. 1024 1025config SPI_TEGRA210_QUAD 1026 tristate "NVIDIA Tegra QSPI Controller" 1027 depends on ARCH_TEGRA || COMPILE_TEST 1028 depends on RESET_CONTROLLER 1029 help 1030 QSPI driver for NVIDIA Tegra QSPI Controller interface. This 1031 controller is different from the SPI controller and is available 1032 on Tegra SoCs starting from Tegra210. 1033 1034config SPI_TEGRA114 1035 tristate "NVIDIA Tegra114 SPI Controller" 1036 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST 1037 depends on RESET_CONTROLLER 1038 help 1039 SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller 1040 is different than the older SoCs SPI controller and also register interface 1041 get changed with this controller. 1042 1043config SPI_TEGRA20_SFLASH 1044 tristate "Nvidia Tegra20 Serial flash Controller" 1045 depends on ARCH_TEGRA || COMPILE_TEST 1046 depends on RESET_CONTROLLER 1047 help 1048 SPI driver for Nvidia Tegra20 Serial flash Controller interface. 1049 The main usecase of this controller is to use spi flash as boot 1050 device. 1051 1052config SPI_TEGRA20_SLINK 1053 tristate "Nvidia Tegra20/Tegra30 SLINK Controller" 1054 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST 1055 depends on RESET_CONTROLLER 1056 help 1057 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface. 1058 1059config SPI_THUNDERX 1060 tristate "Cavium ThunderX SPI controller" 1061 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST) 1062 help 1063 SPI host driver for the hardware found on Cavium ThunderX 1064 SOCs. 1065 1066config SPI_TOPCLIFF_PCH 1067 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI" 1068 depends on PCI && (X86_32 || MIPS || COMPILE_TEST) 1069 help 1070 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 1071 used in some x86 embedded processors. 1072 1073 This driver also supports the ML7213/ML7223/ML7831, a companion chip 1074 for the Atom E6xx series and compatible with the Intel EG20T PCH. 1075 1076config SPI_UNIPHIER 1077 tristate "Socionext UniPhier SPI Controller" 1078 depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF 1079 depends on HAS_IOMEM 1080 help 1081 This enables a driver for the Socionext UniPhier SoC SCSSI SPI controller. 1082 1083 UniPhier SoCs have SCSSI and MCSSI SPI controllers. 1084 Every UniPhier SoC has SCSSI which supports single channel. 1085 Older UniPhier Pro4/Pro5 also has MCSSI which support multiple channels. 1086 This driver supports SCSSI only. 1087 1088 If your SoC supports SCSSI, say Y here. 1089 1090config SPI_XCOMM 1091 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver" 1092 depends on I2C 1093 help 1094 Support for the SPI-I2C bridge found on the Analog Devices 1095 AD-FMCOMMS1-EBZ board. 1096 1097config SPI_XILINX 1098 tristate "Xilinx SPI controller common module" 1099 depends on HAS_IOMEM 1100 select SPI_BITBANG 1101 help 1102 This exposes the SPI controller IP from the Xilinx EDK. 1103 1104 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 1105 Product Specification document (DS464) for hardware details. 1106 1107 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 1108 1109config SPI_XLP 1110 tristate "Cavium ThunderX2 SPI controller driver" 1111 depends on ARCH_THUNDER2 || COMPILE_TEST 1112 help 1113 Enable support for the SPI controller on the Cavium ThunderX2. 1114 (Originally on Netlogic XLP SoCs.) 1115 1116 If you have a Cavium ThunderX2 platform say Y here. 1117 If unsure, say N. 1118 1119config SPI_XTENSA_XTFPGA 1120 tristate "Xtensa SPI controller for xtfpga" 1121 depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST 1122 select SPI_BITBANG 1123 help 1124 SPI driver for xtfpga SPI master controller. 1125 1126 This simple SPI master controller is built into xtfpga bitstreams 1127 and is used to control daughterboard audio codec. It always transfers 1128 16 bit words in SPI mode 0, automatically asserting CS on transfer 1129 start and deasserting on end. 1130 1131config SPI_ZYNQ_QSPI 1132 tristate "Xilinx Zynq QSPI controller" 1133 depends on ARCH_ZYNQ || COMPILE_TEST 1134 help 1135 This enables support for the Zynq Quad SPI controller 1136 in master mode. 1137 This controller only supports SPI memory interface. 1138 1139config SPI_ZYNQMP_GQSPI 1140 tristate "Xilinx ZynqMP GQSPI controller" 1141 depends on (SPI_MASTER && HAS_DMA) || COMPILE_TEST 1142 help 1143 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC. 1144 1145config SPI_AMD 1146 tristate "AMD SPI controller" 1147 depends on SPI_MASTER || COMPILE_TEST 1148 help 1149 Enables SPI controller driver for AMD SoC. 1150 1151# 1152# Add new SPI master controllers in alphabetical order above this line 1153# 1154 1155comment "SPI Multiplexer support" 1156 1157config SPI_MUX 1158 tristate "SPI multiplexer support" 1159 select MULTIPLEXER 1160 help 1161 This adds support for SPI multiplexers. Each SPI mux will be 1162 accessible as a SPI controller, the devices behind the mux will appear 1163 to be chip selects on this controller. It is still necessary to 1164 select one or more specific mux-controller drivers. 1165 1166# 1167# There are lots of SPI device types, with sensors and memory 1168# being probably the most widely used ones. 1169# 1170comment "SPI Protocol Masters" 1171 1172config SPI_SPIDEV 1173 tristate "User mode SPI device driver support" 1174 help 1175 This supports user mode SPI protocol drivers. 1176 1177config SPI_LOOPBACK_TEST 1178 tristate "spi loopback test framework support" 1179 depends on m 1180 help 1181 This enables the SPI loopback testing framework driver 1182 1183 primarily used for development of spi_master drivers 1184 and to detect regressions 1185 1186config SPI_TLE62X0 1187 tristate "Infineon TLE62X0 (for power switching)" 1188 depends on SYSFS 1189 help 1190 SPI driver for Infineon TLE62X0 series line driver chips, 1191 such as the TLE6220, TLE6230 and TLE6240. This provides a 1192 sysfs interface, with each line presented as a kind of GPIO 1193 exposing both switch control and diagnostic feedback. 1194 1195# 1196# Add new SPI protocol masters in alphabetical order above this line 1197# 1198 1199endif # SPI_MASTER 1200 1201# 1202# SLAVE side ... listening to other SPI masters 1203# 1204 1205config SPI_SLAVE 1206 bool "SPI slave protocol handlers" 1207 help 1208 If your system has a slave-capable SPI controller, you can enable 1209 slave protocol handlers. 1210 1211if SPI_SLAVE 1212 1213config SPI_SLAVE_TIME 1214 tristate "SPI slave handler reporting boot up time" 1215 help 1216 SPI slave handler responding with the time of reception of the last 1217 SPI message. 1218 1219config SPI_SLAVE_SYSTEM_CONTROL 1220 tristate "SPI slave handler controlling system state" 1221 help 1222 SPI slave handler to allow remote control of system reboot, power 1223 off, halt, and suspend. 1224 1225endif # SPI_SLAVE 1226 1227config SPI_DYNAMIC 1228 def_bool ACPI || OF_DYNAMIC || SPI_SLAVE 1229 1230endif # SPI 1231