drivers/spi/Kconfig

   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 #
   8 menuconfig 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
  29 if SPI
  30
  31 config 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
  42 config 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
  52 if SPI_MASTER
  53
  54 comment "SPI Master Controller Drivers"
  55
  56 config 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
  63 config 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
  69 config 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
  80 config SPI_BITBANG
  81         tristate "Bitbanging SPI master"
  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
  93 config 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
 103 config SPI_IMX
 104         tristate "Freescale iMX SPI controller"
 105         depends on ARCH_IMX && EXPERIMENTAL
 106         help
 107           This enables using the Freescale iMX SPI controller in master
 108           mode.
 109
 110 config SPI_LM70_LLP
 111         tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
 112         depends on PARPORT && EXPERIMENTAL
 113         select SPI_BITBANG
 114         help
 115           This driver supports the NS LM70 LLP Evaluation Board,
 116           which interfaces to an LM70 temperature sensor using
 117           a parallel port.
 118
 119 config SPI_MPC52xx_PSC
 120         tristate "Freescale MPC52xx PSC SPI controller"
 121         depends on PPC_MPC52xx && EXPERIMENTAL
 122         help
 123           This enables using the Freescale MPC52xx Programmable Serial
 124           Controller in master SPI mode.
 125
 126 config SPI_MPC83xx
 127         tristate "Freescale MPC83xx/QUICC Engine SPI controller"
 128         depends on (PPC_83xx || QUICC_ENGINE) && EXPERIMENTAL
 129         help
 130           This enables using the Freescale MPC83xx and QUICC Engine SPI
 131           controllers in master mode.
 132
 133           Note, this driver uniquely supports the SPI controller on the MPC83xx
 134           family of PowerPC processors, plus processors with QUICC Engine
 135           technology. This driver uses a simple set of shift registers for data
 136           (opposed to the CPM based descriptor model).
 137
 138 config SPI_OMAP_UWIRE
 139         tristate "OMAP1 MicroWire"
 140         depends on ARCH_OMAP1
 141         select SPI_BITBANG
 142         help
 143           This hooks up to the MicroWire controller on OMAP1 chips.
 144
 145 config SPI_OMAP24XX
 146         tristate "McSPI driver for OMAP24xx/OMAP34xx"
 147         depends on ARCH_OMAP24XX || ARCH_OMAP34XX
 148         help
 149           SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
 150           (McSPI) modules.
 151
 152 config SPI_PXA2XX
 153         tristate "PXA2xx SSP SPI master"
 154         depends on ARCH_PXA && EXPERIMENTAL
 155         select PXA_SSP
 156         help
 157           This enables using a PXA2xx SSP port as a SPI master controller.
 158           The driver can be configured to use any SSP port and additional
 159           documentation can be found a Documentation/spi/pxa2xx.
 160
 161 config SPI_S3C24XX
 162         tristate "Samsung S3C24XX series SPI"
 163         depends on ARCH_S3C2410 && EXPERIMENTAL
 164         select SPI_BITBANG
 165         help
 166           SPI driver for Samsung S3C24XX series ARM SoCs
 167
 168 config SPI_S3C24XX_GPIO
 169         tristate "Samsung S3C24XX series SPI by GPIO"
 170         depends on ARCH_S3C2410 && EXPERIMENTAL
 171         select SPI_BITBANG
 172         help
 173           SPI driver for Samsung S3C24XX series ARM SoCs using
 174           GPIO lines to provide the SPI bus. This can be used where
 175           the inbuilt hardware cannot provide the transfer mode, or
 176           where the board is using non hardware connected pins.
 177
 178 config SPI_SH_SCI
 179         tristate "SuperH SCI SPI controller"
 180         depends on SUPERH
 181         select SPI_BITBANG
 182         help
 183           SPI driver for SuperH SCI blocks.
 184
 185 config SPI_TXX9
 186         tristate "Toshiba TXx9 SPI controller"
 187         depends on GENERIC_GPIO && CPU_TX49XX
 188         help
 189           SPI driver for Toshiba TXx9 MIPS SoCs
 190
 191 config SPI_XILINX
 192         tristate "Xilinx SPI controller"
 193         depends on XILINX_VIRTEX && EXPERIMENTAL
 194         select SPI_BITBANG
 195         help
 196           This exposes the SPI controller IP from the Xilinx EDK.
 197
 198           See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
 199           Product Specification document (DS464) for hardware details.
 200
 201 #
 202 # Add new SPI master controllers in alphabetical order above this line
 203 #
 204
 205 #
 206 # There are lots of SPI device types, with sensors and memory
 207 # being probably the most widely used ones.
 208 #
 209 comment "SPI Protocol Masters"
 210
 211 config SPI_AT25
 212         tristate "SPI EEPROMs from most vendors"
 213         depends on SYSFS
 214         help
 215           Enable this driver to get read/write support to most SPI EEPROMs,
 216           after you configure the board init code to know about each eeprom
 217           on your target board.
 218
 219           This driver can also be built as a module.  If so, the module
 220           will be called at25.
 221
 222 config SPI_SPIDEV
 223         tristate "User mode SPI device driver support"
 224         depends on EXPERIMENTAL
 225         help
 226           This supports user mode SPI protocol drivers.
 227
 228           Note that this application programming interface is EXPERIMENTAL
 229           and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
 230
 231 config SPI_TLE62X0
 232         tristate "Infineon TLE62X0 (for power switching)"
 233         depends on SYSFS
 234         help
 235           SPI driver for Infineon TLE62X0 series line driver chips,
 236           such as the TLE6220, TLE6230 and TLE6240.  This provides a
 237           sysfs interface, with each line presented as a kind of GPIO
 238           exposing both switch control and diagnostic feedback.
 239
 240 #
 241 # Add new SPI protocol masters in alphabetical order above this line
 242 #
 243
 244 endif # SPI_MASTER
 245
 246 # (slave support would go here)
 247
 248 endif # SPI