1 # SPDX-License-Identifier: GPL-2.0-only
3 # SPI driver configuration
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.
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.
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.
29 bool "Debug support for SPI drivers"
30 depends on DEBUG_KERNEL
32 Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
33 sysfs, and debugfs support in SPI controller and protocol drivers.
36 # MASTER side ... talking to discrete SPI slave chips including microcontrollers
40 # bool "SPI Master Support"
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
52 bool "SPI memory extension"
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.
58 comment "SPI Master Controller Drivers"
61 tristate "Altera SPI Controller platform driver"
62 select SPI_ALTERA_CORE
65 This is the driver for the Altera SPI Controller.
67 config SPI_ALTERA_CORE
68 tristate "Altera SPI Controller core code" if COMPILE_TEST
71 "The core code for the Altera SPI Controller"
74 tristate "DFL bus driver for Altera SPI Controller"
76 select SPI_ALTERA_CORE
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.
83 tristate "Qualcomm Atheros AR934X/QCA95XX SPI controller driver"
84 depends on ATH79 || COMPILE_TEST
86 This enables support for the SPI controller present on the
87 Qualcomm Atheros AR934X/QCA95XX SoCs.
90 tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
91 depends on ATH79 || COMPILE_TEST
94 This enables support for the SPI controller present on the
95 Atheros AR71XX/AR724X/AR913X SoCs.
97 config SPI_ARMADA_3700
98 tristate "Marvell Armada 3700 SPI Controller"
99 depends on (ARCH_MVEBU && OF) || COMPILE_TEST
101 This enables support for the SPI controller present on the
102 Marvell Armada 3700 SoCs.
104 config SPI_ASPEED_SMC
105 tristate "Aspeed flash controllers in SPI mode"
106 depends on ARCH_ASPEED || COMPILE_TEST
109 This enables support for the Firmware Memory controller (FMC)
110 in the Aspeed AST2600, AST2500 and AST2400 SoCs when attached
111 to SPI NOR chips, and support for the SPI flash memory
112 controller (SPI) for the host firmware. The implementation
113 only supports SPI NOR.
116 tristate "Atmel SPI Controller"
117 depends on ARCH_AT91 || COMPILE_TEST
120 This selects a driver for the Atmel SPI Controller, present on
123 config SPI_AT91_USART
124 tristate "Atmel USART Controller SPI driver"
125 depends on (ARCH_AT91 || COMPILE_TEST)
126 depends on MFD_AT91_USART
128 This selects a driver for the AT91 USART Controller as SPI Master,
129 present on AT91 and SAMA5 SoC series.
131 config SPI_ATMEL_QUADSPI
132 tristate "Atmel Quad SPI Controller"
133 depends on ARCH_AT91 || COMPILE_TEST
134 depends on OF && HAS_IOMEM
136 This enables support for the Quad SPI controller in master mode.
137 This driver does not support generic SPI. The implementation only
138 supports spi-mem interface.
141 tristate "Au1550/Au1200/Au1300 SPI Controller"
142 depends on MIPS_ALCHEMY
145 If you say yes to this option, support will be included for the
146 PSC SPI controller found on Au1550, Au1200 and Au1300 series.
148 config SPI_AXI_SPI_ENGINE
149 tristate "Analog Devices AXI SPI Engine controller"
152 This enables support for the Analog Devices AXI SPI Engine SPI controller.
153 It is part of the SPI Engine framework that is used in some Analog Devices
154 reference designs for FPGAs.
157 tristate "BCM2835 SPI controller"
159 depends on ARCH_BCM2835 || ARCH_BRCMSTB || COMPILE_TEST
161 This selects a driver for the Broadcom BCM2835 SPI master.
163 The BCM2835 contains two types of SPI master controller; the
164 "universal SPI master", and the regular SPI controller. This driver
165 is for the regular SPI controller. Slave mode operation is not also
168 config SPI_BCM2835AUX
169 tristate "BCM2835 SPI auxiliary controller"
170 depends on ((ARCH_BCM2835 || ARCH_BRCMSTB) && GPIOLIB) || COMPILE_TEST
172 This selects a driver for the Broadcom BCM2835 SPI aux master.
174 The BCM2835 contains two types of SPI master controller; the
175 "universal SPI master", and the regular SPI controller.
176 This driver is for the universal/auxiliary SPI controller.
179 tristate "Broadcom BCM63xx SPI controller"
180 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
182 Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
184 config SPI_BCM63XX_HSSPI
185 tristate "Broadcom BCM63XX HS SPI controller driver"
186 depends on BCM63XX || BMIPS_GENERIC || ARCH_BCMBCA || COMPILE_TEST
188 This enables support for the High Speed SPI controller present on
189 newer Broadcom BCM63XX SoCs.
192 tristate "Broadcom BSPI and MSPI controller support"
193 depends on ARCH_BRCMSTB || ARCH_BCM || ARCH_BCM_IPROC || \
194 BMIPS_GENERIC || COMPILE_TEST
195 default ARCH_BCM_IPROC
197 Enables support for the Broadcom SPI flash and MSPI controller.
198 Select this option for any one of BRCMSTB, iProc NSP and NS2 SoCs
199 based platforms. This driver works for both SPI master for SPI NOR
200 flash device as well as MSPI device.
203 tristate "Utilities for Bitbanging SPI masters"
205 With a few GPIO pins, your system can bitbang the SPI protocol.
206 Select this to get SPI support through I/O pins (GPIO, parallel
207 port, etc). Or, some systems' SPI master controller drivers use
208 this code to manage the per-word or per-transfer accesses to the
209 hardware shift registers.
211 This is library code, and is automatically selected by drivers that
212 need it. You only need to select this explicitly to support driver
213 modules that aren't part of this kernel tree.
216 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
220 This uses a custom parallel port cable to connect to an AVR
221 Butterfly <http://www.atmel.com/products/avr/butterfly>, an
222 inexpensive battery powered microcontroller evaluation board.
223 This same cable can be used to flash new firmware.
226 tristate "Cadence SPI controller"
228 This selects the Cadence SPI controller master driver
229 used by Xilinx Zynq and ZynqMP.
231 config SPI_CADENCE_QUADSPI
232 tristate "Cadence Quad SPI controller"
233 depends on OF && (ARM || ARM64 || X86 || COMPILE_TEST)
235 Enable support for the Cadence Quad SPI Flash controller.
237 Cadence QSPI is a specialized controller for connecting an SPI
238 Flash over 1/2/4-bit wide bus. Enable this option if you have a
239 device with a Cadence QSPI controller and want to access the
240 Flash as an MTD device.
242 config SPI_CADENCE_XSPI
243 tristate "Cadence XSPI controller"
244 depends on (OF || COMPILE_TEST) && HAS_IOMEM
247 Enable support for the Cadence XSPI Flash controller.
249 Cadence XSPI is a specialized controller for connecting an SPI
250 Flash over upto 8bit wide bus. Enable this option if you have a
251 device with a Cadence XSPI controller and want to access the
252 Flash as an MTD device.
255 tristate "CLPS711X host SPI controller"
256 depends on ARCH_CLPS711X || COMPILE_TEST
258 This enables dedicated general purpose SPI/Microwire1-compatible
259 master mode interface (SSI1) for CLPS711X-based CPUs.
261 config SPI_COLDFIRE_QSPI
262 tristate "Freescale Coldfire QSPI controller"
263 depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
265 This enables support for the Coldfire QSPI controller in master
269 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
270 depends on ARCH_DAVINCI || ARCH_KEYSTONE
273 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
275 config SPI_DESIGNWARE
276 tristate "DesignWare SPI controller core support"
279 general driver for SPI controller core from DesignWare
284 bool "DMA support for DW SPI controller"
287 tristate "PCI interface driver for DW SPI core"
291 tristate "Memory-mapped io interface driver for DW SPI core"
295 tristate "Baikal-T1 SPI driver for DW SPI core"
296 depends on MIPS_BAIKAL_T1 || COMPILE_TEST
300 Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI
301 controllers. Two of them are pretty much normal: with IRQ, DMA,
302 FIFOs of 64 words depth, 4x CSs, but the third one as being a
303 part of the Baikal-T1 System Boot Controller has got a very
304 limited resources: no IRQ, no DMA, only a single native
305 chip-select and Tx/Rx FIFO with just 8 words depth available.
306 The later one is normally connected to an external SPI-nor flash
307 of 128Mb (in general can be of bigger size).
309 config SPI_DW_BT1_DIRMAP
310 bool "Directly mapped Baikal-T1 Boot SPI flash support"
311 depends on SPI_DW_BT1
313 Directly mapped SPI flash memory is an interface specific to the
314 Baikal-T1 System Boot Controller. It is a 16MB MMIO region, which
315 can be used to access a peripheral memory device just by
316 reading/writing data from/to it. Note that the system APB bus
317 will stall during each IO from/to the dirmap region until the
318 operation is finished. So try not to use it concurrently with
319 time-critical tasks (like the SPI memory operations implemented
325 tristate "Diolan DLN-2 USB SPI adapter"
328 If you say yes to this option, support will be included for Diolan
329 DLN2, a USB to SPI interface.
331 This driver can also be built as a module. If so, the module
332 will be called spi-dln2.
335 tristate "Cirrus Logic EP93xx SPI controller"
336 depends on ARCH_EP93XX || COMPILE_TEST
338 This enables using the Cirrus EP93xx SPI controller in master
342 bool "Falcon SPI controller support"
343 depends on SOC_FALCON
345 The external bus unit (EBU) found on the FALC-ON SoC has SPI
346 emulation that is designed for serial flash access. This driver
347 has only been tested with m25p80 type chips. The hardware has no
348 support for other types of SPI peripherals.
351 tristate "FSI SPI driver"
354 This enables support for the driver for FSI bus attached SPI
358 tristate "Freescale i.MX LPSPI controller"
359 depends on ARCH_MXC || COMPILE_TEST
361 This enables Freescale i.MX LPSPI controllers in master mode.
363 config SPI_FSL_QUADSPI
364 tristate "Freescale QSPI controller"
365 depends on ARCH_MXC || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST
368 This enables support for the Quad SPI controller in master mode.
369 Up to four flash chips can be connected on two buses with two
371 This controller does not support generic SPI messages. It only
372 supports the high-level SPI memory interface.
375 tristate "GXP SPI driver"
376 depends on ARCH_HPE || COMPILE_TEST
378 This enables support for the driver for GXP bus attached SPI
381 config SPI_HISI_KUNPENG
382 tristate "HiSilicon SPI Controller for Kunpeng SoCs"
383 depends on (ARM64 && ACPI) || COMPILE_TEST
385 This enables support for HiSilicon SPI controller found on
388 This driver can also be built as a module. If so, the module
389 will be called hisi-kunpeng-spi.
391 config SPI_HISI_SFC_V3XX
392 tristate "HiSilicon SPI NOR Flash Controller for Hi16XX chipsets"
393 depends on (ARM64 && ACPI) || COMPILE_TEST
396 This enables support for HiSilicon v3xx SPI NOR flash controller
397 found in hi16xx chipsets.
399 config SPI_NXP_FLEXSPI
400 tristate "NXP Flex SPI controller"
401 depends on ARCH_LAYERSCAPE || HAS_IOMEM
403 This enables support for the Flex SPI controller in master mode.
404 Up to four slave devices can be connected on two buses with two
406 This controller does not support generic SPI messages and only
407 supports the high-level SPI memory interface.
410 tristate "GPIO-based bitbanging SPI Master"
411 depends on GPIOLIB || COMPILE_TEST
414 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
415 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
416 slaves connected to a bus using this driver are configured as usual,
417 except that the spi_board_info.controller_data holds the GPIO number
418 for the chipselect used by this controller driver.
420 Note that this driver often won't achieve even 1 Mbit/sec speeds,
421 making it unusually slow for SPI. If your platform can inline
422 GPIO operations, you should be able to leverage that for better
423 speed with a custom version of this driver; see the source code.
426 tristate "IMG SPFI controller"
427 depends on MIPS || COMPILE_TEST
429 This enables support for the SPFI master controller found on
433 tristate "Freescale i.MX SPI controllers"
434 depends on ARCH_MXC || COMPILE_TEST
436 This enables support for the Freescale i.MX SPI controllers.
439 tristate "Ingenic SoCs SPI controller"
440 depends on MACH_INGENIC || COMPILE_TEST
442 This enables support for the Ingenic SoCs SPI controller.
444 To compile this driver as a module, choose M here: the module
445 will be called spi-ingenic.
451 tristate "Intel PCH/PCU SPI flash PCI driver (DANGEROUS)"
453 depends on X86 || COMPILE_TEST
457 This enables PCI support for the Intel PCH/PCU SPI controller in
458 master mode. This controller is present in modern Intel hardware
459 and is used to hold BIOS and other persistent settings. Using
460 this driver it is possible to upgrade BIOS directly from Linux.
462 Say N here unless you know what you are doing. Overwriting the
463 SPI flash may render the system unbootable.
465 To compile this driver as a module, choose M here: the module
466 will be called spi-intel-pci.
468 config SPI_INTEL_PLATFORM
469 tristate "Intel PCH/PCU SPI flash platform driver (DANGEROUS)"
470 depends on X86 || COMPILE_TEST
474 This enables platform support for the Intel PCH/PCU SPI
475 controller in master mode. This controller is present in modern
476 Intel hardware and is used to hold BIOS and other persistent
477 settings. Using this driver it is possible to upgrade BIOS
480 Say N here unless you know what you are doing. Overwriting the
481 SPI flash may render the system unbootable.
483 To compile this driver as a module, choose M here: the module
484 will be called spi-intel-platform.
487 tristate "J-Core SPI Master"
488 depends on OF && (SUPERH || COMPILE_TEST)
490 This enables support for the SPI master controller in the J-Core
491 synthesizable, open source SoC.
494 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
498 This driver supports the NS LM70 LLP Evaluation Board,
499 which interfaces to an LM70 temperature sensor using
502 config SPI_LP8841_RTC
503 tristate "ICP DAS LP-8841 SPI Controller for RTC"
504 depends on MACH_PXA27X_DT || COMPILE_TEST
506 This driver provides an SPI master device to drive Maxim
507 DS-1302 real time clock.
509 Say N here unless you plan to run the kernel on an ICP DAS
510 LP-8x4x industrial computer.
513 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
514 depends on PPC_MPC52xx
516 This drivers supports the MPC52xx SPI controller in master SPI
519 config SPI_MPC52xx_PSC
520 tristate "Freescale MPC52xx PSC SPI controller"
521 depends on PPC_MPC52xx
523 This enables using the Freescale MPC52xx Programmable Serial
524 Controller in master SPI mode.
526 config SPI_MPC512x_PSC
527 tristate "Freescale MPC512x PSC SPI controller"
528 depends on PPC_MPC512x
530 This enables using the Freescale MPC5121 Programmable Serial
531 Controller in SPI master mode.
542 tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"
545 select SPI_FSL_CPM if FSL_SOC
547 This enables using the Freescale SPI controllers in master mode.
548 MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
549 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
550 This also enables using the Aeroflex Gaisler GRLIB SPI controller in
554 tristate "Freescale DSPI controller"
556 depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST
558 This enables support for the Freescale DSPI controller in master
559 mode. VF610, LS1021A and ColdFire platforms uses the controller.
562 tristate "Freescale eSPI controller"
565 This enables using the Freescale eSPI controllers in master mode.
566 From MPC8536, 85xx platform uses the controller, and all P10xx,
567 P20xx, P30xx,P40xx, P50xx uses this controller.
569 config SPI_MESON_SPICC
570 tristate "Amlogic Meson SPICC controller"
571 depends on COMMON_CLK
572 depends on ARCH_MESON || COMPILE_TEST
574 This enables master mode support for the SPICC (SPI communication
575 controller) available in Amlogic Meson SoCs.
577 config SPI_MESON_SPIFC
578 tristate "Amlogic Meson SPIFC controller"
579 depends on ARCH_MESON || COMPILE_TEST
582 This enables master mode support for the SPIFC (SPI flash
583 controller) available in Amlogic Meson SoCs.
585 config SPI_MICROCHIP_CORE
586 tristate "Microchip FPGA SPI controllers"
587 depends on SPI_MASTER
589 This enables the SPI driver for Microchip FPGA SPI controllers.
590 Say Y or M here if you want to use the "hard" controllers on
592 If built as a module, it will be called spi-microchip-core.
595 tristate "MediaTek SPI controller"
596 depends on ARCH_MEDIATEK || COMPILE_TEST
598 This selects the MediaTek(R) SPI bus driver.
599 If you want to use MediaTek(R) SPI interface,
600 say Y or M here.If you are not sure, say N.
601 SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs.
604 tristate "MediaTek MT7621 SPI Controller"
605 depends on RALINK || COMPILE_TEST
607 This selects a driver for the MediaTek MT7621 SPI Controller.
610 tristate "MediaTek SPI NOR controller"
611 depends on ARCH_MEDIATEK || COMPILE_TEST
613 This enables support for SPI NOR controller found on MediaTek
614 ARM SoCs. This is a controller specifically for SPI NOR flash.
615 It can perform generic SPI transfers up to 6 bytes via generic
616 SPI interface as well as several SPI NOR specific instructions
617 via SPI MEM interface.
620 tristate "MediaTek SPI NAND Flash Interface"
621 depends on ARCH_MEDIATEK || COMPILE_TEST
622 depends on MTD_NAND_ECC_MEDIATEK
624 This enables support for SPI-NAND mode on the MediaTek NAND
625 Flash Interface found on MediaTek ARM SoCs. This controller
626 is implemented as a SPI-MEM controller with pipelined ECC
630 tristate "Nuvoton NPCM FLASH Interface Unit"
631 depends on ARCH_NPCM || COMPILE_TEST
632 depends on OF && HAS_IOMEM
634 This enables support for the Flash Interface Unit SPI controller
636 This driver does not support generic SPI. The implementation only
637 supports spi-mem interface.
640 tristate "Nuvoton NPCM PSPI Controller"
641 depends on ARCH_NPCM || COMPILE_TEST
643 This driver provides support for Nuvoton NPCM BMC
644 Peripheral SPI controller in master mode.
646 config SPI_LANTIQ_SSC
647 tristate "Lantiq SSC SPI controller"
648 depends on LANTIQ || X86 || COMPILE_TEST
650 This driver supports the Lantiq SSC SPI controller in master
651 mode. This controller is found on Intel (former Lantiq) SoCs like
652 the Danube, Falcon, xRX200, xRX300, Lightning Mountain.
655 tristate "OpenCores tiny SPI"
656 depends on GPIOLIB || COMPILE_TEST
659 This is the driver for OpenCores tiny SPI master controller.
662 tristate "Cavium OCTEON SPI controller"
663 depends on CAVIUM_OCTEON_SOC
665 SPI host driver for the hardware found on some Cavium OCTEON
668 config SPI_OMAP_UWIRE
669 tristate "OMAP1 MicroWire"
670 depends on ARCH_OMAP1 || (ARM && COMPILE_TEST)
673 This hooks up to the MicroWire controller on OMAP1 chips.
676 tristate "McSPI driver for OMAP"
677 depends on ARCH_OMAP2PLUS || ARCH_K3 || COMPILE_TEST
680 SPI master controller for OMAP24XX and later Multichannel SPI
684 tristate "DRA7xxx QSPI controller support"
685 depends on ARCH_OMAP2PLUS || COMPILE_TEST
687 QSPI master controller for DRA7xxx used for flash devices.
688 This device supports single, dual and quad read support, while
689 it only supports single write mode.
692 tristate "OMAP SPI 100K"
693 depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
695 OMAP SPI 100K master controller for omap7xx boards.
698 tristate "Orion SPI master"
699 depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST
701 This enables using the SPI master controller on the Orion
705 tristate "Microchip PIC32 series SPI"
706 depends on MACH_PIC32 || COMPILE_TEST
708 SPI driver for Microchip PIC32 SPI master controller.
711 tristate "Microchip PIC32 Quad SPI driver"
712 depends on MACH_PIC32 || COMPILE_TEST
714 SPI driver for PIC32 Quad SPI controller.
717 tristate "ARM AMBA PL022 SSP controller"
719 default y if ARCH_REALVIEW
720 default y if INTEGRATOR_IMPD1
721 default y if ARCH_VERSATILE
723 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
724 controller. If you have an embedded system with an AMBA(R)
725 bus and a PL022 controller, say Y or M here.
728 tristate "PPC4xx SPI Controller"
729 depends on PPC32 && 4xx
732 This selects a driver for the PPC4xx SPI Controller.
735 tristate "PXA2xx SSP SPI master"
736 depends on ARCH_PXA || ARCH_MMP || PCI || ACPI || COMPILE_TEST
737 select PXA_SSP if ARCH_PXA || ARCH_MMP
739 This enables using a PXA2xx or Sodaville SSP port as a SPI master
740 controller. The driver can be configured to use any SSP port and
741 additional documentation can be found a Documentation/spi/pxa2xx.rst.
743 config SPI_PXA2XX_PCI
744 def_tristate SPI_PXA2XX && PCI && COMMON_CLK
747 tristate "Rockchip SPI controller driver"
749 This selects a driver for Rockchip SPI controller.
751 If you say yes to this option, support will be included for
752 RK3066, RK3188 and RK3288 families of SPI controller.
753 Rockchip SPI controller support DMA transport and PIO mode.
754 The main usecase of this controller is to use spi flash as boot
757 config SPI_ROCKCHIP_SFC
758 tristate "Rockchip Serial Flash Controller (SFC)"
759 depends on ARCH_ROCKCHIP || COMPILE_TEST
760 depends on HAS_IOMEM && HAS_DMA
762 This enables support for Rockchip serial flash controller. This
763 is a specialized controller used to access SPI flash on some
766 ROCKCHIP SFC supports DMA and PIO modes. When DMA is not available,
767 the driver automatically falls back to PIO mode.
770 tristate "Mikrotik RB4XX SPI master"
771 depends on SPI_MASTER && ATH79
773 SPI controller driver for the Mikrotik RB4xx series boards.
776 tristate "Renesas RPC-IF SPI driver"
777 depends on RENESAS_RPCIF
779 SPI driver for Renesas R-Car Gen3 or RZ/G2 RPC-IF.
782 tristate "Renesas RSPI/QSPI controller"
783 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
785 SPI driver for Renesas RSPI and QSPI blocks.
788 tristate "QTI QSPI controller"
791 QSPI(Quad SPI) driver for Qualcomm QSPI controller.
794 tristate "Qualcomm SPI controller with QUP interface"
795 depends on ARCH_QCOM || COMPILE_TEST
797 Qualcomm Universal Peripheral (QUP) core is an AHB slave that
798 provides a common data path (an output FIFO and an input FIFO)
799 for serial peripheral interface (SPI) mini-core. SPI in master
800 mode supports up to 50MHz, up to four chip selects, programmable
801 data path from 4 bits to 32 bits and numerous protocol variants.
803 This driver can also be built as a module. If so, the module
804 will be called spi_qup.
807 tristate "Qualcomm GENI based SPI controller"
808 depends on QCOM_GENI_SE
810 This driver supports GENI serial engine based SPI controller in
811 master mode on the Qualcomm Technologies Inc.'s SoCs. If you say
812 yes to this option, support will be included for the built-in SPI
813 interface on the Qualcomm Technologies Inc.'s SoCs.
815 This driver can also be built as a module. If so, the module
816 will be called spi-geni-qcom.
819 tristate "Samsung S3C24XX series SPI"
820 depends on ARCH_S3C24XX
823 SPI driver for Samsung S3C24XX series ARM SoCs
825 config SPI_S3C24XX_FIQ
826 bool "S3C24XX driver with FIQ pseudo-DMA"
827 depends on SPI_S3C24XX
830 Enable FIQ support for the S3C24XX SPI driver to provide pseudo
831 DMA by using the fast-interrupt request framework, This allows
832 the driver to get DMA-like performance when there are either
833 no free DMA channels, or when doing transfers that required both
834 TX and RX data paths.
837 tristate "Samsung S3C64XX/Exynos SoC series type SPI"
838 depends on (PLAT_SAMSUNG || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST)
840 SPI driver for Samsung S3C64XX, S5Pv210 and Exynos SoCs.
841 Choose Y/M here only if you build for such Samsung SoC.
844 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
847 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
850 tristate "SuperH MSIOF SPI controller"
852 depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
854 SPI driver for SuperH and SH Mobile MSIOF blocks.
857 tristate "SuperH SPI controller"
858 depends on SUPERH || COMPILE_TEST
860 SPI driver for SuperH SPI blocks.
863 tristate "SuperH SCI SPI controller"
867 SPI driver for SuperH SCI blocks.
870 tristate "SuperH HSPI controller"
871 depends on ARCH_RENESAS || COMPILE_TEST
873 SPI driver for SuperH HSPI blocks.
876 tristate "SiFive SPI controller"
879 This exposes the SPI controller IP from SiFive.
881 config SPI_SLAVE_MT27XX
882 tristate "MediaTek SPI slave device"
883 depends on ARCH_MEDIATEK || COMPILE_TEST
886 This selects the MediaTek(R) SPI slave device driver.
887 If you want to use MediaTek(R) SPI slave interface,
888 say Y or M here.If you are not sure, say N.
889 SPI slave drivers for Mediatek MT27XX series ARM SoCs.
892 tristate "Spreadtrum SPI controller"
893 depends on ARCH_SPRD || COMPILE_TEST
895 SPI driver for Spreadtrum SoCs.
898 tristate "Spreadtrum ADI controller"
899 depends on ARCH_SPRD || COMPILE_TEST
900 depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK)
902 ADI driver based on SPI for Spreadtrum SoCs.
905 tristate "STMicroelectronics STM32 SPI controller"
906 depends on ARCH_STM32 || COMPILE_TEST
908 SPI driver for STMicroelectronics STM32 SoCs.
910 STM32 SPI controller supports DMA and PIO modes. When DMA
911 is not available, the driver automatically falls back to
914 config SPI_STM32_QSPI
915 tristate "STMicroelectronics STM32 QUAD SPI controller"
916 depends on ARCH_STM32 || COMPILE_TEST
920 This enables support for the Quad SPI controller in master mode.
921 This driver does not support generic SPI. The implementation only
922 supports spi-mem interface.
925 tristate "STMicroelectronics SPI SSC-based driver"
926 depends on ARCH_STI || COMPILE_TEST
928 STMicroelectronics SoCs support for SPI. If you say yes to
929 this option, support will be included for the SSC driven SPI.
932 tristate "Allwinner A10 SoCs SPI controller"
933 depends on ARCH_SUNXI || COMPILE_TEST
935 SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
938 tristate "Allwinner A31 SPI controller"
939 depends on ARCH_SUNXI || COMPILE_TEST
940 depends on RESET_CONTROLLER
942 This enables using the SPI controller on the Allwinner A31 SoCs.
944 config SPI_SUNPLUS_SP7021
945 tristate "Sunplus SP7021 SPI controller"
946 depends on SOC_SP7021 || COMPILE_TEST
948 This enables Sunplus SP7021 SPI controller driver on the SP7021 SoCs.
949 This driver can also be built as a module. If so, the module will be
950 called as spi-sunplus-sp7021.
952 If you have a Sunplus SP7021 platform say Y here.
956 tristate "Socionext's SynQuacer HighSpeed SPI controller"
957 depends on ARCH_SYNQUACER || COMPILE_TEST
959 SPI driver for Socionext's High speed SPI controller which provides
960 various operating modes for interfacing to serial peripheral devices
961 that use the de-facto standard SPI protocol.
963 It also supports the new dual-bit and quad-bit SPI protocol.
966 tristate "Macronix MX25F0A SPI controller"
967 depends on SPI_MASTER
968 imply MTD_NAND_ECC_MXIC
970 This selects the Macronix MX25F0A SPI controller driver.
973 tristate "Freescale MXS SPI controller"
977 SPI driver for Freescale MXS devices.
979 config SPI_TEGRA210_QUAD
980 tristate "NVIDIA Tegra QSPI Controller"
981 depends on ARCH_TEGRA || COMPILE_TEST
982 depends on RESET_CONTROLLER
984 QSPI driver for NVIDIA Tegra QSPI Controller interface. This
985 controller is different from the SPI controller and is available
986 on Tegra SoCs starting from Tegra210.
989 tristate "NVIDIA Tegra114 SPI Controller"
990 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
991 depends on RESET_CONTROLLER
993 SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
994 is different than the older SoCs SPI controller and also register interface
995 get changed with this controller.
997 config SPI_TEGRA20_SFLASH
998 tristate "Nvidia Tegra20 Serial flash Controller"
999 depends on ARCH_TEGRA || COMPILE_TEST
1000 depends on RESET_CONTROLLER
1002 SPI driver for Nvidia Tegra20 Serial flash Controller interface.
1003 The main usecase of this controller is to use spi flash as boot
1006 config SPI_TEGRA20_SLINK
1007 tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
1008 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
1009 depends on RESET_CONTROLLER
1011 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
1014 tristate "Cavium ThunderX SPI controller"
1015 depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
1017 SPI host driver for the hardware found on Cavium ThunderX
1020 config SPI_TOPCLIFF_PCH
1021 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
1022 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
1024 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
1025 used in some x86 embedded processors.
1027 This driver also supports the ML7213/ML7223/ML7831, a companion chip
1028 for the Atom E6xx series and compatible with the Intel EG20T PCH.
1031 tristate "Socionext UniPhier SPI Controller"
1032 depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF
1033 depends on HAS_IOMEM
1035 This enables a driver for the Socionext UniPhier SoC SCSSI SPI controller.
1037 UniPhier SoCs have SCSSI and MCSSI SPI controllers.
1038 Every UniPhier SoC has SCSSI which supports single channel.
1039 Older UniPhier Pro4/Pro5 also has MCSSI which support multiple channels.
1040 This driver supports SCSSI only.
1042 If your SoC supports SCSSI, say Y here.
1045 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
1048 Support for the SPI-I2C bridge found on the Analog Devices
1049 AD-FMCOMMS1-EBZ board.
1052 tristate "Xilinx SPI controller common module"
1053 depends on HAS_IOMEM
1056 This exposes the SPI controller IP from the Xilinx EDK.
1058 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
1059 Product Specification document (DS464) for hardware details.
1061 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
1064 tristate "Cavium ThunderX2 SPI controller driver"
1065 depends on ARCH_THUNDER2 || COMPILE_TEST
1067 Enable support for the SPI controller on the Cavium ThunderX2.
1068 (Originally on Netlogic XLP SoCs.)
1070 If you have a Cavium ThunderX2 platform say Y here.
1073 config SPI_XTENSA_XTFPGA
1074 tristate "Xtensa SPI controller for xtfpga"
1075 depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
1078 SPI driver for xtfpga SPI master controller.
1080 This simple SPI master controller is built into xtfpga bitstreams
1081 and is used to control daughterboard audio codec. It always transfers
1082 16 bit words in SPI mode 0, automatically asserting CS on transfer
1083 start and deasserting on end.
1085 config SPI_ZYNQ_QSPI
1086 tristate "Xilinx Zynq QSPI controller"
1087 depends on ARCH_ZYNQ || COMPILE_TEST
1089 This enables support for the Zynq Quad SPI controller
1091 This controller only supports SPI memory interface.
1093 config SPI_ZYNQMP_GQSPI
1094 tristate "Xilinx ZynqMP GQSPI controller"
1095 depends on (SPI_MASTER && HAS_DMA) || COMPILE_TEST
1097 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
1100 tristate "AMD SPI controller"
1101 depends on SPI_MASTER || COMPILE_TEST
1103 Enables SPI controller driver for AMD SoC.
1106 # Add new SPI master controllers in alphabetical order above this line
1109 comment "SPI Multiplexer support"
1112 tristate "SPI multiplexer support"
1115 This adds support for SPI multiplexers. Each SPI mux will be
1116 accessible as a SPI controller, the devices behind the mux will appear
1117 to be chip selects on this controller. It is still necessary to
1118 select one or more specific mux-controller drivers.
1121 # There are lots of SPI device types, with sensors and memory
1122 # being probably the most widely used ones.
1124 comment "SPI Protocol Masters"
1127 tristate "User mode SPI device driver support"
1129 This supports user mode SPI protocol drivers.
1131 Note that this application programming interface is EXPERIMENTAL
1132 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
1134 config SPI_LOOPBACK_TEST
1135 tristate "spi loopback test framework support"
1138 This enables the SPI loopback testing framework driver
1140 primarily used for development of spi_master drivers
1141 and to detect regressions
1144 tristate "Infineon TLE62X0 (for power switching)"
1147 SPI driver for Infineon TLE62X0 series line driver chips,
1148 such as the TLE6220, TLE6230 and TLE6240. This provides a
1149 sysfs interface, with each line presented as a kind of GPIO
1150 exposing both switch control and diagnostic feedback.
1153 # Add new SPI protocol masters in alphabetical order above this line
1159 # SLAVE side ... listening to other SPI masters
1163 bool "SPI slave protocol handlers"
1165 If your system has a slave-capable SPI controller, you can enable
1166 slave protocol handlers.
1170 config SPI_SLAVE_TIME
1171 tristate "SPI slave handler reporting boot up time"
1173 SPI slave handler responding with the time of reception of the last
1176 config SPI_SLAVE_SYSTEM_CONTROL
1177 tristate "SPI slave handler controlling system state"
1179 SPI slave handler to allow remote control of system reboot, power
1180 off, halt, and suspend.
1185 def_bool ACPI || OF_DYNAMIC || SPI_SLAVE