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_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. 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_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. 102 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. 111 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. 115 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 <http://www.atmel.com/products/avr/butterfly>, an 123 inexpensive battery powered microcontroller evaluation board. 124 This same cable can be used to flash new firmware. 125 126config SPI_CLPS711X 127 tristate "CLPS711X host SPI controller" 128 depends on ARCH_CLPS711X 129 help 130 This enables dedicated general purpose SPI/Microwire1-compatible 131 master mode interface (SSI1) for CLPS711X-based CPUs. 132 133config SPI_COLDFIRE_QSPI 134 tristate "Freescale Coldfire QSPI controller" 135 depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x) 136 help 137 This enables support for the Coldfire QSPI controller in master 138 mode. 139 140config SPI_DAVINCI 141 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller" 142 depends on ARCH_DAVINCI 143 select SPI_BITBANG 144 select TI_EDMA 145 help 146 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules. 147 148config SPI_EP93XX 149 tristate "Cirrus Logic EP93xx SPI controller" 150 depends on ARCH_EP93XX 151 help 152 This enables using the Cirrus EP93xx SPI controller in master 153 mode. 154 155config SPI_FALCON 156 tristate "Falcon SPI controller support" 157 depends on SOC_FALCON 158 help 159 The external bus unit (EBU) found on the FALC-ON SoC has SPI 160 emulation that is designed for serial flash access. This driver 161 has only been tested with m25p80 type chips. The hardware has no 162 support for other types of SPI peripherals. 163 164config SPI_GPIO 165 tristate "GPIO-based bitbanging SPI Master" 166 depends on GENERIC_GPIO 167 select SPI_BITBANG 168 help 169 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO 170 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI 171 slaves connected to a bus using this driver are configured as usual, 172 except that the spi_board_info.controller_data holds the GPIO number 173 for the chipselect used by this controller driver. 174 175 Note that this driver often won't achieve even 1 Mbit/sec speeds, 176 making it unusually slow for SPI. If your platform can inline 177 GPIO operations, you should be able to leverage that for better 178 speed with a custom version of this driver; see the source code. 179 180config SPI_IMX 181 tristate "Freescale i.MX SPI controllers" 182 depends on ARCH_MXC 183 select SPI_BITBANG 184 default m if IMX_HAVE_PLATFORM_SPI_IMX 185 help 186 This enables using the Freescale i.MX SPI controllers in master 187 mode. 188 189config SPI_LM70_LLP 190 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 191 depends on PARPORT && EXPERIMENTAL 192 select SPI_BITBANG 193 help 194 This driver supports the NS LM70 LLP Evaluation Board, 195 which interfaces to an LM70 temperature sensor using 196 a parallel port. 197 198config SPI_MPC52xx 199 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 200 depends on PPC_MPC52xx 201 help 202 This drivers supports the MPC52xx SPI controller in master SPI 203 mode. 204 205config SPI_MPC52xx_PSC 206 tristate "Freescale MPC52xx PSC SPI controller" 207 depends on PPC_MPC52xx && EXPERIMENTAL 208 help 209 This enables using the Freescale MPC52xx Programmable Serial 210 Controller in master SPI mode. 211 212config SPI_MPC512x_PSC 213 tristate "Freescale MPC512x PSC SPI controller" 214 depends on PPC_MPC512x 215 help 216 This enables using the Freescale MPC5121 Programmable Serial 217 Controller in SPI master mode. 218 219config SPI_FSL_LIB 220 tristate 221 depends on FSL_SOC 222 223config SPI_FSL_SPI 224 bool "Freescale SPI controller" 225 depends on FSL_SOC 226 select SPI_FSL_LIB 227 help 228 This enables using the Freescale SPI controllers in master mode. 229 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 230 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 231 232config SPI_FSL_ESPI 233 bool "Freescale eSPI controller" 234 depends on FSL_SOC 235 select SPI_FSL_LIB 236 help 237 This enables using the Freescale eSPI controllers in master mode. 238 From MPC8536, 85xx platform uses the controller, and all P10xx, 239 P20xx, P30xx,P40xx, P50xx uses this controller. 240 241config SPI_OC_TINY 242 tristate "OpenCores tiny SPI" 243 depends on GENERIC_GPIO 244 select SPI_BITBANG 245 help 246 This is the driver for OpenCores tiny SPI master controller. 247 248config SPI_OCTEON 249 tristate "Cavium OCTEON SPI controller" 250 depends on CPU_CAVIUM_OCTEON 251 help 252 SPI host driver for the hardware found on some Cavium OCTEON 253 SOCs. 254 255config SPI_OMAP_UWIRE 256 tristate "OMAP1 MicroWire" 257 depends on ARCH_OMAP1 258 select SPI_BITBANG 259 help 260 This hooks up to the MicroWire controller on OMAP1 chips. 261 262config SPI_OMAP24XX 263 tristate "McSPI driver for OMAP" 264 depends on ARCH_OMAP2PLUS 265 help 266 SPI master controller for OMAP24XX and later Multichannel SPI 267 (McSPI) modules. 268 269config SPI_OMAP_100K 270 tristate "OMAP SPI 100K" 271 depends on ARCH_OMAP850 || ARCH_OMAP730 272 help 273 OMAP SPI 100K master controller for omap7xx boards. 274 275config SPI_ORION 276 tristate "Orion SPI master (EXPERIMENTAL)" 277 depends on PLAT_ORION && EXPERIMENTAL 278 help 279 This enables using the SPI master controller on the Orion chips. 280 281config SPI_PL022 282 tristate "ARM AMBA PL022 SSP controller" 283 depends on ARM_AMBA 284 default y if MACH_U300 285 default y if ARCH_REALVIEW 286 default y if INTEGRATOR_IMPD1 287 default y if ARCH_VERSATILE 288 help 289 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 290 controller. If you have an embedded system with an AMBA(R) 291 bus and a PL022 controller, say Y or M here. 292 293config SPI_PPC4xx 294 tristate "PPC4xx SPI Controller" 295 depends on PPC32 && 4xx 296 select SPI_BITBANG 297 help 298 This selects a driver for the PPC4xx SPI Controller. 299 300config SPI_PXA2XX 301 tristate "PXA2xx SSP SPI master" 302 depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL 303 select PXA_SSP if ARCH_PXA 304 help 305 This enables using a PXA2xx or Sodaville SSP port as a SPI master 306 controller. The driver can be configured to use any SSP port and 307 additional documentation can be found a Documentation/spi/pxa2xx. 308 309config SPI_PXA2XX_PCI 310 def_bool SPI_PXA2XX && X86_32 && PCI 311 312config SPI_RSPI 313 tristate "Renesas RSPI controller" 314 depends on SUPERH 315 help 316 SPI driver for Renesas RSPI blocks. 317 318config SPI_S3C24XX 319 tristate "Samsung S3C24XX series SPI" 320 depends on ARCH_S3C24XX && EXPERIMENTAL 321 select SPI_BITBANG 322 help 323 SPI driver for Samsung S3C24XX series ARM SoCs 324 325config SPI_S3C24XX_FIQ 326 bool "S3C24XX driver with FIQ pseudo-DMA" 327 depends on SPI_S3C24XX 328 select FIQ 329 help 330 Enable FIQ support for the S3C24XX SPI driver to provide pseudo 331 DMA by using the fast-interrupt request framework, This allows 332 the driver to get DMA-like performance when there are either 333 no free DMA channels, or when doing transfers that required both 334 TX and RX data paths. 335 336config SPI_S3C64XX 337 tristate "Samsung S3C64XX series type SPI" 338 depends on (ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5P64X0 || ARCH_EXYNOS) 339 select S3C64XX_DMA if ARCH_S3C64XX 340 help 341 SPI driver for Samsung S3C64XX and newer SoCs. 342 343config SPI_SC18IS602 344 tristate "NXP SC18IS602/602B/603 I2C to SPI bridge" 345 depends on I2C 346 help 347 SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge. 348 349config SPI_SH_MSIOF 350 tristate "SuperH MSIOF SPI controller" 351 depends on (SUPERH || ARCH_SHMOBILE) && HAVE_CLK 352 select SPI_BITBANG 353 help 354 SPI driver for SuperH and SH Mobile MSIOF blocks. 355 356config SPI_SH 357 tristate "SuperH SPI controller" 358 depends on SUPERH 359 help 360 SPI driver for SuperH SPI blocks. 361 362config SPI_SH_SCI 363 tristate "SuperH SCI SPI controller" 364 depends on SUPERH 365 select SPI_BITBANG 366 help 367 SPI driver for SuperH SCI blocks. 368 369config SPI_SH_HSPI 370 tristate "SuperH HSPI controller" 371 depends on ARCH_SHMOBILE 372 help 373 SPI driver for SuperH HSPI blocks. 374 375config SPI_SIRF 376 tristate "CSR SiRFprimaII SPI controller" 377 depends on ARCH_PRIMA2 378 select SPI_BITBANG 379 help 380 SPI driver for CSR SiRFprimaII SoCs 381 382config SPI_MXS 383 tristate "Freescale MXS SPI controller" 384 depends on ARCH_MXS 385 select STMP_DEVICE 386 help 387 SPI driver for Freescale MXS devices. 388 389config SPI_TEGRA20_SFLASH 390 tristate "Nvidia Tegra20 Serial flash Controller" 391 depends on ARCH_TEGRA 392 help 393 SPI driver for Nvidia Tegra20 Serial flash Controller interface. 394 The main usecase of this controller is to use spi flash as boot 395 device. 396 397config SPI_TEGRA20_SLINK 398 tristate "Nvidia Tegra20/Tegra30 SLINK Controller" 399 depends on ARCH_TEGRA && TEGRA20_APB_DMA 400 help 401 SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface. 402 403config SPI_TI_SSP 404 tristate "TI Sequencer Serial Port - SPI Support" 405 depends on MFD_TI_SSP 406 help 407 This selects an SPI master implementation using a TI sequencer 408 serial port. 409 410config SPI_TOPCLIFF_PCH 411 tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI" 412 depends on PCI 413 help 414 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 415 used in some x86 embedded processors. 416 417 This driver also supports the ML7213/ML7223/ML7831, a companion chip 418 for the Atom E6xx series and compatible with the Intel EG20T PCH. 419 420config SPI_TXX9 421 tristate "Toshiba TXx9 SPI controller" 422 depends on GENERIC_GPIO && CPU_TX49XX 423 help 424 SPI driver for Toshiba TXx9 MIPS SoCs 425 426config SPI_XCOMM 427 tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver" 428 depends on I2C 429 help 430 Support for the SPI-I2C bridge found on the Analog Devices 431 AD-FMCOMMS1-EBZ board. 432 433config SPI_XILINX 434 tristate "Xilinx SPI controller common module" 435 depends on HAS_IOMEM && EXPERIMENTAL 436 select SPI_BITBANG 437 help 438 This exposes the SPI controller IP from the Xilinx EDK. 439 440 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 441 Product Specification document (DS464) for hardware details. 442 443 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 444 445config SPI_NUC900 446 tristate "Nuvoton NUC900 series SPI" 447 depends on ARCH_W90X900 && EXPERIMENTAL 448 select SPI_BITBANG 449 help 450 SPI driver for Nuvoton NUC900 series ARM SoCs 451 452# 453# Add new SPI master controllers in alphabetical order above this line 454# 455 456config SPI_DESIGNWARE 457 tristate "DesignWare SPI controller core support" 458 help 459 general driver for SPI controller core from DesignWare 460 461config SPI_DW_PCI 462 tristate "PCI interface driver for DW SPI core" 463 depends on SPI_DESIGNWARE && PCI 464 465config SPI_DW_MID_DMA 466 bool "DMA support for DW SPI controller on Intel Moorestown platform" 467 depends on SPI_DW_PCI && INTEL_MID_DMAC 468 469config SPI_DW_MMIO 470 tristate "Memory-mapped io interface driver for DW SPI core" 471 depends on SPI_DESIGNWARE && HAVE_CLK 472 473# 474# There are lots of SPI device types, with sensors and memory 475# being probably the most widely used ones. 476# 477comment "SPI Protocol Masters" 478 479config SPI_SPIDEV 480 tristate "User mode SPI device driver support" 481 depends on EXPERIMENTAL 482 help 483 This supports user mode SPI protocol drivers. 484 485 Note that this application programming interface is EXPERIMENTAL 486 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes. 487 488config SPI_TLE62X0 489 tristate "Infineon TLE62X0 (for power switching)" 490 depends on SYSFS 491 help 492 SPI driver for Infineon TLE62X0 series line driver chips, 493 such as the TLE6220, TLE6230 and TLE6240. This provides a 494 sysfs interface, with each line presented as a kind of GPIO 495 exposing both switch control and diagnostic feedback. 496 497# 498# Add new SPI protocol masters in alphabetical order above this line 499# 500 501endif # SPI_MASTER 502 503# (slave support would go here) 504 505endif # SPI 506