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.
14 The "Serial Peripheral Interface" is a low level synchronous
15 protocol. Chips that support SPI can have data transfer rates
16 up to several tens of Mbit/sec. Chips are addressed with a
17 controller and a chipselect. Most SPI slaves don't support
18 dynamic device discovery; some are even write-only or read-only.
20 SPI is widely used by microcontrollers to talk with sensors,
21 eeprom and flash memory, codecs and various other controller
22 chips, analog to digital (and d-to-a) converters, and more.
23 MMC and SD cards can be accessed using SPI protocol; and for
24 DataFlash cards used in MMC sockets, SPI must always be used.
26 SPI is one of a family of similar protocols using a four wire
27 interface (select, clock, data in, data out) including Microwire
28 (half duplex), SSP, SSI, and PSP. This driver framework should
29 work with most such devices and controllers.
32 boolean "Debug support for SPI drivers"
33 depends on SPI && 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
52 comment "SPI Master Controller Drivers"
56 tristate "Atmel SPI Controller"
57 depends on (ARCH_AT91 || AVR32) && SPI_MASTER
59 This selects a driver for the Atmel SPI Controller, present on
60 many AT32 (AVR32) and AT91 (ARM) chips.
63 tristate "SPI controller driver for ADI Blackfin5xx"
64 depends on SPI_MASTER && BFIN
66 This is the SPI controller master driver for Blackfin 5xx processor.
69 tristate "Au1550/Au12x0 SPI Controller"
70 depends on SPI_MASTER && (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
73 If you say yes to this option, support will be included for the
74 Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
76 This driver can also be built as a module. If so, the module
77 will be called au1550_spi.
80 tristate "Bitbanging SPI master"
81 depends on SPI_MASTER && EXPERIMENTAL
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)"
95 depends on SPI_MASTER && PARPORT && EXPERIMENTAL
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 "Freescale iMX SPI controller"
105 depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
107 This enables using the Freescale iMX SPI controller in master
111 tristate "Freescale MPC83xx SPI controller"
112 depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
115 This enables using the Freescale MPC83xx SPI controller in master
118 Note, this driver uniquely supports the SPI controller on the MPC83xx
119 family of PowerPC processors. The MPC83xx uses a simple set of shift
120 registers for data (opposed to the CPM based descriptor model).
122 config SPI_OMAP_UWIRE
123 tristate "OMAP1 MicroWire"
124 depends on SPI_MASTER && ARCH_OMAP1
127 This hooks up to the MicroWire controller on OMAP1 chips.
131 tristate "PXA2xx SSP SPI master"
132 depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
134 This enables using a PXA2xx SSP port as a SPI master controller.
135 The driver can be configured to use any SSP port and additional
136 documentation can be found a Documentation/spi/pxa2xx.
139 tristate "Samsung S3C24XX series SPI"
140 depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
142 SPI driver for Samsung S3C24XX series ARM SoCs
144 config SPI_S3C24XX_GPIO
145 tristate "Samsung S3C24XX series SPI by GPIO"
146 depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
148 SPI driver for Samsung S3C24XX series ARM SoCs using
149 GPIO lines to provide the SPI bus. This can be used where
150 the inbuilt hardware cannot provide the transfer mode, or
151 where the board is using non hardware connected pins.
153 # Add new SPI master controllers in alphabetical order above this line
157 # There are lots of SPI device types, with sensors and memory
158 # being probably the most widely used ones.
160 comment "SPI Protocol Masters"
161 depends on SPI_MASTER
164 tristate "SPI EEPROMs from most vendors"
165 depends on SPI_MASTER && SYSFS
167 Enable this driver to get read/write support to most SPI EEPROMs,
168 after you configure the board init code to know about each eeprom
169 on your target board.
171 This driver can also be built as a module. If so, the module
175 tristate "User mode SPI device driver support"
176 depends on SPI_MASTER && EXPERIMENTAL
178 This supports user mode SPI protocol drivers.
180 Note that this application programming interface is EXPERIMENTAL
181 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
184 # Add new SPI protocol masters in alphabetical order above this line
187 # (slave support would go here)
189 endmenu # "SPI support"