Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359
  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_DAVINCI
  88. tristate "SPI controller driver for DaVinci/DA8xx SoC's"
  89. depends on SPI_MASTER && ARCH_DAVINCI
  90. select SPI_BITBANG
  91. help
  92. SPI master controller for DaVinci and DA8xx SPI modules.
  93. config SPI_GPIO
  94. tristate "GPIO-based bitbanging SPI Master"
  95. depends on GENERIC_GPIO
  96. select SPI_BITBANG
  97. help
  98. This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
  99. interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
  100. slaves connected to a bus using this driver are configured as usual,
  101. except that the spi_board_info.controller_data holds the GPIO number
  102. for the chipselect used by this controller driver.
  103. Note that this driver often won't achieve even 1 Mbit/sec speeds,
  104. making it unusually slow for SPI. If your platform can inline
  105. GPIO operations, you should be able to leverage that for better
  106. speed with a custom version of this driver; see the source code.
  107. config SPI_IMX
  108. tristate "Freescale i.MX SPI controllers"
  109. depends on ARCH_MXC
  110. select SPI_BITBANG
  111. help
  112. This enables using the Freescale i.MX SPI controllers in master
  113. mode.
  114. config SPI_LM70_LLP
  115. tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
  116. depends on PARPORT && EXPERIMENTAL
  117. select SPI_BITBANG
  118. help
  119. This driver supports the NS LM70 LLP Evaluation Board,
  120. which interfaces to an LM70 temperature sensor using
  121. a parallel port.
  122. config SPI_MPC52xx
  123. tristate "Freescale MPC52xx SPI (non-PSC) controller support"
  124. depends on PPC_MPC52xx && SPI
  125. select SPI_MASTER_OF
  126. help
  127. This drivers supports the MPC52xx SPI controller in master SPI
  128. mode.
  129. config SPI_MPC52xx_PSC
  130. tristate "Freescale MPC52xx PSC SPI controller"
  131. depends on PPC_MPC52xx && EXPERIMENTAL
  132. help
  133. This enables using the Freescale MPC52xx Programmable Serial
  134. Controller in master SPI mode.
  135. config SPI_MPC8xxx
  136. tristate "Freescale MPC8xxx SPI controller"
  137. depends on FSL_SOC
  138. help
  139. This enables using the Freescale MPC8xxx SPI controllers in master
  140. mode.
  141. config SPI_OMAP_UWIRE
  142. tristate "OMAP1 MicroWire"
  143. depends on ARCH_OMAP1
  144. select SPI_BITBANG
  145. help
  146. This hooks up to the MicroWire controller on OMAP1 chips.
  147. config SPI_OMAP24XX
  148. tristate "McSPI driver for OMAP24xx/OMAP34xx"
  149. depends on ARCH_OMAP24XX || ARCH_OMAP34XX
  150. help
  151. SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
  152. (McSPI) modules.
  153. config SPI_OMAP_100K
  154. tristate "OMAP SPI 100K"
  155. depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
  156. help
  157. OMAP SPI 100K master controller for omap7xx boards.
  158. config SPI_ORION
  159. tristate "Orion SPI master (EXPERIMENTAL)"
  160. depends on PLAT_ORION && EXPERIMENTAL
  161. help
  162. This enables using the SPI master controller on the Orion chips.
  163. config SPI_PL022
  164. tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
  165. depends on ARM_AMBA && EXPERIMENTAL
  166. default y if MACH_U300
  167. default y if ARCH_REALVIEW
  168. default y if INTEGRATOR_IMPD1
  169. default y if ARCH_VERSATILE
  170. help
  171. This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
  172. controller. If you have an embedded system with an AMBA(R)
  173. bus and a PL022 controller, say Y or M here.
  174. config SPI_PPC4xx
  175. tristate "PPC4xx SPI Controller"
  176. depends on PPC32 && 4xx && SPI_MASTER
  177. select SPI_BITBANG
  178. help
  179. This selects a driver for the PPC4xx SPI Controller.
  180. config SPI_PXA2XX
  181. tristate "PXA2xx SSP SPI master"
  182. depends on ARCH_PXA && EXPERIMENTAL
  183. select PXA_SSP
  184. help
  185. This enables using a PXA2xx SSP port as a SPI master controller.
  186. The driver can be configured to use any SSP port and additional
  187. documentation can be found a Documentation/spi/pxa2xx.
  188. config SPI_S3C24XX
  189. tristate "Samsung S3C24XX series SPI"
  190. depends on ARCH_S3C2410 && EXPERIMENTAL
  191. select SPI_BITBANG
  192. help
  193. SPI driver for Samsung S3C24XX series ARM SoCs
  194. config SPI_S3C24XX_FIQ
  195. bool "S3C24XX driver with FIQ pseudo-DMA"
  196. depends on SPI_S3C24XX
  197. select FIQ
  198. help
  199. Enable FIQ support for the S3C24XX SPI driver to provide pseudo
  200. DMA by using the fast-interrupt request framework, This allows
  201. the driver to get DMA-like performance when there are either
  202. no free DMA channels, or when doing transfers that required both
  203. TX and RX data paths.
  204. config SPI_S3C24XX_GPIO
  205. tristate "Samsung S3C24XX series SPI by GPIO"
  206. depends on ARCH_S3C2410 && EXPERIMENTAL
  207. select SPI_BITBANG
  208. help
  209. SPI driver for Samsung S3C24XX series ARM SoCs using
  210. GPIO lines to provide the SPI bus. This can be used where
  211. the inbuilt hardware cannot provide the transfer mode, or
  212. where the board is using non hardware connected pins.
  213. config SPI_S3C64XX
  214. tristate "Samsung S3C64XX series type SPI"
  215. depends on ARCH_S3C64XX && EXPERIMENTAL
  216. select S3C64XX_DMA
  217. help
  218. SPI driver for Samsung S3C64XX and newer SoCs.
  219. config SPI_SH_MSIOF
  220. tristate "SuperH MSIOF SPI controller"
  221. depends on SUPERH && HAVE_CLK
  222. select SPI_BITBANG
  223. help
  224. SPI driver for SuperH MSIOF blocks.
  225. config SPI_SH_SCI
  226. tristate "SuperH SCI SPI controller"
  227. depends on SUPERH
  228. select SPI_BITBANG
  229. help
  230. SPI driver for SuperH SCI blocks.
  231. config SPI_STMP3XXX
  232. tristate "Freescale STMP37xx/378x SPI/SSP controller"
  233. depends on ARCH_STMP3XXX && SPI_MASTER
  234. help
  235. SPI driver for Freescale STMP37xx/378x SoC SSP interface
  236. config SPI_TXX9
  237. tristate "Toshiba TXx9 SPI controller"
  238. depends on GENERIC_GPIO && CPU_TX49XX
  239. help
  240. SPI driver for Toshiba TXx9 MIPS SoCs
  241. config SPI_XILINX
  242. tristate "Xilinx SPI controller common module"
  243. depends on HAS_IOMEM && EXPERIMENTAL
  244. select SPI_BITBANG
  245. select SPI_XILINX_OF if (XILINX_VIRTEX || MICROBLAZE)
  246. help
  247. This exposes the SPI controller IP from the Xilinx EDK.
  248. See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
  249. Product Specification document (DS464) for hardware details.
  250. Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
  251. config SPI_XILINX_OF
  252. tristate "Xilinx SPI controller OF device"
  253. depends on SPI_XILINX && (XILINX_VIRTEX || MICROBLAZE)
  254. help
  255. This is the OF driver for the SPI controller IP from the Xilinx EDK.
  256. config SPI_XILINX_PLTFM
  257. tristate "Xilinx SPI controller platform device"
  258. depends on SPI_XILINX
  259. help
  260. This is the platform driver for the SPI controller IP
  261. from the Xilinx EDK.
  262. config SPI_NUC900
  263. tristate "Nuvoton NUC900 series SPI"
  264. depends on ARCH_W90X900 && EXPERIMENTAL
  265. select SPI_BITBANG
  266. help
  267. SPI driver for Nuvoton NUC900 series ARM SoCs
  268. #
  269. # Add new SPI master controllers in alphabetical order above this line
  270. #
  271. config SPI_DESIGNWARE
  272. bool "DesignWare SPI controller core support"
  273. depends on SPI_MASTER
  274. help
  275. general driver for SPI controller core from DesignWare
  276. config SPI_DW_PCI
  277. tristate "PCI interface driver for DW SPI core"
  278. depends on SPI_DESIGNWARE && PCI
  279. #
  280. # There are lots of SPI device types, with sensors and memory
  281. # being probably the most widely used ones.
  282. #
  283. comment "SPI Protocol Masters"
  284. config SPI_SPIDEV
  285. tristate "User mode SPI device driver support"
  286. depends on EXPERIMENTAL
  287. help
  288. This supports user mode SPI protocol drivers.
  289. Note that this application programming interface is EXPERIMENTAL
  290. and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
  291. config SPI_TLE62X0
  292. tristate "Infineon TLE62X0 (for power switching)"
  293. depends on SYSFS
  294. help
  295. SPI driver for Infineon TLE62X0 series line driver chips,
  296. such as the TLE6220, TLE6230 and TLE6240. This provides a
  297. sysfs interface, with each line presented as a kind of GPIO
  298. exposing both switch control and diagnostic feedback.
  299. #
  300. # Add new SPI protocol masters in alphabetical order above this line
  301. #
  302. endif # SPI_MASTER
  303. # (slave support would go here)
  304. endif # SPI