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_DAVINCI 285 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller" 286 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST 287 select SPI_BITBANG 288 help 289 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules. 290 291config SPI_DESIGNWARE 292 tristate "DesignWare SPI controller core support" 293 imply SPI_MEM 294 help 295 general driver for SPI controller core from DesignWare 296 297if SPI_DESIGNWARE 298 299config SPI_DW_DMA 300 bool "DMA support for DW SPI controller" 301 302config SPI_DW_PCI 303 tristate "PCI interface driver for DW SPI core" 304 depends on PCI 305 306config SPI_DW_MMIO 307 tristate "Memory-mapped io interface driver for DW SPI core" 308 depends on HAS_IOMEM 309 310config SPI_DW_BT1 311 tristate "Baikal-T1 SPI driver for DW SPI core" 312 depends on MIPS_BAIKAL_T1 || COMPILE_TEST 313 select MULTIPLEXER 314 help 315 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI 316 controllers. Two of them are pretty much normal: with IRQ, DMA, 317 FIFOs of 64 words depth, 4x CSs, but the third one as being a 318 part of the Baikal-T1 System Boot Controller has got a very 319 limited resources: no IRQ, no DMA, only a single native 320 chip-select and Tx/Rx FIFO with just 8 words depth available. 321 The later one is normally connected to an external SPI-nor flash 322 of 128Mb (in general can be of bigger size). 323 324config SPI_DW_BT1_DIRMAP 325 bool "Directly mapped Baikal-T1 Boot SPI flash support" 326 depends on SPI_DW_BT1 327 help 328 Directly mapped SPI flash memory is an interface specific to the 329 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which 330 can be used to access a peripheral memory device just by 331 reading/writing data from/to it. Note that the system APB bus 332 will stall during each IO from/to the dirmap region until the 333 operation is finished. So try not to use it concurrently with 334 time-critical tasks (like the SPI memory operations implemented 335 in this driver). 336 337endif 338 339config SPI_DLN2 340 tristate "Diolan DLN-2 USB SPI adapter" 341 depends on MFD_DLN2 342 help 343 If you say yes to this option, support will be included for Diolan 344 DLN2, a USB to SPI interface. 345 346 This driver can also be built as a module. If so, the module 347 will be called spi-dln2. 348 349config SPI_EP93XX 350 tristate "Cirrus Logic EP93xx SPI controller" 351 depends on ARCH_EP93XX || COMPILE_TEST 352 help 353 This enables using the Cirrus EP93xx SPI controller in master 354 mode. 355 356config SPI_FALCON 357 bool "Falcon SPI controller support" 358 depends on SOC_FALCON 359 help 360 The external bus unit (EBU) found on the FALC-ON SoC has SPI 361 emulation that is designed for serial flash access. This driver 362 has only been tested with m25p80 type chips. The hardware has no 363 support for other types of SPI peripherals. 364 365config SPI_FSI 366 tristate "FSI SPI driver" 367 depends on FSI 368 help 369 This enables support for the driver for FSI bus attached SPI 370 controllers. 371 372config SPI_FSL_LPSPI 373 tristate "Freescale i.MX LPSPI controller" 374 depends on ARCH_MXC || COMPILE_TEST 375 help 376 This enables Freescale i.MX LPSPI controllers in master mode. 377 378config SPI_FSL_QUADSPI 379 tristate "Freescale QSPI controller" 380 depends on ARCH_MXC || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST 381 depends on HAS_IOMEM 382 help 383 This enables support for the Quad SPI controller in master mode. 384 Up to four flash chips can be connected on two buses with two 385 chipselects each. 386 This controller does not support generic SPI messages. It only 387 supports the high-level SPI memory interface. 388 389config SPI_GXP 390 tristate "GXP SPI driver" 391 depends on ARCH_HPE || COMPILE_TEST 392 help 393 This enables support for the driver for GXP bus attached SPI 394 controllers. 395 396config SPI_HISI_KUNPENG 397 tristate "HiSilicon SPI Controller for Kunpeng SoCs" 398 depends on (ARM64 && ACPI) || COMPILE_TEST 399 help 400 This enables support for HiSilicon SPI controller found on 401 Kunpeng SoCs. 402 403 This driver can also be built as a module. If so, the module 404 will be called hisi-kunpeng-spi. 405 406config SPI_HISI_SFC_V3XX 407 tristate "HiSilicon SPI NOR Flash Controller for Hi16XX chipsets" 408 depends on (ARM64 && ACPI) || COMPILE_TEST 409 depends on HAS_IOMEM 410 help 411 This enables support for HiSilicon v3xx SPI NOR flash controller 412 found in hi16xx chipsets. 413 414config SPI_NXP_FLEXSPI 415 tristate "NXP Flex SPI controller" 416 depends on ARCH_LAYERSCAPE || ARCH_MXC || COMPILE_TEST 417 depends on HAS_IOMEM 418 help 419 This enables support for the Flex SPI controller in master mode. 420 Up to four slave devices can be connected on two buses with two 421 chipselects each. 422 This controller does not support generic SPI messages and only 423 supports the high-level SPI memory interface. 424 425config SPI_GPIO 426 tristate "GPIO-based bitbanging SPI Master" 427 depends on GPIOLIB || COMPILE_TEST 428 select SPI_BITBANG 429 help 430 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO 431 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI 432 slaves connected to a bus using this driver are configured as usual, 433 except that the spi_board_info.controller_data holds the GPIO number 434 for the chipselect used by this controller driver. 435 436 Note that this driver often won't achieve even 1 Mbit/sec speeds, 437 making it unusually slow for SPI. If your platform can inline 438 GPIO operations, you should be able to leverage that for better 439 speed with a custom version of this driver; see the source code. 440 441config SPI_IMG_SPFI 442 tristate "IMG SPFI controller" 443 depends on MIPS || COMPILE_TEST 444 help 445 This enables support for the SPFI master controller found on 446 IMG SoCs. 447 448config SPI_IMX 449 tristate "Freescale i.MX SPI controllers" 450 depends on ARCH_MXC || COMPILE_TEST 451 help 452 This enables support for the Freescale i.MX SPI controllers. 453 454config SPI_INGENIC 455 tristate "Ingenic SoCs SPI controller" 456 depends on MACH_INGENIC || COMPILE_TEST 457 help 458 This enables support for the Ingenic SoCs SPI controller. 459 460 To compile this driver as a module, choose M here: the module 461 will be called spi-ingenic. 462 463config SPI_INTEL 464 tristate 465 466config SPI_INTEL_PCI 467 tristate "Intel PCH/PCU SPI flash PCI driver" 468 depends on PCI 469 depends on X86 || COMPILE_TEST 470 depends on SPI_MEM 471 select SPI_INTEL 472 help 473 This enables PCI support for the Intel PCH/PCU SPI controller in 474 master mode. This controller is used to hold BIOS and other 475 persistent settings. Controllers present in modern Intel hardware 476 only work in hardware sequencing mode, this means that the 477 controller exposes a subset of operations that makes it safer to 478 use. Using this driver it is possible to upgrade BIOS directly 479 from Linux. 480 481 To compile this driver as a module, choose M here: the module 482 will be called spi-intel-pci. 483 484config SPI_INTEL_PLATFORM 485 tristate "Intel PCH/PCU SPI flash platform driver (DANGEROUS)" 486 depends on X86 || COMPILE_TEST 487 depends on SPI_MEM 488 select SPI_INTEL 489 help 490 This enables platform support for the Intel PCH/PCU SPI 491 controller in master mode that is used to hold BIOS and other 492 persistent settings. Most of these controllers work in 493 software sequencing mode, which means that the controller 494 exposes the low level SPI-NOR opcodes to the software. Using 495 this driver it is possible to upgrade BIOS directly from Linux. 496 497 Say N here unless you know what you are doing. Overwriting the 498 SPI flash may render the system unbootable. 499 500 To compile this driver as a module, choose M here: the module 501 will be called spi-intel-platform. 502 503config SPI_JCORE 504 tristate "J-Core SPI Master" 505 depends on OF && (SUPERH || COMPILE_TEST) 506 help 507 This enables support for the SPI master controller in the J-Core 508 synthesizable, open source SoC. 509 510config SPI_LM70_LLP 511 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 512 depends on PARPORT 513 select SPI_BITBANG 514 help 515 This driver supports the NS LM70 LLP Evaluation Board, 516 which interfaces to an LM70 temperature sensor using 517 a parallel port. 518 519config SPI_LP8841_RTC 520 tristate "ICP DAS LP-8841 SPI Controller for RTC" 521 depends on MACH_PXA27X_DT || COMPILE_TEST 522 help 523 This driver provides an SPI master device to drive Maxim 524 DS-1302 real time clock. 525 526 Say N here unless you plan to run the kernel on an ICP DAS 527 LP-8x4x industrial computer. 528 529config SPI_MPC52xx 530 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 531 depends on PPC_MPC52xx 532 help 533 This drivers supports the MPC52xx SPI controller in master SPI 534 mode. 535 536config SPI_MPC52xx_PSC 537 tristate "Freescale MPC52xx PSC SPI controller" 538 depends on PPC_MPC52xx 539 help 540 This enables using the Freescale MPC52xx Programmable Serial 541 Controller in master SPI mode. 542 543config SPI_MPC512x_PSC 544 tristate "Freescale MPC512x PSC SPI controller" 545 depends on PPC_MPC512x 546 help 547 This enables using the Freescale MPC5121 Programmable Serial 548 Controller in SPI master mode. 549 550config SPI_FSL_LIB 551 tristate 552 depends on OF 553 554config SPI_FSL_CPM 555 tristate 556 depends on FSL_SOC 557 558config SPI_FSL_SPI 559 tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller" 560 depends on OF 561 select SPI_FSL_LIB 562 select SPI_FSL_CPM if FSL_SOC 563 help 564 This enables using the Freescale SPI controllers in master mode. 565 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 566 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 567 This also enables using the Aeroflex Gaisler GRLIB SPI controller in 568 master mode. 569 570config SPI_FSL_DSPI 571 tristate "Freescale DSPI controller" 572 select REGMAP_MMIO 573 depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST 574 help 575 This enables support for the Freescale DSPI controller in master 576 mode. VF610, LS1021A and ColdFire platforms uses the controller. 577 578config SPI_FSL_ESPI 579 tristate "Freescale eSPI controller" 580 depends on FSL_SOC 581 help 582 This enables using the Freescale eSPI controllers in master mode. 583 From MPC8536, 85xx platform uses the controller, and all P10xx, 584 P20xx, P30xx,P40xx, P50xx uses this controller. 585 586config SPI_MESON_SPICC 587 tristate "Amlogic Meson SPICC controller" 588 depends on COMMON_CLK 589 depends on ARCH_MESON || COMPILE_TEST 590 help 591 This enables master mode support for the SPICC (SPI communication 592 controller) available in Amlogic Meson SoCs. 593 594config SPI_MESON_SPIFC 595 tristate "Amlogic Meson SPIFC controller" 596 depends on ARCH_MESON || COMPILE_TEST 597 select REGMAP_MMIO 598 help 599 This enables master mode support for the SPIFC (SPI flash 600 controller) available in Amlogic Meson SoCs. 601 602config SPI_MICROCHIP_CORE 603 tristate "Microchip FPGA SPI controllers" 604 depends on SPI_MASTER 605 help 606 This enables the SPI driver for Microchip FPGA SPI controllers. 607 Say Y or M here if you want to use the "hard" controllers on 608 PolarFire SoC. 609 If built as a module, it will be called spi-microchip-core. 610 611config SPI_MICROCHIP_CORE_QSPI 612 tristate "Microchip FPGA QSPI controllers" 613 depends on SPI_MASTER 614 help 615 This enables the QSPI driver for Microchip FPGA QSPI controllers. 616 Say Y or M here if you want to use the QSPI controllers on 617 PolarFire SoC. 618 If built as a module, it will be called spi-microchip-core-qspi. 619 620config SPI_MT65XX 621 tristate "MediaTek SPI controller" 622 depends on ARCH_MEDIATEK || COMPILE_TEST 623 help 624 This selects the MediaTek(R) SPI bus driver. 625 If you want to use MediaTek(R) SPI interface, 626 say Y or M here.If you are not sure, say N. 627 SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs. 628 629config SPI_MT7621 630 tristate "MediaTek MT7621 SPI Controller" 631 depends on RALINK || COMPILE_TEST 632 help 633 This selects a driver for the MediaTek MT7621 SPI Controller. 634 635config SPI_MTK_NOR 636 tristate "MediaTek SPI NOR controller" 637 depends on ARCH_MEDIATEK || COMPILE_TEST 638 help 639 This enables support for SPI NOR controller found on MediaTek 640 ARM SoCs. This is a controller specifically for SPI NOR flash. 641 It can perform generic SPI transfers up to 6 bytes via generic 642 SPI interface as well as several SPI NOR specific instructions 643 via SPI MEM interface. 644 645config SPI_MTK_SNFI 646 tristate "MediaTek SPI NAND Flash Interface" 647 depends on ARCH_MEDIATEK || COMPILE_TEST 648 depends on MTD_NAND_ECC_MEDIATEK 649 help 650 This enables support for SPI-NAND mode on the MediaTek NAND 651 Flash Interface found on MediaTek ARM SoCs. This controller 652 is implemented as a SPI-MEM controller with pipelined ECC 653 capcability. 654 655config SPI_WPCM_FIU 656 tristate "Nuvoton WPCM450 Flash Interface Unit" 657 depends on ARCH_NPCM || COMPILE_TEST 658 select REGMAP 659 help 660 This enables support got the Flash Interface Unit SPI controller 661 present in the Nuvoton WPCM450 SoC. 662 663 This driver does not support generic SPI. The implementation only 664 supports the spi-mem interface. 665 666config SPI_NPCM_FIU 667 tristate "Nuvoton NPCM FLASH Interface Unit" 668 depends on ARCH_NPCM || COMPILE_TEST 669 depends on OF && HAS_IOMEM 670 help 671 This enables support for the Flash Interface Unit SPI controller 672 in master mode. 673 This driver does not support generic SPI. The implementation only 674 supports spi-mem interface. 675 676config SPI_NPCM_PSPI 677 tristate "Nuvoton NPCM PSPI Controller" 678 depends on ARCH_NPCM || COMPILE_TEST 679 help 680 This driver provides support for Nuvoton NPCM BMC 681 Peripheral SPI controller in master mode. 682 683config SPI_LANTIQ_SSC 684 tristate "Lantiq SSC SPI controller" 685 depends on LANTIQ || X86 || COMPILE_TEST 686 help 687 This driver supports the Lantiq SSC SPI controller in master 688 mode. This controller is found on Intel (former Lantiq) SoCs like 689 the Danube, Falcon, xRX200, xRX300, Lightning Mountain. 690 691config SPI_OC_TINY 692 tristate "OpenCores tiny SPI" 693 depends on GPIOLIB || COMPILE_TEST 694 select SPI_BITBANG 695 help 696 This is the driver for OpenCores tiny SPI master controller. 697 698config SPI_OCTEON 699 tristate "Cavium OCTEON SPI controller" 700 depends on CAVIUM_OCTEON_SOC 701 help 702 SPI host driver for the hardware found on some Cavium OCTEON 703 SOCs. 704 705config SPI_OMAP_UWIRE 706 tristate "OMAP1 MicroWire" 707 depends on ARCH_OMAP1 || (ARM && COMPILE_TEST) 708 select SPI_BITBANG 709 help 710 This hooks up to the MicroWire controller on OMAP1 chips. 711 712config SPI_OMAP24XX 713 tristate "McSPI driver for OMAP" 714 depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST 715 select SG_SPLIT 716 help 717 SPI master controller for OMAP24XX and later Multichannel SPI 718 (McSPI) modules. 719 720config SPI_TI_QSPI 721 tristate "DRA7xxx QSPI controller support" 722 depends on ARCH_OMAP2PLUS || COMPILE_TEST 723 help 724 QSPI master controller for DRA7xxx used for flash devices. 725 This device supports single, dual and quad read support, while 726 it only supports single write mode. 727 728config SPI_ORION 729 tristate "Orion SPI master" 730 depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST 731 help 732 This enables using the SPI master controller on the Orion 733 and MVEBU chips. 734 735config SPI_PCI1XXXX 736 tristate "PCI1XXXX SPI Bus support" 737 depends on PCI 738 help 739 Say "yes" to Enable the SPI Bus support for the PCI1xxxx card 740 This is a PCI to SPI Bus driver 741 This driver can be built as module. If so, the module will be 742 called as spi-pci1xxxx. 743 744config SPI_PIC32 745 tristate "Microchip PIC32 series SPI" 746 depends on MACH_PIC32 || COMPILE_TEST 747 help 748 SPI driver for Microchip PIC32 SPI master controller. 749 750config SPI_PIC32_SQI 751 tristate "Microchip PIC32 Quad SPI driver" 752 depends on MACH_PIC32 || COMPILE_TEST 753 help 754 SPI driver for PIC32 Quad SPI controller. 755 756config SPI_PL022 757 tristate "ARM AMBA PL022 SSP controller" 758 depends on ARM_AMBA 759 default y if ARCH_REALVIEW 760 default y if INTEGRATOR_IMPD1 761 default y if ARCH_VERSATILE 762 help 763 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 764 controller. If you have an embedded system with an AMBA(R) 765 bus and a PL022 controller, say Y or M here. 766 767config SPI_PPC4xx 768 tristate "PPC4xx SPI Controller" 769 depends on PPC32 && 4xx 770 select SPI_BITBANG 771 help 772 This selects a driver for the PPC4xx SPI Controller. 773 774config SPI_PXA2XX 775 tristate "PXA2xx SSP SPI master" 776 depends on ARCH_PXA || ARCH_MMP || PCI || ACPI || COMPILE_TEST 777 select PXA_SSP if ARCH_PXA || ARCH_MMP 778 help 779 This enables using a PXA2xx or Sodaville SSP port as a SPI master 780 controller. The driver can be configured to use any SSP port and 781 additional documentation can be found a Documentation/spi/pxa2xx.rst. 782 783config SPI_PXA2XX_PCI 784 def_tristate SPI_PXA2XX && PCI && COMMON_CLK 785 786config SPI_ROCKCHIP 787 tristate "Rockchip SPI controller driver" 788 depends on ARCH_ROCKCHIP || COMPILE_TEST 789 help 790 This selects a driver for Rockchip SPI controller. 791 792 If you say yes to this option, support will be included for 793 RK3066, RK3188 and RK3288 families of SPI controller. 794 Rockchip SPI controller support DMA transport and PIO mode. 795 The main usecase of this controller is to use spi flash as boot 796 device. 797 798config SPI_ROCKCHIP_SFC 799 tristate "Rockchip Serial Flash Controller (SFC)" 800 depends on ARCH_ROCKCHIP || COMPILE_TEST 801 depends on HAS_IOMEM && HAS_DMA 802 help 803 This enables support for Rockchip serial flash controller. This 804 is a specialized controller used to access SPI flash on some 805 Rockchip SOCs. 806 807 ROCKCHIP SFC supports DMA and PIO modes. When DMA is not available, 808 the driver automatically falls back to PIO mode. 809 810config SPI_RB4XX 811 tristate "Mikrotik RB4XX SPI master" 812 depends on SPI_MASTER && ATH79 813 help 814 SPI controller driver for the Mikrotik RB4xx series boards. 815 816config SPI_RPCIF 817 tristate "Renesas RPC-IF SPI driver" 818 depends on RENESAS_RPCIF 819 help 820 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF. 821 822config SPI_RSPI 823 tristate "Renesas RSPI/QSPI controller" 824 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST 825 help 826 SPI driver for Renesas RSPI and QSPI blocks. 827 828config SPI_QCOM_QSPI 829 tristate "QTI QSPI controller" 830 depends on ARCH_QCOM || COMPILE_TEST 831 help 832 QSPI(Quad SPI) driver for Qualcomm QSPI controller. 833 834config SPI_QUP 835 tristate "Qualcomm SPI controller with QUP interface" 836 depends on ARCH_QCOM || COMPILE_TEST 837 help 838 Qualcomm Universal Peripheral (QUP) core is an AHB slave that 839 provides a common data path (an output FIFO and an input FIFO) 840 for serial peripheral interface (SPI) mini-core. SPI in master 841 mode supports up to 50MHz, up to four chip selects, programmable 842 data path from 4 bits to 32 bits and numerous protocol variants. 843 844 This driver can also be built as a module. If so, the module 845 will be called spi_qup. 846 847config SPI_QCOM_GENI 848 tristate "Qualcomm GENI based SPI controller" 849 depends on QCOM_GENI_SE 850 help 851 This driver supports GENI serial engine based SPI controller in 852 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say 853 yes to this option, support will be included for the built-in SPI 854 interface on the Qualcomm Technologies Inc.'s SoCs. 855 856 This driver can also be built as a module. If so, the module 857 will be called spi-geni-qcom. 858 859config SPI_S3C64XX 860 tristate "Samsung S3C64XX/Exynos SoC series type SPI" 861 depends on (PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST) 862 help 863 SPI driver for Samsung S3C64XX, S5Pv210 and Exynos SoCs. 864 Choose Y/M here only if you build for such Samsung SoC. 865 866config SPI_SC18IS602 867 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge" 868 depends on I2C 869 help 870 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge. 871 872config SPI_SH_MSIOF 873 tristate "SuperH MSIOF SPI controller" 874 depends on HAVE_CLK 875 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST 876 help 877 SPI driver for SuperH and SH Mobile MSIOF blocks. 878 879config SPI_SH 880 tristate "SuperH SPI controller" 881 depends on SUPERH || COMPILE_TEST 882 help 883 SPI driver for SuperH SPI blocks. 884 885config SPI_SH_SCI 886 tristate "SuperH SCI SPI controller" 887 depends on SUPERH 888 select SPI_BITBANG 889 help 890 SPI driver for SuperH SCI blocks. 891 892config SPI_SH_HSPI 893 tristate "SuperH HSPI controller" 894 depends on ARCH_RENESAS || COMPILE_TEST 895 help 896 SPI driver for SuperH HSPI blocks. 897 898config SPI_SIFIVE 899 tristate "SiFive SPI controller" 900 depends on HAS_IOMEM 901 help 902 This exposes the SPI controller IP from SiFive. 903 904config SPI_SLAVE_MT27XX 905 tristate "MediaTek SPI slave device" 906 depends on ARCH_MEDIATEK || COMPILE_TEST 907 depends on SPI_SLAVE 908 help 909 This selects the MediaTek(R) SPI slave device driver. 910 If you want to use MediaTek(R) SPI slave interface, 911 say Y or M here.If you are not sure, say N. 912 SPI slave drivers for Mediatek MT27XX series ARM SoCs. 913 914config SPI_SN_F_OSPI 915 tristate "Socionext F_OSPI SPI flash controller" 916 depends on OF && HAS_IOMEM 917 depends on SPI_MEM 918 help 919 This enables support for the Socionext F_OSPI controller 920 for connecting an SPI Flash memory over up to 8-bit wide bus. 921 It supports indirect access mode only. 922 923config SPI_SPRD 924 tristate "Spreadtrum SPI controller" 925 depends on ARCH_SPRD || COMPILE_TEST 926 help 927 SPI driver for Spreadtrum SoCs. 928 929config SPI_SPRD_ADI 930 tristate "Spreadtrum ADI controller" 931 depends on ARCH_SPRD || COMPILE_TEST 932 depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK) 933 help 934 ADI driver based on SPI for Spreadtrum SoCs. 935 936config SPI_STM32 937 tristate "STMicroelectronics STM32 SPI controller" 938 depends on ARCH_STM32 || COMPILE_TEST 939 help 940 SPI driver for STMicroelectronics STM32 SoCs. 941 942 STM32 SPI controller supports DMA and PIO modes. When DMA 943 is not available, the driver automatically falls back to 944 PIO mode. 945 946config SPI_STM32_QSPI 947 tristate "STMicroelectronics STM32 QUAD SPI controller" 948 depends on ARCH_STM32 || COMPILE_TEST 949 depends on OF 950 depends on SPI_MEM 951 help 952 This enables support for the Quad SPI controller in master mode. 953 This driver does not support generic SPI. The implementation only 954 supports spi-mem interface. 955 956config SPI_ST_SSC4 957 tristate "STMicroelectronics SPI SSC-based driver" 958 depends on ARCH_STI || COMPILE_TEST 959 help 960 STMicroelectronics SoCs support for SPI. If you say yes to 961 this option, support will be included for the SSC driven SPI. 962 963config SPI_SUN4I 964 tristate "Allwinner A10 SoCs SPI controller" 965 depends on ARCH_SUNXI || COMPILE_TEST 966 help 967 SPI driver for Allwinner sun4i, sun5i and sun7i SoCs 968 969config SPI_SUN6I 970 tristate "Allwinner A31 SPI controller" 971 depends on ARCH_SUNXI || COMPILE_TEST 972 depends on RESET_CONTROLLER 973 help 974 This enables using the SPI controller on the Allwinner A31 SoCs. 975 976config SPI_SUNPLUS_SP7021 977 tristate "Sunplus SP7021 SPI controller" 978 depends on SOC_SP7021 || COMPILE_TEST 979 help 980 This enables Sunplus SP7021 SPI controller driver on the SP7021 SoCs. 981 This driver can also be built as a module. If so, the module will be 982 called as spi-sunplus-sp7021. 983 984 If you have a Sunplus SP7021 platform say Y here. 985 If unsure, say N. 986 987config SPI_SYNQUACER 988 tristate "Socionext's SynQuacer HighSpeed SPI controller" 989 depends on ARCH_SYNQUACER || COMPILE_TEST 990 help 991 SPI driver for Socionext's High speed SPI controller which provides 992 various operating modes for interfacing to serial peripheral devices 993 that use the de-facto standard SPI protocol. 994 995 It also supports the new dual-bit and quad-bit SPI protocol. 996 997config SPI_MXIC 998 tristate "Macronix MX25F0A SPI controller" 999 depends on SPI_MASTER 1000 imply MTD_NAND_ECC_MXIC 1001 help 1002 This selects the Macronix MX25F0A SPI controller driver. 1003 1004config SPI_MXS 1005 tristate "Freescale MXS SPI controller" 1006 depends on ARCH_MXS 1007 select STMP_DEVICE 1008 help 1009 SPI driver for Freescale MXS devices. 1010 1011config SPI_TEGRA210_QUAD 1012 tristate "NVIDIA Tegra QSPI Controller" 1013 depends on ARCH_TEGRA || COMPILE_TEST 1014 depends on RESET_CONTROLLER 1015 help 1016 QSPI driver for NVIDIA Tegra QSPI Controller interface. This 1017 controller is different from the SPI controller and is available 1018 on Tegra SoCs starting from Tegra210. 1019 1020config SPI_TEGRA114 1021 tristate "NVIDIA Tegra114 SPI Controller" 1022 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST 1023 depends on RESET_CONTROLLER 1024 help 1025 SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller 1026 is different than the older SoCs SPI controller and also register interface 1027 get changed with this controller. 1028 1029config SPI_TEGRA20_SFLASH 1030 tristate "Nvidia Tegra20 Serial flash Controller" 1031 depends on ARCH_TEGRA || COMPILE_TEST 1032 depends on RESET_CONTROLLER 1033 help 1034 SPI driver for Nvidia Tegra20 Serial flash Controller interface. 1035 The main usecase of this controller is to use spi flash as boot 1036 device. 1037 1038config SPI_TEGRA20_SLINK 1039 tristate "Nvidia Tegra20/Tegra30 SLINK Controller" 1040 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST 1041 depends on RESET_CONTROLLER 1042 help 1043 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface. 1044 1045config SPI_THUNDERX 1046 tristate "Cavium ThunderX SPI controller" 1047 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST) 1048 help 1049 SPI host driver for the hardware found on Cavium ThunderX 1050 SOCs. 1051 1052config SPI_TOPCLIFF_PCH 1053 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI" 1054 depends on PCI && (X86_32 || MIPS || COMPILE_TEST) 1055 help 1056 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 1057 used in some x86 embedded processors. 1058 1059 This driver also supports the ML7213/ML7223/ML7831, a companion chip 1060 for the Atom E6xx series and compatible with the Intel EG20T PCH. 1061 1062config SPI_UNIPHIER 1063 tristate "Socionext UniPhier SPI Controller" 1064 depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF 1065 depends on HAS_IOMEM 1066 help 1067 This enables a driver for the Socionext UniPhier SoC SCSSI SPI controller. 1068 1069 UniPhier SoCs have SCSSI and MCSSI SPI controllers. 1070 Every UniPhier SoC has SCSSI which supports single channel. 1071 Older UniPhier Pro4/Pro5 also has MCSSI which support multiple channels. 1072 This driver supports SCSSI only. 1073 1074 If your SoC supports SCSSI, say Y here. 1075 1076config SPI_XCOMM 1077 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver" 1078 depends on I2C 1079 help 1080 Support for the SPI-I2C bridge found on the Analog Devices 1081 AD-FMCOMMS1-EBZ board. 1082 1083config SPI_XILINX 1084 tristate "Xilinx SPI controller common module" 1085 depends on HAS_IOMEM 1086 select SPI_BITBANG 1087 help 1088 This exposes the SPI controller IP from the Xilinx EDK. 1089 1090 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 1091 Product Specification document (DS464) for hardware details. 1092 1093 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 1094 1095config SPI_XLP 1096 tristate "Cavium ThunderX2 SPI controller driver" 1097 depends on ARCH_THUNDER2 || COMPILE_TEST 1098 help 1099 Enable support for the SPI controller on the Cavium ThunderX2. 1100 (Originally on Netlogic XLP SoCs.) 1101 1102 If you have a Cavium ThunderX2 platform say Y here. 1103 If unsure, say N. 1104 1105config SPI_XTENSA_XTFPGA 1106 tristate "Xtensa SPI controller for xtfpga" 1107 depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST 1108 select SPI_BITBANG 1109 help 1110 SPI driver for xtfpga SPI master controller. 1111 1112 This simple SPI master controller is built into xtfpga bitstreams 1113 and is used to control daughterboard audio codec. It always transfers 1114 16 bit words in SPI mode 0, automatically asserting CS on transfer 1115 start and deasserting on end. 1116 1117config SPI_ZYNQ_QSPI 1118 tristate "Xilinx Zynq QSPI controller" 1119 depends on ARCH_ZYNQ || COMPILE_TEST 1120 help 1121 This enables support for the Zynq Quad SPI controller 1122 in master mode. 1123 This controller only supports SPI memory interface. 1124 1125config SPI_ZYNQMP_GQSPI 1126 tristate "Xilinx ZynqMP GQSPI controller" 1127 depends on (SPI_MASTER && HAS_DMA) || COMPILE_TEST 1128 help 1129 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC. 1130 1131config SPI_AMD 1132 tristate "AMD SPI controller" 1133 depends on SPI_MASTER || COMPILE_TEST 1134 help 1135 Enables SPI controller driver for AMD SoC. 1136 1137# 1138# Add new SPI master controllers in alphabetical order above this line 1139# 1140 1141comment "SPI Multiplexer support" 1142 1143config SPI_MUX 1144 tristate "SPI multiplexer support" 1145 select MULTIPLEXER 1146 help 1147 This adds support for SPI multiplexers. Each SPI mux will be 1148 accessible as a SPI controller, the devices behind the mux will appear 1149 to be chip selects on this controller. It is still necessary to 1150 select one or more specific mux-controller drivers. 1151 1152# 1153# There are lots of SPI device types, with sensors and memory 1154# being probably the most widely used ones. 1155# 1156comment "SPI Protocol Masters" 1157 1158config SPI_SPIDEV 1159 tristate "User mode SPI device driver support" 1160 help 1161 This supports user mode SPI protocol drivers. 1162 1163config SPI_LOOPBACK_TEST 1164 tristate "spi loopback test framework support" 1165 depends on m 1166 help 1167 This enables the SPI loopback testing framework driver 1168 1169 primarily used for development of spi_master drivers 1170 and to detect regressions 1171 1172config SPI_TLE62X0 1173 tristate "Infineon TLE62X0 (for power switching)" 1174 depends on SYSFS 1175 help 1176 SPI driver for Infineon TLE62X0 series line driver chips, 1177 such as the TLE6220, TLE6230 and TLE6240. This provides a 1178 sysfs interface, with each line presented as a kind of GPIO 1179 exposing both switch control and diagnostic feedback. 1180 1181# 1182# Add new SPI protocol masters in alphabetical order above this line 1183# 1184 1185endif # SPI_MASTER 1186 1187# 1188# SLAVE side ... listening to other SPI masters 1189# 1190 1191config SPI_SLAVE 1192 bool "SPI slave protocol handlers" 1193 help 1194 If your system has a slave-capable SPI controller, you can enable 1195 slave protocol handlers. 1196 1197if SPI_SLAVE 1198 1199config SPI_SLAVE_TIME 1200 tristate "SPI slave handler reporting boot up time" 1201 help 1202 SPI slave handler responding with the time of reception of the last 1203 SPI message. 1204 1205config SPI_SLAVE_SYSTEM_CONTROL 1206 tristate "SPI slave handler controlling system state" 1207 help 1208 SPI slave handler to allow remote control of system reboot, power 1209 off, halt, and suspend. 1210 1211endif # SPI_SLAVE 1212 1213config SPI_DYNAMIC 1214 def_bool ACPI || OF_DYNAMIC || SPI_SLAVE 1215 1216endif # SPI 1217