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