1# 2# DMA engine configuration 3# 4 5menuconfig DMADEVICES 6 bool "DMA Engine support" 7 depends on HAS_DMA 8 help 9 DMA engines can do asynchronous data transfers without 10 involving the host CPU. Currently, this framework can be 11 used to offload memory copies in the network stack and 12 RAID operations in the MD driver. This menu only presents 13 DMA Device drivers supported by the configured arch, it may 14 be empty in some cases. 15 16config DMADEVICES_DEBUG 17 bool "DMA Engine debugging" 18 depends on DMADEVICES != n 19 help 20 This is an option for use by developers; most people should 21 say N here. This enables DMA engine core and driver debugging. 22 23config DMADEVICES_VDEBUG 24 bool "DMA Engine verbose debugging" 25 depends on DMADEVICES_DEBUG != n 26 help 27 This is an option for use by developers; most people should 28 say N here. This enables deeper (more verbose) debugging of 29 the DMA engine core and drivers. 30 31 32if DMADEVICES 33 34comment "DMA Devices" 35 36#core 37config ASYNC_TX_ENABLE_CHANNEL_SWITCH 38 bool 39 40config ARCH_HAS_ASYNC_TX_FIND_CHANNEL 41 bool 42 43config DMA_ENGINE 44 bool 45 46config DMA_VIRTUAL_CHANNELS 47 tristate 48 49config DMA_ACPI 50 def_bool y 51 depends on ACPI 52 53config DMA_OF 54 def_bool y 55 depends on OF 56 select DMA_ENGINE 57 58#devices 59config ALTERA_MSGDMA 60 tristate "Altera / Intel mSGDMA Engine" 61 select DMA_ENGINE 62 help 63 Enable support for Altera / Intel mSGDMA controller. 64 65config AMBA_PL08X 66 bool "ARM PrimeCell PL080 or PL081 support" 67 depends on ARM_AMBA 68 select DMA_ENGINE 69 select DMA_VIRTUAL_CHANNELS 70 help 71 Say yes if your platform has a PL08x DMAC device which can 72 provide DMA engine support. This includes the original ARM 73 PL080 and PL081, Samsungs PL080 derivative and Faraday 74 Technology's FTDMAC020 PL080 derivative. 75 76config AMCC_PPC440SPE_ADMA 77 tristate "AMCC PPC440SPe ADMA support" 78 depends on 440SPe || 440SP 79 select DMA_ENGINE 80 select DMA_ENGINE_RAID 81 select ARCH_HAS_ASYNC_TX_FIND_CHANNEL 82 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 83 help 84 Enable support for the AMCC PPC440SPe RAID engines. 85 86config AT_HDMAC 87 tristate "Atmel AHB DMA support" 88 depends on ARCH_AT91 89 select DMA_ENGINE 90 help 91 Support the Atmel AHB DMA controller. 92 93config AT_XDMAC 94 tristate "Atmel XDMA support" 95 depends on ARCH_AT91 96 select DMA_ENGINE 97 help 98 Support the Atmel XDMA controller. 99 100config AXI_DMAC 101 tristate "Analog Devices AXI-DMAC DMA support" 102 depends on MICROBLAZE || NIOS2 || ARCH_ZYNQ || ARCH_SOCFPGA || COMPILE_TEST 103 select DMA_ENGINE 104 select DMA_VIRTUAL_CHANNELS 105 help 106 Enable support for the Analog Devices AXI-DMAC peripheral. This DMA 107 controller is often used in Analog Device's reference designs for FPGA 108 platforms. 109 110config BCM_SBA_RAID 111 tristate "Broadcom SBA RAID engine support" 112 depends on ARM64 || COMPILE_TEST 113 depends on MAILBOX && RAID6_PQ 114 select DMA_ENGINE 115 select DMA_ENGINE_RAID 116 select ASYNC_TX_DISABLE_XOR_VAL_DMA 117 select ASYNC_TX_DISABLE_PQ_VAL_DMA 118 default m if ARCH_BCM_IPROC 119 help 120 Enable support for Broadcom SBA RAID Engine. The SBA RAID 121 engine is available on most of the Broadcom iProc SoCs. It 122 has the capability to offload memcpy, xor and pq computation 123 for raid5/6. 124 125config COH901318 126 bool "ST-Ericsson COH901318 DMA support" 127 select DMA_ENGINE 128 depends on ARCH_U300 || COMPILE_TEST 129 help 130 Enable support for ST-Ericsson COH 901 318 DMA. 131 132config DMA_BCM2835 133 tristate "BCM2835 DMA engine support" 134 depends on ARCH_BCM2835 135 select DMA_ENGINE 136 select DMA_VIRTUAL_CHANNELS 137 138config DMA_JZ4740 139 tristate "JZ4740 DMA support" 140 depends on MACH_JZ4740 || COMPILE_TEST 141 select DMA_ENGINE 142 select DMA_VIRTUAL_CHANNELS 143 144config DMA_JZ4780 145 tristate "JZ4780 DMA support" 146 depends on MIPS || COMPILE_TEST 147 select DMA_ENGINE 148 select DMA_VIRTUAL_CHANNELS 149 help 150 This selects support for the DMA controller in Ingenic JZ4780 SoCs. 151 If you have a board based on such a SoC and wish to use DMA for 152 devices which can use the DMA controller, say Y or M here. 153 154config DMA_SA11X0 155 tristate "SA-11x0 DMA support" 156 depends on ARCH_SA1100 || COMPILE_TEST 157 select DMA_ENGINE 158 select DMA_VIRTUAL_CHANNELS 159 help 160 Support the DMA engine found on Intel StrongARM SA-1100 and 161 SA-1110 SoCs. This DMA engine can only be used with on-chip 162 devices. 163 164config DMA_SUN4I 165 tristate "Allwinner A10 DMA SoCs support" 166 depends on MACH_SUN4I || MACH_SUN5I || MACH_SUN7I 167 default (MACH_SUN4I || MACH_SUN5I || MACH_SUN7I) 168 select DMA_ENGINE 169 select DMA_VIRTUAL_CHANNELS 170 help 171 Enable support for the DMA controller present in the sun4i, 172 sun5i and sun7i Allwinner ARM SoCs. 173 174config DMA_SUN6I 175 tristate "Allwinner A31 SoCs DMA support" 176 depends on MACH_SUN6I || MACH_SUN8I || (ARM64 && ARCH_SUNXI) || COMPILE_TEST 177 depends on RESET_CONTROLLER 178 select DMA_ENGINE 179 select DMA_VIRTUAL_CHANNELS 180 help 181 Support for the DMA engine first found in Allwinner A31 SoCs. 182 183config DW_AXI_DMAC 184 tristate "Synopsys DesignWare AXI DMA support" 185 depends on OF || COMPILE_TEST 186 select DMA_ENGINE 187 select DMA_VIRTUAL_CHANNELS 188 help 189 Enable support for Synopsys DesignWare AXI DMA controller. 190 NOTE: This driver wasn't tested on 64 bit platform because 191 of lack 64 bit platform with Synopsys DW AXI DMAC. 192 193config EP93XX_DMA 194 bool "Cirrus Logic EP93xx DMA support" 195 depends on ARCH_EP93XX || COMPILE_TEST 196 select DMA_ENGINE 197 help 198 Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller. 199 200config FSL_DMA 201 tristate "Freescale Elo series DMA support" 202 depends on FSL_SOC 203 select DMA_ENGINE 204 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 205 ---help--- 206 Enable support for the Freescale Elo series DMA controllers. 207 The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the 208 EloPlus is on mpc85xx and mpc86xx and Pxxx parts, and the Elo3 is on 209 some Txxx and Bxxx parts. 210 211config FSL_EDMA 212 tristate "Freescale eDMA engine support" 213 depends on OF 214 select DMA_ENGINE 215 select DMA_VIRTUAL_CHANNELS 216 help 217 Support the Freescale eDMA engine with programmable channel 218 multiplexing capability for DMA request sources(slot). 219 This module can be found on Freescale Vybrid and LS-1 SoCs. 220 221config FSL_QDMA 222 tristate "NXP Layerscape qDMA engine support" 223 depends on ARM || ARM64 224 select DMA_ENGINE 225 select DMA_VIRTUAL_CHANNELS 226 select DMA_ENGINE_RAID 227 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 228 help 229 Support the NXP Layerscape qDMA engine with command queue and legacy mode. 230 Channel virtualization is supported through enqueuing of DMA jobs to, 231 or dequeuing DMA jobs from, different work queues. 232 This module can be found on NXP Layerscape SoCs. 233 The qdma driver only work on SoCs with a DPAA hardware block. 234 235config FSL_RAID 236 tristate "Freescale RAID engine Support" 237 depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH 238 select DMA_ENGINE 239 select DMA_ENGINE_RAID 240 ---help--- 241 Enable support for Freescale RAID Engine. RAID Engine is 242 available on some QorIQ SoCs (like P5020/P5040). It has 243 the capability to offload memcpy, xor and pq computation 244 for raid5/6. 245 246config IMG_MDC_DMA 247 tristate "IMG MDC support" 248 depends on MIPS || COMPILE_TEST 249 depends on MFD_SYSCON 250 select DMA_ENGINE 251 select DMA_VIRTUAL_CHANNELS 252 help 253 Enable support for the IMG multi-threaded DMA controller (MDC). 254 255config IMX_DMA 256 tristate "i.MX DMA support" 257 depends on ARCH_MXC 258 select DMA_ENGINE 259 help 260 Support the i.MX DMA engine. This engine is integrated into 261 Freescale i.MX1/21/27 chips. 262 263config IMX_SDMA 264 tristate "i.MX SDMA support" 265 depends on ARCH_MXC 266 select DMA_ENGINE 267 select DMA_VIRTUAL_CHANNELS 268 help 269 Support the i.MX SDMA engine. This engine is integrated into 270 Freescale i.MX25/31/35/51/53/6 chips. 271 272config INTEL_IDMA64 273 tristate "Intel integrated DMA 64-bit support" 274 select DMA_ENGINE 275 select DMA_VIRTUAL_CHANNELS 276 help 277 Enable DMA support for Intel Low Power Subsystem such as found on 278 Intel Skylake PCH. 279 280config INTEL_IOATDMA 281 tristate "Intel I/OAT DMA support" 282 depends on PCI && X86_64 283 select DMA_ENGINE 284 select DMA_ENGINE_RAID 285 select DCA 286 help 287 Enable support for the Intel(R) I/OAT DMA engine present 288 in recent Intel Xeon chipsets. 289 290 Say Y here if you have such a chipset. 291 292 If unsure, say N. 293 294config INTEL_IOP_ADMA 295 tristate "Intel IOP ADMA support" 296 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX 297 select DMA_ENGINE 298 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 299 help 300 Enable support for the Intel(R) IOP Series RAID engines. 301 302config INTEL_MIC_X100_DMA 303 tristate "Intel MIC X100 DMA Driver" 304 depends on 64BIT && X86 && INTEL_MIC_BUS 305 select DMA_ENGINE 306 help 307 This enables DMA support for the Intel Many Integrated Core 308 (MIC) family of PCIe form factor coprocessor X100 devices that 309 run a 64 bit Linux OS. This driver will be used by both MIC 310 host and card drivers. 311 312 If you are building host kernel with a MIC device or a card 313 kernel for a MIC device, then say M (recommended) or Y, else 314 say N. If unsure say N. 315 316 More information about the Intel MIC family as well as the Linux 317 OS and tools for MIC to use with this driver are available from 318 <http://software.intel.com/en-us/mic-developer>. 319 320config K3_DMA 321 tristate "Hisilicon K3 DMA support" 322 depends on ARCH_HI3xxx || ARCH_HISI || COMPILE_TEST 323 select DMA_ENGINE 324 select DMA_VIRTUAL_CHANNELS 325 help 326 Support the DMA engine for Hisilicon K3 platform 327 devices. 328 329config LPC18XX_DMAMUX 330 bool "NXP LPC18xx/43xx DMA MUX for PL080" 331 depends on ARCH_LPC18XX || COMPILE_TEST 332 depends on OF && AMBA_PL08X 333 select MFD_SYSCON 334 help 335 Enable support for DMA on NXP LPC18xx/43xx platforms 336 with PL080 and multiplexed DMA request lines. 337 338config MCF_EDMA 339 tristate "Freescale eDMA engine support, ColdFire mcf5441x SoCs" 340 depends on M5441x || COMPILE_TEST 341 select DMA_ENGINE 342 select DMA_VIRTUAL_CHANNELS 343 help 344 Support the Freescale ColdFire eDMA engine, 64-channel 345 implementation that performs complex data transfers with 346 minimal intervention from a host processor. 347 This module can be found on Freescale ColdFire mcf5441x SoCs. 348 349config MMP_PDMA 350 bool "MMP PDMA support" 351 depends on ARCH_MMP || ARCH_PXA || COMPILE_TEST 352 select DMA_ENGINE 353 help 354 Support the MMP PDMA engine for PXA and MMP platform. 355 356config MMP_TDMA 357 bool "MMP Two-Channel DMA support" 358 depends on ARCH_MMP || COMPILE_TEST 359 select DMA_ENGINE 360 select MMP_SRAM if ARCH_MMP 361 select GENERIC_ALLOCATOR 362 help 363 Support the MMP Two-Channel DMA engine. 364 This engine used for MMP Audio DMA and pxa910 SQU. 365 It needs sram driver under mach-mmp. 366 367config MOXART_DMA 368 tristate "MOXART DMA support" 369 depends on ARCH_MOXART 370 select DMA_ENGINE 371 select DMA_VIRTUAL_CHANNELS 372 help 373 Enable support for the MOXA ART SoC DMA controller. 374 375 Say Y here if you enabled MMP ADMA, otherwise say N. 376 377config MPC512X_DMA 378 tristate "Freescale MPC512x built-in DMA engine support" 379 depends on PPC_MPC512x || PPC_MPC831x 380 select DMA_ENGINE 381 ---help--- 382 Enable support for the Freescale MPC512x built-in DMA engine. 383 384config MV_XOR 385 bool "Marvell XOR engine support" 386 depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST 387 select DMA_ENGINE 388 select DMA_ENGINE_RAID 389 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 390 ---help--- 391 Enable support for the Marvell XOR engine. 392 393config MV_XOR_V2 394 bool "Marvell XOR engine version 2 support " 395 depends on ARM64 396 select DMA_ENGINE 397 select DMA_ENGINE_RAID 398 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 399 select GENERIC_MSI_IRQ_DOMAIN 400 ---help--- 401 Enable support for the Marvell version 2 XOR engine. 402 403 This engine provides acceleration for copy, XOR and RAID6 404 operations, and is available on Marvell Armada 7K and 8K 405 platforms. 406 407config MXS_DMA 408 bool "MXS DMA support" 409 depends on ARCH_MXS || ARCH_MXC || COMPILE_TEST 410 select STMP_DEVICE 411 select DMA_ENGINE 412 help 413 Support the MXS DMA engine. This engine including APBH-DMA 414 and APBX-DMA is integrated into some Freescale chips. 415 416config MX3_IPU 417 bool "MX3x Image Processing Unit support" 418 depends on ARCH_MXC 419 select DMA_ENGINE 420 default y 421 help 422 If you plan to use the Image Processing unit in the i.MX3x, say 423 Y here. If unsure, select Y. 424 425config MX3_IPU_IRQS 426 int "Number of dynamically mapped interrupts for IPU" 427 depends on MX3_IPU 428 range 2 137 429 default 4 430 help 431 Out of 137 interrupt sources on i.MX31 IPU only very few are used. 432 To avoid bloating the irq_desc[] array we allocate a sufficient 433 number of IRQ slots and map them dynamically to specific sources. 434 435config NBPFAXI_DMA 436 tristate "Renesas Type-AXI NBPF DMA support" 437 select DMA_ENGINE 438 depends on ARM || COMPILE_TEST 439 help 440 Support for "Type-AXI" NBPF DMA IPs from Renesas 441 442config OWL_DMA 443 tristate "Actions Semi Owl SoCs DMA support" 444 depends on ARCH_ACTIONS 445 select DMA_ENGINE 446 select DMA_VIRTUAL_CHANNELS 447 help 448 Enable support for the Actions Semi Owl SoCs DMA controller. 449 450config PCH_DMA 451 tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA" 452 depends on PCI && (X86_32 || COMPILE_TEST) 453 select DMA_ENGINE 454 help 455 Enable support for Intel EG20T PCH DMA engine. 456 457 This driver also can be used for LAPIS Semiconductor IOH(Input/ 458 Output Hub), ML7213, ML7223 and ML7831. 459 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is 460 for MP(Media Phone) use and ML7831 IOH is for general purpose use. 461 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 462 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 463 464config PL330_DMA 465 tristate "DMA API Driver for PL330" 466 select DMA_ENGINE 467 depends on ARM_AMBA 468 help 469 Select if your platform has one or more PL330 DMACs. 470 You need to provide platform specific settings via 471 platform_data for a dma-pl330 device. 472 473config PXA_DMA 474 bool "PXA DMA support" 475 depends on (ARCH_MMP || ARCH_PXA) 476 select DMA_ENGINE 477 select DMA_VIRTUAL_CHANNELS 478 help 479 Support the DMA engine for PXA. It is also compatible with MMP PDMA 480 platform. The internal DMA IP of all PXA variants is supported, with 481 16 to 32 channels for peripheral to memory or memory to memory 482 transfers. 483 484config SIRF_DMA 485 tristate "CSR SiRFprimaII/SiRFmarco DMA support" 486 depends on ARCH_SIRF 487 select DMA_ENGINE 488 help 489 Enable support for the CSR SiRFprimaII DMA engine. 490 491config STE_DMA40 492 bool "ST-Ericsson DMA40 support" 493 depends on ARCH_U8500 494 select DMA_ENGINE 495 help 496 Support for ST-Ericsson DMA40 controller 497 498config ST_FDMA 499 tristate "ST FDMA dmaengine support" 500 depends on ARCH_STI 501 depends on REMOTEPROC 502 select ST_SLIM_REMOTEPROC 503 select DMA_ENGINE 504 select DMA_VIRTUAL_CHANNELS 505 help 506 Enable support for ST FDMA controller. 507 It supports 16 independent DMA channels, accepts up to 32 DMA requests 508 509 Say Y here if you have such a chipset. 510 If unsure, say N. 511 512config STM32_DMA 513 bool "STMicroelectronics STM32 DMA support" 514 depends on ARCH_STM32 || COMPILE_TEST 515 select DMA_ENGINE 516 select DMA_VIRTUAL_CHANNELS 517 help 518 Enable support for the on-chip DMA controller on STMicroelectronics 519 STM32 MCUs. 520 If you have a board based on such a MCU and wish to use DMA say Y 521 here. 522 523config STM32_DMAMUX 524 bool "STMicroelectronics STM32 dma multiplexer support" 525 depends on STM32_DMA || COMPILE_TEST 526 help 527 Enable support for the on-chip DMA multiplexer on STMicroelectronics 528 STM32 MCUs. 529 If you have a board based on such a MCU and wish to use DMAMUX say Y 530 here. 531 532config STM32_MDMA 533 bool "STMicroelectronics STM32 master dma support" 534 depends on ARCH_STM32 || COMPILE_TEST 535 depends on OF 536 select DMA_ENGINE 537 select DMA_VIRTUAL_CHANNELS 538 help 539 Enable support for the on-chip MDMA controller on STMicroelectronics 540 STM32 platforms. 541 If you have a board based on STM32 SoC and wish to use the master DMA 542 say Y here. 543 544config SPRD_DMA 545 tristate "Spreadtrum DMA support" 546 depends on ARCH_SPRD || COMPILE_TEST 547 select DMA_ENGINE 548 select DMA_VIRTUAL_CHANNELS 549 help 550 Enable support for the on-chip DMA controller on Spreadtrum platform. 551 552config S3C24XX_DMAC 553 bool "Samsung S3C24XX DMA support" 554 depends on ARCH_S3C24XX || COMPILE_TEST 555 select DMA_ENGINE 556 select DMA_VIRTUAL_CHANNELS 557 help 558 Support for the Samsung S3C24XX DMA controller driver. The 559 DMA controller is having multiple DMA channels which can be 560 configured for different peripherals like audio, UART, SPI. 561 The DMA controller can transfer data from memory to peripheral, 562 periphal to memory, periphal to periphal and memory to memory. 563 564config TXX9_DMAC 565 tristate "Toshiba TXx9 SoC DMA support" 566 depends on MACH_TX49XX || MACH_TX39XX 567 select DMA_ENGINE 568 help 569 Support the TXx9 SoC internal DMA controller. This can be 570 integrated in chips such as the Toshiba TX4927/38/39. 571 572config TEGRA20_APB_DMA 573 bool "NVIDIA Tegra20 APB DMA support" 574 depends on ARCH_TEGRA 575 select DMA_ENGINE 576 help 577 Support for the NVIDIA Tegra20 APB DMA controller driver. The 578 DMA controller is having multiple DMA channel which can be 579 configured for different peripherals like audio, UART, SPI, 580 I2C etc which is in APB bus. 581 This DMA controller transfers data from memory to peripheral fifo 582 or vice versa. It does not support memory to memory data transfer. 583 584config TEGRA210_ADMA 585 tristate "NVIDIA Tegra210 ADMA support" 586 depends on (ARCH_TEGRA_210_SOC || COMPILE_TEST) && PM_CLK 587 select DMA_ENGINE 588 select DMA_VIRTUAL_CHANNELS 589 help 590 Support for the NVIDIA Tegra210 ADMA controller driver. The 591 DMA controller has multiple DMA channels and is used to service 592 various audio clients in the Tegra210 audio processing engine 593 (APE). This DMA controller transfers data from memory to 594 peripheral and vice versa. It does not support memory to 595 memory data transfer. 596 597config TIMB_DMA 598 tristate "Timberdale FPGA DMA support" 599 depends on MFD_TIMBERDALE || COMPILE_TEST 600 select DMA_ENGINE 601 help 602 Enable support for the Timberdale FPGA DMA engine. 603 604config UNIPHIER_MDMAC 605 tristate "UniPhier MIO DMAC" 606 depends on ARCH_UNIPHIER || COMPILE_TEST 607 depends on OF 608 select DMA_ENGINE 609 select DMA_VIRTUAL_CHANNELS 610 help 611 Enable support for the MIO DMAC (Media I/O DMA controller) on the 612 UniPhier platform. This DMA controller is used as the external 613 DMA engine of the SD/eMMC controllers of the LD4, Pro4, sLD8 SoCs. 614 615config XGENE_DMA 616 tristate "APM X-Gene DMA support" 617 depends on ARCH_XGENE || COMPILE_TEST 618 select DMA_ENGINE 619 select DMA_ENGINE_RAID 620 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 621 help 622 Enable support for the APM X-Gene SoC DMA engine. 623 624config XILINX_DMA 625 tristate "Xilinx AXI DMAS Engine" 626 depends on (ARCH_ZYNQ || MICROBLAZE || ARM64) 627 select DMA_ENGINE 628 help 629 Enable support for Xilinx AXI VDMA Soft IP. 630 631 AXI VDMA engine provides high-bandwidth direct memory access 632 between memory and AXI4-Stream video type target 633 peripherals including peripherals which support AXI4- 634 Stream Video Protocol. It has two stream interfaces/ 635 channels, Memory Mapped to Stream (MM2S) and Stream to 636 Memory Mapped (S2MM) for the data transfers. 637 AXI CDMA engine provides high-bandwidth direct memory access 638 between a memory-mapped source address and a memory-mapped 639 destination address. 640 AXI DMA engine provides high-bandwidth one dimensional direct 641 memory access between memory and AXI4-Stream target peripherals. 642 643config XILINX_ZYNQMP_DMA 644 tristate "Xilinx ZynqMP DMA Engine" 645 depends on (ARCH_ZYNQ || MICROBLAZE || ARM64) 646 select DMA_ENGINE 647 help 648 Enable support for Xilinx ZynqMP DMA controller. 649 650config ZX_DMA 651 tristate "ZTE ZX DMA support" 652 depends on ARCH_ZX || COMPILE_TEST 653 select DMA_ENGINE 654 select DMA_VIRTUAL_CHANNELS 655 help 656 Support the DMA engine for ZTE ZX family platform devices. 657 658 659# driver files 660source "drivers/dma/bestcomm/Kconfig" 661 662source "drivers/dma/mediatek/Kconfig" 663 664source "drivers/dma/qcom/Kconfig" 665 666source "drivers/dma/dw/Kconfig" 667 668source "drivers/dma/hsu/Kconfig" 669 670source "drivers/dma/sh/Kconfig" 671 672source "drivers/dma/ti/Kconfig" 673 674# clients 675comment "DMA Clients" 676 depends on DMA_ENGINE 677 678config ASYNC_TX_DMA 679 bool "Async_tx: Offload support for the async_tx api" 680 depends on DMA_ENGINE 681 help 682 This allows the async_tx api to take advantage of offload engines for 683 memcpy, memset, xor, and raid6 p+q operations. If your platform has 684 a dma engine that can perform raid operations and you have enabled 685 MD_RAID456 say Y. 686 687 If unsure, say N. 688 689config DMATEST 690 tristate "DMA Test client" 691 depends on DMA_ENGINE 692 select DMA_ENGINE_RAID 693 help 694 Simple DMA test client. Say N unless you're debugging a 695 DMA Device driver. 696 697config DMA_ENGINE_RAID 698 bool 699 700endif 701