Kconfig 14 KB

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