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