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.
104 tristate "GPIO-based bitbanging SPI Master"
105 depends on GENERIC_GPIO
108 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
109 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
110 slaves connected to a bus using this driver are configured as usual,
111 except that the spi_board_info.controller_data holds the GPIO number
112 for the chipselect used by this controller driver.
114 Note that this driver often won't achieve even 1 Mbit/sec speeds,
115 making it unusually slow for SPI. If your platform can inline
116 GPIO operations, you should be able to leverage that for better
117 speed with a custom version of this driver; see the source code.
120 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
121 depends on PARPORT && EXPERIMENTAL
124 This driver supports the NS LM70 LLP Evaluation Board,
125 which interfaces to an LM70 temperature sensor using
128 config SPI_MPC52xx_PSC
129 tristate "Freescale MPC52xx PSC SPI controller"
130 depends on PPC_MPC52xx && EXPERIMENTAL
132 This enables using the Freescale MPC52xx Programmable Serial
133 Controller in master SPI mode.
136 tristate "Freescale MPC8xxx SPI controller"
139 This enables using the Freescale MPC8xxx SPI controllers in master
142 This driver uses a simple set of shift registers for data (opposed
143 to the CPM based descriptor model).
145 config SPI_OMAP_UWIRE
146 tristate "OMAP1 MicroWire"
147 depends on ARCH_OMAP1
150 This hooks up to the MicroWire controller on OMAP1 chips.
153 tristate "McSPI driver for OMAP24xx/OMAP34xx"
154 depends on ARCH_OMAP24XX || ARCH_OMAP34XX
156 SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
160 tristate "Orion SPI master (EXPERIMENTAL)"
161 depends on PLAT_ORION && EXPERIMENTAL
163 This enables using the SPI master controller on the Orion chips.
166 tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
167 depends on ARM_AMBA && EXPERIMENTAL
168 default y if MACH_U300
169 default y if ARCH_REALVIEW
170 default y if INTEGRATOR_IMPD1
171 default y if ARCH_VERSATILE
173 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
174 controller. If you have an embedded system with an AMBA(R)
175 bus and a PL022 controller, say Y or M here.
178 tristate "PPC4xx SPI Controller"
179 depends on PPC32 && 4xx && SPI_MASTER
182 This selects a driver for the PPC4xx SPI Controller.
185 tristate "PXA2xx SSP SPI master"
186 depends on ARCH_PXA && EXPERIMENTAL
189 This enables using a PXA2xx SSP port as a SPI master controller.
190 The driver can be configured to use any SSP port and additional
191 documentation can be found a Documentation/spi/pxa2xx.
194 tristate "Samsung S3C24XX series SPI"
195 depends on ARCH_S3C2410 && EXPERIMENTAL
198 SPI driver for Samsung S3C24XX series ARM SoCs
200 config SPI_S3C24XX_GPIO
201 tristate "Samsung S3C24XX series SPI by GPIO"
202 depends on ARCH_S3C2410 && EXPERIMENTAL
205 SPI driver for Samsung S3C24XX series ARM SoCs using
206 GPIO lines to provide the SPI bus. This can be used where
207 the inbuilt hardware cannot provide the transfer mode, or
208 where the board is using non hardware connected pins.
211 tristate "SuperH SCI SPI controller"
215 SPI driver for SuperH SCI blocks.
218 tristate "Toshiba TXx9 SPI controller"
219 depends on GENERIC_GPIO && CPU_TX49XX
221 SPI driver for Toshiba TXx9 MIPS SoCs
224 tristate "Xilinx SPI controller"
225 depends on (XILINX_VIRTEX || MICROBLAZE) && EXPERIMENTAL
228 This exposes the SPI controller IP from the Xilinx EDK.
230 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
231 Product Specification document (DS464) for hardware details.
234 # Add new SPI master controllers in alphabetical order above this line
238 # There are lots of SPI device types, with sensors and memory
239 # being probably the most widely used ones.
241 comment "SPI Protocol Masters"
244 tristate "User mode SPI device driver support"
245 depends on EXPERIMENTAL
247 This supports user mode SPI protocol drivers.
249 Note that this application programming interface is EXPERIMENTAL
250 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
253 tristate "Infineon TLE62X0 (for power switching)"
256 SPI driver for Infineon TLE62X0 series line driver chips,
257 such as the TLE6220, TLE6230 and TLE6240. This provides a
258 sysfs interface, with each line presented as a kind of GPIO
259 exposing both switch control and diagnostic feedback.
262 # Add new SPI protocol masters in alphabetical order above this line
267 # (slave support would go here)