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