Kconfig 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467
  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_MIC_X100_DMA
  30. tristate "Intel MIC X100 DMA Driver"
  31. depends on 64BIT && X86 && INTEL_MIC_BUS
  32. select DMA_ENGINE
  33. help
  34. This enables DMA support for the Intel Many Integrated Core
  35. (MIC) family of PCIe form factor coprocessor X100 devices that
  36. run a 64 bit Linux OS. This driver will be used by both MIC
  37. host and card drivers.
  38. If you are building host kernel with a MIC device or a card
  39. kernel for a MIC device, then say M (recommended) or Y, else
  40. say N. If unsure say N.
  41. More information about the Intel MIC family as well as the Linux
  42. OS and tools for MIC to use with this driver are available from
  43. <http://software.intel.com/en-us/mic-developer>.
  44. config INTEL_MID_DMAC
  45. tristate "Intel MID DMA support for Peripheral DMA controllers"
  46. depends on PCI && X86
  47. select DMA_ENGINE
  48. default n
  49. help
  50. Enable support for the Intel(R) MID DMA engine present
  51. in Intel MID chipsets.
  52. Say Y here if you have such a chipset.
  53. If unsure, say N.
  54. config ASYNC_TX_ENABLE_CHANNEL_SWITCH
  55. bool
  56. config AMBA_PL08X
  57. bool "ARM PrimeCell PL080 or PL081 support"
  58. depends on ARM_AMBA
  59. select DMA_ENGINE
  60. select DMA_VIRTUAL_CHANNELS
  61. help
  62. Platform has a PL08x DMAC device
  63. which can provide DMA engine support
  64. config INTEL_IOATDMA
  65. tristate "Intel I/OAT DMA support"
  66. depends on PCI && X86
  67. select DMA_ENGINE
  68. select DMA_ENGINE_RAID
  69. select DCA
  70. help
  71. Enable support for the Intel(R) I/OAT DMA engine present
  72. in recent Intel Xeon chipsets.
  73. Say Y here if you have such a chipset.
  74. If unsure, say N.
  75. config INTEL_IOP_ADMA
  76. tristate "Intel IOP ADMA support"
  77. depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
  78. select DMA_ENGINE
  79. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  80. help
  81. Enable support for the Intel(R) IOP Series RAID engines.
  82. source "drivers/dma/dw/Kconfig"
  83. config AT_HDMAC
  84. tristate "Atmel AHB DMA support"
  85. depends on ARCH_AT91
  86. select DMA_ENGINE
  87. help
  88. Support the Atmel AHB DMA controller.
  89. config AT_XDMAC
  90. tristate "Atmel XDMA support"
  91. depends on ARCH_AT91
  92. select DMA_ENGINE
  93. help
  94. Support the Atmel XDMA controller.
  95. config FSL_DMA
  96. tristate "Freescale Elo series DMA support"
  97. depends on FSL_SOC
  98. select DMA_ENGINE
  99. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  100. ---help---
  101. Enable support for the Freescale Elo series DMA controllers.
  102. The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the
  103. EloPlus is on mpc85xx and mpc86xx and Pxxx parts, and the Elo3 is on
  104. some Txxx and Bxxx parts.
  105. config MPC512X_DMA
  106. tristate "Freescale MPC512x built-in DMA engine support"
  107. depends on PPC_MPC512x || PPC_MPC831x
  108. select DMA_ENGINE
  109. ---help---
  110. Enable support for the Freescale MPC512x built-in DMA engine.
  111. source "drivers/dma/bestcomm/Kconfig"
  112. config MV_XOR
  113. bool "Marvell XOR engine support"
  114. depends on PLAT_ORION
  115. select DMA_ENGINE
  116. select DMA_ENGINE_RAID
  117. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  118. ---help---
  119. Enable support for the Marvell XOR engine.
  120. config MX3_IPU
  121. bool "MX3x Image Processing Unit support"
  122. depends on ARCH_MXC
  123. select DMA_ENGINE
  124. default y
  125. help
  126. If you plan to use the Image Processing unit in the i.MX3x, say
  127. Y here. If unsure, select Y.
  128. config MX3_IPU_IRQS
  129. int "Number of dynamically mapped interrupts for IPU"
  130. depends on MX3_IPU
  131. range 2 137
  132. default 4
  133. help
  134. Out of 137 interrupt sources on i.MX31 IPU only very few are used.
  135. To avoid bloating the irq_desc[] array we allocate a sufficient
  136. number of IRQ slots and map them dynamically to specific sources.
  137. config TXX9_DMAC
  138. tristate "Toshiba TXx9 SoC DMA support"
  139. depends on MACH_TX49XX || MACH_TX39XX
  140. select DMA_ENGINE
  141. help
  142. Support the TXx9 SoC internal DMA controller. This can be
  143. integrated in chips such as the Toshiba TX4927/38/39.
  144. config TEGRA20_APB_DMA
  145. bool "NVIDIA Tegra20 APB DMA support"
  146. depends on ARCH_TEGRA
  147. select DMA_ENGINE
  148. help
  149. Support for the NVIDIA Tegra20 APB DMA controller driver. The
  150. DMA controller is having multiple DMA channel which can be
  151. configured for different peripherals like audio, UART, SPI,
  152. I2C etc which is in APB bus.
  153. This DMA controller transfers data from memory to peripheral fifo
  154. or vice versa. It does not support memory to memory data transfer.
  155. config S3C24XX_DMAC
  156. tristate "Samsung S3C24XX DMA support"
  157. depends on ARCH_S3C24XX && !S3C24XX_DMA
  158. select DMA_ENGINE
  159. select DMA_VIRTUAL_CHANNELS
  160. help
  161. Support for the Samsung S3C24XX DMA controller driver. The
  162. DMA controller is having multiple DMA channels which can be
  163. configured for different peripherals like audio, UART, SPI.
  164. The DMA controller can transfer data from memory to peripheral,
  165. periphal to memory, periphal to periphal and memory to memory.
  166. source "drivers/dma/sh/Kconfig"
  167. config COH901318
  168. bool "ST-Ericsson COH901318 DMA support"
  169. select DMA_ENGINE
  170. depends on ARCH_U300
  171. help
  172. Enable support for ST-Ericsson COH 901 318 DMA.
  173. config STE_DMA40
  174. bool "ST-Ericsson DMA40 support"
  175. depends on ARCH_U8500
  176. select DMA_ENGINE
  177. help
  178. Support for ST-Ericsson DMA40 controller
  179. config AMCC_PPC440SPE_ADMA
  180. tristate "AMCC PPC440SPe ADMA support"
  181. depends on 440SPe || 440SP
  182. select DMA_ENGINE
  183. select DMA_ENGINE_RAID
  184. select ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  185. select ASYNC_TX_ENABLE_CHANNEL_SWITCH
  186. help
  187. Enable support for the AMCC PPC440SPe RAID engines.
  188. config TIMB_DMA
  189. tristate "Timberdale FPGA DMA support"
  190. depends on MFD_TIMBERDALE
  191. select DMA_ENGINE
  192. help
  193. Enable support for the Timberdale FPGA DMA engine.
  194. config SIRF_DMA
  195. tristate "CSR SiRFprimaII/SiRFmarco DMA support"
  196. depends on ARCH_SIRF
  197. select DMA_ENGINE
  198. help
  199. Enable support for the CSR SiRFprimaII DMA engine.
  200. config TI_EDMA
  201. bool "TI EDMA support"
  202. depends on ARCH_DAVINCI || ARCH_OMAP || ARCH_KEYSTONE
  203. select DMA_ENGINE
  204. select DMA_VIRTUAL_CHANNELS
  205. select TI_PRIV_EDMA
  206. default n
  207. help
  208. Enable support for the TI EDMA controller. This DMA
  209. engine is found on TI DaVinci and AM33xx parts.
  210. config ARCH_HAS_ASYNC_TX_FIND_CHANNEL
  211. bool
  212. config PL330_DMA
  213. tristate "DMA API Driver for PL330"
  214. select DMA_ENGINE
  215. depends on ARM_AMBA
  216. help
  217. Select if your platform has one or more PL330 DMACs.
  218. You need to provide platform specific settings via
  219. platform_data for a dma-pl330 device.
  220. config PCH_DMA
  221. tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA"
  222. depends on PCI && (X86_32 || COMPILE_TEST)
  223. select DMA_ENGINE
  224. help
  225. Enable support for Intel EG20T PCH DMA engine.
  226. This driver also can be used for LAPIS Semiconductor IOH(Input/
  227. Output Hub), ML7213, ML7223 and ML7831.
  228. ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is
  229. for MP(Media Phone) use and ML7831 IOH is for general purpose use.
  230. ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series.
  231. ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH.
  232. config IMX_SDMA
  233. tristate "i.MX SDMA support"
  234. depends on ARCH_MXC
  235. select DMA_ENGINE
  236. help
  237. Support the i.MX SDMA engine. This engine is integrated into
  238. Freescale i.MX25/31/35/51/53/6 chips.
  239. config IMX_DMA
  240. tristate "i.MX DMA support"
  241. depends on ARCH_MXC
  242. select DMA_ENGINE
  243. help
  244. Support the i.MX DMA engine. This engine is integrated into
  245. Freescale i.MX1/21/27 chips.
  246. config MXS_DMA
  247. bool "MXS DMA support"
  248. depends on SOC_IMX23 || SOC_IMX28 || SOC_IMX6Q
  249. select STMP_DEVICE
  250. select DMA_ENGINE
  251. help
  252. Support the MXS DMA engine. This engine including APBH-DMA
  253. and APBX-DMA is integrated into Freescale i.MX23/28/MX6Q/MX6DL chips.
  254. config EP93XX_DMA
  255. bool "Cirrus Logic EP93xx DMA support"
  256. depends on ARCH_EP93XX
  257. select DMA_ENGINE
  258. help
  259. Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller.
  260. config DMA_SA11X0
  261. tristate "SA-11x0 DMA support"
  262. depends on ARCH_SA1100
  263. select DMA_ENGINE
  264. select DMA_VIRTUAL_CHANNELS
  265. help
  266. Support the DMA engine found on Intel StrongARM SA-1100 and
  267. SA-1110 SoCs. This DMA engine can only be used with on-chip
  268. devices.
  269. config MMP_TDMA
  270. bool "MMP Two-Channel DMA support"
  271. depends on ARCH_MMP
  272. select DMA_ENGINE
  273. select MMP_SRAM
  274. help
  275. Support the MMP Two-Channel DMA engine.
  276. This engine used for MMP Audio DMA and pxa910 SQU.
  277. It needs sram driver under mach-mmp.
  278. Say Y here if you enabled MMP ADMA, otherwise say N.
  279. config DMA_OMAP
  280. tristate "OMAP DMA support"
  281. depends on ARCH_OMAP
  282. select DMA_ENGINE
  283. select DMA_VIRTUAL_CHANNELS
  284. config DMA_BCM2835
  285. tristate "BCM2835 DMA engine support"
  286. depends on ARCH_BCM2835
  287. select DMA_ENGINE
  288. select DMA_VIRTUAL_CHANNELS
  289. config TI_CPPI41
  290. tristate "AM33xx CPPI41 DMA support"
  291. depends on ARCH_OMAP
  292. select DMA_ENGINE
  293. help
  294. The Communications Port Programming Interface (CPPI) 4.1 DMA engine
  295. is currently used by the USB driver on AM335x platforms.
  296. config MMP_PDMA
  297. bool "MMP PDMA support"
  298. depends on (ARCH_MMP || ARCH_PXA)
  299. select DMA_ENGINE
  300. help
  301. Support the MMP PDMA engine for PXA and MMP platform.
  302. config DMA_JZ4740
  303. tristate "JZ4740 DMA support"
  304. depends on MACH_JZ4740
  305. select DMA_ENGINE
  306. select DMA_VIRTUAL_CHANNELS
  307. config K3_DMA
  308. tristate "Hisilicon K3 DMA support"
  309. depends on ARCH_HI3xxx
  310. select DMA_ENGINE
  311. select DMA_VIRTUAL_CHANNELS
  312. help
  313. Support the DMA engine for Hisilicon K3 platform
  314. devices.
  315. config MOXART_DMA
  316. tristate "MOXART DMA support"
  317. depends on ARCH_MOXART
  318. select DMA_ENGINE
  319. select DMA_OF
  320. select DMA_VIRTUAL_CHANNELS
  321. help
  322. Enable support for the MOXA ART SoC DMA controller.
  323. config FSL_EDMA
  324. tristate "Freescale eDMA engine support"
  325. depends on OF
  326. select DMA_ENGINE
  327. select DMA_VIRTUAL_CHANNELS
  328. help
  329. Support the Freescale eDMA engine with programmable channel
  330. multiplexing capability for DMA request sources(slot).
  331. This module can be found on Freescale Vybrid and LS-1 SoCs.
  332. config XILINX_VDMA
  333. tristate "Xilinx AXI VDMA Engine"
  334. depends on (ARCH_ZYNQ || MICROBLAZE)
  335. select DMA_ENGINE
  336. help
  337. Enable support for Xilinx AXI VDMA Soft IP.
  338. This engine provides high-bandwidth direct memory access
  339. between memory and AXI4-Stream video type target
  340. peripherals including peripherals which support AXI4-
  341. Stream Video Protocol. It has two stream interfaces/
  342. channels, Memory Mapped to Stream (MM2S) and Stream to
  343. Memory Mapped (S2MM) for the data transfers.
  344. config DMA_SUN6I
  345. tristate "Allwinner A31 SoCs DMA support"
  346. depends on MACH_SUN6I || MACH_SUN8I || COMPILE_TEST
  347. depends on RESET_CONTROLLER
  348. select DMA_ENGINE
  349. select DMA_VIRTUAL_CHANNELS
  350. help
  351. Support for the DMA engine first found in Allwinner A31 SoCs.
  352. config NBPFAXI_DMA
  353. tristate "Renesas Type-AXI NBPF DMA support"
  354. select DMA_ENGINE
  355. depends on ARM || COMPILE_TEST
  356. help
  357. Support for "Type-AXI" NBPF DMA IPs from Renesas
  358. config DMA_ENGINE
  359. bool
  360. config DMA_VIRTUAL_CHANNELS
  361. tristate
  362. config DMA_ACPI
  363. def_bool y
  364. depends on ACPI
  365. config DMA_OF
  366. def_bool y
  367. depends on OF
  368. select DMA_ENGINE
  369. comment "DMA Clients"
  370. depends on DMA_ENGINE
  371. config ASYNC_TX_DMA
  372. bool "Async_tx: Offload support for the async_tx api"
  373. depends on DMA_ENGINE
  374. help
  375. This allows the async_tx api to take advantage of offload engines for
  376. memcpy, memset, xor, and raid6 p+q operations. If your platform has
  377. a dma engine that can perform raid operations and you have enabled
  378. MD_RAID456 say Y.
  379. If unsure, say N.
  380. config DMATEST
  381. tristate "DMA Test client"
  382. depends on DMA_ENGINE
  383. help
  384. Simple DMA test client. Say N unless you're debugging a
  385. DMA Device driver.
  386. config DMA_ENGINE_RAID
  387. bool
  388. config QCOM_BAM_DMA
  389. tristate "QCOM BAM DMA support"
  390. depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
  391. select DMA_ENGINE
  392. select DMA_VIRTUAL_CHANNELS
  393. ---help---
  394. Enable support for the QCOM BAM DMA controller. This controller
  395. provides DMA capabilities for a variety of on-chip devices.
  396. endif