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