Kconfig 10 KB

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