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 "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
  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_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
 119 config SPI_IMX
 120         tristate "Freescale iMX SPI controller"
 121         depends on ARCH_MX1 && EXPERIMENTAL
 122         help
 123           This enables using the Freescale iMX SPI controller in master
 124           mode.
 125
 126 config SPI_LM70_LLP
 127         tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
 128         depends on PARPORT && EXPERIMENTAL
 129         select SPI_BITBANG
 130         help
 131           This driver supports the NS LM70 LLP Evaluation Board,
 132           which interfaces to an LM70 temperature sensor using
 133           a parallel port.
 134
 135 config SPI_MPC52xx_PSC
 136         tristate "Freescale MPC52xx PSC SPI controller"
 137         depends on PPC_MPC52xx && EXPERIMENTAL
 138         help
 139           This enables using the Freescale MPC52xx Programmable Serial
 140           Controller in master SPI mode.
 141
 142 config SPI_MPC8xxx
 143         tristate "Freescale MPC8xxx SPI controller"
 144         depends on FSL_SOC
 145         help
 146           This enables using the Freescale MPC8xxx SPI controllers in master
 147           mode.
 148
 149           This driver uses a simple set of shift registers for data (opposed
 150           to the CPM based descriptor model).
 151
 152 config SPI_OMAP_UWIRE
 153         tristate "OMAP1 MicroWire"
 154         depends on ARCH_OMAP1
 155         select SPI_BITBANG
 156         help
 157           This hooks up to the MicroWire controller on OMAP1 chips.
 158
 159 config SPI_OMAP24XX
 160         tristate "McSPI driver for OMAP24xx/OMAP34xx"
 161         depends on ARCH_OMAP24XX || ARCH_OMAP34XX
 162         help
 163           SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
 164           (McSPI) modules.
 165
 166 config SPI_ORION
 167         tristate "Orion SPI master (EXPERIMENTAL)"
 168         depends on PLAT_ORION && EXPERIMENTAL
 169         help
 170           This enables using the SPI master controller on the Orion chips.
 171
 172 config SPI_PL022
 173         tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
 174         depends on ARM_AMBA && EXPERIMENTAL
 175         default y if MACH_U300
 176         help
 177           This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
 178           controller. If you have an embedded system with an AMBA(R)
 179           bus and a PL022 controller, say Y or M here.
 180
 181 config SPI_PXA2XX
 182         tristate "PXA2xx SSP SPI master"
 183         depends on ARCH_PXA && EXPERIMENTAL
 184         select PXA_SSP
 185         help
 186           This enables using a PXA2xx SSP port as a SPI master controller.
 187           The driver can be configured to use any SSP port and additional
 188           documentation can be found a Documentation/spi/pxa2xx.
 189
 190 config SPI_S3C24XX
 191         tristate "Samsung S3C24XX series SPI"
 192         depends on ARCH_S3C2410 && EXPERIMENTAL
 193         select SPI_BITBANG
 194         help
 195           SPI driver for Samsung S3C24XX series ARM SoCs
 196
 197 config SPI_S3C24XX_GPIO
 198         tristate "Samsung S3C24XX series SPI by GPIO"
 199         depends on ARCH_S3C2410 && EXPERIMENTAL
 200         select SPI_BITBANG
 201         help
 202           SPI driver for Samsung S3C24XX series ARM SoCs using
 203           GPIO lines to provide the SPI bus. This can be used where
 204           the inbuilt hardware cannot provide the transfer mode, or
 205           where the board is using non hardware connected pins.
 206
 207 config SPI_SH_SCI
 208         tristate "SuperH SCI SPI controller"
 209         depends on SUPERH
 210         select SPI_BITBANG
 211         help
 212           SPI driver for SuperH SCI blocks.
 213
 214 config SPI_TXX9
 215         tristate "Toshiba TXx9 SPI controller"
 216         depends on GENERIC_GPIO && CPU_TX49XX
 217         help
 218           SPI driver for Toshiba TXx9 MIPS SoCs
 219
 220 config SPI_XILINX
 221         tristate "Xilinx SPI controller"
 222         depends on (XILINX_VIRTEX || MICROBLAZE) && EXPERIMENTAL
 223         select SPI_BITBANG
 224         help
 225           This exposes the SPI controller IP from the Xilinx EDK.
 226
 227           See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
 228           Product Specification document (DS464) for hardware details.
 229
 230 #
 231 # Add new SPI master controllers in alphabetical order above this line
 232 #
 233
 234 #
 235 # There are lots of SPI device types, with sensors and memory
 236 # being probably the most widely used ones.
 237 #
 238 comment "SPI Protocol Masters"
 239
 240 config SPI_SPIDEV
 241         tristate "User mode SPI device driver support"
 242         depends on EXPERIMENTAL
 243         help
 244           This supports user mode SPI protocol drivers.
 245
 246           Note that this application programming interface is EXPERIMENTAL
 247           and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
 248
 249 config SPI_TLE62X0
 250         tristate "Infineon TLE62X0 (for power switching)"
 251         depends on SYSFS
 252         help
 253           SPI driver for Infineon TLE62X0 series line driver chips,
 254           such as the TLE6220, TLE6230 and TLE6240.  This provides a
 255           sysfs interface, with each line presented as a kind of GPIO
 256           exposing both switch control and diagnostic feedback.
 257
 258 #
 259 # Add new SPI protocol masters in alphabetical order above this line
 260 #
 261
 262 endif # SPI_MASTER
 263
 264 # (slave support would go here)
 265
 266 endif # SPI