xref: /openbmc/linux/drivers/spi/Kconfig (revision bb970707)
1#
2# SPI driver configuration
3#
4# NOTE:  the reason this doesn't show SPI slave support is mostly that
5# nobody's needed a slave side API yet.  The master-role API is not
6# fully appropriate there, so it'd need some thought to do well.
7#
8menuconfig SPI
9	bool "SPI support"
10	depends on HAS_IOMEM
11	help
12	  The "Serial Peripheral Interface" is a low level synchronous
13	  protocol.  Chips that support SPI can have data transfer rates
14	  up to several tens of Mbit/sec.  Chips are addressed with a
15	  controller and a chipselect.  Most SPI slaves don't support
16	  dynamic device discovery; some are even write-only or read-only.
17
18	  SPI is widely used by microcontrollers to talk with sensors,
19	  eeprom and flash memory, codecs and various other controller
20	  chips, analog to digital (and d-to-a) converters, and more.
21	  MMC and SD cards can be accessed using SPI protocol; and for
22	  DataFlash cards used in MMC sockets, SPI must always be used.
23
24	  SPI is one of a family of similar protocols using a four wire
25	  interface (select, clock, data in, data out) including Microwire
26	  (half duplex), SSP, SSI, and PSP.  This driver framework should
27	  work with most such devices and controllers.
28
29if SPI
30
31config SPI_DEBUG
32	bool "Debug support for SPI drivers"
33	depends on DEBUG_KERNEL
34	help
35	  Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
36	  sysfs, and debugfs support in SPI controller and protocol drivers.
37
38#
39# MASTER side ... talking to discrete SPI slave chips including microcontrollers
40#
41
42config SPI_MASTER
43#	bool "SPI Master Support"
44	bool
45	default SPI
46	help
47	  If your system has an master-capable SPI controller (which
48	  provides the clock and chipselect), you can enable that
49	  controller and the protocol drivers for the SPI slave chips
50	  that are connected.
51
52if SPI_MASTER
53
54comment "SPI Master Controller Drivers"
55
56config SPI_ALTERA
57	tristate "Altera SPI Controller"
58	select SPI_BITBANG
59	help
60	  This is the driver for the Altera SPI Controller.
61
62config SPI_ATH79
63	tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
64	depends on ATH79 && GPIOLIB
65	select SPI_BITBANG
66	help
67	  This enables support for the SPI controller present on the
68	  Atheros AR71XX/AR724X/AR913X SoCs.
69
70config SPI_ATMEL
71	tristate "Atmel SPI Controller"
72	depends on HAS_DMA
73	depends on (ARCH_AT91 || AVR32 || COMPILE_TEST)
74	help
75	  This selects a driver for the Atmel SPI Controller, present on
76	  many AT32 (AVR32) and AT91 (ARM) chips.
77
78config SPI_AU1550
79	tristate "Au1550/Au1200/Au1300 SPI Controller"
80	depends on MIPS_ALCHEMY
81	select SPI_BITBANG
82	help
83	  If you say yes to this option, support will be included for the
84	  PSC SPI controller found on Au1550, Au1200 and Au1300 series.
85
86config SPI_AXI_SPI_ENGINE
87	tristate "Analog Devices AXI SPI Engine controller"
88	depends on HAS_IOMEM
89	help
90	  This enables support for the Analog Devices AXI SPI Engine SPI controller.
91	  It is part of the SPI Engine framework that is used in some Analog Devices
92	  reference designs for FPGAs.
93
94config SPI_BCM2835
95	tristate "BCM2835 SPI controller"
96	depends on GPIOLIB
97	depends on ARCH_BCM2835 || COMPILE_TEST
98	help
99	  This selects a driver for the Broadcom BCM2835 SPI master.
100
101	  The BCM2835 contains two types of SPI master controller; the
102	  "universal SPI master", and the regular SPI controller. This driver
103	  is for the regular SPI controller. Slave mode operation is not also
104	  not supported.
105
106config SPI_BCM2835AUX
107	tristate "BCM2835 SPI auxiliary controller"
108	depends on (ARCH_BCM2835 && GPIOLIB) || COMPILE_TEST
109	help
110	  This selects a driver for the Broadcom BCM2835 SPI aux master.
111
112	  The BCM2835 contains two types of SPI master controller; the
113	  "universal SPI master", and the regular SPI controller.
114	  This driver is for the universal/auxiliary SPI controller.
115
116config SPI_BFIN5XX
117	tristate "SPI controller driver for ADI Blackfin5xx"
118	depends on BLACKFIN && !BF60x
119	help
120	  This is the SPI controller master driver for Blackfin 5xx processor.
121
122config SPI_ADI_V3
123	tristate "SPI controller v3 for ADI"
124	depends on BF60x
125	help
126	  This is the SPI controller v3 master driver
127	  found on Blackfin 60x processor.
128
129config SPI_BFIN_SPORT
130	tristate "SPI bus via Blackfin SPORT"
131	depends on BLACKFIN
132	help
133	  Enable support for a SPI bus via the Blackfin SPORT peripheral.
134
135config SPI_BCM53XX
136	tristate "Broadcom BCM53xx SPI controller"
137	depends on ARCH_BCM_5301X
138	depends on BCMA_POSSIBLE
139	select BCMA
140	help
141          Enable support for the SPI controller on Broadcom BCM53xx ARM SoCs.
142
143config SPI_BCM63XX
144	tristate "Broadcom BCM63xx SPI controller"
145	depends on BCM63XX || COMPILE_TEST
146	help
147          Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
148
149config SPI_BCM63XX_HSSPI
150	tristate "Broadcom BCM63XX HS SPI controller driver"
151	depends on BCM63XX || COMPILE_TEST
152	help
153	  This enables support for the High Speed SPI controller present on
154	  newer Broadcom BCM63XX SoCs.
155
156config SPI_BITBANG
157	tristate "Utilities for Bitbanging SPI masters"
158	help
159	  With a few GPIO pins, your system can bitbang the SPI protocol.
160	  Select this to get SPI support through I/O pins (GPIO, parallel
161	  port, etc).  Or, some systems' SPI master controller drivers use
162	  this code to manage the per-word or per-transfer accesses to the
163	  hardware shift registers.
164
165	  This is library code, and is automatically selected by drivers that
166	  need it.  You only need to select this explicitly to support driver
167	  modules that aren't part of this kernel tree.
168
169config SPI_BUTTERFLY
170	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
171	depends on PARPORT
172	select SPI_BITBANG
173	help
174	  This uses a custom parallel port cable to connect to an AVR
175	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
176	  inexpensive battery powered microcontroller evaluation board.
177	  This same cable can be used to flash new firmware.
178
179config SPI_CADENCE
180	tristate "Cadence SPI controller"
181	help
182	  This selects the Cadence SPI controller master driver
183	  used by Xilinx Zynq and ZynqMP.
184
185config SPI_CLPS711X
186	tristate "CLPS711X host SPI controller"
187	depends on ARCH_CLPS711X || COMPILE_TEST
188	help
189	  This enables dedicated general purpose SPI/Microwire1-compatible
190	  master mode interface (SSI1) for CLPS711X-based CPUs.
191
192config SPI_COLDFIRE_QSPI
193	tristate "Freescale Coldfire QSPI controller"
194	depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
195	help
196	  This enables support for the Coldfire QSPI controller in master
197	  mode.
198
199config SPI_DAVINCI
200	tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
201	depends on ARCH_DAVINCI || ARCH_KEYSTONE
202	select SPI_BITBANG
203	help
204	  SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
205
206config SPI_DESIGNWARE
207	tristate "DesignWare SPI controller core support"
208	help
209	  general driver for SPI controller core from DesignWare
210
211config SPI_DW_PCI
212	tristate "PCI interface driver for DW SPI core"
213	depends on SPI_DESIGNWARE && PCI
214
215config SPI_DW_MID_DMA
216	bool "DMA support for DW SPI controller on Intel MID platform"
217	depends on SPI_DW_PCI && DW_DMAC_PCI
218
219config SPI_DW_MMIO
220	tristate "Memory-mapped io interface driver for DW SPI core"
221	depends on SPI_DESIGNWARE
222
223config SPI_DLN2
224       tristate "Diolan DLN-2 USB SPI adapter"
225       depends on MFD_DLN2
226       help
227         If you say yes to this option, support will be included for Diolan
228         DLN2, a USB to SPI interface.
229
230         This driver can also be built as a module.  If so, the module
231         will be called spi-dln2.
232
233config SPI_EFM32
234	tristate "EFM32 SPI controller"
235	depends on OF && ARM && (ARCH_EFM32 || COMPILE_TEST)
236	select SPI_BITBANG
237	help
238	  Driver for the spi controller found on Energy Micro's EFM32 SoCs.
239
240config SPI_EP93XX
241	tristate "Cirrus Logic EP93xx SPI controller"
242	depends on HAS_DMA
243	depends on ARCH_EP93XX || COMPILE_TEST
244	help
245	  This enables using the Cirrus EP93xx SPI controller in master
246	  mode.
247
248config SPI_FALCON
249	tristate "Falcon SPI controller support"
250	depends on SOC_FALCON
251	help
252	  The external bus unit (EBU) found on the FALC-ON SoC has SPI
253	  emulation that is designed for serial flash access. This driver
254	  has only been tested with m25p80 type chips. The hardware has no
255	  support for other types of SPI peripherals.
256
257config SPI_GPIO
258	tristate "GPIO-based bitbanging SPI Master"
259	depends on GPIOLIB || COMPILE_TEST
260	select SPI_BITBANG
261	help
262	  This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
263	  interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
264	  slaves connected to a bus using this driver are configured as usual,
265	  except that the spi_board_info.controller_data holds the GPIO number
266	  for the chipselect used by this controller driver.
267
268	  Note that this driver often won't achieve even 1 Mbit/sec speeds,
269	  making it unusually slow for SPI.  If your platform can inline
270	  GPIO operations, you should be able to leverage that for better
271	  speed with a custom version of this driver; see the source code.
272
273config SPI_IMG_SPFI
274	tristate "IMG SPFI controller"
275	depends on MIPS || COMPILE_TEST
276	help
277	  This enables support for the SPFI master controller found on
278	  IMG SoCs.
279
280config SPI_IMX
281	tristate "Freescale i.MX SPI controllers"
282	depends on ARCH_MXC || COMPILE_TEST
283	select SPI_BITBANG
284	help
285	  This enables using the Freescale i.MX SPI controllers in master
286	  mode.
287
288config SPI_LM70_LLP
289	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
290	depends on PARPORT
291	select SPI_BITBANG
292	help
293	  This driver supports the NS LM70 LLP Evaluation Board,
294	  which interfaces to an LM70 temperature sensor using
295	  a parallel port.
296
297config SPI_LP8841_RTC
298	tristate "ICP DAS LP-8841 SPI Controller for RTC"
299	depends on MACH_PXA27X_DT || COMPILE_TEST
300	help
301	  This driver provides an SPI master device to drive Maxim
302	  DS-1302 real time clock.
303
304	  Say N here unless you plan to run the kernel on an ICP DAS
305	  LP-8x4x industrial computer.
306
307config SPI_MPC52xx
308	tristate "Freescale MPC52xx SPI (non-PSC) controller support"
309	depends on PPC_MPC52xx
310	help
311	  This drivers supports the MPC52xx SPI controller in master SPI
312	  mode.
313
314config SPI_MPC52xx_PSC
315	tristate "Freescale MPC52xx PSC SPI controller"
316	depends on PPC_MPC52xx
317	help
318	  This enables using the Freescale MPC52xx Programmable Serial
319	  Controller in master SPI mode.
320
321config SPI_MPC512x_PSC
322	tristate "Freescale MPC512x PSC SPI controller"
323	depends on PPC_MPC512x
324	help
325	  This enables using the Freescale MPC5121 Programmable Serial
326	  Controller in SPI master mode.
327
328config SPI_FSL_LIB
329	tristate
330	depends on OF
331
332config SPI_FSL_CPM
333	tristate
334	depends on FSL_SOC
335
336config SPI_FSL_SPI
337	tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"
338	depends on OF
339	select SPI_FSL_LIB
340	select SPI_FSL_CPM if FSL_SOC
341	help
342	  This enables using the Freescale SPI controllers in master mode.
343	  MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
344	  MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
345	  This also enables using the Aeroflex Gaisler GRLIB SPI controller in
346	  master mode.
347
348config SPI_FSL_DSPI
349	tristate "Freescale DSPI controller"
350	select REGMAP_MMIO
351	depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || COMPILE_TEST
352	help
353	  This enables support for the Freescale DSPI controller in master
354	  mode. VF610 platform uses the controller.
355
356config SPI_FSL_ESPI
357	tristate "Freescale eSPI controller"
358	depends on FSL_SOC
359	select SPI_FSL_LIB
360	help
361	  This enables using the Freescale eSPI controllers in master mode.
362	  From MPC8536, 85xx platform uses the controller, and all P10xx,
363	  P20xx, P30xx,P40xx, P50xx uses this controller.
364
365config SPI_MESON_SPIFC
366	tristate "Amlogic Meson SPIFC controller"
367	depends on ARCH_MESON || COMPILE_TEST
368	select REGMAP_MMIO
369	help
370	  This enables master mode support for the SPIFC (SPI flash
371	  controller) available in Amlogic Meson SoCs.
372
373config SPI_MT65XX
374	tristate "MediaTek SPI controller"
375	depends on ARCH_MEDIATEK || COMPILE_TEST
376	help
377	  This selects the MediaTek(R) SPI bus driver.
378	  If you want to use MediaTek(R) SPI interface,
379	  say Y or M here.If you are not sure, say N.
380	  SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs.
381
382config SPI_NUC900
383	tristate "Nuvoton NUC900 series SPI"
384	depends on ARCH_W90X900
385	select SPI_BITBANG
386	help
387	  SPI driver for Nuvoton NUC900 series ARM SoCs
388
389config SPI_OC_TINY
390	tristate "OpenCores tiny SPI"
391	depends on GPIOLIB || COMPILE_TEST
392	select SPI_BITBANG
393	help
394	  This is the driver for OpenCores tiny SPI master controller.
395
396config SPI_OCTEON
397	tristate "Cavium OCTEON SPI controller"
398	depends on CAVIUM_OCTEON_SOC
399	help
400	  SPI host driver for the hardware found on some Cavium OCTEON
401	  SOCs.
402
403config SPI_OMAP_UWIRE
404	tristate "OMAP1 MicroWire"
405	depends on ARCH_OMAP1
406	select SPI_BITBANG
407	help
408	  This hooks up to the MicroWire controller on OMAP1 chips.
409
410config SPI_OMAP24XX
411	tristate "McSPI driver for OMAP"
412	depends on HAS_DMA
413	depends on ARCH_OMAP2PLUS || COMPILE_TEST
414	help
415	  SPI master controller for OMAP24XX and later Multichannel SPI
416	  (McSPI) modules.
417
418config SPI_TI_QSPI
419	tristate "DRA7xxx QSPI controller support"
420	depends on ARCH_OMAP2PLUS || COMPILE_TEST
421	help
422	  QSPI master controller for DRA7xxx used for flash devices.
423	  This device supports single, dual and quad read support, while
424	  it only supports single write mode.
425
426config SPI_OMAP_100K
427	tristate "OMAP SPI 100K"
428	depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
429	help
430	  OMAP SPI 100K master controller for omap7xx boards.
431
432config SPI_ORION
433	tristate "Orion SPI master"
434	depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST
435	help
436	  This enables using the SPI master controller on the Orion chips.
437
438config SPI_PIC32
439	tristate "Microchip PIC32 series SPI"
440	depends on MACH_PIC32 || COMPILE_TEST
441	help
442	  SPI driver for Microchip PIC32 SPI master controller.
443
444config SPI_PIC32_SQI
445	tristate "Microchip PIC32 Quad SPI driver"
446	depends on MACH_PIC32 || COMPILE_TEST
447	depends on HAS_DMA
448	help
449	  SPI driver for PIC32 Quad SPI controller.
450
451config SPI_PL022
452	tristate "ARM AMBA PL022 SSP controller"
453	depends on ARM_AMBA
454	default y if MACH_U300
455	default y if ARCH_REALVIEW
456	default y if INTEGRATOR_IMPD1
457	default y if ARCH_VERSATILE
458	help
459	  This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
460	  controller. If you have an embedded system with an AMBA(R)
461	  bus and a PL022 controller, say Y or M here.
462
463config SPI_PPC4xx
464	tristate "PPC4xx SPI Controller"
465	depends on PPC32 && 4xx
466	select SPI_BITBANG
467	help
468	  This selects a driver for the PPC4xx SPI Controller.
469
470config SPI_PXA2XX
471	tristate "PXA2xx SSP SPI master"
472	depends on (ARCH_PXA || PCI || ACPI)
473	select PXA_SSP if ARCH_PXA
474	help
475	  This enables using a PXA2xx or Sodaville SSP port as a SPI master
476	  controller. The driver can be configured to use any SSP port and
477	  additional documentation can be found a Documentation/spi/pxa2xx.
478
479config SPI_PXA2XX_PCI
480	def_tristate SPI_PXA2XX && PCI && COMMON_CLK
481
482config SPI_ROCKCHIP
483	tristate "Rockchip SPI controller driver"
484	help
485	  This selects a driver for Rockchip SPI controller.
486
487	  If you say yes to this option, support will be included for
488	  RK3066, RK3188 and RK3288 families of SPI controller.
489	  Rockchip SPI controller support DMA transport and PIO mode.
490	  The main usecase of this controller is to use spi flash as boot
491	  device.
492
493config SPI_RB4XX
494	tristate "Mikrotik RB4XX SPI master"
495	depends on SPI_MASTER && ATH79
496	help
497	  SPI controller driver for the Mikrotik RB4xx series boards.
498
499config SPI_RSPI
500	tristate "Renesas RSPI/QSPI controller"
501	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
502	help
503	  SPI driver for Renesas RSPI and QSPI blocks.
504
505config SPI_QUP
506	tristate "Qualcomm SPI controller with QUP interface"
507	depends on ARCH_QCOM || (ARM && COMPILE_TEST)
508	help
509	  Qualcomm Universal Peripheral (QUP) core is an AHB slave that
510	  provides a common data path (an output FIFO and an input FIFO)
511	  for serial peripheral interface (SPI) mini-core. SPI in master
512	  mode supports up to 50MHz, up to four chip selects, programmable
513	  data path from 4 bits to 32 bits and numerous protocol variants.
514
515	  This driver can also be built as a module.  If so, the module
516	  will be called spi_qup.
517
518config SPI_S3C24XX
519	tristate "Samsung S3C24XX series SPI"
520	depends on ARCH_S3C24XX
521	select SPI_BITBANG
522	help
523	  SPI driver for Samsung S3C24XX series ARM SoCs
524
525config SPI_S3C24XX_FIQ
526	bool "S3C24XX driver with FIQ pseudo-DMA"
527	depends on SPI_S3C24XX
528	select FIQ
529	help
530	  Enable FIQ support for the S3C24XX SPI driver to provide pseudo
531	  DMA by using the fast-interrupt request framework, This allows
532	  the driver to get DMA-like performance when there are either
533	  no free DMA channels, or when doing transfers that required both
534	  TX and RX data paths.
535
536config SPI_S3C64XX
537	tristate "Samsung S3C64XX series type SPI"
538	depends on (PLAT_SAMSUNG || ARCH_EXYNOS)
539	help
540	  SPI driver for Samsung S3C64XX and newer SoCs.
541
542config SPI_SC18IS602
543	tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
544	depends on I2C
545	help
546	  SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
547
548config SPI_SH_MSIOF
549	tristate "SuperH MSIOF SPI controller"
550	depends on HAVE_CLK && HAS_DMA
551	depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
552	help
553	  SPI driver for SuperH and SH Mobile MSIOF blocks.
554
555config SPI_SH
556	tristate "SuperH SPI controller"
557	depends on SUPERH || COMPILE_TEST
558	help
559	  SPI driver for SuperH SPI blocks.
560
561config SPI_SH_SCI
562	tristate "SuperH SCI SPI controller"
563	depends on SUPERH
564	select SPI_BITBANG
565	help
566	  SPI driver for SuperH SCI blocks.
567
568config SPI_SH_HSPI
569	tristate "SuperH HSPI controller"
570	depends on ARCH_RENESAS || COMPILE_TEST
571	help
572	  SPI driver for SuperH HSPI blocks.
573
574config SPI_SIRF
575	tristate "CSR SiRFprimaII SPI controller"
576	depends on SIRF_DMA
577	select SPI_BITBANG
578	help
579	  SPI driver for CSR SiRFprimaII SoCs
580
581config SPI_ST_SSC4
582	tristate "STMicroelectronics SPI SSC-based driver"
583	depends on ARCH_STI || COMPILE_TEST
584	help
585	  STMicroelectronics SoCs support for SPI. If you say yes to
586	  this option, support will be included for the SSC driven SPI.
587
588config SPI_SUN4I
589	tristate "Allwinner A10 SoCs SPI controller"
590	depends on ARCH_SUNXI || COMPILE_TEST
591	help
592	  SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
593
594config SPI_SUN6I
595	tristate "Allwinner A31 SPI controller"
596	depends on ARCH_SUNXI || COMPILE_TEST
597	depends on RESET_CONTROLLER
598	help
599	  This enables using the SPI controller on the Allwinner A31 SoCs.
600
601config SPI_MXS
602	tristate "Freescale MXS SPI controller"
603	depends on ARCH_MXS
604	select STMP_DEVICE
605	help
606	  SPI driver for Freescale MXS devices.
607
608config SPI_TEGRA114
609	tristate "NVIDIA Tegra114 SPI Controller"
610	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
611	depends on RESET_CONTROLLER && HAS_DMA
612	help
613	  SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
614	  is different than the older SoCs SPI controller and also register interface
615	  get changed with this controller.
616
617config SPI_TEGRA20_SFLASH
618	tristate "Nvidia Tegra20 Serial flash Controller"
619	depends on ARCH_TEGRA || COMPILE_TEST
620	depends on RESET_CONTROLLER
621	help
622	  SPI driver for Nvidia Tegra20 Serial flash Controller interface.
623	  The main usecase of this controller is to use spi flash as boot
624	  device.
625
626config SPI_TEGRA20_SLINK
627	tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
628	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
629	depends on RESET_CONTROLLER && HAS_DMA
630	help
631	  SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
632
633config SPI_TOPCLIFF_PCH
634	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
635	depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
636	help
637	  SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
638	  used in some x86 embedded processors.
639
640	  This driver also supports the ML7213/ML7223/ML7831, a companion chip
641	  for the Atom E6xx series and compatible with the Intel EG20T PCH.
642
643config SPI_TXX9
644	tristate "Toshiba TXx9 SPI controller"
645	depends on GPIOLIB && (CPU_TX49XX || COMPILE_TEST)
646	help
647	  SPI driver for Toshiba TXx9 MIPS SoCs
648
649config SPI_XCOMM
650	tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
651	depends on I2C
652	help
653	  Support for the SPI-I2C bridge found on the Analog Devices
654	  AD-FMCOMMS1-EBZ board.
655
656config SPI_XILINX
657	tristate "Xilinx SPI controller common module"
658	depends on HAS_IOMEM
659	select SPI_BITBANG
660	help
661	  This exposes the SPI controller IP from the Xilinx EDK.
662
663	  See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
664	  Product Specification document (DS464) for hardware details.
665
666	  Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
667
668config SPI_XLP
669	tristate "Netlogic XLP SPI controller driver"
670	depends on CPU_XLP || ARCH_VULCAN || COMPILE_TEST
671	help
672	  Enable support for the SPI controller on the Netlogic XLP SoCs.
673	  Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX, XLP9XX
674	  and XLP5XX.
675
676	  If you have a Netlogic XLP platform say Y here.
677	  If unsure, say N.
678
679config SPI_XTENSA_XTFPGA
680	tristate "Xtensa SPI controller for xtfpga"
681	depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
682	select SPI_BITBANG
683	help
684	  SPI driver for xtfpga SPI master controller.
685
686	  This simple SPI master controller is built into xtfpga bitstreams
687	  and is used to control daughterboard audio codec. It always transfers
688	  16 bit words in SPI mode 0, automatically asserting CS on transfer
689	  start and deasserting on end.
690
691config SPI_ZYNQMP_GQSPI
692	tristate "Xilinx ZynqMP GQSPI controller"
693	depends on SPI_MASTER && HAS_DMA
694	help
695	  Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
696
697#
698# Add new SPI master controllers in alphabetical order above this line
699#
700
701#
702# There are lots of SPI device types, with sensors and memory
703# being probably the most widely used ones.
704#
705comment "SPI Protocol Masters"
706
707config SPI_SPIDEV
708	tristate "User mode SPI device driver support"
709	help
710	  This supports user mode SPI protocol drivers.
711
712	  Note that this application programming interface is EXPERIMENTAL
713	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
714
715config SPI_LOOPBACK_TEST
716	tristate "spi loopback test framework support"
717	depends on m
718	help
719	  This enables the SPI loopback testing framework driver
720
721	  primarily used for development of spi_master drivers
722	  and to detect regressions
723
724config SPI_TLE62X0
725	tristate "Infineon TLE62X0 (for power switching)"
726	depends on SYSFS
727	help
728	  SPI driver for Infineon TLE62X0 series line driver chips,
729	  such as the TLE6220, TLE6230 and TLE6240.  This provides a
730	  sysfs interface, with each line presented as a kind of GPIO
731	  exposing both switch control and diagnostic feedback.
732
733#
734# Add new SPI protocol masters in alphabetical order above this line
735#
736
737endif # SPI_MASTER
738
739# (slave support would go here)
740
741endif # SPI
742