2 # SPI driver configuration
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.
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.
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.
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.
32 boolean "Debug support for SPI drivers"
33 depends on DEBUG_KERNEL
35 Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
36 sysfs, and debugfs support in SPI controller and protocol drivers.
39 # MASTER side ... talking to discrete SPI slave chips including microcontrollers
43 # boolean "SPI Master Support"
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
54 comment "SPI Master Controller Drivers"
57 tristate "Atmel SPI Controller"
58 depends on (ARCH_AT91 || AVR32)
60 This selects a driver for the Atmel SPI Controller, present on
61 many AT32 (AVR32) and AT91 (ARM) chips.
64 tristate "SPI controller driver for ADI Blackfin5xx"
67 This is the SPI controller master driver for Blackfin 5xx processor.
70 tristate "Au1550/Au12x0 SPI Controller"
71 depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
74 If you say yes to this option, support will be included for the
75 Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
77 This driver can also be built as a module. If so, the module
78 will be called au1550_spi.
81 tristate "Utilities for Bitbanging SPI masters"
83 With a few GPIO pins, your system can bitbang the SPI protocol.
84 Select this to get SPI support through I/O pins (GPIO, parallel
85 port, etc). Or, some systems' SPI master controller drivers use
86 this code to manage the per-word or per-transfer accesses to the
87 hardware shift registers.
89 This is library code, and is automatically selected by drivers that
90 need it. You only need to select this explicitly to support driver
91 modules that aren't part of this kernel tree.
94 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
98 This uses a custom parallel port cable to connect to an AVR
99 Butterfly <http://www.atmel.com/products/avr/butterfly>, an
100 inexpensive battery powered microcontroller evaluation board.
101 This same cable can be used to flash new firmware.
103 config SPI_COLDFIRE_QSPI
104 tristate "Freescale Coldfire QSPI controller"
105 depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
107 This enables support for the Coldfire QSPI controller in master
110 This driver can also be built as a module. If so, the module
111 will be called coldfire_qspi.
114 tristate "SPI controller driver for DaVinci/DA8xx SoC's"
115 depends on SPI_MASTER && ARCH_DAVINCI
118 SPI master controller for DaVinci and DA8xx SPI modules.
121 tristate "Cirrus Logic EP93xx SPI controller"
122 depends on ARCH_EP93XX
124 This enables using the Cirrus EP93xx SPI controller in master
127 To compile this driver as a module, choose M here. The module will be
131 tristate "GPIO-based bitbanging SPI Master"
132 depends on GENERIC_GPIO
135 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
136 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
137 slaves connected to a bus using this driver are configured as usual,
138 except that the spi_board_info.controller_data holds the GPIO number
139 for the chipselect used by this controller driver.
141 Note that this driver often won't achieve even 1 Mbit/sec speeds,
142 making it unusually slow for SPI. If your platform can inline
143 GPIO operations, you should be able to leverage that for better
144 speed with a custom version of this driver; see the source code.
147 tristate "Freescale i.MX SPI controllers"
151 This enables using the Freescale i.MX SPI controllers in master
155 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
156 depends on PARPORT && EXPERIMENTAL
159 This driver supports the NS LM70 LLP Evaluation Board,
160 which interfaces to an LM70 temperature sensor using
164 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
165 depends on PPC_MPC52xx && SPI
168 This drivers supports the MPC52xx SPI controller in master SPI
171 config SPI_MPC52xx_PSC
172 tristate "Freescale MPC52xx PSC SPI controller"
173 depends on PPC_MPC52xx && EXPERIMENTAL
175 This enables using the Freescale MPC52xx Programmable Serial
176 Controller in master SPI mode.
178 config SPI_MPC512x_PSC
179 tristate "Freescale MPC512x PSC SPI controller"
180 depends on SPI_MASTER && PPC_MPC512x
182 This enables using the Freescale MPC5121 Programmable Serial
183 Controller in SPI master mode.
186 tristate "Freescale MPC8xxx SPI controller"
189 This enables using the Freescale MPC8xxx SPI controllers in master
192 config SPI_OMAP_UWIRE
193 tristate "OMAP1 MicroWire"
194 depends on ARCH_OMAP1
197 This hooks up to the MicroWire controller on OMAP1 chips.
200 tristate "McSPI driver for OMAP"
201 depends on ARCH_OMAP2PLUS
203 SPI master controller for OMAP24XX and later Multichannel SPI
207 tristate "OMAP SPI 100K"
208 depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
210 OMAP SPI 100K master controller for omap7xx boards.
213 tristate "Orion SPI master (EXPERIMENTAL)"
214 depends on PLAT_ORION && EXPERIMENTAL
216 This enables using the SPI master controller on the Orion chips.
219 tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
220 depends on ARM_AMBA && EXPERIMENTAL
221 default y if MACH_U300
222 default y if ARCH_REALVIEW
223 default y if INTEGRATOR_IMPD1
224 default y if ARCH_VERSATILE
226 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
227 controller. If you have an embedded system with an AMBA(R)
228 bus and a PL022 controller, say Y or M here.
231 tristate "PPC4xx SPI Controller"
232 depends on PPC32 && 4xx && SPI_MASTER
235 This selects a driver for the PPC4xx SPI Controller.
238 tristate "PXA2xx SSP SPI master"
239 depends on ARCH_PXA && EXPERIMENTAL
242 This enables using a PXA2xx SSP port as a SPI master controller.
243 The driver can be configured to use any SSP port and additional
244 documentation can be found a Documentation/spi/pxa2xx.
247 tristate "Samsung S3C24XX series SPI"
248 depends on ARCH_S3C2410 && EXPERIMENTAL
251 SPI driver for Samsung S3C24XX series ARM SoCs
253 config SPI_S3C24XX_FIQ
254 bool "S3C24XX driver with FIQ pseudo-DMA"
255 depends on SPI_S3C24XX
258 Enable FIQ support for the S3C24XX SPI driver to provide pseudo
259 DMA by using the fast-interrupt request framework, This allows
260 the driver to get DMA-like performance when there are either
261 no free DMA channels, or when doing transfers that required both
262 TX and RX data paths.
264 config SPI_S3C24XX_GPIO
265 tristate "Samsung S3C24XX series SPI by GPIO"
266 depends on ARCH_S3C2410 && EXPERIMENTAL
269 SPI driver for Samsung S3C24XX series ARM SoCs using
270 GPIO lines to provide the SPI bus. This can be used where
271 the inbuilt hardware cannot provide the transfer mode, or
272 where the board is using non hardware connected pins.
275 tristate "Samsung S3C64XX series type SPI"
276 depends on ARCH_S3C64XX && EXPERIMENTAL
279 SPI driver for Samsung S3C64XX and newer SoCs.
282 tristate "SuperH MSIOF SPI controller"
283 depends on SUPERH && HAVE_CLK
286 SPI driver for SuperH MSIOF blocks.
289 tristate "SuperH SCI SPI controller"
293 SPI driver for SuperH SCI blocks.
296 tristate "Freescale STMP37xx/378x SPI/SSP controller"
297 depends on ARCH_STMP3XXX && SPI_MASTER
299 SPI driver for Freescale STMP37xx/378x SoC SSP interface
302 tristate "Nvidia Tegra SPI controller"
303 depends on ARCH_TEGRA
304 select TEGRA_SYSTEM_DMA
306 SPI driver for NVidia Tegra SoCs
309 tristate "Toshiba TXx9 SPI controller"
310 depends on GENERIC_GPIO && CPU_TX49XX
312 SPI driver for Toshiba TXx9 MIPS SoCs
315 tristate "Xilinx SPI controller common module"
316 depends on HAS_IOMEM && EXPERIMENTAL
318 select SPI_XILINX_OF if (XILINX_VIRTEX || MICROBLAZE)
320 This exposes the SPI controller IP from the Xilinx EDK.
322 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
323 Product Specification document (DS464) for hardware details.
325 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
328 tristate "Xilinx SPI controller OF device"
329 depends on SPI_XILINX && (XILINX_VIRTEX || MICROBLAZE)
331 This is the OF driver for the SPI controller IP from the Xilinx EDK.
333 config SPI_XILINX_PLTFM
334 tristate "Xilinx SPI controller platform device"
335 depends on SPI_XILINX
337 This is the platform driver for the SPI controller IP
341 tristate "Nuvoton NUC900 series SPI"
342 depends on ARCH_W90X900 && EXPERIMENTAL
345 SPI driver for Nuvoton NUC900 series ARM SoCs
348 # Add new SPI master controllers in alphabetical order above this line
352 tristate "RK29 SPI master controller core support"
353 depends on ARCH_RK29 && SPI_MASTER
355 general driver for SPI controller core from RockChips
358 bool "RK29 SPI0 master controller"
361 enable SPI0 master controller for RK29
364 bool "RK29 SPI1 master controller"
367 enable SPI1 master controller for RK29
369 config LCD_USE_SPIM_CONTROL
370 bool "Switch gpio to spim with spin lock"
373 switch gpio that used for lcd to spim with spin lock.
376 bool "If lcd use spi0 to init lcd then select this item"
377 depends on SPIM_RK29 && LCD_USE_SPIM_CONTROL
379 choose spi bus num to use.
382 bool "If lcd use spi1 to init lcd then select this item"
383 depends on SPIM_RK29 && LCD_USE_SPIM_CONTROL
384 default y if LCD_USE_SPIM_CONTROL
386 choose spi bus num to use.
388 config SPI_DESIGNWARE
389 tristate "DesignWare SPI controller core support"
390 depends on SPI_MASTER
392 general driver for SPI controller core from DesignWare
395 tristate "PCI interface driver for DW SPI core"
396 depends on SPI_DESIGNWARE && PCI
399 tristate "Memory-mapped io interface driver for DW SPI core"
400 depends on SPI_DESIGNWARE && HAVE_CLK
403 # There are lots of SPI device types, with sensors and memory
404 # being probably the most widely used ones.
406 comment "SPI Protocol Masters"
409 tristate "User mode SPI device driver support"
410 depends on EXPERIMENTAL
412 This supports user mode SPI protocol drivers.
414 Note that this application programming interface is EXPERIMENTAL
415 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
418 tristate "Infineon TLE62X0 (for power switching)"
421 SPI driver for Infineon TLE62X0 series line driver chips,
422 such as the TLE6220, TLE6230 and TLE6240. This provides a
423 sysfs interface, with each line presented as a kind of GPIO
424 exposing both switch control and diagnostic feedback.
427 # Add new SPI protocol masters in alphabetical order above this line
432 # (slave support would go here)