Kconfig 8.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333
  1. #
  2. # DMA engine configuration
  3. #
  4. menuconfig DMADEVICES
  5. bool "DMA Engine support"
  6. depends on HAS_DMA
  7. help
  8. DMA engines can do asynchronous data transfers without
  9. involving the host CPU. Currently, this framework can be
  10. used to offload memory copies in the network stack and
  11. RAID operations in the MD driver. This menu only presents
  12. DMA Device drivers supported by the configured arch, it may
  13. be empty in some cases.
  14. config DMADEVICES_DEBUG
  15. bool "DMA Engine debugging"
  16. depends on DMADEVICES != n
  17. help
  18. This is an option for use by developers; most people should
  19. say N here. This enables DMA engine core and driver debugging.
  20. config DMADEVICES_VDEBUG
  21. bool "DMA Engine verbose debugging"
  22. depends on DMADEVICES_DEBUG != n
  23. help
  24. This is an option for use by developers; most people should
  25. say N here. This enables deeper (more verbose) debugging of
  26. the DMA engine core and drivers.
  27. if DMADEVICES
  28. comment "DMA Devices"
  29. config INTEL_MID_DMAC
  30. tristate "Intel MID DMA support for Peripheral DMA controllers"
  31. depends on PCI && X86
  32. select DMA_ENGINE
  33. default n
  34. help
  35. Enable support for the Intel(R) MID DMA engine present
  36. in Intel MID chipsets.
  37. Say Y here if you have such a chipset.
  38. If unsure, say N.
  39. config ASYNC_TX_ENABLE_CHANNEL_SWITCH
  40. bool
  41. config AMBA_PL08X
  42. bool "ARM PrimeCell PL080 or PL081 support"
  43. depends on ARM_AMBA && EXPERIMENTAL
  44. select DMA_ENGINE
  45. select DMA_VIRTUAL_CHANNELS
  46. help
  47. Platform has a PL08x DMAC device
  48. which can provide DMA engine support
  49. config INTEL_IOATDMA
  50. tristate "Intel I/OAT DMA support"
  51. depends on PCI && X86
  52. select DMA_ENGINE
  53. select DCA
  54. select ASYNC_TX_DISABLE_PQ_VAL_DMA
  55. select ASYNC_TX_DISABLE_XOR_VAL_DMA
  56. help
  57. Enable support for the Intel(R) I/OAT DMA engine present
  58. in recent Intel Xeon chipsets.
  59. Say Y here if you have such a chipset.
  60. If unsure, say N.
  61. config INTEL_IOP_ADMA
  62. tristate "Intel IOP ADMA support"
  63. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
  64. select DMA_ENGINE
  65. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  66. help
  67. Enable support for the Intel(R) IOP Series RAID engines.
  68. config DW_DMAC
  69. tristate "Synopsys DesignWare AHB DMA support"
  70. depends on HAVE_CLK
  71. select DMA_ENGINE
  72. default y if CPU_AT32AP7000
  73. help
  74. Support the Synopsys DesignWare AHB DMA controller. This
  75. can be integrated in chips such as the Atmel AT32ap7000.
  76. config AT_HDMAC
  77. tristate "Atmel AHB DMA support"
  78. depends on ARCH_AT91
  79. select DMA_ENGINE
  80. help
  81. Support the Atmel AHB DMA controller.
  82. config FSL_DMA
  83. tristate "Freescale Elo and Elo Plus DMA support"
  84. depends on FSL_SOC
  85. select DMA_ENGINE
  86. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  87. ---help---
  88. Enable support for the Freescale Elo and Elo Plus DMA controllers.
  89. The Elo is the DMA controller on some 82xx and 83xx parts, and the
  90. Elo Plus is the DMA controller on 85xx and 86xx parts.
  91. config MPC512X_DMA
  92. tristate "Freescale MPC512x built-in DMA engine support"
  93. depends on PPC_MPC512x || PPC_MPC831x
  94. select DMA_ENGINE
  95. ---help---
  96. Enable support for the Freescale MPC512x built-in DMA engine.
  97. config MV_XOR
  98. bool "Marvell XOR engine support"
  99. depends on PLAT_ORION
  100. select DMA_ENGINE
  101. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  102. ---help---
  103. Enable support for the Marvell XOR engine.
  104. config MX3_IPU
  105. bool "MX3x Image Processing Unit support"
  106. depends on ARCH_MXC
  107. select DMA_ENGINE
  108. default y
  109. help
  110. If you plan to use the Image Processing unit in the i.MX3x, say
  111. Y here. If unsure, select Y.
  112. config MX3_IPU_IRQS
  113. int "Number of dynamically mapped interrupts for IPU"
  114. depends on MX3_IPU
  115. range 2 137
  116. default 4
  117. help
  118. Out of 137 interrupt sources on i.MX31 IPU only very few are used.
  119. To avoid bloating the irq_desc[] array we allocate a sufficient
  120. number of IRQ slots and map them dynamically to specific sources.
  121. config TXX9_DMAC
  122. tristate "Toshiba TXx9 SoC DMA support"
  123. depends on MACH_TX49XX || MACH_TX39XX
  124. select DMA_ENGINE
  125. help
  126. Support the TXx9 SoC internal DMA controller. This can be
  127. integrated in chips such as the Toshiba TX4927/38/39.
  128. config TEGRA20_APB_DMA
  129. bool "NVIDIA Tegra20 APB DMA support"
  130. depends on ARCH_TEGRA
  131. select DMA_ENGINE
  132. help
  133. Support for the NVIDIA Tegra20 APB DMA controller driver. The
  134. DMA controller is having multiple DMA channel which can be
  135. configured for different peripherals like audio, UART, SPI,
  136. I2C etc which is in APB bus.
  137. This DMA controller transfers data from memory to peripheral fifo
  138. or vice versa. It does not support memory to memory data transfer.
  139. config SH_DMAE
  140. tristate "Renesas SuperH DMAC support"
  141. depends on (SUPERH && SH_DMA) || (ARM && ARCH_SHMOBILE)
  142. depends on !SH_DMA_API
  143. select DMA_ENGINE
  144. help
  145. Enable support for the Renesas SuperH DMA controllers.
  146. config COH901318
  147. bool "ST-Ericsson COH901318 DMA support"
  148. select DMA_ENGINE
  149. depends on ARCH_U300
  150. help
  151. Enable support for ST-Ericsson COH 901 318 DMA.
  152. config STE_DMA40
  153. bool "ST-Ericsson DMA40 support"
  154. depends on ARCH_U8500
  155. select DMA_ENGINE
  156. help
  157. Support for ST-Ericsson DMA40 controller
  158. config AMCC_PPC440SPE_ADMA
  159. tristate "AMCC PPC440SPe ADMA support"
  160. depends on 440SPe || 440SP
  161. select DMA_ENGINE
  162. select ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  163. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  164. help
  165. Enable support for the AMCC PPC440SPe RAID engines.
  166. config TIMB_DMA
  167. tristate "Timberdale FPGA DMA support"
  168. depends on MFD_TIMBERDALE || HAS_IOMEM
  169. select DMA_ENGINE
  170. help
  171. Enable support for the Timberdale FPGA DMA engine.
  172. config SIRF_DMA
  173. tristate "CSR SiRFprimaII DMA support"
  174. depends on ARCH_PRIMA2
  175. select DMA_ENGINE
  176. help
  177. Enable support for the CSR SiRFprimaII DMA engine.
  178. config ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  179. bool
  180. config PL330_DMA
  181. tristate "DMA API Driver for PL330"
  182. select DMA_ENGINE
  183. depends on ARM_AMBA
  184. help
  185. Select if your platform has one or more PL330 DMACs.
  186. You need to provide platform specific settings via
  187. platform_data for a dma-pl330 device.
  188. config PCH_DMA
  189. tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA"
  190. depends on PCI && X86
  191. select DMA_ENGINE
  192. help
  193. Enable support for Intel EG20T PCH DMA engine.
  194. This driver also can be used for LAPIS Semiconductor IOH(Input/
  195. Output Hub), ML7213, ML7223 and ML7831.
  196. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  197. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  198. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  199. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  200. config IMX_SDMA
  201. tristate "i.MX SDMA support"
  202. depends on ARCH_MXC
  203. select DMA_ENGINE
  204. help
  205. Support the i.MX SDMA engine. This engine is integrated into
  206. Freescale i.MX25/31/35/51/53 chips.
  207. config IMX_DMA
  208. tristate "i.MX DMA support"
  209. depends on ARCH_MXC
  210. select DMA_ENGINE
  211. help
  212. Support the i.MX DMA engine. This engine is integrated into
  213. Freescale i.MX1/21/27 chips.
  214. config MXS_DMA
  215. bool "MXS DMA support"
  216. depends on SOC_IMX23 || SOC_IMX28 || SOC_IMX6Q
  217. select STMP_DEVICE
  218. select DMA_ENGINE
  219. help
  220. Support the MXS DMA engine. This engine including APBH-DMA
  221. and APBX-DMA is integrated into Freescale i.MX23/28 chips.
  222. config EP93XX_DMA
  223. bool "Cirrus Logic EP93xx DMA support"
  224. depends on ARCH_EP93XX
  225. select DMA_ENGINE
  226. help
  227. Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller.
  228. config DMA_SA11X0
  229. tristate "SA-11x0 DMA support"
  230. depends on ARCH_SA1100
  231. select DMA_ENGINE
  232. select DMA_VIRTUAL_CHANNELS
  233. help
  234. Support the DMA engine found on Intel StrongARM SA-1100 and
  235. SA-1110 SoCs. This DMA engine can only be used with on-chip
  236. devices.
  237. config MMP_TDMA
  238. bool "MMP Two-Channel DMA support"
  239. depends on ARCH_MMP
  240. select DMA_ENGINE
  241. help
  242. Support the MMP Two-Channel DMA engine.
  243. This engine used for MMP Audio DMA and pxa910 SQU.
  244. Say Y here if you enabled MMP ADMA, otherwise say N.
  245. config DMA_OMAP
  246. tristate "OMAP DMA support"
  247. depends on ARCH_OMAP
  248. select DMA_ENGINE
  249. select DMA_VIRTUAL_CHANNELS
  250. config DMA_ENGINE
  251. bool
  252. config DMA_VIRTUAL_CHANNELS
  253. tristate
  254. comment "DMA Clients"
  255. depends on DMA_ENGINE
  256. config NET_DMA
  257. bool "Network: TCP receive copy offload"
  258. depends on DMA_ENGINE && NET
  259. default (INTEL_IOATDMA || FSL_DMA)
  260. help
  261. This enables the use of DMA engines in the network stack to
  262. offload receive copy-to-user operations, freeing CPU cycles.
  263. Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
  264. say N.
  265. config ASYNC_TX_DMA
  266. bool "Async_tx: Offload support for the async_tx api"
  267. depends on DMA_ENGINE
  268. help
  269. This allows the async_tx api to take advantage of offload engines for
  270. memcpy, memset, xor, and raid6 p+q operations. If your platform has
  271. a dma engine that can perform raid operations and you have enabled
  272. MD_RAID456 say Y.
  273. If unsure, say N.
  274. config DMATEST
  275. tristate "DMA Test client"
  276. depends on DMA_ENGINE
  277. help
  278. Simple DMA test client. Say N unless you're debugging a
  279. DMA Device driver.
  280. endif