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_AU1550
84	tristate "Au1550/Au12x0 SPI Controller"
85	depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
86	select SPI_BITBANG
87	help
88	  If you say yes to this option, support will be included for the
89	  Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
90
91	  This driver can also be built as a module.  If so, the module
92	  will be called au1550_spi.
93
94config SPI_BITBANG
95	tristate "Utilities for Bitbanging SPI masters"
96	help
97	  With a few GPIO pins, your system can bitbang the SPI protocol.
98	  Select this to get SPI support through I/O pins (GPIO, parallel
99	  port, etc).  Or, some systems' SPI master controller drivers use
100	  this code to manage the per-word or per-transfer accesses to the
101	  hardware shift registers.
102
103	  This is library code, and is automatically selected by drivers that
104	  need it.  You only need to select this explicitly to support driver
105	  modules that aren't part of this kernel tree.
106
107config SPI_BUTTERFLY
108	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
109	depends on PARPORT
110	select SPI_BITBANG
111	help
112	  This uses a custom parallel port cable to connect to an AVR
113	  Butterfly <http://www.atmel.com/products/avr/butterfly>, an
114	  inexpensive battery powered microcontroller evaluation board.
115	  This same cable can be used to flash new firmware.
116
117config SPI_COLDFIRE_QSPI
118	tristate "Freescale Coldfire QSPI controller"
119	depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
120	help
121	  This enables support for the Coldfire QSPI controller in master
122	  mode.
123
124	  This driver can also be built as a module.  If so, the module
125	  will be called coldfire_qspi.
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
134	  This driver can also be built as a module. The module will be called
135	  davinci_spi.
136
137config SPI_EP93XX
138	tristate "Cirrus Logic EP93xx SPI controller"
139	depends on ARCH_EP93XX
140	help
141	  This enables using the Cirrus EP93xx SPI controller in master
142	  mode.
143
144	  To compile this driver as a module, choose M here. The module will be
145	  called ep93xx_spi.
146
147config SPI_GPIO
148	tristate "GPIO-based bitbanging SPI Master"
149	depends on GENERIC_GPIO
150	select SPI_BITBANG
151	help
152	  This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
153	  interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
154	  slaves connected to a bus using this driver are configured as usual,
155	  except that the spi_board_info.controller_data holds the GPIO number
156	  for the chipselect used by this controller driver.
157
158	  Note that this driver often won't achieve even 1 Mbit/sec speeds,
159	  making it unusually slow for SPI.  If your platform can inline
160	  GPIO operations, you should be able to leverage that for better
161	  speed with a custom version of this driver; see the source code.
162
163config SPI_IMX_VER_IMX1
164	def_bool y if SOC_IMX1
165
166config SPI_IMX_VER_0_0
167	def_bool y if SOC_IMX21 || SOC_IMX27
168
169config SPI_IMX_VER_0_4
170	def_bool y if SOC_IMX31
171
172config SPI_IMX_VER_0_7
173	def_bool y if ARCH_MX25 || SOC_IMX35 || SOC_IMX51 || SOC_IMX53
174
175config SPI_IMX_VER_2_3
176	def_bool y if SOC_IMX51 || SOC_IMX53
177
178config SPI_IMX
179	tristate "Freescale i.MX SPI controllers"
180	depends on ARCH_MXC
181	select SPI_BITBANG
182	default m if IMX_HAVE_PLATFORM_SPI_IMX
183	help
184	  This enables using the Freescale i.MX SPI controllers in master
185	  mode.
186
187config SPI_LM70_LLP
188	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
189	depends on PARPORT && EXPERIMENTAL
190	select SPI_BITBANG
191	help
192	  This driver supports the NS LM70 LLP Evaluation Board,
193	  which interfaces to an LM70 temperature sensor using
194	  a parallel port.
195
196config SPI_MPC52xx
197	tristate "Freescale MPC52xx SPI (non-PSC) controller support"
198	depends on PPC_MPC52xx && SPI
199	select SPI_MASTER_OF
200	help
201	  This drivers supports the MPC52xx SPI controller in master SPI
202	  mode.
203
204config SPI_MPC52xx_PSC
205	tristate "Freescale MPC52xx PSC SPI controller"
206	depends on PPC_MPC52xx && EXPERIMENTAL
207	help
208	  This enables using the Freescale MPC52xx Programmable Serial
209	  Controller in master SPI mode.
210
211config SPI_MPC512x_PSC
212	tristate "Freescale MPC512x PSC SPI controller"
213	depends on SPI_MASTER && PPC_MPC512x
214	help
215	  This enables using the Freescale MPC5121 Programmable Serial
216	  Controller in SPI master mode.
217
218config SPI_FSL_LIB
219	tristate
220	depends on FSL_SOC
221
222config SPI_FSL_SPI
223	tristate "Freescale SPI controller"
224	depends on FSL_SOC
225	select SPI_FSL_LIB
226	help
227	  This enables using the Freescale SPI controllers in master mode.
228	  MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
229	  MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
230
231config SPI_FSL_ESPI
232	tristate "Freescale eSPI controller"
233	depends on FSL_SOC
234	select SPI_FSL_LIB
235	help
236	  This enables using the Freescale eSPI controllers in master mode.
237	  From MPC8536, 85xx platform uses the controller, and all P10xx,
238	  P20xx, P30xx,P40xx, P50xx uses this controller.
239
240config SPI_OC_TINY
241	tristate "OpenCores tiny SPI"
242	depends on GENERIC_GPIO
243	select SPI_BITBANG
244	help
245	  This is the driver for OpenCores tiny SPI master controller.
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 SPI_MASTER && (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 (EXPERIMENTAL)"
275	depends on ARM_AMBA && EXPERIMENTAL
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 && SPI_MASTER
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_S3C24XX
305	tristate "Samsung S3C24XX series SPI"
306	depends on ARCH_S3C2410 && EXPERIMENTAL
307	select SPI_BITBANG
308	help
309	  SPI driver for Samsung S3C24XX series ARM SoCs
310
311config SPI_S3C24XX_FIQ
312	bool "S3C24XX driver with FIQ pseudo-DMA"
313	depends on SPI_S3C24XX
314	select FIQ
315	help
316	  Enable FIQ support for the S3C24XX SPI driver to provide pseudo
317	  DMA by using the fast-interrupt request framework, This allows
318	  the driver to get DMA-like performance when there are either
319	  no free DMA channels, or when doing transfers that required both
320	  TX and RX data paths.
321
322config SPI_S3C24XX_GPIO
323	tristate "Samsung S3C24XX series SPI by GPIO"
324	depends on ARCH_S3C2410 && EXPERIMENTAL
325	select SPI_BITBANG
326	help
327	  SPI driver for Samsung S3C24XX series ARM SoCs using
328	  GPIO lines to provide the SPI bus. This can be used where
329	  the inbuilt hardware cannot provide the transfer mode, or
330	  where the board is using non hardware connected pins.
331
332config SPI_S3C64XX
333	tristate "Samsung S3C64XX series type SPI"
334	depends on (ARCH_S3C64XX || ARCH_S5P64X0)
335	select S3C64XX_DMA if ARCH_S3C64XX
336	help
337	  SPI driver for Samsung S3C64XX and newer SoCs.
338
339config SPI_SH_MSIOF
340	tristate "SuperH MSIOF SPI controller"
341	depends on SUPERH && HAVE_CLK
342	select SPI_BITBANG
343	help
344	  SPI driver for SuperH MSIOF blocks.
345
346config SPI_SH
347	tristate "SuperH SPI controller"
348	depends on SUPERH
349	help
350	  SPI driver for SuperH SPI blocks.
351
352config SPI_SH_SCI
353	tristate "SuperH SCI SPI controller"
354	depends on SUPERH
355	select SPI_BITBANG
356	help
357	  SPI driver for SuperH SCI blocks.
358
359config SPI_STMP3XXX
360	tristate "Freescale STMP37xx/378x SPI/SSP controller"
361	depends on ARCH_STMP3XXX && SPI_MASTER
362	help
363	  SPI driver for Freescale STMP37xx/378x SoC SSP interface
364
365config SPI_TEGRA
366	tristate "Nvidia Tegra SPI controller"
367	depends on ARCH_TEGRA
368	select TEGRA_SYSTEM_DMA
369	help
370	  SPI driver for NVidia Tegra SoCs
371
372config SPI_TI_SSP
373	tristate "TI Sequencer Serial Port - SPI Support"
374	depends on MFD_TI_SSP
375	help
376	  This selects an SPI master implementation using a TI sequencer
377	  serial port.
378
379	  To compile this driver as a module, choose M here: the
380	  module will be called ti-ssp-spi.
381
382config SPI_TOPCLIFF_PCH
383	tristate "Topcliff PCH SPI Controller"
384	depends on PCI
385	help
386	  SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
387	  used in some x86 embedded processors.
388
389config SPI_TXX9
390	tristate "Toshiba TXx9 SPI controller"
391	depends on GENERIC_GPIO && CPU_TX49XX
392	help
393	  SPI driver for Toshiba TXx9 MIPS SoCs
394
395config SPI_XILINX
396	tristate "Xilinx SPI controller common module"
397	depends on HAS_IOMEM && EXPERIMENTAL
398	select SPI_BITBANG
399	help
400	  This exposes the SPI controller IP from the Xilinx EDK.
401
402	  See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
403	  Product Specification document (DS464) for hardware details.
404
405	  Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
406
407config SPI_NUC900
408	tristate "Nuvoton NUC900 series SPI"
409	depends on ARCH_W90X900 && EXPERIMENTAL
410	select SPI_BITBANG
411	help
412	  SPI driver for Nuvoton NUC900 series ARM SoCs
413
414#
415# Add new SPI master controllers in alphabetical order above this line
416#
417
418config SPI_DESIGNWARE
419	tristate "DesignWare SPI controller core support"
420	depends on SPI_MASTER
421	help
422	  general driver for SPI controller core from DesignWare
423
424config SPI_DW_PCI
425	tristate "PCI interface driver for DW SPI core"
426	depends on SPI_DESIGNWARE && PCI
427
428config SPI_DW_MID_DMA
429	bool "DMA support for DW SPI controller on Intel Moorestown platform"
430	depends on SPI_DW_PCI && INTEL_MID_DMAC
431
432config SPI_DW_MMIO
433	tristate "Memory-mapped io interface driver for DW SPI core"
434	depends on SPI_DESIGNWARE && HAVE_CLK
435
436#
437# There are lots of SPI device types, with sensors and memory
438# being probably the most widely used ones.
439#
440comment "SPI Protocol Masters"
441
442config SPI_SPIDEV
443	tristate "User mode SPI device driver support"
444	depends on EXPERIMENTAL
445	help
446	  This supports user mode SPI protocol drivers.
447
448	  Note that this application programming interface is EXPERIMENTAL
449	  and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
450
451config SPI_TLE62X0
452	tristate "Infineon TLE62X0 (for power switching)"
453	depends on SYSFS
454	help
455	  SPI driver for Infineon TLE62X0 series line driver chips,
456	  such as the TLE6220, TLE6230 and TLE6240.  This provides a
457	  sysfs interface, with each line presented as a kind of GPIO
458	  exposing both switch control and diagnostic feedback.
459
460#
461# Add new SPI protocol masters in alphabetical order above this line
462#
463
464endif # SPI_MASTER
465
466# (slave support would go here)
467
468endif # SPI
469