Kconfig 13 KB

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