Kconfig revision 6b52c00f2b4931c12117dc32a7cf6d5ee59f14ea 
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_BFIN5XX
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/Au1200/Au1300 SPI Controller"
91	depends on MIPS_ALCHEMY && EXPERIMENTAL
92	select SPI_BITBANG
93	help
94	  If you say yes to this option, support will be included for the
95	  PSC SPI controller found on Au1550, Au1200 and Au1300 series.
96
97config SPI_BCM63XX
98	tristate "Broadcom BCM63xx SPI controller"
99	depends on BCM63XX
100	help
101          Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
102
103config SPI_BITBANG
104	tristate "Utilities for Bitbanging SPI masters"
105	help
106	  With a few GPIO pins, your system can bitbang the SPI protocol.
107	  Select this to get SPI support through I/O pins (GPIO, parallel
108	  port, etc).  Or, some systems' SPI master controller drivers use
109	  this code to manage the per-word or per-transfer accesses to the
110	  hardware shift registers.
111
112	  This is library code, and is automatically selected by drivers that
113	  need it.  You only need to select this explicitly to support driver
114	  modules that aren't part of this kernel tree.
115
116config SPI_BUTTERFLY
117	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
118	depends on PARPORT
119	select SPI_BITBANG
120	help
121	  This uses a custom parallel port cable to connect to an AVR
122	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
123	  inexpensive battery powered microcontroller evaluation board.
124	  This same cable can be used to flash new firmware.
125
126config SPI_COLDFIRE_QSPI
127	tristate "Freescale Coldfire QSPI controller"
128	depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
129	help
130	  This enables support for the Coldfire QSPI controller in master
131	  mode.
132
133config SPI_DAVINCI
134	tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
135	depends on ARCH_DAVINCI
136	select SPI_BITBANG
137	help
138	  SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
139
140config SPI_EP93XX
141	tristate "Cirrus Logic EP93xx SPI controller"
142	depends on ARCH_EP93XX
143	help
144	  This enables using the Cirrus EP93xx SPI controller in master
145	  mode.
146
147config SPI_FALCON
148	tristate "Falcon SPI controller support"
149	depends on SOC_FALCON
150	help
151	  The external bus unit (EBU) found on the FALC-ON SoC has SPI
152	  emulation that is designed for serial flash access. This driver
153	  has only been tested with m25p80 type chips. The hardware has no
154	  support for other types of SPI peripherals.
155
156config SPI_GPIO
157	tristate "GPIO-based bitbanging SPI Master"
158	depends on GENERIC_GPIO
159	select SPI_BITBANG
160	help
161	  This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
162	  interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
163	  slaves connected to a bus using this driver are configured as usual,
164	  except that the spi_board_info.controller_data holds the GPIO number
165	  for the chipselect used by this controller driver.
166
167	  Note that this driver often won't achieve even 1 Mbit/sec speeds,
168	  making it unusually slow for SPI.  If your platform can inline
169	  GPIO operations, you should be able to leverage that for better
170	  speed with a custom version of this driver; see the source code.
171
172config SPI_IMX
173	tristate "Freescale i.MX SPI controllers"
174	depends on ARCH_MXC
175	select SPI_BITBANG
176	default m if IMX_HAVE_PLATFORM_SPI_IMX
177	help
178	  This enables using the Freescale i.MX SPI controllers in master
179	  mode.
180
181config SPI_LM70_LLP
182	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
183	depends on PARPORT && EXPERIMENTAL
184	select SPI_BITBANG
185	help
186	  This driver supports the NS LM70 LLP Evaluation Board,
187	  which interfaces to an LM70 temperature sensor using
188	  a parallel port.
189
190config SPI_MPC52xx
191	tristate "Freescale MPC52xx SPI (non-PSC) controller support"
192	depends on PPC_MPC52xx
193	help
194	  This drivers supports the MPC52xx SPI controller in master SPI
195	  mode.
196
197config SPI_MPC52xx_PSC
198	tristate "Freescale MPC52xx PSC SPI controller"
199	depends on PPC_MPC52xx && EXPERIMENTAL
200	help
201	  This enables using the Freescale MPC52xx Programmable Serial
202	  Controller in master SPI mode.
203
204config SPI_MPC512x_PSC
205	tristate "Freescale MPC512x PSC SPI controller"
206	depends on PPC_MPC512x
207	help
208	  This enables using the Freescale MPC5121 Programmable Serial
209	  Controller in SPI master mode.
210
211config SPI_FSL_LIB
212	tristate
213	depends on FSL_SOC
214
215config SPI_FSL_SPI
216	bool "Freescale SPI controller"
217	depends on FSL_SOC
218	select SPI_FSL_LIB
219	help
220	  This enables using the Freescale SPI controllers in master mode.
221	  MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
222	  MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
223
224config SPI_FSL_ESPI
225	bool "Freescale eSPI controller"
226	depends on FSL_SOC
227	select SPI_FSL_LIB
228	help
229	  This enables using the Freescale eSPI controllers in master mode.
230	  From MPC8536, 85xx platform uses the controller, and all P10xx,
231	  P20xx, P30xx,P40xx, P50xx uses this controller.
232
233config SPI_OC_TINY
234	tristate "OpenCores tiny SPI"
235	depends on GENERIC_GPIO
236	select SPI_BITBANG
237	help
238	  This is the driver for OpenCores tiny SPI master controller.
239
240config SPI_OCTEON
241	tristate "Cavium OCTEON SPI controller"
242	depends on CPU_CAVIUM_OCTEON
243	help
244	  SPI host driver for the hardware found on some Cavium OCTEON
245	  SOCs.
246
247config SPI_OMAP_UWIRE
248	tristate "OMAP1 MicroWire"
249	depends on ARCH_OMAP1
250	select SPI_BITBANG
251	help
252	  This hooks up to the MicroWire controller on OMAP1 chips.
253
254config SPI_OMAP24XX
255	tristate "McSPI driver for OMAP"
256	depends on ARCH_OMAP2PLUS
257	help
258	  SPI master controller for OMAP24XX and later Multichannel SPI
259	  (McSPI) modules.
260
261config SPI_OMAP_100K
262	tristate "OMAP SPI 100K"
263	depends on ARCH_OMAP850 || ARCH_OMAP730
264	help
265	  OMAP SPI 100K master controller for omap7xx boards.
266
267config SPI_ORION
268	tristate "Orion SPI master (EXPERIMENTAL)"
269	depends on PLAT_ORION && EXPERIMENTAL
270	help
271	  This enables using the SPI master controller on the Orion chips.
272
273config SPI_PL022
274	tristate "ARM AMBA PL022 SSP controller"
275	depends on ARM_AMBA
276	default y if MACH_U300
277	default y if ARCH_REALVIEW
278	default y if INTEGRATOR_IMPD1
279	default y if ARCH_VERSATILE
280	help
281	  This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
282	  controller. If you have an embedded system with an AMBA(R)
283	  bus and a PL022 controller, say Y or M here.
284
285config SPI_PPC4xx
286	tristate "PPC4xx SPI Controller"
287	depends on PPC32 && 4xx
288	select SPI_BITBANG
289	help
290	  This selects a driver for the PPC4xx SPI Controller.
291
292config SPI_PXA2XX
293	tristate "PXA2xx SSP SPI master"
294	depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
295	select PXA_SSP if ARCH_PXA
296	help
297	  This enables using a PXA2xx or Sodaville SSP port as a SPI master
298	  controller. The driver can be configured to use any SSP port and
299	  additional documentation can be found a Documentation/spi/pxa2xx.
300
301config SPI_PXA2XX_PCI
302	def_bool SPI_PXA2XX && X86_32 && PCI
303
304config SPI_RSPI
305	tristate "Renesas RSPI controller"
306	depends on SUPERH
307	help
308	  SPI driver for Renesas RSPI blocks.
309
310config SPI_S3C24XX
311	tristate "Samsung S3C24XX series SPI"
312	depends on ARCH_S3C24XX && EXPERIMENTAL
313	select SPI_BITBANG
314	help
315	  SPI driver for Samsung S3C24XX series ARM SoCs
316
317config SPI_S3C24XX_FIQ
318	bool "S3C24XX driver with FIQ pseudo-DMA"
319	depends on SPI_S3C24XX
320	select FIQ
321	help
322	  Enable FIQ support for the S3C24XX SPI driver to provide pseudo
323	  DMA by using the fast-interrupt request framework, This allows
324	  the driver to get DMA-like performance when there are either
325	  no free DMA channels, or when doing transfers that required both
326	  TX and RX data paths.
327
328config SPI_S3C64XX
329	tristate "Samsung S3C64XX series type SPI"
330	depends on (ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5P64X0 || ARCH_EXYNOS)
331	select S3C64XX_DMA if ARCH_S3C64XX
332	help
333	  SPI driver for Samsung S3C64XX and newer SoCs.
334
335config SPI_SH_MSIOF
336	tristate "SuperH MSIOF SPI controller"
337	depends on SUPERH && HAVE_CLK
338	select SPI_BITBANG
339	help
340	  SPI driver for SuperH MSIOF blocks.
341
342config SPI_SH
343	tristate "SuperH SPI controller"
344	depends on SUPERH
345	help
346	  SPI driver for SuperH SPI blocks.
347
348config SPI_SH_SCI
349	tristate "SuperH SCI SPI controller"
350	depends on SUPERH
351	select SPI_BITBANG
352	help
353	  SPI driver for SuperH SCI blocks.
354
355config SPI_SH_HSPI
356	tristate "SuperH HSPI controller"
357	depends on ARCH_SHMOBILE
358	help
359	  SPI driver for SuperH HSPI blocks.
360
361config SPI_SIRF
362	tristate "CSR SiRFprimaII SPI controller"
363	depends on ARCH_PRIMA2
364	select SPI_BITBANG
365	help
366	  SPI driver for CSR SiRFprimaII SoCs
367
368config SPI_STMP3XXX
369	tristate "Freescale STMP37xx/378x SPI/SSP controller"
370	depends on ARCH_STMP3XXX
371	help
372	  SPI driver for Freescale STMP37xx/378x SoC SSP interface
373
374config SPI_TEGRA
375	tristate "Nvidia Tegra SPI controller"
376	depends on ARCH_TEGRA && (TEGRA_SYSTEM_DMA || TEGRA20_APB_DMA)
377	help
378	  SPI driver for NVidia Tegra SoCs
379
380config SPI_TI_SSP
381	tristate "TI Sequencer Serial Port - SPI Support"
382	depends on MFD_TI_SSP
383	help
384	  This selects an SPI master implementation using a TI sequencer
385	  serial port.
386
387config SPI_TOPCLIFF_PCH
388	tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
389	depends on PCI
390	help
391	  SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
392	  used in some x86 embedded processors.
393
394	  This driver also supports the ML7213/ML7223/ML7831, a companion chip
395	  for the Atom E6xx series and compatible with the Intel EG20T PCH.
396
397config SPI_TXX9
398	tristate "Toshiba TXx9 SPI controller"
399	depends on GENERIC_GPIO && CPU_TX49XX
400	help
401	  SPI driver for Toshiba TXx9 MIPS SoCs
402
403config SPI_XCOMM
404	tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
405	depends on I2C
406	help
407	  Support for the SPI-I2C bridge found on the Analog Devices
408	  AD-FMCOMMS1-EBZ board.
409
410config SPI_XILINX
411	tristate "Xilinx SPI controller common module"
412	depends on HAS_IOMEM && EXPERIMENTAL
413	select SPI_BITBANG
414	help
415	  This exposes the SPI controller IP from the Xilinx EDK.
416
417	  See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
418	  Product Specification document (DS464) for hardware details.
419
420	  Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
421
422config SPI_NUC900
423	tristate "Nuvoton NUC900 series SPI"
424	depends on ARCH_W90X900 && EXPERIMENTAL
425	select SPI_BITBANG
426	help
427	  SPI driver for Nuvoton NUC900 series ARM SoCs
428
429#
430# Add new SPI master controllers in alphabetical order above this line
431#
432
433config SPI_DESIGNWARE
434	tristate "DesignWare SPI controller core support"
435	help
436	  general driver for SPI controller core from DesignWare
437
438config SPI_DW_PCI
439	tristate "PCI interface driver for DW SPI core"
440	depends on SPI_DESIGNWARE && PCI
441
442config SPI_DW_MID_DMA
443	bool "DMA support for DW SPI controller on Intel Moorestown platform"
444	depends on SPI_DW_PCI && INTEL_MID_DMAC
445
446config SPI_DW_MMIO
447	tristate "Memory-mapped io interface driver for DW SPI core"
448	depends on SPI_DESIGNWARE && HAVE_CLK
449
450#
451# There are lots of SPI device types, with sensors and memory
452# being probably the most widely used ones.
453#
454comment "SPI Protocol Masters"
455
456config SPI_SPIDEV
457	tristate "User mode SPI device driver support"
458	depends on EXPERIMENTAL
459	help
460	  This supports user mode SPI protocol drivers.
461
462	  Note that this application programming interface is EXPERIMENTAL
463	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
464
465config SPI_TLE62X0
466	tristate "Infineon TLE62X0 (for power switching)"
467	depends on SYSFS
468	help
469	  SPI driver for Infineon TLE62X0 series line driver chips,
470	  such as the TLE6220, TLE6230 and TLE6240.  This provides a
471	  sysfs interface, with each line presented as a kind of GPIO
472	  exposing both switch control and diagnostic feedback.
473
474#
475# Add new SPI protocol masters in alphabetical order above this line
476#
477
478endif # SPI_MASTER
479
480# (slave support would go here)
481
482endif # SPI
483