Kconfig 9.9 KB

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