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_ATMEL 57 tristate "Atmel SPI Controller" 58 depends on (ARCH_AT91 || AVR32) 59 help 60 This selects a driver for the Atmel SPI Controller, present on 61 many AT32 (AVR32) and AT91 (ARM) chips. 62 63config SPI_BFIN 64 tristate "SPI controller driver for ADI Blackfin5xx" 65 depends on BLACKFIN 66 help 67 This is the SPI controller master driver for Blackfin 5xx processor. 68 69config SPI_AU1550 70 tristate "Au1550/Au12x0 SPI Controller" 71 depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL 72 select SPI_BITBANG 73 help 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). 76 77 This driver can also be built as a module. If so, the module 78 will be called au1550_spi. 79 80config SPI_BITBANG 81 tristate "Utilities for Bitbanging SPI masters" 82 help 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. 88 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. 92 93config SPI_BUTTERFLY 94 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" 95 depends on PARPORT 96 select SPI_BITBANG 97 help 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. 102 103config SPI_GPIO 104 tristate "GPIO-based bitbanging SPI Master" 105 depends on GENERIC_GPIO 106 select SPI_BITBANG 107 help 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. 113 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. 118 119config SPI_IMX 120 tristate "Freescale i.MX SPI controllers" 121 depends on ARCH_MXC 122 select SPI_BITBANG 123 help 124 This enables using the Freescale i.MX SPI controllers in master 125 mode. 126 127config SPI_LM70_LLP 128 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 129 depends on PARPORT && EXPERIMENTAL 130 select SPI_BITBANG 131 help 132 This driver supports the NS LM70 LLP Evaluation Board, 133 which interfaces to an LM70 temperature sensor using 134 a parallel port. 135 136config SPI_MPC52xx_PSC 137 tristate "Freescale MPC52xx PSC SPI controller" 138 depends on PPC_MPC52xx && EXPERIMENTAL 139 help 140 This enables using the Freescale MPC52xx Programmable Serial 141 Controller in master SPI mode. 142 143config SPI_MPC8xxx 144 tristate "Freescale MPC8xxx SPI controller" 145 depends on FSL_SOC 146 help 147 This enables using the Freescale MPC8xxx SPI controllers in master 148 mode. 149 150 This driver uses a simple set of shift registers for data (opposed 151 to the CPM based descriptor model). 152 153config SPI_OMAP_UWIRE 154 tristate "OMAP1 MicroWire" 155 depends on ARCH_OMAP1 156 select SPI_BITBANG 157 help 158 This hooks up to the MicroWire controller on OMAP1 chips. 159 160config SPI_OMAP24XX 161 tristate "McSPI driver for OMAP24xx/OMAP34xx" 162 depends on ARCH_OMAP24XX || ARCH_OMAP34XX 163 help 164 SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI 165 (McSPI) modules. 166 167config SPI_ORION 168 tristate "Orion SPI master (EXPERIMENTAL)" 169 depends on PLAT_ORION && EXPERIMENTAL 170 help 171 This enables using the SPI master controller on the Orion chips. 172 173config SPI_PL022 174 tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)" 175 depends on ARM_AMBA && EXPERIMENTAL 176 default y if MACH_U300 177 default y if ARCH_REALVIEW 178 default y if INTEGRATOR_IMPD1 179 default y if ARCH_VERSATILE 180 help 181 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 182 controller. If you have an embedded system with an AMBA(R) 183 bus and a PL022 controller, say Y or M here. 184 185config SPI_PPC4xx 186 tristate "PPC4xx SPI Controller" 187 depends on PPC32 && 4xx && SPI_MASTER 188 select SPI_BITBANG 189 help 190 This selects a driver for the PPC4xx SPI Controller. 191 192config SPI_PXA2XX 193 tristate "PXA2xx SSP SPI master" 194 depends on ARCH_PXA && EXPERIMENTAL 195 select PXA_SSP 196 help 197 This enables using a PXA2xx SSP port as a SPI master controller. 198 The driver can be configured to use any SSP port and additional 199 documentation can be found a Documentation/spi/pxa2xx. 200 201config SPI_S3C24XX 202 tristate "Samsung S3C24XX series SPI" 203 depends on ARCH_S3C2410 && EXPERIMENTAL 204 select SPI_BITBANG 205 help 206 SPI driver for Samsung S3C24XX series ARM SoCs 207 208config SPI_S3C24XX_GPIO 209 tristate "Samsung S3C24XX series SPI by GPIO" 210 depends on ARCH_S3C2410 && EXPERIMENTAL 211 select SPI_BITBANG 212 help 213 SPI driver for Samsung S3C24XX series ARM SoCs using 214 GPIO lines to provide the SPI bus. This can be used where 215 the inbuilt hardware cannot provide the transfer mode, or 216 where the board is using non hardware connected pins. 217 218config SPI_SH_SCI 219 tristate "SuperH SCI SPI controller" 220 depends on SUPERH 221 select SPI_BITBANG 222 help 223 SPI driver for SuperH SCI blocks. 224 225config SPI_STMP3XXX 226 tristate "Freescale STMP37xx/378x SPI/SSP controller" 227 depends on ARCH_STMP3XXX && SPI_MASTER 228 help 229 SPI driver for Freescale STMP37xx/378x SoC SSP interface 230 231config SPI_TXX9 232 tristate "Toshiba TXx9 SPI controller" 233 depends on GENERIC_GPIO && CPU_TX49XX 234 help 235 SPI driver for Toshiba TXx9 MIPS SoCs 236 237config SPI_XILINX 238 tristate "Xilinx SPI controller" 239 depends on (XILINX_VIRTEX || MICROBLAZE) && EXPERIMENTAL 240 select SPI_BITBANG 241 help 242 This exposes the SPI controller IP from the Xilinx EDK. 243 244 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 245 Product Specification document (DS464) for hardware details. 246 247# 248# Add new SPI master controllers in alphabetical order above this line 249# 250 251# 252# There are lots of SPI device types, with sensors and memory 253# being probably the most widely used ones. 254# 255comment "SPI Protocol Masters" 256 257config SPI_SPIDEV 258 tristate "User mode SPI device driver support" 259 depends on EXPERIMENTAL 260 help 261 This supports user mode SPI protocol drivers. 262 263 Note that this application programming interface is EXPERIMENTAL 264 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes. 265 266config SPI_TLE62X0 267 tristate "Infineon TLE62X0 (for power switching)" 268 depends on SYSFS 269 help 270 SPI driver for Infineon TLE62X0 series line driver chips, 271 such as the TLE6220, TLE6230 and TLE6240. This provides a 272 sysfs interface, with each line presented as a kind of GPIO 273 exposing both switch control and diagnostic feedback. 274 275# 276# Add new SPI protocol masters in alphabetical order above this line 277# 278 279endif # SPI_MASTER 280 281# (slave support would go here) 282 283endif # SPI 284