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