Root/drivers/spi/Kconfig

Source at commit 6c17a31f1fc515425221067cb3ece599c09dbc5d created 9 years 3 months ago.
By Werner Almesberger, atusb, atben: moved from spi/ to ieee802154/; renamed atusb to spi_atusb
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_ATH79
57    tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
58    depends on ATH79 && GENERIC_GPIO
59    select SPI_BITBANG
60    help
61      This enables support for the SPI controller present on the
62      Atheros AR71XX/AR724X/AR913X SoCs.
63
64config SPI_ATMEL
65    tristate "Atmel SPI Controller"
66    depends on (ARCH_AT91 || AVR32)
67    help
68      This selects a driver for the Atmel SPI Controller, present on
69      many AT32 (AVR32) and AT91 (ARM) chips.
70
71config SPI_BFIN
72    tristate "SPI controller driver for ADI Blackfin5xx"
73    depends on BLACKFIN
74    help
75      This is the SPI controller master driver for Blackfin 5xx processor.
76
77config SPI_AU1550
78    tristate "Au1550/Au12x0 SPI Controller"
79    depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
80    select SPI_BITBANG
81    help
82      If you say yes to this option, support will be included for the
83      Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
84
85      This driver can also be built as a module. If so, the module
86      will be called au1550_spi.
87
88config SPI_BITBANG
89    tristate "Utilities for Bitbanging SPI masters"
90    help
91      With a few GPIO pins, your system can bitbang the SPI protocol.
92      Select this to get SPI support through I/O pins (GPIO, parallel
93      port, etc). Or, some systems' SPI master controller drivers use
94      this code to manage the per-word or per-transfer accesses to the
95      hardware shift registers.
96
97      This is library code, and is automatically selected by drivers that
98      need it. You only need to select this explicitly to support driver
99      modules that aren't part of this kernel tree.
100
101config SPI_BUTTERFLY
102    tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
103    depends on PARPORT
104    select SPI_BITBANG
105    help
106      This uses a custom parallel port cable to connect to an AVR
107      Butterfly <http://www.atmel.com/products/avr/butterfly>, an
108      inexpensive battery powered microcontroller evaluation board.
109      This same cable can be used to flash new firmware.
110
111config SPI_COLDFIRE_QSPI
112    tristate "Freescale Coldfire QSPI controller"
113    depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
114    help
115      This enables support for the Coldfire QSPI controller in master
116      mode.
117
118      This driver can also be built as a module. If so, the module
119      will be called coldfire_qspi.
120
121config SPI_DAVINCI
122    tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
123    depends on SPI_MASTER && ARCH_DAVINCI
124    select SPI_BITBANG
125    help
126      SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
127
128      This driver can also be built as a module. The module will be called
129      davinci_spi.
130
131config SPI_EP93XX
132    tristate "Cirrus Logic EP93xx SPI controller"
133    depends on ARCH_EP93XX
134    help
135      This enables using the Cirrus EP93xx SPI controller in master
136      mode.
137
138      To compile this driver as a module, choose M here. The module will be
139      called ep93xx_spi.
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_VER_IMX1
158    def_bool y if SOC_IMX1
159
160config SPI_IMX_VER_0_0
161    def_bool y if SOC_IMX21 || SOC_IMX27
162
163config SPI_IMX_VER_0_4
164    def_bool y if ARCH_MX31
165
166config SPI_IMX_VER_0_7
167    def_bool y if ARCH_MX25 || ARCH_MX35 || ARCH_MX51 || ARCH_MX53
168
169config SPI_IMX_VER_2_3
170    def_bool y if ARCH_MX51 || ARCH_MX53
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 && SPI
193    select SPI_MASTER_OF
194    help
195      This drivers supports the MPC52xx SPI controller in master SPI
196      mode.
197
198config SPI_MPC52xx_PSC
199    tristate "Freescale MPC52xx PSC SPI controller"
200    depends on PPC_MPC52xx && EXPERIMENTAL
201    help
202      This enables using the Freescale MPC52xx Programmable Serial
203      Controller in master SPI mode.
204
205config SPI_MPC512x_PSC
206    tristate "Freescale MPC512x PSC SPI controller"
207    depends on SPI_MASTER && PPC_MPC512x
208    help
209      This enables using the Freescale MPC5121 Programmable Serial
210      Controller in SPI master mode.
211
212config SPI_FSL_LIB
213    tristate
214    depends on FSL_SOC
215
216config SPI_FSL_SPI
217    tristate "Freescale SPI controller"
218    depends on FSL_SOC
219    select SPI_FSL_LIB
220    help
221      This enables using the Freescale SPI controllers in master mode.
222      MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
223      MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
224
225config SPI_FSL_ESPI
226    tristate "Freescale eSPI controller"
227    depends on FSL_SOC
228    select SPI_FSL_LIB
229    help
230      This enables using the Freescale eSPI controllers in master mode.
231      From MPC8536, 85xx platform uses the controller, and all P10xx,
232      P20xx, P30xx,P40xx, P50xx uses this controller.
233
234config SPI_OMAP_UWIRE
235    tristate "OMAP1 MicroWire"
236    depends on ARCH_OMAP1
237    select SPI_BITBANG
238    help
239      This hooks up to the MicroWire controller on OMAP1 chips.
240
241config SPI_OMAP24XX
242    tristate "McSPI driver for OMAP"
243    depends on ARCH_OMAP2PLUS
244    help
245      SPI master controller for OMAP24XX and later Multichannel SPI
246      (McSPI) modules.
247
248config SPI_OMAP_100K
249    tristate "OMAP SPI 100K"
250    depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
251    help
252      OMAP SPI 100K master controller for omap7xx boards.
253
254config SPI_ORION
255    tristate "Orion SPI master (EXPERIMENTAL)"
256    depends on PLAT_ORION && EXPERIMENTAL
257    help
258      This enables using the SPI master controller on the Orion chips.
259
260config SPI_PL022
261    tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
262    depends on ARM_AMBA && EXPERIMENTAL
263    default y if MACH_U300
264    default y if ARCH_REALVIEW
265    default y if INTEGRATOR_IMPD1
266    default y if ARCH_VERSATILE
267    help
268      This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
269      controller. If you have an embedded system with an AMBA(R)
270      bus and a PL022 controller, say Y or M here.
271
272config SPI_PPC4xx
273    tristate "PPC4xx SPI Controller"
274    depends on PPC32 && 4xx && SPI_MASTER
275    select SPI_BITBANG
276    help
277      This selects a driver for the PPC4xx SPI Controller.
278
279config SPI_PXA2XX
280    tristate "PXA2xx SSP SPI master"
281    depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
282    select PXA_SSP if ARCH_PXA
283    help
284      This enables using a PXA2xx or Sodaville SSP port as a SPI master
285      controller. The driver can be configured to use any SSP port and
286      additional documentation can be found a Documentation/spi/pxa2xx.
287
288config SPI_PXA2XX_PCI
289    def_bool SPI_PXA2XX && X86_32 && PCI
290
291config SPI_S3C24XX
292    tristate "Samsung S3C24XX series SPI"
293    depends on ARCH_S3C2410 && EXPERIMENTAL
294    select SPI_BITBANG
295    help
296      SPI driver for Samsung S3C24XX series ARM SoCs
297
298config SPI_S3C24XX_FIQ
299    bool "S3C24XX driver with FIQ pseudo-DMA"
300    depends on SPI_S3C24XX
301    select FIQ
302    help
303      Enable FIQ support for the S3C24XX SPI driver to provide pseudo
304      DMA by using the fast-interrupt request framework, This allows
305      the driver to get DMA-like performance when there are either
306      no free DMA channels, or when doing transfers that required both
307      TX and RX data paths.
308
309config SPI_S3C24XX_GPIO
310    tristate "Samsung S3C24XX series SPI by GPIO"
311    depends on ARCH_S3C2410 && EXPERIMENTAL
312    select SPI_BITBANG
313    help
314      SPI driver for Samsung S3C24XX series ARM SoCs using
315      GPIO lines to provide the SPI bus. This can be used where
316      the inbuilt hardware cannot provide the transfer mode, or
317      where the board is using non hardware connected pins.
318
319config SPI_S3C64XX
320    tristate "Samsung S3C64XX series type SPI"
321    depends on (ARCH_S3C64XX || ARCH_S5P64X0)
322    select S3C64XX_DMA if ARCH_S3C64XX
323    help
324      SPI driver for Samsung S3C64XX and newer SoCs.
325
326config SPI_SH_MSIOF
327    tristate "SuperH MSIOF SPI controller"
328    depends on SUPERH && HAVE_CLK
329    select SPI_BITBANG
330    help
331      SPI driver for SuperH MSIOF blocks.
332
333config SPI_SH_SCI
334    tristate "SuperH SCI SPI controller"
335    depends on SUPERH
336    select SPI_BITBANG
337    help
338      SPI driver for SuperH SCI blocks.
339
340config SPI_STMP3XXX
341    tristate "Freescale STMP37xx/378x SPI/SSP controller"
342    depends on ARCH_STMP3XXX && SPI_MASTER
343    help
344      SPI driver for Freescale STMP37xx/378x SoC SSP interface
345
346config SPI_TEGRA
347    tristate "Nvidia Tegra SPI controller"
348    depends on ARCH_TEGRA
349    select TEGRA_SYSTEM_DMA
350    help
351      SPI driver for NVidia Tegra SoCs
352
353config SPI_TOPCLIFF_PCH
354    tristate "Topcliff PCH SPI Controller"
355    depends on PCI
356    help
357      SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
358      used in some x86 embedded processors.
359
360config SPI_TXX9
361    tristate "Toshiba TXx9 SPI controller"
362    depends on GENERIC_GPIO && CPU_TX49XX
363    help
364      SPI driver for Toshiba TXx9 MIPS SoCs
365
366config SPI_XILINX
367    tristate "Xilinx SPI controller common module"
368    depends on HAS_IOMEM && EXPERIMENTAL
369    select SPI_BITBANG
370    help
371      This exposes the SPI controller IP from the Xilinx EDK.
372
373      See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
374      Product Specification document (DS464) for hardware details.
375
376      Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
377
378config SPI_NUC900
379    tristate "Nuvoton NUC900 series SPI"
380    depends on ARCH_W90X900 && EXPERIMENTAL
381    select SPI_BITBANG
382    help
383      SPI driver for Nuvoton NUC900 series ARM SoCs
384
385#
386# Add new SPI master controllers in alphabetical order above this line
387#
388
389config SPI_DESIGNWARE
390    tristate "DesignWare SPI controller core support"
391    depends on SPI_MASTER
392    help
393      general driver for SPI controller core from DesignWare
394
395config SPI_DW_PCI
396    tristate "PCI interface driver for DW SPI core"
397    depends on SPI_DESIGNWARE && PCI
398
399config SPI_DW_MID_DMA
400    bool "DMA support for DW SPI controller on Intel Moorestown platform"
401    depends on SPI_DW_PCI && INTEL_MID_DMAC
402
403config SPI_DW_MMIO
404    tristate "Memory-mapped io interface driver for DW SPI core"
405    depends on SPI_DESIGNWARE && HAVE_CLK
406
407#
408# There are lots of SPI device types, with sensors and memory
409# being probably the most widely used ones.
410#
411comment "SPI Protocol Masters"
412
413config SPI_SPIDEV
414    tristate "User mode SPI device driver support"
415    depends on EXPERIMENTAL
416    help
417      This supports user mode SPI protocol drivers.
418
419      Note that this application programming interface is EXPERIMENTAL
420      and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
421
422config SPI_TLE62X0
423    tristate "Infineon TLE62X0 (for power switching)"
424    depends on SYSFS
425    help
426      SPI driver for Infineon TLE62X0 series line driver chips,
427      such as the TLE6220, TLE6230 and TLE6240. This provides a
428      sysfs interface, with each line presented as a kind of GPIO
429      exposing both switch control and diagnostic feedback.
430
431#
432# Add new SPI protocol masters in alphabetical order above this line
433#
434
435endif # SPI_MASTER
436
437# (slave support would go here)
438
439endif # SPI
440

Archive Download this file



interactive