Loading...
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 || 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_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
164 tristate "Freescale i.MX SPI controllers"
165 depends on ARCH_MXC
166 select SPI_BITBANG
167 default m if IMX_HAVE_PLATFORM_SPI_IMX
168 help
169 This enables using the Freescale i.MX SPI controllers in master
170 mode.
171
172config SPI_LM70_LLP
173 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
174 depends on PARPORT && EXPERIMENTAL
175 select SPI_BITBANG
176 help
177 This driver supports the NS LM70 LLP Evaluation Board,
178 which interfaces to an LM70 temperature sensor using
179 a parallel port.
180
181config SPI_MPC52xx
182 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
183 depends on PPC_MPC52xx
184 help
185 This drivers supports the MPC52xx SPI controller in master SPI
186 mode.
187
188config SPI_MPC52xx_PSC
189 tristate "Freescale MPC52xx PSC SPI controller"
190 depends on PPC_MPC52xx && EXPERIMENTAL
191 help
192 This enables using the Freescale MPC52xx Programmable Serial
193 Controller in master SPI mode.
194
195config SPI_MPC512x_PSC
196 tristate "Freescale MPC512x PSC SPI controller"
197 depends on PPC_MPC512x
198 help
199 This enables using the Freescale MPC5121 Programmable Serial
200 Controller in SPI master mode.
201
202config SPI_FSL_LIB
203 tristate
204 depends on FSL_SOC
205
206config SPI_FSL_SPI
207 bool "Freescale SPI controller"
208 depends on FSL_SOC
209 select SPI_FSL_LIB
210 help
211 This enables using the Freescale SPI controllers in master mode.
212 MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
213 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
214
215config SPI_FSL_ESPI
216 bool "Freescale eSPI controller"
217 depends on FSL_SOC
218 select SPI_FSL_LIB
219 help
220 This enables using the Freescale eSPI controllers in master mode.
221 From MPC8536, 85xx platform uses the controller, and all P10xx,
222 P20xx, P30xx,P40xx, P50xx uses this controller.
223
224config SPI_OC_TINY
225 tristate "OpenCores tiny SPI"
226 depends on GENERIC_GPIO
227 select SPI_BITBANG
228 help
229 This is the driver for OpenCores tiny SPI master controller.
230
231config SPI_OMAP_UWIRE
232 tristate "OMAP1 MicroWire"
233 depends on ARCH_OMAP1
234 select SPI_BITBANG
235 help
236 This hooks up to the MicroWire controller on OMAP1 chips.
237
238config SPI_OMAP24XX
239 tristate "McSPI driver for OMAP"
240 depends on ARCH_OMAP2PLUS
241 help
242 SPI master controller for OMAP24XX and later Multichannel SPI
243 (McSPI) modules.
244
245config SPI_OMAP_100K
246 tristate "OMAP SPI 100K"
247 depends on ARCH_OMAP850 || ARCH_OMAP730
248 help
249 OMAP SPI 100K master controller for omap7xx boards.
250
251config SPI_ORION
252 tristate "Orion SPI master (EXPERIMENTAL)"
253 depends on PLAT_ORION && EXPERIMENTAL
254 help
255 This enables using the SPI master controller on the Orion chips.
256
257config SPI_PL022
258 tristate "ARM AMBA PL022 SSP controller"
259 depends on ARM_AMBA
260 default y if MACH_U300
261 default y if ARCH_REALVIEW
262 default y if INTEGRATOR_IMPD1
263 default y if ARCH_VERSATILE
264 help
265 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
266 controller. If you have an embedded system with an AMBA(R)
267 bus and a PL022 controller, say Y or M here.
268
269config SPI_PPC4xx
270 tristate "PPC4xx SPI Controller"
271 depends on PPC32 && 4xx
272 select SPI_BITBANG
273 help
274 This selects a driver for the PPC4xx SPI Controller.
275
276config SPI_PXA2XX
277 tristate "PXA2xx SSP SPI master"
278 depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
279 select PXA_SSP if ARCH_PXA
280 help
281 This enables using a PXA2xx or Sodaville SSP port as a SPI master
282 controller. The driver can be configured to use any SSP port and
283 additional documentation can be found a Documentation/spi/pxa2xx.
284
285config SPI_PXA2XX_PCI
286 def_bool SPI_PXA2XX && X86_32 && PCI
287
288config SPI_RSPI
289 tristate "Renesas RSPI controller"
290 depends on SUPERH
291 help
292 SPI driver for Renesas RSPI blocks.
293
294config SPI_S3C24XX
295 tristate "Samsung S3C24XX series SPI"
296 depends on ARCH_S3C24XX && EXPERIMENTAL
297 select SPI_BITBANG
298 help
299 SPI driver for Samsung S3C24XX series ARM SoCs
300
301config SPI_S3C24XX_FIQ
302 bool "S3C24XX driver with FIQ pseudo-DMA"
303 depends on SPI_S3C24XX
304 select FIQ
305 help
306 Enable FIQ support for the S3C24XX SPI driver to provide pseudo
307 DMA by using the fast-interrupt request framework, This allows
308 the driver to get DMA-like performance when there are either
309 no free DMA channels, or when doing transfers that required both
310 TX and RX data paths.
311
312config SPI_S3C64XX
313 tristate "Samsung S3C64XX series type SPI"
314 depends on (ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5P64X0 || ARCH_EXYNOS)
315 select S3C64XX_DMA if ARCH_S3C64XX
316 help
317 SPI driver for Samsung S3C64XX and newer SoCs.
318
319config SPI_SH_MSIOF
320 tristate "SuperH MSIOF SPI controller"
321 depends on SUPERH && HAVE_CLK
322 select SPI_BITBANG
323 help
324 SPI driver for SuperH MSIOF blocks.
325
326config SPI_SH
327 tristate "SuperH SPI controller"
328 depends on SUPERH
329 help
330 SPI driver for SuperH SPI blocks.
331
332config SPI_SH_SCI
333 tristate "SuperH SCI SPI controller"
334 depends on SUPERH
335 select SPI_BITBANG
336 help
337 SPI driver for SuperH SCI blocks.
338
339config SPI_SH_HSPI
340 tristate "SuperH HSPI controller"
341 depends on ARCH_SHMOBILE
342 help
343 SPI driver for SuperH HSPI blocks.
344
345config SPI_SIRF
346 tristate "CSR SiRFprimaII SPI controller"
347 depends on ARCH_PRIMA2
348 select SPI_BITBANG
349 help
350 SPI driver for CSR SiRFprimaII SoCs
351
352config SPI_STMP3XXX
353 tristate "Freescale STMP37xx/378x SPI/SSP controller"
354 depends on ARCH_STMP3XXX
355 help
356 SPI driver for Freescale STMP37xx/378x SoC SSP interface
357
358config SPI_TEGRA
359 tristate "Nvidia Tegra SPI controller"
360 depends on ARCH_TEGRA && TEGRA_SYSTEM_DMA
361 help
362 SPI driver for NVidia Tegra SoCs
363
364config SPI_TI_SSP
365 tristate "TI Sequencer Serial Port - SPI Support"
366 depends on MFD_TI_SSP
367 help
368 This selects an SPI master implementation using a TI sequencer
369 serial port.
370
371config SPI_TOPCLIFF_PCH
372 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
373 depends on PCI
374 help
375 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
376 used in some x86 embedded processors.
377
378 This driver also supports the ML7213/ML7223/ML7831, a companion chip
379 for the Atom E6xx series and compatible with the Intel EG20T PCH.
380
381config SPI_TXX9
382 tristate "Toshiba TXx9 SPI controller"
383 depends on GENERIC_GPIO && CPU_TX49XX
384 help
385 SPI driver for Toshiba TXx9 MIPS SoCs
386
387config SPI_XILINX
388 tristate "Xilinx SPI controller common module"
389 depends on HAS_IOMEM && EXPERIMENTAL
390 select SPI_BITBANG
391 help
392 This exposes the SPI controller IP from the Xilinx EDK.
393
394 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
395 Product Specification document (DS464) for hardware details.
396
397 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
398
399config SPI_NUC900
400 tristate "Nuvoton NUC900 series SPI"
401 depends on ARCH_W90X900 && EXPERIMENTAL
402 select SPI_BITBANG
403 help
404 SPI driver for Nuvoton NUC900 series ARM SoCs
405
406#
407# Add new SPI master controllers in alphabetical order above this line
408#
409
410config SPI_DESIGNWARE
411 tristate "DesignWare SPI controller core support"
412 help
413 general driver for SPI controller core from DesignWare
414
415config SPI_DW_PCI
416 tristate "PCI interface driver for DW SPI core"
417 depends on SPI_DESIGNWARE && PCI
418
419config SPI_DW_MID_DMA
420 bool "DMA support for DW SPI controller on Intel Moorestown platform"
421 depends on SPI_DW_PCI && INTEL_MID_DMAC
422
423config SPI_DW_MMIO
424 tristate "Memory-mapped io interface driver for DW SPI core"
425 depends on SPI_DESIGNWARE && HAVE_CLK
426
427#
428# There are lots of SPI device types, with sensors and memory
429# being probably the most widely used ones.
430#
431comment "SPI Protocol Masters"
432
433config SPI_SPIDEV
434 tristate "User mode SPI device driver support"
435 depends on EXPERIMENTAL
436 help
437 This supports user mode SPI protocol drivers.
438
439 Note that this application programming interface is EXPERIMENTAL
440 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
441
442config SPI_TLE62X0
443 tristate "Infineon TLE62X0 (for power switching)"
444 depends on SYSFS
445 help
446 SPI driver for Infineon TLE62X0 series line driver chips,
447 such as the TLE6220, TLE6230 and TLE6240. This provides a
448 sysfs interface, with each line presented as a kind of GPIO
449 exposing both switch control and diagnostic feedback.
450
451#
452# Add new SPI protocol masters in alphabetical order above this line
453#
454
455endif # SPI_MASTER
456
457# (slave support would go here)
458
459endif # SPI
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 ARM || ARM64 || AVR32 || HEXAGON || MIPS || SUPERH
414 depends on ARCH_OMAP2PLUS || COMPILE_TEST
415 help
416 SPI master controller for OMAP24XX and later Multichannel SPI
417 (McSPI) modules.
418
419config SPI_TI_QSPI
420 tristate "DRA7xxx QSPI controller support"
421 depends on ARCH_OMAP2PLUS || COMPILE_TEST
422 help
423 QSPI master controller for DRA7xxx used for flash devices.
424 This device supports single, dual and quad read support, while
425 it only supports single write mode.
426
427config SPI_OMAP_100K
428 tristate "OMAP SPI 100K"
429 depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
430 help
431 OMAP SPI 100K master controller for omap7xx boards.
432
433config SPI_ORION
434 tristate "Orion SPI master"
435 depends on PLAT_ORION || COMPILE_TEST
436 help
437 This enables using the SPI master controller on the Orion chips.
438
439config SPI_PL022
440 tristate "ARM AMBA PL022 SSP controller"
441 depends on ARM_AMBA
442 default y if MACH_U300
443 default y if ARCH_REALVIEW
444 default y if INTEGRATOR_IMPD1
445 default y if ARCH_VERSATILE
446 help
447 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
448 controller. If you have an embedded system with an AMBA(R)
449 bus and a PL022 controller, say Y or M here.
450
451config SPI_PPC4xx
452 tristate "PPC4xx SPI Controller"
453 depends on PPC32 && 4xx
454 select SPI_BITBANG
455 help
456 This selects a driver for the PPC4xx SPI Controller.
457
458config SPI_PXA2XX
459 tristate "PXA2xx SSP SPI master"
460 depends on (ARCH_PXA || PCI || ACPI)
461 select PXA_SSP if ARCH_PXA
462 help
463 This enables using a PXA2xx or Sodaville SSP port as a SPI master
464 controller. The driver can be configured to use any SSP port and
465 additional documentation can be found a Documentation/spi/pxa2xx.
466
467config SPI_PXA2XX_PCI
468 def_tristate SPI_PXA2XX && PCI && COMMON_CLK
469
470config SPI_ROCKCHIP
471 tristate "Rockchip SPI controller driver"
472 depends on ARM || ARM64 || AVR32 || HEXAGON || MIPS || SUPERH
473 help
474 This selects a driver for Rockchip SPI controller.
475
476 If you say yes to this option, support will be included for
477 RK3066, RK3188 and RK3288 families of SPI controller.
478 Rockchip SPI controller support DMA transport and PIO mode.
479 The main usecase of this controller is to use spi flash as boot
480 device.
481
482config SPI_RB4XX
483 tristate "Mikrotik RB4XX SPI master"
484 depends on SPI_MASTER && ATH79
485 help
486 SPI controller driver for the Mikrotik RB4xx series boards.
487
488config SPI_RSPI
489 tristate "Renesas RSPI/QSPI controller"
490 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
491 help
492 SPI driver for Renesas RSPI and QSPI blocks.
493
494config SPI_QUP
495 tristate "Qualcomm SPI controller with QUP interface"
496 depends on ARCH_QCOM || (ARM && COMPILE_TEST)
497 help
498 Qualcomm Universal Peripheral (QUP) core is an AHB slave that
499 provides a common data path (an output FIFO and an input FIFO)
500 for serial peripheral interface (SPI) mini-core. SPI in master
501 mode supports up to 50MHz, up to four chip selects, programmable
502 data path from 4 bits to 32 bits and numerous protocol variants.
503
504 This driver can also be built as a module. If so, the module
505 will be called spi_qup.
506
507config SPI_S3C24XX
508 tristate "Samsung S3C24XX series SPI"
509 depends on ARCH_S3C24XX
510 select SPI_BITBANG
511 help
512 SPI driver for Samsung S3C24XX series ARM SoCs
513
514config SPI_S3C24XX_FIQ
515 bool "S3C24XX driver with FIQ pseudo-DMA"
516 depends on SPI_S3C24XX
517 select FIQ
518 help
519 Enable FIQ support for the S3C24XX SPI driver to provide pseudo
520 DMA by using the fast-interrupt request framework, This allows
521 the driver to get DMA-like performance when there are either
522 no free DMA channels, or when doing transfers that required both
523 TX and RX data paths.
524
525config SPI_S3C64XX
526 tristate "Samsung S3C64XX series type SPI"
527 depends on (PLAT_SAMSUNG || ARCH_EXYNOS)
528 help
529 SPI driver for Samsung S3C64XX and newer SoCs.
530
531config SPI_SC18IS602
532 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
533 depends on I2C
534 help
535 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
536
537config SPI_SH_MSIOF
538 tristate "SuperH MSIOF SPI controller"
539 depends on HAVE_CLK && HAS_DMA
540 depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
541 help
542 SPI driver for SuperH and SH Mobile MSIOF blocks.
543
544config SPI_SH
545 tristate "SuperH SPI controller"
546 depends on SUPERH || COMPILE_TEST
547 help
548 SPI driver for SuperH SPI blocks.
549
550config SPI_SH_SCI
551 tristate "SuperH SCI SPI controller"
552 depends on SUPERH
553 select SPI_BITBANG
554 help
555 SPI driver for SuperH SCI blocks.
556
557config SPI_SH_HSPI
558 tristate "SuperH HSPI controller"
559 depends on ARCH_RENESAS || COMPILE_TEST
560 help
561 SPI driver for SuperH HSPI blocks.
562
563config SPI_SIRF
564 tristate "CSR SiRFprimaII SPI controller"
565 depends on SIRF_DMA
566 select SPI_BITBANG
567 help
568 SPI driver for CSR SiRFprimaII SoCs
569
570config SPI_ST_SSC4
571 tristate "STMicroelectronics SPI SSC-based driver"
572 depends on ARCH_STI
573 help
574 STMicroelectronics SoCs support for SPI. If you say yes to
575 this option, support will be included for the SSC driven SPI.
576
577config SPI_SUN4I
578 tristate "Allwinner A10 SoCs SPI controller"
579 depends on ARCH_SUNXI || COMPILE_TEST
580 help
581 SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
582
583config SPI_SUN6I
584 tristate "Allwinner A31 SPI controller"
585 depends on ARCH_SUNXI || COMPILE_TEST
586 depends on RESET_CONTROLLER
587 help
588 This enables using the SPI controller on the Allwinner A31 SoCs.
589
590config SPI_MXS
591 tristate "Freescale MXS SPI controller"
592 depends on ARCH_MXS
593 select STMP_DEVICE
594 help
595 SPI driver for Freescale MXS devices.
596
597config SPI_TEGRA114
598 tristate "NVIDIA Tegra114 SPI Controller"
599 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
600 depends on RESET_CONTROLLER && HAS_DMA
601 help
602 SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
603 is different than the older SoCs SPI controller and also register interface
604 get changed with this controller.
605
606config SPI_TEGRA20_SFLASH
607 tristate "Nvidia Tegra20 Serial flash Controller"
608 depends on ARCH_TEGRA || COMPILE_TEST
609 depends on RESET_CONTROLLER
610 help
611 SPI driver for Nvidia Tegra20 Serial flash Controller interface.
612 The main usecase of this controller is to use spi flash as boot
613 device.
614
615config SPI_TEGRA20_SLINK
616 tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
617 depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
618 depends on RESET_CONTROLLER && HAS_DMA
619 help
620 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
621
622config SPI_TOPCLIFF_PCH
623 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
624 depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
625 help
626 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
627 used in some x86 embedded processors.
628
629 This driver also supports the ML7213/ML7223/ML7831, a companion chip
630 for the Atom E6xx series and compatible with the Intel EG20T PCH.
631
632config SPI_TXX9
633 tristate "Toshiba TXx9 SPI controller"
634 depends on GPIOLIB && (CPU_TX49XX || COMPILE_TEST)
635 help
636 SPI driver for Toshiba TXx9 MIPS SoCs
637
638config SPI_XCOMM
639 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
640 depends on I2C
641 help
642 Support for the SPI-I2C bridge found on the Analog Devices
643 AD-FMCOMMS1-EBZ board.
644
645config SPI_XILINX
646 tristate "Xilinx SPI controller common module"
647 depends on HAS_IOMEM
648 select SPI_BITBANG
649 help
650 This exposes the SPI controller IP from the Xilinx EDK.
651
652 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
653 Product Specification document (DS464) for hardware details.
654
655 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
656
657config SPI_XLP
658 tristate "Netlogic XLP SPI controller driver"
659 depends on CPU_XLP || COMPILE_TEST
660 help
661 Enable support for the SPI controller on the Netlogic XLP SoCs.
662 Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX, XLP9XX
663 and XLP5XX.
664
665 If you have a Netlogic XLP platform say Y here.
666 If unsure, say N.
667
668config SPI_XTENSA_XTFPGA
669 tristate "Xtensa SPI controller for xtfpga"
670 depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
671 select SPI_BITBANG
672 help
673 SPI driver for xtfpga SPI master controller.
674
675 This simple SPI master controller is built into xtfpga bitstreams
676 and is used to control daughterboard audio codec. It always transfers
677 16 bit words in SPI mode 0, automatically asserting CS on transfer
678 start and deasserting on end.
679
680config SPI_ZYNQMP_GQSPI
681 tristate "Xilinx ZynqMP GQSPI controller"
682 depends on SPI_MASTER && HAS_DMA
683 help
684 Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
685
686#
687# Add new SPI master controllers in alphabetical order above this line
688#
689
690#
691# There are lots of SPI device types, with sensors and memory
692# being probably the most widely used ones.
693#
694comment "SPI Protocol Masters"
695
696config SPI_SPIDEV
697 tristate "User mode SPI device driver support"
698 help
699 This supports user mode SPI protocol drivers.
700
701 Note that this application programming interface is EXPERIMENTAL
702 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
703
704config SPI_LOOPBACK_TEST
705 tristate "spi loopback test framework support"
706 depends on m
707 help
708 This enables the SPI loopback testing framework driver
709
710 primarily used for development of spi_master drivers
711 and to detect regressions
712
713config SPI_TLE62X0
714 tristate "Infineon TLE62X0 (for power switching)"
715 depends on SYSFS
716 help
717 SPI driver for Infineon TLE62X0 series line driver chips,
718 such as the TLE6220, TLE6230 and TLE6240. This provides a
719 sysfs interface, with each line presented as a kind of GPIO
720 exposing both switch control and diagnostic feedback.
721
722#
723# Add new SPI protocol masters in alphabetical order above this line
724#
725
726endif # SPI_MASTER
727
728# (slave support would go here)
729
730endif # SPI