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# 8menu "SPI support" 9 depends on HAS_IOMEM 10 11config SPI 12 bool "SPI support" 13 help 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. 19 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. 25 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. 30 31config SPI_DEBUG 32 boolean "Debug support for SPI drivers" 33 depends on SPI && 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 52comment "SPI Master Controller Drivers" 53 depends on SPI_MASTER 54 55config SPI_ATMEL 56 tristate "Atmel SPI Controller" 57 depends on (ARCH_AT91 || AVR32) && SPI_MASTER 58 help 59 This selects a driver for the Atmel SPI Controller, present on 60 many AT32 (AVR32) and AT91 (ARM) chips. 61 62config SPI_BFIN 63 tristate "SPI controller driver for ADI Blackfin5xx" 64 depends on SPI_MASTER && BFIN 65 help 66 This is the SPI controller master driver for Blackfin 5xx processor. 67 68config SPI_AU1550 69 tristate "Au1550/Au12x0 SPI Controller" 70 depends on SPI_MASTER && (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL 71 select SPI_BITBANG 72 help 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). 75 76 This driver can also be built as a module. If so, the module 77 will be called au1550_spi. 78 79config SPI_BITBANG 80 tristate "Bitbanging SPI master" 81 depends on SPI_MASTER && EXPERIMENTAL 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 SPI_MASTER && PARPORT && EXPERIMENTAL 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_IMX 104 tristate "Freescale iMX SPI controller" 105 depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL 106 help 107 This enables using the Freescale iMX SPI controller in master 108 mode. 109 110config SPI_MPC52xx_PSC 111 tristate "Freescale MPC52xx PSC SPI controller" 112 depends on SPI_MASTER && PPC_MPC52xx && EXPERIMENTAL 113 help 114 This enables using the Freescale MPC52xx Programmable Serial 115 Controller in master SPI mode. 116 117config SPI_MPC83xx 118 tristate "Freescale MPC83xx SPI controller" 119 depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL 120 select SPI_BITBANG 121 help 122 This enables using the Freescale MPC83xx SPI controller in master 123 mode. 124 125 Note, this driver uniquely supports the SPI controller on the MPC83xx 126 family of PowerPC processors. The MPC83xx uses a simple set of shift 127 registers for data (opposed to the CPM based descriptor model). 128 129config SPI_OMAP_UWIRE 130 tristate "OMAP1 MicroWire" 131 depends on SPI_MASTER && ARCH_OMAP1 132 select SPI_BITBANG 133 help 134 This hooks up to the MicroWire controller on OMAP1 chips. 135 136 137config SPI_PXA2XX 138 tristate "PXA2xx SSP SPI master" 139 depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL 140 help 141 This enables using a PXA2xx SSP port as a SPI master controller. 142 The driver can be configured to use any SSP port and additional 143 documentation can be found a Documentation/spi/pxa2xx. 144 145config SPI_S3C24XX 146 tristate "Samsung S3C24XX series SPI" 147 depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL 148 help 149 SPI driver for Samsung S3C24XX series ARM SoCs 150 151config SPI_S3C24XX_GPIO 152 tristate "Samsung S3C24XX series SPI by GPIO" 153 depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL 154 help 155 SPI driver for Samsung S3C24XX series ARM SoCs using 156 GPIO lines to provide the SPI bus. This can be used where 157 the inbuilt hardware cannot provide the transfer mode, or 158 where the board is using non hardware connected pins. 159# 160# Add new SPI master controllers in alphabetical order above this line 161# 162 163# 164# There are lots of SPI device types, with sensors and memory 165# being probably the most widely used ones. 166# 167comment "SPI Protocol Masters" 168 depends on SPI_MASTER 169 170config SPI_AT25 171 tristate "SPI EEPROMs from most vendors" 172 depends on SPI_MASTER && SYSFS 173 help 174 Enable this driver to get read/write support to most SPI EEPROMs, 175 after you configure the board init code to know about each eeprom 176 on your target board. 177 178 This driver can also be built as a module. If so, the module 179 will be called at25. 180 181config SPI_SPIDEV 182 tristate "User mode SPI device driver support" 183 depends on SPI_MASTER && EXPERIMENTAL 184 help 185 This supports user mode SPI protocol drivers. 186 187 Note that this application programming interface is EXPERIMENTAL 188 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes. 189 190# 191# Add new SPI protocol masters in alphabetical order above this line 192# 193 194# (slave support would go here) 195 196endmenu # "SPI support" 197 198