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_COLDFIRE_QSPI
 104         tristate "Freescale Coldfire QSPI controller"
 105         depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
 106         help
 107           This enables support for the Coldfire QSPI controller in master
 108           mode.
 109
 110           This driver can also be built as a module.  If so, the module
 111           will be called coldfire_qspi.
 112
 113 config SPI_DAVINCI
 114         tristate "SPI controller driver for DaVinci/DA8xx SoC's"
 115         depends on SPI_MASTER && ARCH_DAVINCI
 116         select SPI_BITBANG
 117         help
 118           SPI master controller for DaVinci and DA8xx SPI modules.
 119
 120 config SPI_GPIO
 121         tristate "GPIO-based bitbanging SPI Master"
 122         depends on GENERIC_GPIO
 123         select SPI_BITBANG
 124         help
 125           This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
 126           interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
 127           slaves connected to a bus using this driver are configured as usual,
 128           except that the spi_board_info.controller_data holds the GPIO number
 129           for the chipselect used by this controller driver.
 130
 131           Note that this driver often won't achieve even 1 Mbit/sec speeds,
 132           making it unusually slow for SPI.  If your platform can inline
 133           GPIO operations, you should be able to leverage that for better
 134           speed with a custom version of this driver; see the source code.
 135
 136 config SPI_IMX
 137         tristate "Freescale i.MX SPI controllers"
 138         depends on ARCH_MXC
 139         select SPI_BITBANG
 140         help
 141           This enables using the Freescale i.MX SPI controllers in master
 142           mode.
 143
 144 config SPI_LM70_LLP
 145         tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
 146         depends on PARPORT && EXPERIMENTAL
 147         select SPI_BITBANG
 148         help
 149           This driver supports the NS LM70 LLP Evaluation Board,
 150           which interfaces to an LM70 temperature sensor using
 151           a parallel port.
 152
 153 config SPI_MPC52xx
 154         tristate "Freescale MPC52xx SPI (non-PSC) controller support"
 155         depends on PPC_MPC52xx && SPI
 156         select SPI_MASTER_OF
 157         help
 158           This drivers supports the MPC52xx SPI controller in master SPI
 159           mode.
 160
 161 config SPI_MPC52xx_PSC
 162         tristate "Freescale MPC52xx PSC SPI controller"
 163         depends on PPC_MPC52xx && EXPERIMENTAL
 164         help
 165           This enables using the Freescale MPC52xx Programmable Serial
 166           Controller in master SPI mode.
 167
 168 config SPI_MPC8xxx
 169         tristate "Freescale MPC8xxx SPI controller"
 170         depends on FSL_SOC
 171         help
 172           This enables using the Freescale MPC8xxx SPI controllers in master
 173           mode.
 174
 175 config SPI_OMAP_UWIRE
 176         tristate "OMAP1 MicroWire"
 177         depends on ARCH_OMAP1
 178         select SPI_BITBANG
 179         help
 180           This hooks up to the MicroWire controller on OMAP1 chips.
 181
 182 config SPI_OMAP24XX
 183         tristate "McSPI driver for OMAP24xx/OMAP34xx"
 184         depends on ARCH_OMAP24XX || ARCH_OMAP34XX
 185         help
 186           SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
 187           (McSPI) modules.
 188
 189 config SPI_OMAP_100K
 190         tristate "OMAP SPI 100K"
 191         depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
 192         help
 193           OMAP SPI 100K master controller for omap7xx boards.
 194
 195 config SPI_ORION
 196         tristate "Orion SPI master (EXPERIMENTAL)"
 197         depends on PLAT_ORION && EXPERIMENTAL
 198         help
 199           This enables using the SPI master controller on the Orion chips.
 200
 201 config SPI_PL022
 202         tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
 203         depends on ARM_AMBA && EXPERIMENTAL
 204         default y if MACH_U300
 205         default y if ARCH_REALVIEW
 206         default y if INTEGRATOR_IMPD1
 207         default y if ARCH_VERSATILE
 208         help
 209           This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
 210           controller. If you have an embedded system with an AMBA(R)
 211           bus and a PL022 controller, say Y or M here.
 212
 213 config SPI_PPC4xx
 214         tristate "PPC4xx SPI Controller"
 215         depends on PPC32 && 4xx && SPI_MASTER
 216         select SPI_BITBANG
 217         help
 218           This selects a driver for the PPC4xx SPI Controller.
 219
 220 config SPI_PXA2XX
 221         tristate "PXA2xx SSP SPI master"
 222         depends on ARCH_PXA && EXPERIMENTAL
 223         select PXA_SSP
 224         help
 225           This enables using a PXA2xx SSP port as a SPI master controller.
 226           The driver can be configured to use any SSP port and additional
 227           documentation can be found a Documentation/spi/pxa2xx.
 228
 229 config SPI_S3C24XX
 230         tristate "Samsung S3C24XX series SPI"
 231         depends on ARCH_S3C2410 && EXPERIMENTAL
 232         select SPI_BITBANG
 233         help
 234           SPI driver for Samsung S3C24XX series ARM SoCs
 235
 236 config SPI_S3C24XX_FIQ
 237         bool "S3C24XX driver with FIQ pseudo-DMA"
 238         depends on SPI_S3C24XX
 239         select FIQ
 240         help
 241           Enable FIQ support for the S3C24XX SPI driver to provide pseudo
 242           DMA by using the fast-interrupt request framework, This allows
 243           the driver to get DMA-like performance when there are either
 244           no free DMA channels, or when doing transfers that required both
 245           TX and RX data paths.
 246
 247 config SPI_S3C24XX_GPIO
 248         tristate "Samsung S3C24XX series SPI by GPIO"
 249         depends on ARCH_S3C2410 && EXPERIMENTAL
 250         select SPI_BITBANG
 251         help
 252           SPI driver for Samsung S3C24XX series ARM SoCs using
 253           GPIO lines to provide the SPI bus. This can be used where
 254           the inbuilt hardware cannot provide the transfer mode, or
 255           where the board is using non hardware connected pins.
 256
 257 config SPI_S3C64XX
 258         tristate "Samsung S3C64XX series type SPI"
 259         depends on ARCH_S3C64XX && EXPERIMENTAL
 260         select S3C64XX_DMA
 261         help
 262           SPI driver for Samsung S3C64XX and newer SoCs.
 263
 264 config SPI_SH_MSIOF
 265         tristate "SuperH MSIOF SPI controller"
 266         depends on SUPERH && HAVE_CLK
 267         select SPI_BITBANG
 268         help
 269           SPI driver for SuperH MSIOF blocks.
 270
 271 config SPI_SH_SCI
 272         tristate "SuperH SCI SPI controller"
 273         depends on SUPERH
 274         select SPI_BITBANG
 275         help
 276           SPI driver for SuperH SCI blocks.
 277
 278 config SPI_STMP3XXX
 279         tristate "Freescale STMP37xx/378x SPI/SSP controller"
 280         depends on ARCH_STMP3XXX && SPI_MASTER
 281         help
 282           SPI driver for Freescale STMP37xx/378x SoC SSP interface
 283
 284 config SPI_TXX9
 285         tristate "Toshiba TXx9 SPI controller"
 286         depends on GENERIC_GPIO && CPU_TX49XX
 287         help
 288           SPI driver for Toshiba TXx9 MIPS SoCs
 289
 290 config SPI_XILINX
 291         tristate "Xilinx SPI controller common module"
 292         depends on HAS_IOMEM && EXPERIMENTAL
 293         select SPI_BITBANG
 294         select SPI_XILINX_OF if (XILINX_VIRTEX || MICROBLAZE)
 295         help
 296           This exposes the SPI controller IP from the Xilinx EDK.
 297
 298           See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
 299           Product Specification document (DS464) for hardware details.
 300
 301           Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
 302
 303 config SPI_XILINX_OF
 304         tristate "Xilinx SPI controller OF device"
 305         depends on SPI_XILINX && (XILINX_VIRTEX || MICROBLAZE)
 306         help
 307           This is the OF driver for the SPI controller IP from the Xilinx EDK.
 308
 309 config SPI_XILINX_PLTFM
 310         tristate "Xilinx SPI controller platform device"
 311         depends on SPI_XILINX
 312         help
 313           This is the platform driver for the SPI controller IP
 314           from the Xilinx EDK.
 315
 316 config SPI_NUC900
 317         tristate "Nuvoton NUC900 series SPI"
 318         depends on ARCH_W90X900 && EXPERIMENTAL
 319         select SPI_BITBANG
 320         help
 321           SPI driver for Nuvoton NUC900 series ARM SoCs
 322
 323 #
 324 # Add new SPI master controllers in alphabetical order above this line
 325 #
 326
 327 config SPI_DESIGNWARE
 328         bool "DesignWare SPI controller core support"
 329         depends on SPI_MASTER
 330         help
 331           general driver for SPI controller core from DesignWare
 332
 333 config SPI_DW_PCI
 334         tristate "PCI interface driver for DW SPI core"
 335         depends on SPI_DESIGNWARE && PCI
 336
 337 #
 338 # There are lots of SPI device types, with sensors and memory
 339 # being probably the most widely used ones.
 340 #
 341 comment "SPI Protocol Masters"
 342
 343 config SPI_SPIDEV
 344         tristate "User mode SPI device driver support"
 345         depends on EXPERIMENTAL
 346         help
 347           This supports user mode SPI protocol drivers.
 348
 349           Note that this application programming interface is EXPERIMENTAL
 350           and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
 351
 352 config SPI_TLE62X0
 353         tristate "Infineon TLE62X0 (for power switching)"
 354         depends on SYSFS
 355         help
 356           SPI driver for Infineon TLE62X0 series line driver chips,
 357           such as the TLE6220, TLE6230 and TLE6240.  This provides a
 358           sysfs interface, with each line presented as a kind of GPIO
 359           exposing both switch control and diagnostic feedback.
 360
 361 #
 362 # Add new SPI protocol masters in alphabetical order above this line
 363 #
 364
 365 endif # SPI_MASTER
 366
 367 # (slave support would go here)
 368
 369 endif # SPI