Linux Audio

Check our new training course

Loading...
v3.1
  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	boolean "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#	boolean "SPI Master Support"
 44	boolean
 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 && GENERIC_GPIO
 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 (ARCH_AT91 || AVR32)
 73	help
 74	  This selects a driver for the Atmel SPI Controller, present on
 75	  many AT32 (AVR32) and AT91 (ARM) chips.
 76
 77config SPI_BFIN
 
 
 
 
 
 
 
 
 
 
 
 78	tristate "SPI controller driver for ADI Blackfin5xx"
 79	depends on BLACKFIN
 80	help
 81	  This is the SPI controller master driver for Blackfin 5xx processor.
 82
 
 
 
 
 
 
 
 83config SPI_BFIN_SPORT
 84	tristate "SPI bus via Blackfin SPORT"
 85	depends on BLACKFIN
 86	help
 87	  Enable support for a SPI bus via the Blackfin SPORT peripheral.
 88
 89config SPI_AU1550
 90	tristate "Au1550/Au12x0 SPI Controller"
 91	depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
 92	select SPI_BITBANG
 93	help
 94	  If you say yes to this option, support will be included for the
 95	  Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
 
 
 
 
 
 
 
 
 
 
 
 
 
 96
 97config SPI_BITBANG
 98	tristate "Utilities for Bitbanging SPI masters"
 99	help
100	  With a few GPIO pins, your system can bitbang the SPI protocol.
101	  Select this to get SPI support through I/O pins (GPIO, parallel
102	  port, etc).  Or, some systems' SPI master controller drivers use
103	  this code to manage the per-word or per-transfer accesses to the
104	  hardware shift registers.
105
106	  This is library code, and is automatically selected by drivers that
107	  need it.  You only need to select this explicitly to support driver
108	  modules that aren't part of this kernel tree.
109
110config SPI_BUTTERFLY
111	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
112	depends on PARPORT
113	select SPI_BITBANG
114	help
115	  This uses a custom parallel port cable to connect to an AVR
116	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
117	  inexpensive battery powered microcontroller evaluation board.
118	  This same cable can be used to flash new firmware.
119
 
 
 
 
 
 
 
120config SPI_COLDFIRE_QSPI
121	tristate "Freescale Coldfire QSPI controller"
122	depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
123	help
124	  This enables support for the Coldfire QSPI controller in master
125	  mode.
126
127config SPI_DAVINCI
128	tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
129	depends on SPI_MASTER && ARCH_DAVINCI
130	select SPI_BITBANG
131	help
132	  SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
133
 
 
 
 
 
 
 
134config SPI_EP93XX
135	tristate "Cirrus Logic EP93xx SPI controller"
136	depends on ARCH_EP93XX
137	help
138	  This enables using the Cirrus EP93xx SPI controller in master
139	  mode.
140
 
 
 
 
 
 
 
 
 
141config SPI_GPIO
142	tristate "GPIO-based bitbanging SPI Master"
143	depends on GENERIC_GPIO
144	select SPI_BITBANG
145	help
146	  This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
147	  interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
148	  slaves connected to a bus using this driver are configured as usual,
149	  except that the spi_board_info.controller_data holds the GPIO number
150	  for the chipselect used by this controller driver.
151
152	  Note that this driver often won't achieve even 1 Mbit/sec speeds,
153	  making it unusually slow for SPI.  If your platform can inline
154	  GPIO operations, you should be able to leverage that for better
155	  speed with a custom version of this driver; see the source code.
156
157config SPI_IMX
158	tristate "Freescale i.MX SPI controllers"
159	depends on ARCH_MXC
160	select SPI_BITBANG
161	default m if IMX_HAVE_PLATFORM_SPI_IMX
162	help
163	  This enables using the Freescale i.MX SPI controllers in master
164	  mode.
165
166config SPI_LM70_LLP
167	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
168	depends on PARPORT && EXPERIMENTAL
169	select SPI_BITBANG
170	help
171	  This driver supports the NS LM70 LLP Evaluation Board,
172	  which interfaces to an LM70 temperature sensor using
173	  a parallel port.
174
175config SPI_MPC52xx
176	tristate "Freescale MPC52xx SPI (non-PSC) controller support"
177	depends on PPC_MPC52xx && SPI
178	select SPI_MASTER_OF
179	help
180	  This drivers supports the MPC52xx SPI controller in master SPI
181	  mode.
182
183config SPI_MPC52xx_PSC
184	tristate "Freescale MPC52xx PSC SPI controller"
185	depends on PPC_MPC52xx && EXPERIMENTAL
186	help
187	  This enables using the Freescale MPC52xx Programmable Serial
188	  Controller in master SPI mode.
189
190config SPI_MPC512x_PSC
191	tristate "Freescale MPC512x PSC SPI controller"
192	depends on SPI_MASTER && PPC_MPC512x
193	help
194	  This enables using the Freescale MPC5121 Programmable Serial
195	  Controller in SPI master mode.
196
197config SPI_FSL_LIB
198	tristate
 
 
 
 
199	depends on FSL_SOC
200
201config SPI_FSL_SPI
202	tristate "Freescale SPI controller"
203	depends on FSL_SOC
204	select SPI_FSL_LIB
 
205	help
206	  This enables using the Freescale SPI controllers in master mode.
207	  MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
208	  MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
 
 
 
 
 
 
 
 
 
 
 
209
210config SPI_FSL_ESPI
211	tristate "Freescale eSPI controller"
212	depends on FSL_SOC
213	select SPI_FSL_LIB
214	help
215	  This enables using the Freescale eSPI controllers in master mode.
216	  From MPC8536, 85xx platform uses the controller, and all P10xx,
217	  P20xx, P30xx,P40xx, P50xx uses this controller.
218
219config SPI_OC_TINY
220	tristate "OpenCores tiny SPI"
221	depends on GENERIC_GPIO
222	select SPI_BITBANG
223	help
224	  This is the driver for OpenCores tiny SPI master controller.
225
 
 
 
 
 
 
 
226config SPI_OMAP_UWIRE
227	tristate "OMAP1 MicroWire"
228	depends on ARCH_OMAP1
229	select SPI_BITBANG
230	help
231	  This hooks up to the MicroWire controller on OMAP1 chips.
232
233config SPI_OMAP24XX
234	tristate "McSPI driver for OMAP"
235	depends on ARCH_OMAP2PLUS
 
236	help
237	  SPI master controller for OMAP24XX and later Multichannel SPI
238	  (McSPI) modules.
239
 
 
 
 
 
 
 
 
240config SPI_OMAP_100K
241	tristate "OMAP SPI 100K"
242	depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
243	help
244	  OMAP SPI 100K master controller for omap7xx boards.
245
246config SPI_ORION
247	tristate "Orion SPI master (EXPERIMENTAL)"
248	depends on PLAT_ORION && EXPERIMENTAL
249	help
250	  This enables using the SPI master controller on the Orion chips.
251
252config SPI_PL022
253	tristate "ARM AMBA PL022 SSP controller"
254	depends on ARM_AMBA
255	default y if MACH_U300
256	default y if ARCH_REALVIEW
257	default y if INTEGRATOR_IMPD1
258	default y if ARCH_VERSATILE
259	help
260	  This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
261	  controller. If you have an embedded system with an AMBA(R)
262	  bus and a PL022 controller, say Y or M here.
263
264config SPI_PPC4xx
265	tristate "PPC4xx SPI Controller"
266	depends on PPC32 && 4xx && SPI_MASTER
267	select SPI_BITBANG
268	help
269	  This selects a driver for the PPC4xx SPI Controller.
270
 
 
 
 
 
 
 
 
 
 
 
271config SPI_PXA2XX
272	tristate "PXA2xx SSP SPI master"
273	depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
274	select PXA_SSP if ARCH_PXA
275	help
276	  This enables using a PXA2xx or Sodaville SSP port as a SPI master
277	  controller. The driver can be configured to use any SSP port and
278	  additional documentation can be found a Documentation/spi/pxa2xx.
279
280config SPI_PXA2XX_PCI
281	def_bool SPI_PXA2XX && X86_32 && PCI
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
282
283config SPI_S3C24XX
284	tristate "Samsung S3C24XX series SPI"
285	depends on ARCH_S3C2410 && EXPERIMENTAL
286	select SPI_BITBANG
287	help
288	  SPI driver for Samsung S3C24XX series ARM SoCs
289
290config SPI_S3C24XX_FIQ
291	bool "S3C24XX driver with FIQ pseudo-DMA"
292	depends on SPI_S3C24XX
293	select FIQ
294	help
295	  Enable FIQ support for the S3C24XX SPI driver to provide pseudo
296	  DMA by using the fast-interrupt request framework, This allows
297	  the driver to get DMA-like performance when there are either
298	  no free DMA channels, or when doing transfers that required both
299	  TX and RX data paths.
300
301config SPI_S3C64XX
302	tristate "Samsung S3C64XX series type SPI"
303	depends on (ARCH_S3C64XX || ARCH_S5P64X0)
304	select S3C64XX_DMA if ARCH_S3C64XX
305	help
306	  SPI driver for Samsung S3C64XX and newer SoCs.
307
 
 
 
 
 
 
308config SPI_SH_MSIOF
309	tristate "SuperH MSIOF SPI controller"
310	depends on SUPERH && HAVE_CLK
311	select SPI_BITBANG
312	help
313	  SPI driver for SuperH MSIOF blocks.
314
315config SPI_SH
316	tristate "SuperH SPI controller"
317	depends on SUPERH
318	help
319	  SPI driver for SuperH SPI blocks.
320
321config SPI_SH_SCI
322	tristate "SuperH SCI SPI controller"
323	depends on SUPERH
324	select SPI_BITBANG
325	help
326	  SPI driver for SuperH SCI blocks.
327
328config SPI_STMP3XXX
329	tristate "Freescale STMP37xx/378x SPI/SSP controller"
330	depends on ARCH_STMP3XXX && SPI_MASTER
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
331	help
332	  SPI driver for Freescale STMP37xx/378x SoC SSP interface
333
334config SPI_TEGRA
335	tristate "Nvidia Tegra SPI controller"
336	depends on ARCH_TEGRA
337	select TEGRA_SYSTEM_DMA
338	help
339	  SPI driver for NVidia Tegra SoCs
 
 
340
341config SPI_TI_SSP
342	tristate "TI Sequencer Serial Port - SPI Support"
343	depends on MFD_TI_SSP
 
344	help
345	  This selects an SPI master implementation using a TI sequencer
346	  serial port.
 
 
 
 
 
 
 
 
347
348config SPI_TOPCLIFF_PCH
349	tristate "Intel EG20T PCH/OKI SEMICONDUCTOR ML7213 IOH SPI controller"
350	depends on PCI
351	help
352	  SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
353	  used in some x86 embedded processors.
354
355	  This driver also supports the ML7213, a companion chip for the
356	  Atom E6xx series and compatible with the Intel EG20T PCH.
357
358config SPI_TXX9
359	tristate "Toshiba TXx9 SPI controller"
360	depends on GENERIC_GPIO && CPU_TX49XX
361	help
362	  SPI driver for Toshiba TXx9 MIPS SoCs
363
 
 
 
 
 
 
 
364config SPI_XILINX
365	tristate "Xilinx SPI controller common module"
366	depends on HAS_IOMEM && EXPERIMENTAL
367	select SPI_BITBANG
368	help
369	  This exposes the SPI controller IP from the Xilinx EDK.
370
371	  See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
372	  Product Specification document (DS464) for hardware details.
373
374	  Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
375
 
 
 
 
 
 
 
 
 
 
 
 
 
376config SPI_NUC900
377	tristate "Nuvoton NUC900 series SPI"
378	depends on ARCH_W90X900 && EXPERIMENTAL
379	select SPI_BITBANG
380	help
381	  SPI driver for Nuvoton NUC900 series ARM SoCs
382
383#
384# Add new SPI master controllers in alphabetical order above this line
385#
386
387config SPI_DESIGNWARE
388	tristate "DesignWare SPI controller core support"
389	depends on SPI_MASTER
390	help
391	  general driver for SPI controller core from DesignWare
392
393config SPI_DW_PCI
394	tristate "PCI interface driver for DW SPI core"
395	depends on SPI_DESIGNWARE && PCI
396
397config SPI_DW_MID_DMA
398	bool "DMA support for DW SPI controller on Intel Moorestown platform"
399	depends on SPI_DW_PCI && INTEL_MID_DMAC
400
401config SPI_DW_MMIO
402	tristate "Memory-mapped io interface driver for DW SPI core"
403	depends on SPI_DESIGNWARE && HAVE_CLK
404
405#
406# There are lots of SPI device types, with sensors and memory
407# being probably the most widely used ones.
408#
409comment "SPI Protocol Masters"
410
411config SPI_SPIDEV
412	tristate "User mode SPI device driver support"
413	depends on EXPERIMENTAL
414	help
415	  This supports user mode SPI protocol drivers.
416
417	  Note that this application programming interface is EXPERIMENTAL
418	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
419
420config SPI_TLE62X0
421	tristate "Infineon TLE62X0 (for power switching)"
422	depends on SYSFS
423	help
424	  SPI driver for Infineon TLE62X0 series line driver chips,
425	  such as the TLE6220, TLE6230 and TLE6240.  This provides a
426	  sysfs interface, with each line presented as a kind of GPIO
427	  exposing both switch control and diagnostic feedback.
428
429#
430# Add new SPI protocol masters in alphabetical order above this line
431#
432
433endif # SPI_MASTER
434
435# (slave support would go here)
436
437endif # SPI
v3.15
  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	boolean "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#	boolean "SPI Master Support"
 44	boolean
 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 (ARCH_AT91 || AVR32 || COMPILE_TEST)
 73	help
 74	  This selects a driver for the Atmel SPI Controller, present on
 75	  many AT32 (AVR32) and AT91 (ARM) chips.
 76
 77config SPI_BCM2835
 78	tristate "BCM2835 SPI controller"
 79	depends on ARCH_BCM2835 || COMPILE_TEST
 80	help
 81	  This selects a driver for the Broadcom BCM2835 SPI master.
 82
 83	  The BCM2835 contains two types of SPI master controller; the
 84	  "universal SPI master", and the regular SPI controller. This driver
 85	  is for the regular SPI controller. Slave mode operation is not also
 86	  not supported.
 87
 88config SPI_BFIN5XX
 89	tristate "SPI controller driver for ADI Blackfin5xx"
 90	depends on BLACKFIN && !BF60x
 91	help
 92	  This is the SPI controller master driver for Blackfin 5xx processor.
 93
 94config SPI_BFIN_V3
 95	tristate "SPI controller v3 for Blackfin"
 96	depends on BF60x
 97	help
 98	  This is the SPI controller v3 master driver
 99	  found on Blackfin 60x processor.
100
101config SPI_BFIN_SPORT
102	tristate "SPI bus via Blackfin SPORT"
103	depends on BLACKFIN
104	help
105	  Enable support for a SPI bus via the Blackfin SPORT peripheral.
106
107config SPI_AU1550
108	tristate "Au1550/Au1200/Au1300 SPI Controller"
109	depends on MIPS_ALCHEMY
110	select SPI_BITBANG
111	help
112	  If you say yes to this option, support will be included for the
113	  PSC SPI controller found on Au1550, Au1200 and Au1300 series.
114
115config SPI_BCM63XX
116	tristate "Broadcom BCM63xx SPI controller"
117	depends on BCM63XX
118	help
119          Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
120
121config SPI_BCM63XX_HSSPI
122	tristate "Broadcom BCM63XX HS SPI controller driver"
123	depends on BCM63XX || COMPILE_TEST
124	help
125	  This enables support for the High Speed SPI controller present on
126	  newer Broadcom BCM63XX SoCs.
127
128config SPI_BITBANG
129	tristate "Utilities for Bitbanging SPI masters"
130	help
131	  With a few GPIO pins, your system can bitbang the SPI protocol.
132	  Select this to get SPI support through I/O pins (GPIO, parallel
133	  port, etc).  Or, some systems' SPI master controller drivers use
134	  this code to manage the per-word or per-transfer accesses to the
135	  hardware shift registers.
136
137	  This is library code, and is automatically selected by drivers that
138	  need it.  You only need to select this explicitly to support driver
139	  modules that aren't part of this kernel tree.
140
141config SPI_BUTTERFLY
142	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
143	depends on PARPORT
144	select SPI_BITBANG
145	help
146	  This uses a custom parallel port cable to connect to an AVR
147	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
148	  inexpensive battery powered microcontroller evaluation board.
149	  This same cable can be used to flash new firmware.
150
151config SPI_CLPS711X
152	tristate "CLPS711X host SPI controller"
153	depends on ARCH_CLPS711X || COMPILE_TEST
154	help
155	  This enables dedicated general purpose SPI/Microwire1-compatible
156	  master mode interface (SSI1) for CLPS711X-based CPUs.
157
158config SPI_COLDFIRE_QSPI
159	tristate "Freescale Coldfire QSPI controller"
160	depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
161	help
162	  This enables support for the Coldfire QSPI controller in master
163	  mode.
164
165config SPI_DAVINCI
166	tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
167	depends on ARCH_DAVINCI || ARCH_KEYSTONE
168	select SPI_BITBANG
169	help
170	  SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
171
172config SPI_EFM32
173	tristate "EFM32 SPI controller"
174	depends on OF && ARM && (ARCH_EFM32 || COMPILE_TEST)
175	select SPI_BITBANG
176	help
177	  Driver for the spi controller found on Energy Micro's EFM32 SoCs.
178
179config SPI_EP93XX
180	tristate "Cirrus Logic EP93xx SPI controller"
181	depends on ARCH_EP93XX || COMPILE_TEST
182	help
183	  This enables using the Cirrus EP93xx SPI controller in master
184	  mode.
185
186config SPI_FALCON
187	tristate "Falcon SPI controller support"
188	depends on SOC_FALCON
189	help
190	  The external bus unit (EBU) found on the FALC-ON SoC has SPI
191	  emulation that is designed for serial flash access. This driver
192	  has only been tested with m25p80 type chips. The hardware has no
193	  support for other types of SPI peripherals.
194
195config SPI_GPIO
196	tristate "GPIO-based bitbanging SPI Master"
197	depends on GPIOLIB
198	select SPI_BITBANG
199	help
200	  This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
201	  interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
202	  slaves connected to a bus using this driver are configured as usual,
203	  except that the spi_board_info.controller_data holds the GPIO number
204	  for the chipselect used by this controller driver.
205
206	  Note that this driver often won't achieve even 1 Mbit/sec speeds,
207	  making it unusually slow for SPI.  If your platform can inline
208	  GPIO operations, you should be able to leverage that for better
209	  speed with a custom version of this driver; see the source code.
210
211config SPI_IMX
212	tristate "Freescale i.MX SPI controllers"
213	depends on ARCH_MXC || COMPILE_TEST
214	select SPI_BITBANG
 
215	help
216	  This enables using the Freescale i.MX SPI controllers in master
217	  mode.
218
219config SPI_LM70_LLP
220	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
221	depends on PARPORT
222	select SPI_BITBANG
223	help
224	  This driver supports the NS LM70 LLP Evaluation Board,
225	  which interfaces to an LM70 temperature sensor using
226	  a parallel port.
227
228config SPI_MPC52xx
229	tristate "Freescale MPC52xx SPI (non-PSC) controller support"
230	depends on PPC_MPC52xx
 
231	help
232	  This drivers supports the MPC52xx SPI controller in master SPI
233	  mode.
234
235config SPI_MPC52xx_PSC
236	tristate "Freescale MPC52xx PSC SPI controller"
237	depends on PPC_MPC52xx
238	help
239	  This enables using the Freescale MPC52xx Programmable Serial
240	  Controller in master SPI mode.
241
242config SPI_MPC512x_PSC
243	tristate "Freescale MPC512x PSC SPI controller"
244	depends on PPC_MPC512x
245	help
246	  This enables using the Freescale MPC5121 Programmable Serial
247	  Controller in SPI master mode.
248
249config SPI_FSL_LIB
250	tristate
251	depends on OF
252
253config SPI_FSL_CPM
254	tristate
255	depends on FSL_SOC
256
257config SPI_FSL_SPI
258	bool "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"
259	depends on OF
260	select SPI_FSL_LIB
261	select SPI_FSL_CPM if FSL_SOC
262	help
263	  This enables using the Freescale SPI controllers in master mode.
264	  MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
265	  MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
266	  This also enables using the Aeroflex Gaisler GRLIB SPI controller in
267	  master mode.
268
269config SPI_FSL_DSPI
270	tristate "Freescale DSPI controller"
271	select SPI_BITBANG
272	select REGMAP_MMIO
273	depends on SOC_VF610 || COMPILE_TEST
274	help
275	  This enables support for the Freescale DSPI controller in master
276	  mode. VF610 platform uses the controller.
277
278config SPI_FSL_ESPI
279	bool "Freescale eSPI controller"
280	depends on FSL_SOC
281	select SPI_FSL_LIB
282	help
283	  This enables using the Freescale eSPI controllers in master mode.
284	  From MPC8536, 85xx platform uses the controller, and all P10xx,
285	  P20xx, P30xx,P40xx, P50xx uses this controller.
286
287config SPI_OC_TINY
288	tristate "OpenCores tiny SPI"
289	depends on GPIOLIB
290	select SPI_BITBANG
291	help
292	  This is the driver for OpenCores tiny SPI master controller.
293
294config SPI_OCTEON
295	tristate "Cavium OCTEON SPI controller"
296	depends on CAVIUM_OCTEON_SOC
297	help
298	  SPI host driver for the hardware found on some Cavium OCTEON
299	  SOCs.
300
301config SPI_OMAP_UWIRE
302	tristate "OMAP1 MicroWire"
303	depends on ARCH_OMAP1
304	select SPI_BITBANG
305	help
306	  This hooks up to the MicroWire controller on OMAP1 chips.
307
308config SPI_OMAP24XX
309	tristate "McSPI driver for OMAP"
310	depends on ARM || ARM64 || AVR32 || HEXAGON || MIPS || SUPERH
311	depends on ARCH_OMAP2PLUS || COMPILE_TEST
312	help
313	  SPI master controller for OMAP24XX and later Multichannel SPI
314	  (McSPI) modules.
315
316config SPI_TI_QSPI
317	tristate "DRA7xxx QSPI controller support"
318	depends on ARCH_OMAP2PLUS || COMPILE_TEST
319	help
320	  QSPI master controller for DRA7xxx used for flash devices.
321	  This device supports single, dual and quad read support, while
322	  it only supports single write mode.
323
324config SPI_OMAP_100K
325	tristate "OMAP SPI 100K"
326	depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
327	help
328	  OMAP SPI 100K master controller for omap7xx boards.
329
330config SPI_ORION
331	tristate "Orion SPI master"
332	depends on PLAT_ORION || COMPILE_TEST
333	help
334	  This enables using the SPI master controller on the Orion chips.
335
336config SPI_PL022
337	tristate "ARM AMBA PL022 SSP controller"
338	depends on ARM_AMBA
339	default y if MACH_U300
340	default y if ARCH_REALVIEW
341	default y if INTEGRATOR_IMPD1
342	default y if ARCH_VERSATILE
343	help
344	  This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
345	  controller. If you have an embedded system with an AMBA(R)
346	  bus and a PL022 controller, say Y or M here.
347
348config SPI_PPC4xx
349	tristate "PPC4xx SPI Controller"
350	depends on PPC32 && 4xx
351	select SPI_BITBANG
352	help
353	  This selects a driver for the PPC4xx SPI Controller.
354
355config SPI_PXA2XX_PXADMA
356	bool "PXA2xx SSP legacy PXA DMA API support"
357	depends on SPI_PXA2XX && ARCH_PXA
358	help
359	  Enable PXA private legacy DMA API support. Note that this is
360	  deprecated in favor of generic DMA engine API.
361
362config SPI_PXA2XX_DMA
363	def_bool y
364	depends on SPI_PXA2XX && !SPI_PXA2XX_PXADMA
365
366config SPI_PXA2XX
367	tristate "PXA2xx SSP SPI master"
368	depends on (ARCH_PXA || PCI || ACPI)
369	select PXA_SSP if ARCH_PXA
370	help
371	  This enables using a PXA2xx or Sodaville SSP port as a SPI master
372	  controller. The driver can be configured to use any SSP port and
373	  additional documentation can be found a Documentation/spi/pxa2xx.
374
375config SPI_PXA2XX_PCI
376	def_tristate SPI_PXA2XX && PCI
377
378config SPI_RSPI
379	tristate "Renesas RSPI/QSPI controller"
380	depends on (SUPERH && SH_DMAE_BASE) || ARCH_SHMOBILE
381	help
382	  SPI driver for Renesas RSPI and QSPI blocks.
383
384config SPI_QUP
385	tristate "Qualcomm SPI controller with QUP interface"
386	depends on ARCH_QCOM || (ARM && COMPILE_TEST)
387	help
388	  Qualcomm Universal Peripheral (QUP) core is an AHB slave that
389	  provides a common data path (an output FIFO and an input FIFO)
390	  for serial peripheral interface (SPI) mini-core. SPI in master
391	  mode supports up to 50MHz, up to four chip selects, programmable
392	  data path from 4 bits to 32 bits and numerous protocol variants.
393
394	  This driver can also be built as a module.  If so, the module
395	  will be called spi_qup.
396
397config SPI_S3C24XX
398	tristate "Samsung S3C24XX series SPI"
399	depends on ARCH_S3C24XX
400	select SPI_BITBANG
401	help
402	  SPI driver for Samsung S3C24XX series ARM SoCs
403
404config SPI_S3C24XX_FIQ
405	bool "S3C24XX driver with FIQ pseudo-DMA"
406	depends on SPI_S3C24XX
407	select FIQ
408	help
409	  Enable FIQ support for the S3C24XX SPI driver to provide pseudo
410	  DMA by using the fast-interrupt request framework, This allows
411	  the driver to get DMA-like performance when there are either
412	  no free DMA channels, or when doing transfers that required both
413	  TX and RX data paths.
414
415config SPI_S3C64XX
416	tristate "Samsung S3C64XX series type SPI"
417	depends on PLAT_SAMSUNG
418	select S3C64XX_PL080 if ARCH_S3C64XX
419	help
420	  SPI driver for Samsung S3C64XX and newer SoCs.
421
422config SPI_SC18IS602
423	tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
424	depends on I2C
425	help
426	  SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
427
428config SPI_SH_MSIOF
429	tristate "SuperH MSIOF SPI controller"
430	depends on HAVE_CLK
431	depends on SUPERH || ARCH_SHMOBILE || COMPILE_TEST
432	help
433	  SPI driver for SuperH and SH Mobile MSIOF blocks.
434
435config SPI_SH
436	tristate "SuperH SPI controller"
437	depends on SUPERH || COMPILE_TEST
438	help
439	  SPI driver for SuperH SPI blocks.
440
441config SPI_SH_SCI
442	tristate "SuperH SCI SPI controller"
443	depends on SUPERH
444	select SPI_BITBANG
445	help
446	  SPI driver for SuperH SCI blocks.
447
448config SPI_SH_HSPI
449	tristate "SuperH HSPI controller"
450	depends on ARCH_SHMOBILE || COMPILE_TEST
451	help
452	  SPI driver for SuperH HSPI blocks.
453
454config SPI_SIRF
455	tristate "CSR SiRFprimaII SPI controller"
456	depends on SIRF_DMA
457	select SPI_BITBANG
458	help
459	  SPI driver for CSR SiRFprimaII SoCs
460
461config SPI_SUN4I
462	tristate "Allwinner A10 SoCs SPI controller"
463	depends on ARCH_SUNXI || COMPILE_TEST
464	help
465	  SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
466
467config SPI_SUN6I
468	tristate "Allwinner A31 SPI controller"
469	depends on ARCH_SUNXI || COMPILE_TEST
470	depends on RESET_CONTROLLER
471	help
472	  This enables using the SPI controller on the Allwinner A31 SoCs.
473
474config SPI_MXS
475	tristate "Freescale MXS SPI controller"
476	depends on ARCH_MXS
477	select STMP_DEVICE
478	help
479	  SPI driver for Freescale MXS devices.
480
481config SPI_TEGRA114
482	tristate "NVIDIA Tegra114 SPI Controller"
483	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
484	depends on RESET_CONTROLLER
485	help
486	  SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
487	  is different than the older SoCs SPI controller and also register interface
488	  get changed with this controller.
489
490config SPI_TEGRA20_SFLASH
491	tristate "Nvidia Tegra20 Serial flash Controller"
492	depends on ARCH_TEGRA || COMPILE_TEST
493	depends on RESET_CONTROLLER
494	help
495	  SPI driver for Nvidia Tegra20 Serial flash Controller interface.
496	  The main usecase of this controller is to use spi flash as boot
497	  device.
498
499config SPI_TEGRA20_SLINK
500	tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
501	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
502	depends on RESET_CONTROLLER
503	help
504	  SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
505
506config SPI_TOPCLIFF_PCH
507	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
508	depends on PCI
509	help
510	  SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
511	  used in some x86 embedded processors.
512
513	  This driver also supports the ML7213/ML7223/ML7831, a companion chip
514	  for the Atom E6xx series and compatible with the Intel EG20T PCH.
515
516config SPI_TXX9
517	tristate "Toshiba TXx9 SPI controller"
518	depends on GPIOLIB && (CPU_TX49XX || COMPILE_TEST)
519	help
520	  SPI driver for Toshiba TXx9 MIPS SoCs
521
522config SPI_XCOMM
523	tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
524	depends on I2C
525	help
526	  Support for the SPI-I2C bridge found on the Analog Devices
527	  AD-FMCOMMS1-EBZ board.
528
529config SPI_XILINX
530	tristate "Xilinx SPI controller common module"
531	depends on HAS_IOMEM
532	select SPI_BITBANG
533	help
534	  This exposes the SPI controller IP from the Xilinx EDK.
535
536	  See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
537	  Product Specification document (DS464) for hardware details.
538
539	  Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
540
541config SPI_XTENSA_XTFPGA
542	tristate "Xtensa SPI controller for xtfpga"
543	depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
544	select SPI_BITBANG
545	help
546	  SPI driver for xtfpga SPI master controller.
547
548	  This simple SPI master controller is built into xtfpga bitstreams
549	  and is used to control daughterboard audio codec. It always transfers
550	  16 bit words in SPI mode 0, automatically asserting CS on transfer
551	  start and deasserting on end.
552
553
554config SPI_NUC900
555	tristate "Nuvoton NUC900 series SPI"
556	depends on ARCH_W90X900
557	select SPI_BITBANG
558	help
559	  SPI driver for Nuvoton NUC900 series ARM SoCs
560
561#
562# Add new SPI master controllers in alphabetical order above this line
563#
564
565config SPI_DESIGNWARE
566	tristate "DesignWare SPI controller core support"
 
567	help
568	  general driver for SPI controller core from DesignWare
569
570config SPI_DW_PCI
571	tristate "PCI interface driver for DW SPI core"
572	depends on SPI_DESIGNWARE && PCI
573
574config SPI_DW_MID_DMA
575	bool "DMA support for DW SPI controller on Intel Moorestown platform"
576	depends on SPI_DW_PCI && INTEL_MID_DMAC
577
578config SPI_DW_MMIO
579	tristate "Memory-mapped io interface driver for DW SPI core"
580	depends on SPI_DESIGNWARE
581
582#
583# There are lots of SPI device types, with sensors and memory
584# being probably the most widely used ones.
585#
586comment "SPI Protocol Masters"
587
588config SPI_SPIDEV
589	tristate "User mode SPI device driver support"
 
590	help
591	  This supports user mode SPI protocol drivers.
592
593	  Note that this application programming interface is EXPERIMENTAL
594	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
595
596config SPI_TLE62X0
597	tristate "Infineon TLE62X0 (for power switching)"
598	depends on SYSFS
599	help
600	  SPI driver for Infineon TLE62X0 series line driver chips,
601	  such as the TLE6220, TLE6230 and TLE6240.  This provides a
602	  sysfs interface, with each line presented as a kind of GPIO
603	  exposing both switch control and diagnostic feedback.
604
605#
606# Add new SPI protocol masters in alphabetical order above this line
607#
608
609endif # SPI_MASTER
610
611# (slave support would go here)
612
613endif # SPI