Kconfig 9.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378
  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. config S3C24XX_DMAC
  132. tristate "Samsung S3C24XX DMA support"
  133. depends on ARCH_S3C24XX && !S3C24XX_DMA
  134. select DMA_ENGINE
  135. select DMA_VIRTUAL_CHANNELS
  136. help
  137. Support for the Samsung S3C24XX DMA controller driver. The
  138. DMA controller is having multiple DMA channels which can be
  139. configured for different peripherals like audio, UART, SPI.
  140. The DMA controller can transfer data from memory to peripheral,
  141. periphal to memory, periphal to periphal and memory to memory.
  142. source "drivers/dma/sh/Kconfig"
  143. config COH901318
  144. bool "ST-Ericsson COH901318 DMA support"
  145. select DMA_ENGINE
  146. depends on ARCH_U300
  147. help
  148. Enable support for ST-Ericsson COH 901 318 DMA.
  149. config STE_DMA40
  150. bool "ST-Ericsson DMA40 support"
  151. depends on ARCH_U8500
  152. select DMA_ENGINE
  153. help
  154. Support for ST-Ericsson DMA40 controller
  155. config AMCC_PPC440SPE_ADMA
  156. tristate "AMCC PPC440SPe ADMA support"
  157. depends on 440SPe || 440SP
  158. select DMA_ENGINE
  159. select ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  160. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  161. help
  162. Enable support for the AMCC PPC440SPe RAID engines.
  163. config TIMB_DMA
  164. tristate "Timberdale FPGA DMA support"
  165. depends on MFD_TIMBERDALE || HAS_IOMEM
  166. select DMA_ENGINE
  167. help
  168. Enable support for the Timberdale FPGA DMA engine.
  169. config SIRF_DMA
  170. tristate "CSR SiRFprimaII/SiRFmarco DMA support"
  171. depends on ARCH_SIRF
  172. select DMA_ENGINE
  173. help
  174. Enable support for the CSR SiRFprimaII DMA engine.
  175. config TI_EDMA
  176. bool "TI EDMA support"
  177. depends on ARCH_DAVINCI || ARCH_OMAP
  178. select DMA_ENGINE
  179. select DMA_VIRTUAL_CHANNELS
  180. default n
  181. help
  182. Enable support for the TI EDMA controller. This DMA
  183. engine is found on TI DaVinci and AM33xx parts.
  184. config ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  185. bool
  186. config PL330_DMA
  187. tristate "DMA API Driver for PL330"
  188. select DMA_ENGINE
  189. depends on ARM_AMBA
  190. help
  191. Select if your platform has one or more PL330 DMACs.
  192. You need to provide platform specific settings via
  193. platform_data for a dma-pl330 device.
  194. config PCH_DMA
  195. tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA"
  196. depends on PCI && X86
  197. select DMA_ENGINE
  198. help
  199. Enable support for Intel EG20T PCH DMA engine.
  200. This driver also can be used for LAPIS Semiconductor IOH(Input/
  201. Output Hub), ML7213, ML7223 and ML7831.
  202. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  203. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  204. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  205. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  206. config IMX_SDMA
  207. tristate "i.MX SDMA support"
  208. depends on ARCH_MXC
  209. select DMA_ENGINE
  210. help
  211. Support the i.MX SDMA engine. This engine is integrated into
  212. Freescale i.MX25/31/35/51/53 chips.
  213. config IMX_DMA
  214. tristate "i.MX DMA support"
  215. depends on ARCH_MXC
  216. select DMA_ENGINE
  217. help
  218. Support the i.MX DMA engine. This engine is integrated into
  219. Freescale i.MX1/21/27 chips.
  220. config MXS_DMA
  221. bool "MXS DMA support"
  222. depends on SOC_IMX23 || SOC_IMX28 || SOC_IMX6Q
  223. select STMP_DEVICE
  224. select DMA_ENGINE
  225. help
  226. Support the MXS DMA engine. This engine including APBH-DMA
  227. and APBX-DMA is integrated into Freescale i.MX23/28 chips.
  228. config EP93XX_DMA
  229. bool "Cirrus Logic EP93xx DMA support"
  230. depends on ARCH_EP93XX
  231. select DMA_ENGINE
  232. help
  233. Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller.
  234. config DMA_SA11X0
  235. tristate "SA-11x0 DMA support"
  236. depends on ARCH_SA1100
  237. select DMA_ENGINE
  238. select DMA_VIRTUAL_CHANNELS
  239. help
  240. Support the DMA engine found on Intel StrongARM SA-1100 and
  241. SA-1110 SoCs. This DMA engine can only be used with on-chip
  242. devices.
  243. config MMP_TDMA
  244. bool "MMP Two-Channel DMA support"
  245. depends on ARCH_MMP
  246. select DMA_ENGINE
  247. help
  248. Support the MMP Two-Channel DMA engine.
  249. This engine used for MMP Audio DMA and pxa910 SQU.
  250. Say Y here if you enabled MMP ADMA, otherwise say N.
  251. config DMA_OMAP
  252. tristate "OMAP DMA support"
  253. depends on ARCH_OMAP
  254. select DMA_ENGINE
  255. select DMA_VIRTUAL_CHANNELS
  256. config TI_CPPI41
  257. tristate "AM33xx CPPI41 DMA support"
  258. depends on ARCH_OMAP
  259. select DMA_ENGINE
  260. help
  261. The Communications Port Programming Interface (CPPI) 4.1 DMA engine
  262. is currently used by the USB driver on AM335x platforms.
  263. config MMP_PDMA
  264. bool "MMP PDMA support"
  265. depends on (ARCH_MMP || ARCH_PXA)
  266. select DMA_ENGINE
  267. help
  268. Support the MMP PDMA engine for PXA and MMP platfrom.
  269. config DMA_JZ4740
  270. tristate "JZ4740 DMA support"
  271. depends on MACH_JZ4740
  272. select DMA_ENGINE
  273. select DMA_VIRTUAL_CHANNELS
  274. config K3_DMA
  275. tristate "Hisilicon K3 DMA support"
  276. depends on ARCH_HI3xxx
  277. select DMA_ENGINE
  278. select DMA_VIRTUAL_CHANNELS
  279. help
  280. Support the DMA engine for Hisilicon K3 platform
  281. devices.
  282. config DMA_ENGINE
  283. bool
  284. config DMA_VIRTUAL_CHANNELS
  285. tristate
  286. config DMA_ACPI
  287. def_bool y
  288. depends on ACPI
  289. config DMA_OF
  290. def_bool y
  291. depends on OF
  292. comment "DMA Clients"
  293. depends on DMA_ENGINE
  294. config NET_DMA
  295. bool "Network: TCP receive copy offload"
  296. depends on DMA_ENGINE && NET
  297. default (INTEL_IOATDMA || FSL_DMA)
  298. help
  299. This enables the use of DMA engines in the network stack to
  300. offload receive copy-to-user operations, freeing CPU cycles.
  301. Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
  302. say N.
  303. config ASYNC_TX_DMA
  304. bool "Async_tx: Offload support for the async_tx api"
  305. depends on DMA_ENGINE
  306. help
  307. This allows the async_tx api to take advantage of offload engines for
  308. memcpy, memset, xor, and raid6 p+q operations. If your platform has
  309. a dma engine that can perform raid operations and you have enabled
  310. MD_RAID456 say Y.
  311. If unsure, say N.
  312. config DMATEST
  313. tristate "DMA Test client"
  314. depends on DMA_ENGINE
  315. help
  316. Simple DMA test client. Say N unless you're debugging a
  317. DMA Device driver.
  318. endif