Kconfig 9.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366
  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
  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. help
  55. Enable support for the Intel(R) I/OAT DMA engine present
  56. in recent Intel Xeon chipsets.
  57. Say Y here if you have such a chipset.
  58. If unsure, say N.
  59. config INTEL_IOP_ADMA
  60. tristate "Intel IOP ADMA support"
  61. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
  62. select DMA_ENGINE
  63. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  64. help
  65. Enable support for the Intel(R) IOP Series RAID engines.
  66. source "drivers/dma/dw/Kconfig"
  67. config AT_HDMAC
  68. tristate "Atmel AHB DMA support"
  69. depends on ARCH_AT91
  70. select DMA_ENGINE
  71. help
  72. Support the Atmel AHB DMA controller.
  73. config FSL_DMA
  74. tristate "Freescale Elo and Elo Plus DMA support"
  75. depends on FSL_SOC
  76. select DMA_ENGINE
  77. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  78. ---help---
  79. Enable support for the Freescale Elo and Elo Plus DMA controllers.
  80. The Elo is the DMA controller on some 82xx and 83xx parts, and the
  81. Elo Plus is the DMA controller on 85xx and 86xx parts.
  82. config MPC512X_DMA
  83. tristate "Freescale MPC512x built-in DMA engine support"
  84. depends on PPC_MPC512x || PPC_MPC831x
  85. select DMA_ENGINE
  86. ---help---
  87. Enable support for the Freescale MPC512x built-in DMA engine.
  88. source "drivers/dma/bestcomm/Kconfig"
  89. config MV_XOR
  90. bool "Marvell XOR engine support"
  91. depends on PLAT_ORION
  92. select DMA_ENGINE
  93. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  94. ---help---
  95. Enable support for the Marvell XOR engine.
  96. config MX3_IPU
  97. bool "MX3x Image Processing Unit support"
  98. depends on ARCH_MXC
  99. select DMA_ENGINE
  100. default y
  101. help
  102. If you plan to use the Image Processing unit in the i.MX3x, say
  103. Y here. If unsure, select Y.
  104. config MX3_IPU_IRQS
  105. int "Number of dynamically mapped interrupts for IPU"
  106. depends on MX3_IPU
  107. range 2 137
  108. default 4
  109. help
  110. Out of 137 interrupt sources on i.MX31 IPU only very few are used.
  111. To avoid bloating the irq_desc[] array we allocate a sufficient
  112. number of IRQ slots and map them dynamically to specific sources.
  113. config TXX9_DMAC
  114. tristate "Toshiba TXx9 SoC DMA support"
  115. depends on MACH_TX49XX || MACH_TX39XX
  116. select DMA_ENGINE
  117. help
  118. Support the TXx9 SoC internal DMA controller. This can be
  119. integrated in chips such as the Toshiba TX4927/38/39.
  120. config TEGRA20_APB_DMA
  121. bool "NVIDIA Tegra20 APB DMA support"
  122. depends on ARCH_TEGRA
  123. select DMA_ENGINE
  124. help
  125. Support for the NVIDIA Tegra20 APB DMA controller driver. The
  126. DMA controller is having multiple DMA channel which can be
  127. configured for different peripherals like audio, UART, SPI,
  128. I2C etc which is in APB bus.
  129. This DMA controller transfers data from memory to peripheral fifo
  130. or vice versa. It does not support memory to memory data transfer.
  131. source "drivers/dma/sh/Kconfig"
  132. config COH901318
  133. bool "ST-Ericsson COH901318 DMA support"
  134. select DMA_ENGINE
  135. depends on ARCH_U300
  136. help
  137. Enable support for ST-Ericsson COH 901 318 DMA.
  138. config STE_DMA40
  139. bool "ST-Ericsson DMA40 support"
  140. depends on ARCH_U8500
  141. select DMA_ENGINE
  142. help
  143. Support for ST-Ericsson DMA40 controller
  144. config AMCC_PPC440SPE_ADMA
  145. tristate "AMCC PPC440SPe ADMA support"
  146. depends on 440SPe || 440SP
  147. select DMA_ENGINE
  148. select ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  149. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  150. help
  151. Enable support for the AMCC PPC440SPe RAID engines.
  152. config TIMB_DMA
  153. tristate "Timberdale FPGA DMA support"
  154. depends on MFD_TIMBERDALE || HAS_IOMEM
  155. select DMA_ENGINE
  156. help
  157. Enable support for the Timberdale FPGA DMA engine.
  158. config SIRF_DMA
  159. tristate "CSR SiRFprimaII/SiRFmarco DMA support"
  160. depends on ARCH_SIRF
  161. select DMA_ENGINE
  162. help
  163. Enable support for the CSR SiRFprimaII DMA engine.
  164. config TI_EDMA
  165. bool "TI EDMA support"
  166. depends on ARCH_DAVINCI || ARCH_OMAP
  167. select DMA_ENGINE
  168. select DMA_VIRTUAL_CHANNELS
  169. default n
  170. help
  171. Enable support for the TI EDMA controller. This DMA
  172. engine is found on TI DaVinci and AM33xx parts.
  173. config ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  174. bool
  175. config PL330_DMA
  176. tristate "DMA API Driver for PL330"
  177. select DMA_ENGINE
  178. depends on ARM_AMBA
  179. help
  180. Select if your platform has one or more PL330 DMACs.
  181. You need to provide platform specific settings via
  182. platform_data for a dma-pl330 device.
  183. config PCH_DMA
  184. tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA"
  185. depends on PCI && X86
  186. select DMA_ENGINE
  187. help
  188. Enable support for Intel EG20T PCH DMA engine.
  189. This driver also can be used for LAPIS Semiconductor IOH(Input/
  190. Output Hub), ML7213, ML7223 and ML7831.
  191. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  192. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  193. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  194. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  195. config IMX_SDMA
  196. tristate "i.MX SDMA support"
  197. depends on ARCH_MXC
  198. select DMA_ENGINE
  199. help
  200. Support the i.MX SDMA engine. This engine is integrated into
  201. Freescale i.MX25/31/35/51/53 chips.
  202. config IMX_DMA
  203. tristate "i.MX DMA support"
  204. depends on ARCH_MXC
  205. select DMA_ENGINE
  206. help
  207. Support the i.MX DMA engine. This engine is integrated into
  208. Freescale i.MX1/21/27 chips.
  209. config MXS_DMA
  210. bool "MXS DMA support"
  211. depends on SOC_IMX23 || SOC_IMX28 || SOC_IMX6Q
  212. select STMP_DEVICE
  213. select DMA_ENGINE
  214. help
  215. Support the MXS DMA engine. This engine including APBH-DMA
  216. and APBX-DMA is integrated into Freescale i.MX23/28 chips.
  217. config EP93XX_DMA
  218. bool "Cirrus Logic EP93xx DMA support"
  219. depends on ARCH_EP93XX
  220. select DMA_ENGINE
  221. help
  222. Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller.
  223. config DMA_SA11X0
  224. tristate "SA-11x0 DMA support"
  225. depends on ARCH_SA1100
  226. select DMA_ENGINE
  227. select DMA_VIRTUAL_CHANNELS
  228. help
  229. Support the DMA engine found on Intel StrongARM SA-1100 and
  230. SA-1110 SoCs. This DMA engine can only be used with on-chip
  231. devices.
  232. config MMP_TDMA
  233. bool "MMP Two-Channel DMA support"
  234. depends on ARCH_MMP
  235. select DMA_ENGINE
  236. help
  237. Support the MMP Two-Channel DMA engine.
  238. This engine used for MMP Audio DMA and pxa910 SQU.
  239. Say Y here if you enabled MMP ADMA, otherwise say N.
  240. config DMA_OMAP
  241. tristate "OMAP DMA support"
  242. depends on ARCH_OMAP
  243. select DMA_ENGINE
  244. select DMA_VIRTUAL_CHANNELS
  245. config TI_CPPI41
  246. tristate "AM33xx CPPI41 DMA support"
  247. depends on ARCH_OMAP
  248. select DMA_ENGINE
  249. help
  250. The Communications Port Programming Interface (CPPI) 4.1 DMA engine
  251. is currently used by the USB driver on AM335x platforms.
  252. config MMP_PDMA
  253. bool "MMP PDMA support"
  254. depends on (ARCH_MMP || ARCH_PXA)
  255. select DMA_ENGINE
  256. help
  257. Support the MMP PDMA engine for PXA and MMP platfrom.
  258. config DMA_JZ4740
  259. tristate "JZ4740 DMA support"
  260. depends on MACH_JZ4740
  261. select DMA_ENGINE
  262. select DMA_VIRTUAL_CHANNELS
  263. config K3_DMA
  264. tristate "Hisilicon K3 DMA support"
  265. depends on ARCH_HI3xxx
  266. select DMA_ENGINE
  267. select DMA_VIRTUAL_CHANNELS
  268. help
  269. Support the DMA engine for Hisilicon K3 platform
  270. devices.
  271. config DMA_ENGINE
  272. bool
  273. config DMA_VIRTUAL_CHANNELS
  274. tristate
  275. config DMA_ACPI
  276. def_bool y
  277. depends on ACPI
  278. config DMA_OF
  279. def_bool y
  280. depends on OF
  281. comment "DMA Clients"
  282. depends on DMA_ENGINE
  283. config NET_DMA
  284. bool "Network: TCP receive copy offload"
  285. depends on DMA_ENGINE && NET
  286. default (INTEL_IOATDMA || FSL_DMA)
  287. help
  288. This enables the use of DMA engines in the network stack to
  289. offload receive copy-to-user operations, freeing CPU cycles.
  290. Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
  291. say N.
  292. config ASYNC_TX_DMA
  293. bool "Async_tx: Offload support for the async_tx api"
  294. depends on DMA_ENGINE
  295. help
  296. This allows the async_tx api to take advantage of offload engines for
  297. memcpy, memset, xor, and raid6 p+q operations. If your platform has
  298. a dma engine that can perform raid operations and you have enabled
  299. MD_RAID456 say Y.
  300. If unsure, say N.
  301. config DMATEST
  302. tristate "DMA Test client"
  303. depends on DMA_ENGINE
  304. help
  305. Simple DMA test client. Say N unless you're debugging a
  306. DMA Device driver.
  307. endif