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.
13 The "Serial Peripheral Interface" is a low level synchronous
14 protocol. Chips that support SPI can have data transfer rates
15 up to several tens of Mbit/sec. Chips are addressed with a
16 controller and a chipselect. Most SPI slaves don't support
17 dynamic device discovery; some are even write-only or read-only.
19 SPI is widely used by microcontrollers to talk with sensors,
20 eeprom and flash memory, codecs and various other controller
21 chips, analog to digital (and d-to-a) converters, and more.
22 MMC and SD cards can be accessed using SPI protocol; and for
23 DataFlash cards used in MMC sockets, SPI must always be used.
25 SPI is one of a family of similar protocols using a four wire
26 interface (select, clock, data in, data out) including Microwire
27 (half duplex), SSP, SSI, and PSP. This driver framework should
28 work with most such devices and controllers.
31 boolean "Debug support for SPI drivers"
32 depends on SPI && DEBUG_KERNEL
34 Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
35 sysfs, and debugfs support in SPI controller and protocol drivers.
38 # MASTER side ... talking to discrete SPI slave chips including microcontrollers
42 # boolean "SPI Master Support"
46 If your system has an master-capable SPI controller (which
47 provides the clock and chipselect), you can enable that
48 controller and the protocol drivers for the SPI slave chips
51 comment "SPI Master Controller Drivers"
55 tristate "Atmel SPI Controller"
56 depends on (ARCH_AT91 || AVR32) && SPI_MASTER
58 This selects a driver for the Atmel SPI Controller, present on
59 many AT32 (AVR32) and AT91 (ARM) chips.
62 tristate "SPI controller driver for ADI Blackfin5xx"
63 depends on SPI_MASTER && BFIN
65 This is the SPI controller master driver for Blackfin 5xx processor.
68 tristate "Au1550/Au12x0 SPI Controller"
69 depends on SPI_MASTER && (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
72 If you say yes to this option, support will be included for the
73 Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
75 This driver can also be built as a module. If so, the module
76 will be called au1550_spi.
79 tristate "Bitbanging SPI master"
80 depends on SPI_MASTER && EXPERIMENTAL
82 With a few GPIO pins, your system can bitbang the SPI protocol.
83 Select this to get SPI support through I/O pins (GPIO, parallel
84 port, etc). Or, some systems' SPI master controller drivers use
85 this code to manage the per-word or per-transfer accesses to the
86 hardware shift registers.
88 This is library code, and is automatically selected by drivers that
89 need it. You only need to select this explicitly to support driver
90 modules that aren't part of this kernel tree.
93 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
94 depends on SPI_MASTER && PARPORT && EXPERIMENTAL
97 This uses a custom parallel port cable to connect to an AVR
98 Butterfly <http://www.atmel.com/products/avr/butterfly>, an
99 inexpensive battery powered microcontroller evaluation board.
100 This same cable can be used to flash new firmware.
103 tristate "Freescale iMX SPI controller"
104 depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
106 This enables using the Freescale iMX SPI controller in master
110 tristate "Freescale MPC83xx SPI controller"
111 depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
114 This enables using the Freescale MPC83xx SPI controller in master
117 Note, this driver uniquely supports the SPI controller on the MPC83xx
118 family of PowerPC processors. The MPC83xx uses a simple set of shift
119 registers for data (opposed to the CPM based descriptor model).
121 config SPI_OMAP_UWIRE
122 tristate "OMAP1 MicroWire"
123 depends on SPI_MASTER && ARCH_OMAP1
126 This hooks up to the MicroWire controller on OMAP1 chips.
129 bool "McSPI driver for OMAP24xx"
130 depends on SPI_MASTER && ARCH_OMAP24XX
132 SPI master controller for OMAP24xx McSPI modules.
135 tristate "PXA2xx SSP SPI master"
136 depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
138 This enables using a PXA2xx SSP port as a SPI master controller.
139 The driver can be configured to use any SSP port and additional
140 documentation can be found a Documentation/spi/pxa2xx.
143 tristate "Samsung S3C24XX series SPI"
144 depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
146 SPI driver for Samsung S3C24XX series ARM SoCs
148 config SPI_S3C24XX_GPIO
149 tristate "Samsung S3C24XX series SPI by GPIO"
150 depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
152 SPI driver for Samsung S3C24XX series ARM SoCs using
153 GPIO lines to provide the SPI bus. This can be used where
154 the inbuilt hardware cannot provide the transfer mode, or
155 where the board is using non hardware connected pins.
157 # Add new SPI master controllers in alphabetical order above this line
161 # There are lots of SPI device types, with sensors and memory
162 # being probably the most widely used ones.
164 comment "SPI Protocol Masters"
165 depends on SPI_MASTER
168 tristate "SPI EEPROMs from most vendors"
169 depends on SPI_MASTER && SYSFS
171 Enable this driver to get read/write support to most SPI EEPROMs,
172 after you configure the board init code to know about each eeprom
173 on your target board.
175 This driver can also be built as a module. If so, the module
179 tristate "User mode SPI device driver support"
180 depends on SPI_MASTER && EXPERIMENTAL
182 This supports user mode SPI protocol drivers.
184 Note that this application programming interface is EXPERIMENTAL
185 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
188 # Add new SPI protocol masters in alphabetical order above this line
191 # (slave support would go here)
193 endmenu # "SPI support"