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 10config SPI 11 bool "SPI support" 12 help 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. 18 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. 24 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. 29 30config SPI_DEBUG 31 boolean "Debug support for SPI drivers" 32 depends on SPI && DEBUG_KERNEL 33 help 34 Say "yes" to enable debug messaging (like dev_dbg and pr_debug), 35 sysfs, and debugfs support in SPI controller and protocol drivers. 36 37# 38# MASTER side ... talking to discrete SPI slave chips including microcontrollers 39# 40 41config SPI_MASTER 42# boolean "SPI Master Support" 43 boolean 44 default SPI 45 help 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 49 that are connected. 50 51comment "SPI Master Controller Drivers" 52 depends on SPI_MASTER 53 54config SPI_ATMEL 55 tristate "Atmel SPI Controller" 56 depends on (ARCH_AT91 || AVR32) && SPI_MASTER 57 help 58 This selects a driver for the Atmel SPI Controller, present on 59 many AT32 (AVR32) and AT91 (ARM) chips. 60 61config SPI_BFIN 62 tristate "SPI controller driver for ADI Blackfin5xx" 63 depends on SPI_MASTER && BFIN 64 help 65 This is the SPI controller master driver for Blackfin 5xx processor. 66 67config SPI_BITBANG 68 tristate "Bitbanging SPI master" 69 depends on SPI_MASTER && EXPERIMENTAL 70 help 71 With a few GPIO pins, your system can bitbang the SPI protocol. 72 Select this to get SPI support through I/O pins (GPIO, parallel 73 port, etc). Or, some systems' SPI master controller drivers use 74 this code to manage the per-word or per-transfer accesses to the 75 hardware shift registers. 76 77 This is library code, and is automatically selected by drivers that 78 need it. You only need to select this explicitly to support driver 79 modules that aren't part of this kernel tree. 80 81config SPI_BUTTERFLY 82 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" 83 depends on SPI_MASTER && PARPORT && EXPERIMENTAL 84 select SPI_BITBANG 85 help 86 This uses a custom parallel port cable to connect to an AVR 87 Butterfly <http://www.atmel.com/products/avr/butterfly>, an 88 inexpensive battery powered microcontroller evaluation board. 89 This same cable can be used to flash new firmware. 90 91config SPI_IMX 92 tristate "Freescale iMX SPI controller" 93 depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL 94 help 95 This enables using the Freescale iMX SPI controller in master 96 mode. 97 98config SPI_MPC83xx 99 tristate "Freescale MPC83xx SPI controller" 100 depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL 101 select SPI_BITBANG 102 help 103 This enables using the Freescale MPC83xx SPI controller in master 104 mode. 105 106 Note, this driver uniquely supports the SPI controller on the MPC83xx 107 family of PowerPC processors. The MPC83xx uses a simple set of shift 108 registers for data (opposed to the CPM based descriptor model). 109 110config SPI_OMAP_UWIRE 111 tristate "OMAP1 MicroWire" 112 depends on SPI_MASTER && ARCH_OMAP1 113 select SPI_BITBANG 114 help 115 This hooks up to the MicroWire controller on OMAP1 chips. 116 117 118config SPI_PXA2XX 119 tristate "PXA2xx SSP SPI master" 120 depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL 121 help 122 This enables using a PXA2xx SSP port as a SPI master controller. 123 The driver can be configured to use any SSP port and additional 124 documentation can be found a Documentation/spi/pxa2xx. 125 126config SPI_S3C24XX 127 tristate "Samsung S3C24XX series SPI" 128 depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL 129 help 130 SPI driver for Samsung S3C24XX series ARM SoCs 131 132config SPI_S3C24XX_GPIO 133 tristate "Samsung S3C24XX series SPI by GPIO" 134 depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL 135 help 136 SPI driver for Samsung S3C24XX series ARM SoCs using 137 GPIO lines to provide the SPI bus. This can be used where 138 the inbuilt hardware cannot provide the transfer mode, or 139 where the board is using non hardware connected pins. 140# 141# Add new SPI master controllers in alphabetical order above this line 142# 143 144# 145# There are lots of SPI device types, with sensors and memory 146# being probably the most widely used ones. 147# 148comment "SPI Protocol Masters" 149 depends on SPI_MASTER 150 151config SPI_AT25 152 tristate "SPI EEPROMs from most vendors" 153 depends on SPI_MASTER && SYSFS 154 help 155 Enable this driver to get read/write support to most SPI EEPROMs, 156 after you configure the board init code to know about each eeprom 157 on your target board. 158 159 This driver can also be built as a module. If so, the module 160 will be called at25. 161 162# 163# Add new SPI protocol masters in alphabetical order above this line 164# 165 166# (slave support would go here) 167 168endmenu # "SPI support" 169 170