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