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_ATMEL 57 tristate "Atmel SPI Controller" 58 depends on (ARCH_AT91 || AVR32) 59 help 60 This selects a driver for the Atmel SPI Controller, present on 61 many AT32 (AVR32) and AT91 (ARM) chips. 62 63config SPI_BFIN 64 tristate "SPI controller driver for ADI Blackfin5xx" 65 depends on BLACKFIN 66 help 67 This is the SPI controller master driver for Blackfin 5xx processor. 68 69config SPI_AU1550 70 tristate "Au1550/Au12x0 SPI Controller" 71 depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL 72 select SPI_BITBANG 73 help 74 If you say yes to this option, support will be included for the 75 Au1550 SPI controller (may also work with Au1200,Au1210,Au1250). 76 77 This driver can also be built as a module. If so, the module 78 will be called au1550_spi. 79 80config SPI_BITBANG 81 tristate "Utilities for Bitbanging SPI masters" 82 help 83 With a few GPIO pins, your system can bitbang the SPI protocol. 84 Select this to get SPI support through I/O pins (GPIO, parallel 85 port, etc). Or, some systems' SPI master controller drivers use 86 this code to manage the per-word or per-transfer accesses to the 87 hardware shift registers. 88 89 This is library code, and is automatically selected by drivers that 90 need it. You only need to select this explicitly to support driver 91 modules that aren't part of this kernel tree. 92 93config SPI_BUTTERFLY 94 tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)" 95 depends on PARPORT 96 select SPI_BITBANG 97 help 98 This uses a custom parallel port cable to connect to an AVR 99 Butterfly <http://www.atmel.com/products/avr/butterfly>, an 100 inexpensive battery powered microcontroller evaluation board. 101 This same cable can be used to flash new firmware. 102 103config SPI_COLDFIRE_QSPI 104 tristate "Freescale Coldfire QSPI controller" 105 depends on (M520x || M523x || M5249 || M527x || M528x || M532x) 106 help 107 This enables support for the Coldfire QSPI controller in master 108 mode. 109 110 This driver can also be built as a module. If so, the module 111 will be called coldfire_qspi. 112 113config SPI_DAVINCI 114 tristate "SPI controller driver for DaVinci/DA8xx SoC's" 115 depends on SPI_MASTER && ARCH_DAVINCI 116 select SPI_BITBANG 117 help 118 SPI master controller for DaVinci and DA8xx SPI modules. 119 120config SPI_EP93XX 121 tristate "Cirrus Logic EP93xx SPI controller" 122 depends on ARCH_EP93XX 123 help 124 This enables using the Cirrus EP93xx SPI controller in master 125 mode. 126 127 To compile this driver as a module, choose M here. The module will be 128 called ep93xx_spi. 129 130config SPI_GPIO 131 tristate "GPIO-based bitbanging SPI Master" 132 depends on GENERIC_GPIO 133 select SPI_BITBANG 134 help 135 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO 136 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI 137 slaves connected to a bus using this driver are configured as usual, 138 except that the spi_board_info.controller_data holds the GPIO number 139 for the chipselect used by this controller driver. 140 141 Note that this driver often won't achieve even 1 Mbit/sec speeds, 142 making it unusually slow for SPI. If your platform can inline 143 GPIO operations, you should be able to leverage that for better 144 speed with a custom version of this driver; see the source code. 145 146config SPI_IMX_VER_IMX1 147 def_bool y if SOC_IMX1 148 149config SPI_IMX_VER_0_0 150 def_bool y if SOC_IMX21 || SOC_IMX27 151 152config SPI_IMX_VER_0_4 153 def_bool y if ARCH_MX31 154 155config SPI_IMX_VER_0_7 156 def_bool y if ARCH_MX25 || ARCH_MX35 || ARCH_MX51 157 158config SPI_IMX_VER_2_3 159 def_bool y if ARCH_MX51 160 161config SPI_IMX 162 tristate "Freescale i.MX SPI controllers" 163 depends on ARCH_MXC 164 select SPI_BITBANG 165 default m if IMX_HAVE_PLATFORM_SPI_IMX 166 help 167 This enables using the Freescale i.MX SPI controllers in master 168 mode. 169 170config SPI_LM70_LLP 171 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)" 172 depends on PARPORT && EXPERIMENTAL 173 select SPI_BITBANG 174 help 175 This driver supports the NS LM70 LLP Evaluation Board, 176 which interfaces to an LM70 temperature sensor using 177 a parallel port. 178 179config SPI_MPC52xx 180 tristate "Freescale MPC52xx SPI (non-PSC) controller support" 181 depends on PPC_MPC52xx && SPI 182 select SPI_MASTER_OF 183 help 184 This drivers supports the MPC52xx SPI controller in master SPI 185 mode. 186 187config SPI_MPC52xx_PSC 188 tristate "Freescale MPC52xx PSC SPI controller" 189 depends on PPC_MPC52xx && EXPERIMENTAL 190 help 191 This enables using the Freescale MPC52xx Programmable Serial 192 Controller in master SPI mode. 193 194config SPI_MPC512x_PSC 195 tristate "Freescale MPC512x PSC SPI controller" 196 depends on SPI_MASTER && PPC_MPC512x 197 help 198 This enables using the Freescale MPC5121 Programmable Serial 199 Controller in SPI master mode. 200 201config SPI_FSL_LIB 202 tristate 203 depends on FSL_SOC 204 205config SPI_FSL_SPI 206 tristate "Freescale SPI controller" 207 depends on FSL_SOC 208 select SPI_FSL_LIB 209 help 210 This enables using the Freescale SPI controllers in master mode. 211 MPC83xx platform uses the controller in cpu mode or CPM/QE mode. 212 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode. 213 214config SPI_FSL_ESPI 215 tristate "Freescale eSPI controller" 216 depends on FSL_SOC 217 select SPI_FSL_LIB 218 help 219 This enables using the Freescale eSPI controllers in master mode. 220 From MPC8536, 85xx platform uses the controller, and all P10xx, 221 P20xx, P30xx,P40xx, P50xx uses this controller. 222 223config SPI_OMAP_UWIRE 224 tristate "OMAP1 MicroWire" 225 depends on ARCH_OMAP1 226 select SPI_BITBANG 227 help 228 This hooks up to the MicroWire controller on OMAP1 chips. 229 230config SPI_OMAP24XX 231 tristate "McSPI driver for OMAP" 232 depends on ARCH_OMAP2PLUS 233 help 234 SPI master controller for OMAP24XX and later Multichannel SPI 235 (McSPI) modules. 236 237config SPI_OMAP_100K 238 tristate "OMAP SPI 100K" 239 depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730) 240 help 241 OMAP SPI 100K master controller for omap7xx boards. 242 243config SPI_ORION 244 tristate "Orion SPI master (EXPERIMENTAL)" 245 depends on PLAT_ORION && EXPERIMENTAL 246 help 247 This enables using the SPI master controller on the Orion chips. 248 249config SPI_PL022 250 tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)" 251 depends on ARM_AMBA && EXPERIMENTAL 252 default y if MACH_U300 253 default y if ARCH_REALVIEW 254 default y if INTEGRATOR_IMPD1 255 default y if ARCH_VERSATILE 256 help 257 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP 258 controller. If you have an embedded system with an AMBA(R) 259 bus and a PL022 controller, say Y or M here. 260 261config SPI_PPC4xx 262 tristate "PPC4xx SPI Controller" 263 depends on PPC32 && 4xx && SPI_MASTER 264 select SPI_BITBANG 265 help 266 This selects a driver for the PPC4xx SPI Controller. 267 268config SPI_PXA2XX 269 tristate "PXA2xx SSP SPI master" 270 depends on ARCH_PXA && EXPERIMENTAL 271 select PXA_SSP 272 help 273 This enables using a PXA2xx SSP port as a SPI master controller. 274 The driver can be configured to use any SSP port and additional 275 documentation can be found a Documentation/spi/pxa2xx. 276 277config SPI_S3C24XX 278 tristate "Samsung S3C24XX series SPI" 279 depends on ARCH_S3C2410 && EXPERIMENTAL 280 select SPI_BITBANG 281 help 282 SPI driver for Samsung S3C24XX series ARM SoCs 283 284config SPI_S3C24XX_FIQ 285 bool "S3C24XX driver with FIQ pseudo-DMA" 286 depends on SPI_S3C24XX 287 select FIQ 288 help 289 Enable FIQ support for the S3C24XX SPI driver to provide pseudo 290 DMA by using the fast-interrupt request framework, This allows 291 the driver to get DMA-like performance when there are either 292 no free DMA channels, or when doing transfers that required both 293 TX and RX data paths. 294 295config SPI_S3C24XX_GPIO 296 tristate "Samsung S3C24XX series SPI by GPIO" 297 depends on ARCH_S3C2410 && EXPERIMENTAL 298 select SPI_BITBANG 299 help 300 SPI driver for Samsung S3C24XX series ARM SoCs using 301 GPIO lines to provide the SPI bus. This can be used where 302 the inbuilt hardware cannot provide the transfer mode, or 303 where the board is using non hardware connected pins. 304 305config SPI_S3C64XX 306 tristate "Samsung S3C64XX series type SPI" 307 depends on ARCH_S3C64XX && EXPERIMENTAL 308 select S3C64XX_DMA 309 help 310 SPI driver for Samsung S3C64XX and newer SoCs. 311 312config SPI_SH_MSIOF 313 tristate "SuperH MSIOF SPI controller" 314 depends on SUPERH && HAVE_CLK 315 select SPI_BITBANG 316 help 317 SPI driver for SuperH MSIOF blocks. 318 319config SPI_SH_SCI 320 tristate "SuperH SCI SPI controller" 321 depends on SUPERH 322 select SPI_BITBANG 323 help 324 SPI driver for SuperH SCI blocks. 325 326config SPI_STMP3XXX 327 tristate "Freescale STMP37xx/378x SPI/SSP controller" 328 depends on ARCH_STMP3XXX && SPI_MASTER 329 help 330 SPI driver for Freescale STMP37xx/378x SoC SSP interface 331 332config SPI_TEGRA 333 tristate "Nvidia Tegra SPI controller" 334 depends on ARCH_TEGRA 335 select TEGRA_SYSTEM_DMA 336 help 337 SPI driver for NVidia Tegra SoCs 338 339config SPI_TOPCLIFF_PCH 340 tristate "Topcliff PCH SPI Controller" 341 depends on PCI 342 help 343 SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus 344 used in some x86 embedded processors. 345 346config SPI_TXX9 347 tristate "Toshiba TXx9 SPI controller" 348 depends on GENERIC_GPIO && CPU_TX49XX 349 help 350 SPI driver for Toshiba TXx9 MIPS SoCs 351 352config SPI_XILINX 353 tristate "Xilinx SPI controller common module" 354 depends on HAS_IOMEM && EXPERIMENTAL 355 select SPI_BITBANG 356 select SPI_XILINX_OF if (XILINX_VIRTEX || MICROBLAZE) 357 help 358 This exposes the SPI controller IP from the Xilinx EDK. 359 360 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" 361 Product Specification document (DS464) for hardware details. 362 363 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)" 364 365config SPI_XILINX_OF 366 tristate "Xilinx SPI controller OF device" 367 depends on SPI_XILINX && (XILINX_VIRTEX || MICROBLAZE) 368 help 369 This is the OF driver for the SPI controller IP from the Xilinx EDK. 370 371config SPI_XILINX_PLTFM 372 tristate "Xilinx SPI controller platform device" 373 depends on SPI_XILINX 374 help 375 This is the platform driver for the SPI controller IP 376 from the Xilinx EDK. 377 378config SPI_NUC900 379 tristate "Nuvoton NUC900 series SPI" 380 depends on ARCH_W90X900 && EXPERIMENTAL 381 select SPI_BITBANG 382 help 383 SPI driver for Nuvoton NUC900 series ARM SoCs 384 385# 386# Add new SPI master controllers in alphabetical order above this line 387# 388 389config SPI_DESIGNWARE 390 tristate "DesignWare SPI controller core support" 391 depends on SPI_MASTER 392 help 393 general driver for SPI controller core from DesignWare 394 395config SPI_DW_PCI 396 tristate "PCI interface driver for DW SPI core" 397 depends on SPI_DESIGNWARE && PCI 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