Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468
  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. #
  8. menuconfig 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. SPI is widely used by microcontrollers to talk with sensors,
  18. eeprom and flash memory, codecs and various other controller
  19. chips, analog to digital (and d-to-a) converters, and more.
  20. MMC and SD cards can be accessed using SPI protocol; and for
  21. DataFlash cards used in MMC sockets, SPI must always be used.
  22. SPI is one of a family of similar protocols using a four wire
  23. interface (select, clock, data in, data out) including Microwire
  24. (half duplex), SSP, SSI, and PSP. This driver framework should
  25. work with most such devices and controllers.
  26. if SPI
  27. config SPI_DEBUG
  28. boolean "Debug support for SPI drivers"
  29. depends on DEBUG_KERNEL
  30. help
  31. Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
  32. sysfs, and debugfs support in SPI controller and protocol drivers.
  33. #
  34. # MASTER side ... talking to discrete SPI slave chips including microcontrollers
  35. #
  36. config SPI_MASTER
  37. # boolean "SPI Master Support"
  38. boolean
  39. default SPI
  40. help
  41. If your system has an master-capable SPI controller (which
  42. provides the clock and chipselect), you can enable that
  43. controller and the protocol drivers for the SPI slave chips
  44. that are connected.
  45. if SPI_MASTER
  46. comment "SPI Master Controller Drivers"
  47. config SPI_ALTERA
  48. tristate "Altera SPI Controller"
  49. select SPI_BITBANG
  50. help
  51. This is the driver for the Altera SPI Controller.
  52. config SPI_ATH79
  53. tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
  54. depends on ATH79 && GENERIC_GPIO
  55. select SPI_BITBANG
  56. help
  57. This enables support for the SPI controller present on the
  58. Atheros AR71XX/AR724X/AR913X SoCs.
  59. config SPI_ATMEL
  60. tristate "Atmel SPI Controller"
  61. depends on (ARCH_AT91 || AVR32)
  62. help
  63. This selects a driver for the Atmel SPI Controller, present on
  64. many AT32 (AVR32) and AT91 (ARM) chips.
  65. config SPI_BFIN
  66. tristate "SPI controller driver for ADI Blackfin5xx"
  67. depends on BLACKFIN
  68. help
  69. This is the SPI controller master driver for Blackfin 5xx processor.
  70. config SPI_AU1550
  71. tristate "Au1550/Au12x0 SPI Controller"
  72. depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
  73. select SPI_BITBANG
  74. help
  75. If you say yes to this option, support will be included for the
  76. Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
  77. This driver can also be built as a module. If so, the module
  78. will be called au1550_spi.
  79. config SPI_BITBANG
  80. tristate "Utilities for Bitbanging SPI masters"
  81. help
  82. With a few GPIO pins, your system can bitbang the SPI protocol.
  83. Select this to get SPI support through I/O pins (GPIO, parallel
  84. port, etc). Or, some systems' SPI master controller drivers use
  85. this code to manage the per-word or per-transfer accesses to the
  86. hardware shift registers.
  87. This is library code, and is automatically selected by drivers that
  88. need it. You only need to select this explicitly to support driver
  89. modules that aren't part of this kernel tree.
  90. config SPI_BUTTERFLY
  91. tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
  92. depends on PARPORT
  93. select SPI_BITBANG
  94. help
  95. This uses a custom parallel port cable to connect to an AVR
  96. Butterfly <http://www.atmel.com/products/avr/butterfly>, an
  97. inexpensive battery powered microcontroller evaluation board.
  98. This same cable can be used to flash new firmware.
  99. config SPI_COLDFIRE_QSPI
  100. tristate "Freescale Coldfire QSPI controller"
  101. depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
  102. help
  103. This enables support for the Coldfire QSPI controller in master
  104. mode.
  105. This driver can also be built as a module. If so, the module
  106. will be called coldfire_qspi.
  107. config SPI_DAVINCI
  108. tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
  109. depends on SPI_MASTER && ARCH_DAVINCI
  110. select SPI_BITBANG
  111. help
  112. SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
  113. This driver can also be built as a module. The module will be called
  114. davinci_spi.
  115. config SPI_EP93XX
  116. tristate "Cirrus Logic EP93xx SPI controller"
  117. depends on ARCH_EP93XX
  118. help
  119. This enables using the Cirrus EP93xx SPI controller in master
  120. mode.
  121. To compile this driver as a module, choose M here. The module will be
  122. called ep93xx_spi.
  123. config SPI_GPIO
  124. tristate "GPIO-based bitbanging SPI Master"
  125. depends on GENERIC_GPIO
  126. select SPI_BITBANG
  127. help
  128. This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
  129. interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
  130. slaves connected to a bus using this driver are configured as usual,
  131. except that the spi_board_info.controller_data holds the GPIO number
  132. for the chipselect used by this controller driver.
  133. Note that this driver often won't achieve even 1 Mbit/sec speeds,
  134. making it unusually slow for SPI. If your platform can inline
  135. GPIO operations, you should be able to leverage that for better
  136. speed with a custom version of this driver; see the source code.
  137. config SPI_IMX_VER_IMX1
  138. def_bool y if SOC_IMX1
  139. config SPI_IMX_VER_0_0
  140. def_bool y if SOC_IMX21 || SOC_IMX27
  141. config SPI_IMX_VER_0_4
  142. def_bool y if SOC_IMX31
  143. config SPI_IMX_VER_0_7
  144. def_bool y if ARCH_MX25 || SOC_IMX35 || SOC_IMX51 || SOC_IMX53
  145. config SPI_IMX_VER_2_3
  146. def_bool y if SOC_IMX51 || SOC_IMX53
  147. config SPI_IMX
  148. tristate "Freescale i.MX SPI controllers"
  149. depends on ARCH_MXC
  150. select SPI_BITBANG
  151. default m if IMX_HAVE_PLATFORM_SPI_IMX
  152. help
  153. This enables using the Freescale i.MX SPI controllers in master
  154. mode.
  155. config SPI_LM70_LLP
  156. tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
  157. depends on PARPORT && EXPERIMENTAL
  158. select SPI_BITBANG
  159. help
  160. This driver supports the NS LM70 LLP Evaluation Board,
  161. which interfaces to an LM70 temperature sensor using
  162. a parallel port.
  163. config SPI_MPC52xx
  164. tristate "Freescale MPC52xx SPI (non-PSC) controller support"
  165. depends on PPC_MPC52xx && SPI
  166. select SPI_MASTER_OF
  167. help
  168. This drivers supports the MPC52xx SPI controller in master SPI
  169. mode.
  170. config SPI_MPC52xx_PSC
  171. tristate "Freescale MPC52xx PSC SPI controller"
  172. depends on PPC_MPC52xx && EXPERIMENTAL
  173. help
  174. This enables using the Freescale MPC52xx Programmable Serial
  175. Controller in master SPI mode.
  176. config SPI_MPC512x_PSC
  177. tristate "Freescale MPC512x PSC SPI controller"
  178. depends on SPI_MASTER && PPC_MPC512x
  179. help
  180. This enables using the Freescale MPC5121 Programmable Serial
  181. Controller in SPI master mode.
  182. config SPI_FSL_LIB
  183. tristate
  184. depends on FSL_SOC
  185. config SPI_FSL_SPI
  186. tristate "Freescale SPI controller"
  187. depends on FSL_SOC
  188. select SPI_FSL_LIB
  189. help
  190. This enables using the Freescale SPI controllers in master mode.
  191. MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
  192. MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
  193. config SPI_FSL_ESPI
  194. tristate "Freescale eSPI controller"
  195. depends on FSL_SOC
  196. select SPI_FSL_LIB
  197. help
  198. This enables using the Freescale eSPI controllers in master mode.
  199. From MPC8536, 85xx platform uses the controller, and all P10xx,
  200. P20xx, P30xx,P40xx, P50xx uses this controller.
  201. config SPI_OC_TINY
  202. tristate "OpenCores tiny SPI"
  203. depends on GENERIC_GPIO
  204. select SPI_BITBANG
  205. help
  206. This is the driver for OpenCores tiny SPI master controller.
  207. config SPI_OMAP_UWIRE
  208. tristate "OMAP1 MicroWire"
  209. depends on ARCH_OMAP1
  210. select SPI_BITBANG
  211. help
  212. This hooks up to the MicroWire controller on OMAP1 chips.
  213. config SPI_OMAP24XX
  214. tristate "McSPI driver for OMAP"
  215. depends on ARCH_OMAP2PLUS
  216. help
  217. SPI master controller for OMAP24XX and later Multichannel SPI
  218. (McSPI) modules.
  219. config SPI_OMAP_100K
  220. tristate "OMAP SPI 100K"
  221. depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
  222. help
  223. OMAP SPI 100K master controller for omap7xx boards.
  224. config SPI_ORION
  225. tristate "Orion SPI master (EXPERIMENTAL)"
  226. depends on PLAT_ORION && EXPERIMENTAL
  227. help
  228. This enables using the SPI master controller on the Orion chips.
  229. config SPI_PL022
  230. tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
  231. depends on ARM_AMBA && EXPERIMENTAL
  232. default y if MACH_U300
  233. default y if ARCH_REALVIEW
  234. default y if INTEGRATOR_IMPD1
  235. default y if ARCH_VERSATILE
  236. help
  237. This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
  238. controller. If you have an embedded system with an AMBA(R)
  239. bus and a PL022 controller, say Y or M here.
  240. config SPI_PPC4xx
  241. tristate "PPC4xx SPI Controller"
  242. depends on PPC32 && 4xx && SPI_MASTER
  243. select SPI_BITBANG
  244. help
  245. This selects a driver for the PPC4xx SPI Controller.
  246. config SPI_PXA2XX
  247. tristate "PXA2xx SSP SPI master"
  248. depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
  249. select PXA_SSP if ARCH_PXA
  250. help
  251. This enables using a PXA2xx or Sodaville SSP port as a SPI master
  252. controller. The driver can be configured to use any SSP port and
  253. additional documentation can be found a Documentation/spi/pxa2xx.
  254. config SPI_PXA2XX_PCI
  255. def_bool SPI_PXA2XX && X86_32 && PCI
  256. config SPI_S3C24XX
  257. tristate "Samsung S3C24XX series SPI"
  258. depends on ARCH_S3C2410 && EXPERIMENTAL
  259. select SPI_BITBANG
  260. help
  261. SPI driver for Samsung S3C24XX series ARM SoCs
  262. config SPI_S3C24XX_FIQ
  263. bool "S3C24XX driver with FIQ pseudo-DMA"
  264. depends on SPI_S3C24XX
  265. select FIQ
  266. help
  267. Enable FIQ support for the S3C24XX SPI driver to provide pseudo
  268. DMA by using the fast-interrupt request framework, This allows
  269. the driver to get DMA-like performance when there are either
  270. no free DMA channels, or when doing transfers that required both
  271. TX and RX data paths.
  272. config SPI_S3C24XX_GPIO
  273. tristate "Samsung S3C24XX series SPI by GPIO"
  274. depends on ARCH_S3C2410 && EXPERIMENTAL
  275. select SPI_BITBANG
  276. help
  277. SPI driver for Samsung S3C24XX series ARM SoCs using
  278. GPIO lines to provide the SPI bus. This can be used where
  279. the inbuilt hardware cannot provide the transfer mode, or
  280. where the board is using non hardware connected pins.
  281. config SPI_S3C64XX
  282. tristate "Samsung S3C64XX series type SPI"
  283. depends on (ARCH_S3C64XX || ARCH_S5P64X0)
  284. select S3C64XX_DMA if ARCH_S3C64XX
  285. help
  286. SPI driver for Samsung S3C64XX and newer SoCs.
  287. config SPI_SH_MSIOF
  288. tristate "SuperH MSIOF SPI controller"
  289. depends on SUPERH && HAVE_CLK
  290. select SPI_BITBANG
  291. help
  292. SPI driver for SuperH MSIOF blocks.
  293. config SPI_SH
  294. tristate "SuperH SPI controller"
  295. depends on SUPERH
  296. help
  297. SPI driver for SuperH SPI blocks.
  298. config SPI_SH_SCI
  299. tristate "SuperH SCI SPI controller"
  300. depends on SUPERH
  301. select SPI_BITBANG
  302. help
  303. SPI driver for SuperH SCI blocks.
  304. config SPI_STMP3XXX
  305. tristate "Freescale STMP37xx/378x SPI/SSP controller"
  306. depends on ARCH_STMP3XXX && SPI_MASTER
  307. help
  308. SPI driver for Freescale STMP37xx/378x SoC SSP interface
  309. config SPI_TEGRA
  310. tristate "Nvidia Tegra SPI controller"
  311. depends on ARCH_TEGRA
  312. select TEGRA_SYSTEM_DMA
  313. help
  314. SPI driver for NVidia Tegra SoCs
  315. config SPI_TI_SSP
  316. tristate "TI Sequencer Serial Port - SPI Support"
  317. depends on MFD_TI_SSP
  318. help
  319. This selects an SPI master implementation using a TI sequencer
  320. serial port.
  321. To compile this driver as a module, choose M here: the
  322. module will be called ti-ssp-spi.
  323. config SPI_TOPCLIFF_PCH
  324. tristate "Topcliff PCH SPI Controller"
  325. depends on PCI
  326. help
  327. SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
  328. used in some x86 embedded processors.
  329. config SPI_TXX9
  330. tristate "Toshiba TXx9 SPI controller"
  331. depends on GENERIC_GPIO && CPU_TX49XX
  332. help
  333. SPI driver for Toshiba TXx9 MIPS SoCs
  334. config SPI_XILINX
  335. tristate "Xilinx SPI controller common module"
  336. depends on HAS_IOMEM && EXPERIMENTAL
  337. select SPI_BITBANG
  338. help
  339. This exposes the SPI controller IP from the Xilinx EDK.
  340. See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
  341. Product Specification document (DS464) for hardware details.
  342. Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
  343. config SPI_NUC900
  344. tristate "Nuvoton NUC900 series SPI"
  345. depends on ARCH_W90X900 && EXPERIMENTAL
  346. select SPI_BITBANG
  347. help
  348. SPI driver for Nuvoton NUC900 series ARM SoCs
  349. #
  350. # Add new SPI master controllers in alphabetical order above this line
  351. #
  352. config SPI_DESIGNWARE
  353. tristate "DesignWare SPI controller core support"
  354. depends on SPI_MASTER
  355. help
  356. general driver for SPI controller core from DesignWare
  357. config SPI_DW_PCI
  358. tristate "PCI interface driver for DW SPI core"
  359. depends on SPI_DESIGNWARE && PCI
  360. config SPI_DW_MID_DMA
  361. bool "DMA support for DW SPI controller on Intel Moorestown platform"
  362. depends on SPI_DW_PCI && INTEL_MID_DMAC
  363. config SPI_DW_MMIO
  364. tristate "Memory-mapped io interface driver for DW SPI core"
  365. depends on SPI_DESIGNWARE && HAVE_CLK
  366. #
  367. # There are lots of SPI device types, with sensors and memory
  368. # being probably the most widely used ones.
  369. #
  370. comment "SPI Protocol Masters"
  371. config SPI_SPIDEV
  372. tristate "User mode SPI device driver support"
  373. depends on EXPERIMENTAL
  374. help
  375. This supports user mode SPI protocol drivers.
  376. Note that this application programming interface is EXPERIMENTAL
  377. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  378. config SPI_TLE62X0
  379. tristate "Infineon TLE62X0 (for power switching)"
  380. depends on SYSFS
  381. help
  382. SPI driver for Infineon TLE62X0 series line driver chips,
  383. such as the TLE6220, TLE6230 and TLE6240. This provides a
  384. sysfs interface, with each line presented as a kind of GPIO
  385. exposing both switch control and diagnostic feedback.
  386. #
  387. # Add new SPI protocol masters in alphabetical order above this line
  388. #
  389. endif # SPI_MASTER
  390. # (slave support would go here)
  391. endif # SPI