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