Kconfig 14 KB

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