2# SPI driver configuration
   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.
   8menuconfig 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.
  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.
  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.
  29if SPI
  31config 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.
  39# MASTER side ... talking to discrete SPI slave chips including microcontrollers
  42config 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.
  54comment "SPI Master Controller Drivers"
  56config SPI_ALTERA
  57        tristate "Altera SPI Controller"
  58        select SPI_BITBANG
  59        help
  60          This is the driver for the Altera SPI Controller.
  62config SPI_ATH79
  63        tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
  64        depends on ATH79 && GENERIC_GPIO
  65        select SPI_BITBANG
  66        help
  67          This enables support for the SPI controller present on the
  68          Atheros AR71XX/AR724X/AR913X SoCs.
  70config SPI_ATMEL
  71        tristate "Atmel SPI Controller"
  72        depends on (ARCH_AT91 || AVR32)
  73        help
  74          This selects a driver for the Atmel SPI Controller, present on
  75          many AT32 (AVR32) and AT91 (ARM) chips.
  77config SPI_BFIN5XX
  78        tristate "SPI controller driver for ADI Blackfin5xx"
  79        depends on BLACKFIN
  80        help
  81          This is the SPI controller master driver for Blackfin 5xx processor.
  83config SPI_BFIN_SPORT
  84        tristate "SPI bus via Blackfin SPORT"
  85        depends on BLACKFIN
  86        help
  87          Enable support for a SPI bus via the Blackfin SPORT peripheral.
  89config SPI_AU1550
  90        tristate "Au1550/Au1200/Au1300 SPI Controller"
  91        depends on MIPS_ALCHEMY && EXPERIMENTAL
  92        select SPI_BITBANG
  93        help
  94          If you say yes to this option, support will be included for the
  95          PSC SPI controller found on Au1550, Au1200 and Au1300 series.
  97config SPI_BCM63XX
  98        tristate "Broadcom BCM63xx SPI controller"
  99        depends on BCM63XX
 100        help
 101          Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
 103config SPI_BITBANG
 104        tristate "Utilities for Bitbanging SPI masters"
 105        help
 106          With a few GPIO pins, your system can bitbang the SPI protocol.
 107          Select this to get SPI support through I/O pins (GPIO, parallel
 108          port, etc).  Or, some systems' SPI master controller drivers use
 109          this code to manage the per-word or per-transfer accesses to the
 110          hardware shift registers.
 112          This is library code, and is automatically selected by drivers that
 113          need it.  You only need to select this explicitly to support driver
 114          modules that aren't part of this kernel tree.
 116config SPI_BUTTERFLY
 117        tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
 118        depends on PARPORT
 119        select SPI_BITBANG
 120        help
 121          This uses a custom parallel port cable to connect to an AVR
 122          Butterfly <>, an
 123          inexpensive battery powered microcontroller evaluation board.
 124          This same cable can be used to flash new firmware.
 127        tristate "Freescale Coldfire QSPI controller"
 128        depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
 129        help
 130          This enables support for the Coldfire QSPI controller in master
 131          mode.
 133config SPI_DAVINCI
 134        tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
 135        depends on ARCH_DAVINCI
 136        select SPI_BITBANG
 137        help
 138          SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
 140config SPI_EP93XX
 141        tristate "Cirrus Logic EP93xx SPI controller"
 142        depends on ARCH_EP93XX
 143        help
 144          This enables using the Cirrus EP93xx SPI controller in master
 145          mode.
 147config SPI_FALCON
 148        tristate "Falcon SPI controller support"
 149        depends on SOC_FALCON
 150        help
 151          The external bus unit (EBU) found on the FALC-ON SoC has SPI
 152          emulation that is designed for serial flash access. This driver
 153          has only been tested with m25p80 type chips. The hardware has no
 154          support for other types of SPI peripherals.
 156config SPI_GPIO
 157        tristate "GPIO-based bitbanging SPI Master"
 158        depends on GENERIC_GPIO
 159        select SPI_BITBANG
 160        help
 161          This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
 162          interface to manage MOSI, MISO, SCK, and chipselect signals.  SPI
 163          slaves connected to a bus using this driver are configured as usual,
 164          except that the spi_board_info.controller_data holds the GPIO number
 165          for the chipselect used by this controller driver.
 167          Note that this driver often won't achieve even 1 Mbit/sec speeds,
 168          making it unusually slow for SPI.  If your platform can inline
 169          GPIO operations, you should be able to leverage that for better
 170          speed with a custom version of this driver; see the source code.
 172config SPI_IMX
 173        tristate "Freescale i.MX SPI controllers"
 174        depends on ARCH_MXC
 175        select SPI_BITBANG
 176        default m if IMX_HAVE_PLATFORM_SPI_IMX
 177        help
 178          This enables using the Freescale i.MX SPI controllers in master
 179          mode.
 181config SPI_LM70_LLP
 182        tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
 183        depends on PARPORT && EXPERIMENTAL
 184        select SPI_BITBANG
 185        help
 186          This driver supports the NS LM70 LLP Evaluation Board,
 187          which interfaces to an LM70 temperature sensor using
 188          a parallel port.
 190config SPI_MPC52xx
 191        tristate "Freescale MPC52xx SPI (non-PSC) controller support"
 192        depends on PPC_MPC52xx
 193        help
 194          This drivers supports the MPC52xx SPI controller in master SPI
 195          mode.
 197config SPI_MPC52xx_PSC
 198        tristate "Freescale MPC52xx PSC SPI controller"
 199        depends on PPC_MPC52xx && EXPERIMENTAL
 200        help
 201          This enables using the Freescale MPC52xx Programmable Serial
 202          Controller in master SPI mode.
 204config SPI_MPC512x_PSC
 205        tristate "Freescale MPC512x PSC SPI controller"
 206        depends on PPC_MPC512x
 207        help
 208          This enables using the Freescale MPC5121 Programmable Serial
 209          Controller in SPI master mode.
 211config SPI_FSL_LIB
 212        tristate
 213        depends on FSL_SOC
 215config SPI_FSL_SPI
 216        bool "Freescale SPI controller"
 217        depends on FSL_SOC
 218        select SPI_FSL_LIB
 219        help
 220          This enables using the Freescale SPI controllers in master mode.
 221          MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
 222          MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
 224config SPI_FSL_ESPI
 225        bool "Freescale eSPI controller"
 226        depends on FSL_SOC
 227        select SPI_FSL_LIB
 228        help
 229          This enables using the Freescale eSPI controllers in master mode.
 230          From MPC8536, 85xx platform uses the controller, and all P10xx,
 231          P20xx, P30xx,P40xx, P50xx uses this controller.
 233config SPI_OC_TINY
 234        tristate "OpenCores tiny SPI"
 235        depends on GENERIC_GPIO
 236        select SPI_BITBANG
 237        help
 238          This is the driver for OpenCores tiny SPI master controller.
 240config SPI_OMAP_UWIRE
 241        tristate "OMAP1 MicroWire"
 242        depends on ARCH_OMAP1
 243        select SPI_BITBANG
 244        help
 245          This hooks up to the MicroWire controller on OMAP1 chips.
 247config SPI_OMAP24XX
 248        tristate "McSPI driver for OMAP"
 249        depends on ARCH_OMAP2PLUS
 250        help
 251          SPI master controller for OMAP24XX and later Multichannel SPI
 252          (McSPI) modules.
 254config SPI_OMAP_100K
 255        tristate "OMAP SPI 100K"
 256        depends on ARCH_OMAP850 || ARCH_OMAP730
 257        help
 258          OMAP SPI 100K master controller for omap7xx boards.
 260config SPI_ORION
 261        tristate "Orion SPI master (EXPERIMENTAL)"
 262        depends on PLAT_ORION && EXPERIMENTAL
 263        help
 264          This enables using the SPI master controller on the Orion chips.
 266config SPI_PL022
 267        tristate "ARM AMBA PL022 SSP controller"
 268        depends on ARM_AMBA
 269        default y if MACH_U300
 270        default y if ARCH_REALVIEW
 271        default y if INTEGRATOR_IMPD1
 272        default y if ARCH_VERSATILE
 273        help
 274          This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
 275          controller. If you have an embedded system with an AMBA(R)
 276          bus and a PL022 controller, say Y or M here.
 278config SPI_PPC4xx
 279        tristate "PPC4xx SPI Controller"
 280        depends on PPC32 && 4xx
 281        select SPI_BITBANG
 282        help
 283          This selects a driver for the PPC4xx SPI Controller.
 285config SPI_PXA2XX
 286        tristate "PXA2xx SSP SPI master"
 287        depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
 288        select PXA_SSP if ARCH_PXA
 289        help
 290          This enables using a PXA2xx or Sodaville SSP port as a SPI master
 291          controller. The driver can be configured to use any SSP port and
 292          additional documentation can be found a Documentation/spi/pxa2xx.
 294config SPI_PXA2XX_PCI
 295        def_bool SPI_PXA2XX && X86_32 && PCI
 297config SPI_RSPI
 298        tristate "Renesas RSPI controller"
 299        depends on SUPERH
 300        help
 301          SPI driver for Renesas RSPI blocks.
 303config SPI_S3C24XX
 304        tristate "Samsung S3C24XX series SPI"
 305        depends on ARCH_S3C24XX && EXPERIMENTAL
 306        select SPI_BITBANG
 307        help
 308          SPI driver for Samsung S3C24XX series ARM SoCs
 310config SPI_S3C24XX_FIQ
 311        bool "S3C24XX driver with FIQ pseudo-DMA"
 312        depends on SPI_S3C24XX
 313        select FIQ
 314        help
 315          Enable FIQ support for the S3C24XX SPI driver to provide pseudo
 316          DMA by using the fast-interrupt request framework, This allows
 317          the driver to get DMA-like performance when there are either
 318          no free DMA channels, or when doing transfers that required both
 319          TX and RX data paths.
 321config SPI_S3C64XX
 322        tristate "Samsung S3C64XX series type SPI"
 323        depends on (ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5P64X0 || ARCH_EXYNOS)
 324        select S3C64XX_DMA if ARCH_S3C64XX
 325        help
 326          SPI driver for Samsung S3C64XX and newer SoCs.
 328config SPI_SH_MSIOF
 329        tristate "SuperH MSIOF SPI controller"
 330        depends on SUPERH && HAVE_CLK
 331        select SPI_BITBANG
 332        help
 333          SPI driver for SuperH MSIOF blocks.
 335config SPI_SH
 336        tristate "SuperH SPI controller"
 337        depends on SUPERH
 338        help
 339          SPI driver for SuperH SPI blocks.
 341config SPI_SH_SCI
 342        tristate "SuperH SCI SPI controller"
 343        depends on SUPERH
 344        select SPI_BITBANG
 345        help
 346          SPI driver for SuperH SCI blocks.
 348config SPI_SH_HSPI
 349        tristate "SuperH HSPI controller"
 350        depends on ARCH_SHMOBILE
 351        help
 352          SPI driver for SuperH HSPI blocks.
 354config SPI_SIRF
 355        tristate "CSR SiRFprimaII SPI controller"
 356        depends on ARCH_PRIMA2
 357        select SPI_BITBANG
 358        help
 359          SPI driver for CSR SiRFprimaII SoCs
 361config SPI_STMP3XXX
 362        tristate "Freescale STMP37xx/378x SPI/SSP controller"
 363        depends on ARCH_STMP3XXX
 364        help
 365          SPI driver for Freescale STMP37xx/378x SoC SSP interface
 367config SPI_TEGRA
 368        tristate "Nvidia Tegra SPI controller"
 369        depends on ARCH_TEGRA && (TEGRA_SYSTEM_DMA || TEGRA20_APB_DMA)
 370        help
 371          SPI driver for NVidia Tegra SoCs
 373config SPI_TI_SSP
 374        tristate "TI Sequencer Serial Port - SPI Support"
 375        depends on MFD_TI_SSP
 376        help
 377          This selects an SPI master implementation using a TI sequencer
 378          serial port.
 381        tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
 382        depends on PCI
 383        help
 384          SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
 385          used in some x86 embedded processors.
 387          This driver also supports the ML7213/ML7223/ML7831, a companion chip
 388          for the Atom E6xx series and compatible with the Intel EG20T PCH.
 390config SPI_TXX9
 391        tristate "Toshiba TXx9 SPI controller"
 392        depends on GENERIC_GPIO && CPU_TX49XX
 393        help
 394          SPI driver for Toshiba TXx9 MIPS SoCs
 396config SPI_XCOMM
 397        tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
 398        depends on I2C
 399        help
 400          Support for the SPI-I2C bridge found on the Analog Devices
 401          AD-FMCOMMS1-EBZ board.
 403config SPI_XILINX
 404        tristate "Xilinx SPI controller common module"
 405        depends on HAS_IOMEM && EXPERIMENTAL
 406        select SPI_BITBANG
 407        help
 408          This exposes the SPI controller IP from the Xilinx EDK.
 410          See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
 411          Product Specification document (DS464) for hardware details.
 413          Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
 415config SPI_NUC900
 416        tristate "Nuvoton NUC900 series SPI"
 417        depends on ARCH_W90X900 && EXPERIMENTAL
 418        select SPI_BITBANG
 419        help
 420          SPI driver for Nuvoton NUC900 series ARM SoCs
 423# Add new SPI master controllers in alphabetical order above this line
 427        tristate "DesignWare SPI controller core support"
 428        help
 429          general driver for SPI controller core from DesignWare
 431config SPI_DW_PCI
 432        tristate "PCI interface driver for DW SPI core"
 433        depends on SPI_DESIGNWARE && PCI
 435config SPI_DW_MID_DMA
 436        bool "DMA support for DW SPI controller on Intel Moorestown platform"
 437        depends on SPI_DW_PCI && INTEL_MID_DMAC
 439config SPI_DW_MMIO
 440        tristate "Memory-mapped io interface driver for DW SPI core"
 441        depends on SPI_DESIGNWARE && HAVE_CLK
 444# There are lots of SPI device types, with sensors and memory
 445# being probably the most widely used ones.
 447comment "SPI Protocol Masters"
 449config SPI_SPIDEV
 450        tristate "User mode SPI device driver support"
 451        depends on EXPERIMENTAL
 452        help
 453          This supports user mode SPI protocol drivers.
 455          Note that this application programming interface is EXPERIMENTAL
 456          and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
 458config SPI_TLE62X0
 459        tristate "Infineon TLE62X0 (for power switching)"
 460        depends on SYSFS
 461        help
 462          SPI driver for Infineon TLE62X0 series line driver chips,
 463          such as the TLE6220, TLE6230 and TLE6240.  This provides a
 464          sysfs interface, with each line presented as a kind of GPIO
 465          exposing both switch control and diagnostic feedback.
 468# Add new SPI protocol masters in alphabetical order above this line
 471endif # SPI_MASTER
 473# (slave support would go here)
 475endif # SPI
 476 kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.