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# 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. 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 29if SPI 30 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. 37 38# 39# MASTER side ... talking to discrete SPI slave chips including microcontrollers 40# 41 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. 51 52if SPI_MASTER 53 54comment "SPI Master Controller Drivers" 55 56config SPI_ALTERA 57 tristate "Altera SPI Controller" 58 select SPI_BITBANG 59 help 60 This is the driver for the Altera SPI Controller. 61 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. 69 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. 76 77config SPI_BFIN 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. 82 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. 88 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. 96 97config SPI_BITBANG 98 tristate "Utilities for Bitbanging SPI masters" 99 help 100 With a few GPIO pins, your system can bitbang the SPI protocol. 101 Select this to get SPI support through I/O pins (GPIO, parallel 102 port, etc). Or, some systems' SPI master controller drivers use 103 this code to manage the per-word or per-transfer accesses to the 104 hardware shift registers. 105 106 This is library code, and is automatically selected by drivers that 107 need it. You only need to select this explicitly to support driver 108 modules that aren't part of this kernel tree. 109 110config SPI_BUTTERFLY 111 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" 112 depends on PARPORT 113 select SPI_BITBANG 114 help 115 This uses a custom parallel port cable to connect to an AVR 116 Butterfly <http://www.atmel.com/products/avr/butterfly>, an 117 inexpensive battery powered microcontroller evaluation board. 118 This same cable can be used to flash new firmware. 119 120config SPI_COLDFIRE_QSPI 121 tristate "Freescale Coldfire QSPI controller" 122 depends on (M520x || M523x || M5249 || M527x || M528x || M532x) 123 help 124 This enables support for the Coldfire QSPI controller in master 125 mode. 126 127config SPI_DAVINCI 128 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller" 129 depends on SPI_MASTER && ARCH_DAVINCI 130 select SPI_BITBANG 131 help 132 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules. 133 134config SPI_EP93XX 135 tristate "Cirrus Logic EP93xx SPI controller" 136 depends on ARCH_EP93XX 137 help 138 This enables using the Cirrus EP93xx SPI controller in master 139 mode. 140 141config SPI_GPIO 142 tristate "GPIO-based bitbanging SPI Master" 143 depends on GENERIC_GPIO 144 select SPI_BITBANG 145 help 146 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO 147 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI 148 slaves connected to a bus using this driver are configured as usual, 149 except that the spi_board_info.controller_data holds the GPIO number 150 for the chipselect used by this controller driver. 151 152 Note that this driver often won't achieve even 1 Mbit/sec speeds, 153 making it unusually slow for SPI. If your platform can inline 154 GPIO operations, you should be able to leverage that for better 155 speed with a custom version of this driver; see the source code. 156 157config SPI_IMX 158 tristate "Freescale i.MX SPI controllers" 159 depends on ARCH_MXC 160 select SPI_BITBANG 161 default m if IMX_HAVE_PLATFORM_SPI_IMX 162 help 163 This enables using the Freescale i.MX SPI controllers in master 164 mode. 165 166config SPI_LM70_LLP 167 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 168 depends on PARPORT && EXPERIMENTAL 169 select SPI_BITBANG 170 help 171 This driver supports the NS LM70 LLP Evaluation Board, 172 which interfaces to an LM70 temperature sensor using 173 a parallel port. 174 175config SPI_MPC52xx 176 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 177 depends on PPC_MPC52xx 178 help 179 This drivers supports the MPC52xx SPI controller in master SPI 180 mode. 181 182config SPI_MPC52xx_PSC 183 tristate "Freescale MPC52xx PSC SPI controller" 184 depends on PPC_MPC52xx && EXPERIMENTAL 185 help 186 This enables using the Freescale MPC52xx Programmable Serial 187 Controller in master SPI mode. 188 189config SPI_MPC512x_PSC 190 tristate "Freescale MPC512x PSC SPI controller" 191 depends on SPI_MASTER && PPC_MPC512x 192 help 193 This enables using the Freescale MPC5121 Programmable Serial 194 Controller in SPI master mode. 195 196config SPI_FSL_LIB 197 tristate 198 depends on FSL_SOC 199 200config SPI_FSL_SPI 201 bool "Freescale SPI controller" 202 depends on FSL_SOC 203 select SPI_FSL_LIB 204 help 205 This enables using the Freescale SPI controllers in master mode. 206 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 207 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 208 209config SPI_FSL_ESPI 210 bool "Freescale eSPI controller" 211 depends on FSL_SOC 212 select SPI_FSL_LIB 213 help 214 This enables using the Freescale eSPI controllers in master mode. 215 From MPC8536, 85xx platform uses the controller, and all P10xx, 216 P20xx, P30xx,P40xx, P50xx uses this controller. 217 218config SPI_OC_TINY 219 tristate "OpenCores tiny SPI" 220 depends on GENERIC_GPIO 221 select SPI_BITBANG 222 help 223 This is the driver for OpenCores tiny SPI master controller. 224 225config SPI_OMAP_UWIRE 226 tristate "OMAP1 MicroWire" 227 depends on ARCH_OMAP1 228 select SPI_BITBANG 229 help 230 This hooks up to the MicroWire controller on OMAP1 chips. 231 232config SPI_OMAP24XX 233 tristate "McSPI driver for OMAP" 234 depends on ARCH_OMAP2PLUS 235 help 236 SPI master controller for OMAP24XX and later Multichannel SPI 237 (McSPI) modules. 238 239config SPI_OMAP_100K 240 tristate "OMAP SPI 100K" 241 depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730) 242 help 243 OMAP SPI 100K master controller for omap7xx boards. 244 245config SPI_ORION 246 tristate "Orion SPI master (EXPERIMENTAL)" 247 depends on PLAT_ORION && EXPERIMENTAL 248 help 249 This enables using the SPI master controller on the Orion chips. 250 251config SPI_PL022 252 tristate "ARM AMBA PL022 SSP controller" 253 depends on ARM_AMBA 254 default y if MACH_U300 255 default y if ARCH_REALVIEW 256 default y if INTEGRATOR_IMPD1 257 default y if ARCH_VERSATILE 258 help 259 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 260 controller. If you have an embedded system with an AMBA(R) 261 bus and a PL022 controller, say Y or M here. 262 263config SPI_PPC4xx 264 tristate "PPC4xx SPI Controller" 265 depends on PPC32 && 4xx && SPI_MASTER 266 select SPI_BITBANG 267 help 268 This selects a driver for the PPC4xx SPI Controller. 269 270config SPI_PXA2XX 271 tristate "PXA2xx SSP SPI master" 272 depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL 273 select PXA_SSP if ARCH_PXA 274 help 275 This enables using a PXA2xx or Sodaville SSP port as a SPI master 276 controller. The driver can be configured to use any SSP port and 277 additional documentation can be found a Documentation/spi/pxa2xx. 278 279config SPI_PXA2XX_PCI 280 def_bool SPI_PXA2XX && X86_32 && PCI 281 282config SPI_S3C24XX 283 tristate "Samsung S3C24XX series SPI" 284 depends on ARCH_S3C2410 && EXPERIMENTAL 285 select SPI_BITBANG 286 help 287 SPI driver for Samsung S3C24XX series ARM SoCs 288 289config SPI_S3C24XX_FIQ 290 bool "S3C24XX driver with FIQ pseudo-DMA" 291 depends on SPI_S3C24XX 292 select FIQ 293 help 294 Enable FIQ support for the S3C24XX SPI driver to provide pseudo 295 DMA by using the fast-interrupt request framework, This allows 296 the driver to get DMA-like performance when there are either 297 no free DMA channels, or when doing transfers that required both 298 TX and RX data paths. 299 300config SPI_S3C64XX 301 tristate "Samsung S3C64XX series type SPI" 302 depends on (ARCH_S3C64XX || ARCH_S5P64X0) 303 select S3C64XX_DMA if ARCH_S3C64XX 304 help 305 SPI driver for Samsung S3C64XX and newer SoCs. 306 307config SPI_SH_MSIOF 308 tristate "SuperH MSIOF SPI controller" 309 depends on SUPERH && HAVE_CLK 310 select SPI_BITBANG 311 help 312 SPI driver for SuperH MSIOF blocks. 313 314config SPI_SH 315 tristate "SuperH SPI controller" 316 depends on SUPERH 317 help 318 SPI driver for SuperH SPI blocks. 319 320config SPI_SH_SCI 321 tristate "SuperH SCI SPI controller" 322 depends on SUPERH 323 select SPI_BITBANG 324 help 325 SPI driver for SuperH SCI blocks. 326 327config SPI_STMP3XXX 328 tristate "Freescale STMP37xx/378x SPI/SSP controller" 329 depends on ARCH_STMP3XXX && SPI_MASTER 330 help 331 SPI driver for Freescale STMP37xx/378x SoC SSP interface 332 333config SPI_TEGRA 334 tristate "Nvidia Tegra SPI controller" 335 depends on ARCH_TEGRA && TEGRA_SYSTEM_DMA 336 help 337 SPI driver for NVidia Tegra SoCs 338 339config SPI_TI_SSP 340 tristate "TI Sequencer Serial Port - SPI Support" 341 depends on MFD_TI_SSP 342 help 343 This selects an SPI master implementation using a TI sequencer 344 serial port. 345 346config SPI_TOPCLIFF_PCH 347 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI" 348 depends on PCI 349 help 350 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 351 used in some x86 embedded processors. 352 353 This driver also supports the ML7213/ML7223/ML7831, a companion chip 354 for the Atom E6xx series and compatible with the Intel EG20T PCH. 355 356config SPI_TXX9 357 tristate "Toshiba TXx9 SPI controller" 358 depends on GENERIC_GPIO && CPU_TX49XX 359 help 360 SPI driver for Toshiba TXx9 MIPS SoCs 361 362config SPI_XILINX 363 tristate "Xilinx SPI controller common module" 364 depends on HAS_IOMEM && EXPERIMENTAL 365 select SPI_BITBANG 366 help 367 This exposes the SPI controller IP from the Xilinx EDK. 368 369 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 370 Product Specification document (DS464) for hardware details. 371 372 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 373 374config SPI_NUC900 375 tristate "Nuvoton NUC900 series SPI" 376 depends on ARCH_W90X900 && EXPERIMENTAL 377 select SPI_BITBANG 378 help 379 SPI driver for Nuvoton NUC900 series ARM SoCs 380 381# 382# Add new SPI master controllers in alphabetical order above this line 383# 384 385config SPI_DESIGNWARE 386 tristate "DesignWare SPI controller core support" 387 depends on SPI_MASTER 388 help 389 general driver for SPI controller core from DesignWare 390 391config SPI_DW_PCI 392 tristate "PCI interface driver for DW SPI core" 393 depends on SPI_DESIGNWARE && PCI 394 395config SPI_DW_MID_DMA 396 bool "DMA support for DW SPI controller on Intel Moorestown platform" 397 depends on SPI_DW_PCI && INTEL_MID_DMAC 398 399config SPI_DW_MMIO 400 tristate "Memory-mapped io interface driver for DW SPI core" 401 depends on SPI_DESIGNWARE && HAVE_CLK 402 403# 404# There are lots of SPI device types, with sensors and memory 405# being probably the most widely used ones. 406# 407comment "SPI Protocol Masters" 408 409config SPI_SPIDEV 410 tristate "User mode SPI device driver support" 411 depends on EXPERIMENTAL 412 help 413 This supports user mode SPI protocol drivers. 414 415 Note that this application programming interface is EXPERIMENTAL 416 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes. 417 418config SPI_TLE62X0 419 tristate "Infineon TLE62X0 (for power switching)" 420 depends on SYSFS 421 help 422 SPI driver for Infineon TLE62X0 series line driver chips, 423 such as the TLE6220, TLE6230 and TLE6240. This provides a 424 sysfs interface, with each line presented as a kind of GPIO 425 exposing both switch control and diagnostic feedback. 426 427# 428# Add new SPI protocol masters in alphabetical order above this line 429# 430 431endif # SPI_MASTER 432 433# (slave support would go here) 434 435endif # SPI 436