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 89 This driver can also be built as a module. If so, the module 90 will be called spi_bfin_sport. 91 92config SPI_AU1550 93 tristate "Au1550/Au12x0 SPI Controller" 94 depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL 95 select SPI_BITBANG 96 help 97 If you say yes to this option, support will be included for the 98 Au1550 SPI controller (may also work with Au1200,Au1210,Au1250). 99 100 This driver can also be built as a module. If so, the module 101 will be called au1550_spi. 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 || M527x || M528x || M532x) 129 help 130 This enables support for the Coldfire QSPI controller in master 131 mode. 132 133 This driver can also be built as a module. If so, the module 134 will be called coldfire_qspi. 135 136config SPI_DAVINCI 137 tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller" 138 depends on SPI_MASTER && ARCH_DAVINCI 139 select SPI_BITBANG 140 help 141 SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules. 142 143 This driver can also be built as a module. The module will be called 144 davinci_spi. 145 146config SPI_EP93XX 147 tristate "Cirrus Logic EP93xx SPI controller" 148 depends on ARCH_EP93XX 149 help 150 This enables using the Cirrus EP93xx SPI controller in master 151 mode. 152 153 To compile this driver as a module, choose M here. The module will be 154 called ep93xx_spi. 155 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. 166 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. 171 172config SPI_IMX_VER_IMX1 173 def_bool y if SOC_IMX1 174 175config SPI_IMX_VER_0_0 176 def_bool y if SOC_IMX21 || SOC_IMX27 177 178config SPI_IMX_VER_0_4 179 def_bool y if SOC_IMX31 180 181config SPI_IMX_VER_0_7 182 def_bool y if ARCH_MX25 || SOC_IMX35 || SOC_IMX51 || SOC_IMX53 183 184config SPI_IMX_VER_2_3 185 def_bool y if SOC_IMX51 || SOC_IMX53 186 187config SPI_IMX 188 tristate "Freescale i.MX SPI controllers" 189 depends on ARCH_MXC 190 select SPI_BITBANG 191 default m if IMX_HAVE_PLATFORM_SPI_IMX 192 help 193 This enables using the Freescale i.MX SPI controllers in master 194 mode. 195 196config SPI_LM70_LLP 197 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 198 depends on PARPORT && EXPERIMENTAL 199 select SPI_BITBANG 200 help 201 This driver supports the NS LM70 LLP Evaluation Board, 202 which interfaces to an LM70 temperature sensor using 203 a parallel port. 204 205config SPI_MPC52xx 206 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 207 depends on PPC_MPC52xx && SPI 208 select SPI_MASTER_OF 209 help 210 This drivers supports the MPC52xx SPI controller in master SPI 211 mode. 212 213config SPI_MPC52xx_PSC 214 tristate "Freescale MPC52xx PSC SPI controller" 215 depends on PPC_MPC52xx && EXPERIMENTAL 216 help 217 This enables using the Freescale MPC52xx Programmable Serial 218 Controller in master SPI mode. 219 220config SPI_MPC512x_PSC 221 tristate "Freescale MPC512x PSC SPI controller" 222 depends on SPI_MASTER && PPC_MPC512x 223 help 224 This enables using the Freescale MPC5121 Programmable Serial 225 Controller in SPI master mode. 226 227config SPI_FSL_LIB 228 tristate 229 depends on FSL_SOC 230 231config SPI_FSL_SPI 232 tristate "Freescale SPI controller" 233 depends on FSL_SOC 234 select SPI_FSL_LIB 235 help 236 This enables using the Freescale SPI controllers in master mode. 237 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 238 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 239 240config SPI_FSL_ESPI 241 tristate "Freescale eSPI controller" 242 depends on FSL_SOC 243 select SPI_FSL_LIB 244 help 245 This enables using the Freescale eSPI controllers in master mode. 246 From MPC8536, 85xx platform uses the controller, and all P10xx, 247 P20xx, P30xx,P40xx, P50xx uses this controller. 248 249config SPI_OC_TINY 250 tristate "OpenCores tiny SPI" 251 depends on GENERIC_GPIO 252 select SPI_BITBANG 253 help 254 This is the driver for OpenCores tiny SPI master controller. 255 256config SPI_OMAP_UWIRE 257 tristate "OMAP1 MicroWire" 258 depends on ARCH_OMAP1 259 select SPI_BITBANG 260 help 261 This hooks up to the MicroWire controller on OMAP1 chips. 262 263config SPI_OMAP24XX 264 tristate "McSPI driver for OMAP" 265 depends on ARCH_OMAP2PLUS 266 help 267 SPI master controller for OMAP24XX and later Multichannel SPI 268 (McSPI) modules. 269 270config SPI_OMAP_100K 271 tristate "OMAP SPI 100K" 272 depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730) 273 help 274 OMAP SPI 100K master controller for omap7xx boards. 275 276config SPI_ORION 277 tristate "Orion SPI master (EXPERIMENTAL)" 278 depends on PLAT_ORION && EXPERIMENTAL 279 help 280 This enables using the SPI master controller on the Orion chips. 281 282config SPI_PL022 283 tristate "ARM AMBA PL022 SSP controller" 284 depends on ARM_AMBA 285 default y if MACH_U300 286 default y if ARCH_REALVIEW 287 default y if INTEGRATOR_IMPD1 288 default y if ARCH_VERSATILE 289 help 290 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 291 controller. If you have an embedded system with an AMBA(R) 292 bus and a PL022 controller, say Y or M here. 293 294config SPI_PPC4xx 295 tristate "PPC4xx SPI Controller" 296 depends on PPC32 && 4xx && SPI_MASTER 297 select SPI_BITBANG 298 help 299 This selects a driver for the PPC4xx SPI Controller. 300 301config SPI_PXA2XX 302 tristate "PXA2xx SSP SPI master" 303 depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL 304 select PXA_SSP if ARCH_PXA 305 help 306 This enables using a PXA2xx or Sodaville SSP port as a SPI master 307 controller. The driver can be configured to use any SSP port and 308 additional documentation can be found a Documentation/spi/pxa2xx. 309 310config SPI_PXA2XX_PCI 311 def_bool SPI_PXA2XX && X86_32 && PCI 312 313config SPI_S3C24XX 314 tristate "Samsung S3C24XX series SPI" 315 depends on ARCH_S3C2410 && EXPERIMENTAL 316 select SPI_BITBANG 317 help 318 SPI driver for Samsung S3C24XX series ARM SoCs 319 320config SPI_S3C24XX_FIQ 321 bool "S3C24XX driver with FIQ pseudo-DMA" 322 depends on SPI_S3C24XX 323 select FIQ 324 help 325 Enable FIQ support for the S3C24XX SPI driver to provide pseudo 326 DMA by using the fast-interrupt request framework, This allows 327 the driver to get DMA-like performance when there are either 328 no free DMA channels, or when doing transfers that required both 329 TX and RX data paths. 330 331config SPI_S3C24XX_GPIO 332 tristate "Samsung S3C24XX series SPI by GPIO" 333 depends on ARCH_S3C2410 && EXPERIMENTAL 334 select SPI_BITBANG 335 help 336 SPI driver for Samsung S3C24XX series ARM SoCs using 337 GPIO lines to provide the SPI bus. This can be used where 338 the inbuilt hardware cannot provide the transfer mode, or 339 where the board is using non hardware connected pins. 340 341config SPI_S3C64XX 342 tristate "Samsung S3C64XX series type SPI" 343 depends on (ARCH_S3C64XX || ARCH_S5P64X0) 344 select S3C64XX_DMA if ARCH_S3C64XX 345 help 346 SPI driver for Samsung S3C64XX and newer SoCs. 347 348config SPI_SH_MSIOF 349 tristate "SuperH MSIOF SPI controller" 350 depends on SUPERH && HAVE_CLK 351 select SPI_BITBANG 352 help 353 SPI driver for SuperH MSIOF blocks. 354 355config SPI_SH 356 tristate "SuperH SPI controller" 357 depends on SUPERH 358 help 359 SPI driver for SuperH SPI blocks. 360 361config SPI_SH_SCI 362 tristate "SuperH SCI SPI controller" 363 depends on SUPERH 364 select SPI_BITBANG 365 help 366 SPI driver for SuperH SCI blocks. 367 368config SPI_STMP3XXX 369 tristate "Freescale STMP37xx/378x SPI/SSP controller" 370 depends on ARCH_STMP3XXX && SPI_MASTER 371 help 372 SPI driver for Freescale STMP37xx/378x SoC SSP interface 373 374config SPI_TEGRA 375 tristate "Nvidia Tegra SPI controller" 376 depends on ARCH_TEGRA 377 select TEGRA_SYSTEM_DMA 378 help 379 SPI driver for NVidia Tegra SoCs 380 381config SPI_TI_SSP 382 tristate "TI Sequencer Serial Port - SPI Support" 383 depends on MFD_TI_SSP 384 help 385 This selects an SPI master implementation using a TI sequencer 386 serial port. 387 388 To compile this driver as a module, choose M here: the 389 module will be called ti-ssp-spi. 390 391config SPI_TOPCLIFF_PCH 392 tristate "Topcliff PCH SPI Controller" 393 depends on PCI 394 help 395 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 396 used in some x86 embedded processors. 397 398config SPI_TXX9 399 tristate "Toshiba TXx9 SPI controller" 400 depends on GENERIC_GPIO && CPU_TX49XX 401 help 402 SPI driver for Toshiba TXx9 MIPS SoCs 403 404config SPI_XILINX 405 tristate "Xilinx SPI controller common module" 406 depends on HAS_IOMEM && EXPERIMENTAL 407 select SPI_BITBANG 408 help 409 This exposes the SPI controller IP from the Xilinx EDK. 410 411 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 412 Product Specification document (DS464) for hardware details. 413 414 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 415 416config SPI_NUC900 417 tristate "Nuvoton NUC900 series SPI" 418 depends on ARCH_W90X900 && EXPERIMENTAL 419 select SPI_BITBANG 420 help 421 SPI driver for Nuvoton NUC900 series ARM SoCs 422 423# 424# Add new SPI master controllers in alphabetical order above this line 425# 426 427config SPI_DESIGNWARE 428 tristate "DesignWare SPI controller core support" 429 depends on SPI_MASTER 430 help 431 general driver for SPI controller core from DesignWare 432 433config SPI_DW_PCI 434 tristate "PCI interface driver for DW SPI core" 435 depends on SPI_DESIGNWARE && PCI 436 437config SPI_DW_MID_DMA 438 bool "DMA support for DW SPI controller on Intel Moorestown platform" 439 depends on SPI_DW_PCI && INTEL_MID_DMAC 440 441config SPI_DW_MMIO 442 tristate "Memory-mapped io interface driver for DW SPI core" 443 depends on SPI_DESIGNWARE && HAVE_CLK 444 445# 446# There are lots of SPI device types, with sensors and memory 447# being probably the most widely used ones. 448# 449comment "SPI Protocol Masters" 450 451config SPI_SPIDEV 452 tristate "User mode SPI device driver support" 453 depends on EXPERIMENTAL 454 help 455 This supports user mode SPI protocol drivers. 456 457 Note that this application programming interface is EXPERIMENTAL 458 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes. 459 460config SPI_TLE62X0 461 tristate "Infineon TLE62X0 (for power switching)" 462 depends on SYSFS 463 help 464 SPI driver for Infineon TLE62X0 series line driver chips, 465 such as the TLE6220, TLE6230 and TLE6240. This provides a 466 sysfs interface, with each line presented as a kind of GPIO 467 exposing both switch control and diagnostic feedback. 468 469# 470# Add new SPI protocol masters in alphabetical order above this line 471# 472 473endif # SPI_MASTER 474 475# (slave support would go here) 476 477endif # SPI 478