rjw | 1f88458 | 2022-01-06 17:20:42 +0800 | [diff] [blame^] | 1 | # |
| 2 | # DMA engine configuration |
| 3 | # |
| 4 | |
| 5 | menuconfig 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 | |
| 16 | config 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 | |
| 23 | config 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 | |
| 32 | if DMADEVICES |
| 33 | |
| 34 | comment "DMA Devices" |
| 35 | |
| 36 | #core |
| 37 | config ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 38 | bool |
| 39 | |
| 40 | config ARCH_HAS_ASYNC_TX_FIND_CHANNEL |
| 41 | bool |
| 42 | |
| 43 | config DMA_ENGINE |
| 44 | bool |
| 45 | |
| 46 | config DMA_VIRTUAL_CHANNELS |
| 47 | tristate |
| 48 | |
| 49 | config DMA_ACPI |
| 50 | def_bool y |
| 51 | depends on ACPI |
| 52 | |
| 53 | config DMA_OF |
| 54 | def_bool y |
| 55 | depends on OF |
| 56 | select DMA_ENGINE |
| 57 | |
| 58 | #devices |
| 59 | config ALTERA_MSGDMA |
| 60 | tristate "Altera / Intel mSGDMA Engine" |
| 61 | select DMA_ENGINE |
| 62 | help |
| 63 | Enable support for Altera / Intel mSGDMA controller. |
| 64 | |
| 65 | config 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 | |
| 76 | config 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 | |
| 86 | config 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 | |
| 93 | config 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 | |
| 100 | config 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 | |
| 110 | config 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 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 | |
| 125 | config 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 | |
| 132 | config DMA_BCM2835 |
| 133 | tristate "BCM2835 DMA engine support" |
| 134 | depends on ARCH_BCM2835 |
| 135 | select DMA_ENGINE |
| 136 | select DMA_VIRTUAL_CHANNELS |
| 137 | |
| 138 | config DMA_JZ4740 |
| 139 | tristate "JZ4740 DMA support" |
| 140 | depends on MACH_JZ4740 || COMPILE_TEST |
| 141 | select DMA_ENGINE |
| 142 | select DMA_VIRTUAL_CHANNELS |
| 143 | |
| 144 | config 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 | |
| 154 | config DMA_MTK_UART |
| 155 | tristate "MediaTek SoCs APDMA support for UART" |
| 156 | depends on OF |
| 157 | select DMA_ENGINE |
| 158 | select DMA_VIRTUAL_CHANNELS |
| 159 | help |
| 160 | Enable support for MediaTek SoC uart DMA engine. |
| 161 | This DMA engine just only used when 8250 mtk uart is enabled. |
| 162 | This DMA controller transfers data from memory to peripheral. |
| 163 | It does not support memory to memory data transfer. |
| 164 | |
| 165 | config DMA_OMAP |
| 166 | tristate "OMAP DMA support" |
| 167 | depends on ARCH_OMAP || COMPILE_TEST |
| 168 | select DMA_ENGINE |
| 169 | select DMA_VIRTUAL_CHANNELS |
| 170 | select TI_DMA_CROSSBAR if (SOC_DRA7XX || COMPILE_TEST) |
| 171 | |
| 172 | config DMA_SA11X0 |
| 173 | tristate "SA-11x0 DMA support" |
| 174 | depends on ARCH_SA1100 || COMPILE_TEST |
| 175 | select DMA_ENGINE |
| 176 | select DMA_VIRTUAL_CHANNELS |
| 177 | help |
| 178 | Support the DMA engine found on Intel StrongARM SA-1100 and |
| 179 | SA-1110 SoCs. This DMA engine can only be used with on-chip |
| 180 | devices. |
| 181 | |
| 182 | config DMA_SUN4I |
| 183 | tristate "Allwinner A10 DMA SoCs support" |
| 184 | depends on MACH_SUN4I || MACH_SUN5I || MACH_SUN7I |
| 185 | default (MACH_SUN4I || MACH_SUN5I || MACH_SUN7I) |
| 186 | select DMA_ENGINE |
| 187 | select DMA_VIRTUAL_CHANNELS |
| 188 | help |
| 189 | Enable support for the DMA controller present in the sun4i, |
| 190 | sun5i and sun7i Allwinner ARM SoCs. |
| 191 | |
| 192 | config DMA_SUN6I |
| 193 | tristate "Allwinner A31 SoCs DMA support" |
| 194 | depends on MACH_SUN6I || MACH_SUN8I || (ARM64 && ARCH_SUNXI) || COMPILE_TEST |
| 195 | depends on RESET_CONTROLLER |
| 196 | select DMA_ENGINE |
| 197 | select DMA_VIRTUAL_CHANNELS |
| 198 | help |
| 199 | Support for the DMA engine first found in Allwinner A31 SoCs. |
| 200 | |
| 201 | config EP93XX_DMA |
| 202 | bool "Cirrus Logic EP93xx DMA support" |
| 203 | depends on ARCH_EP93XX || COMPILE_TEST |
| 204 | select DMA_ENGINE |
| 205 | help |
| 206 | Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller. |
| 207 | |
| 208 | config FSL_DMA |
| 209 | tristate "Freescale Elo series DMA support" |
| 210 | depends on FSL_SOC |
| 211 | select DMA_ENGINE |
| 212 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 213 | ---help--- |
| 214 | Enable support for the Freescale Elo series DMA controllers. |
| 215 | The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the |
| 216 | EloPlus is on mpc85xx and mpc86xx and Pxxx parts, and the Elo3 is on |
| 217 | some Txxx and Bxxx parts. |
| 218 | |
| 219 | config FSL_EDMA |
| 220 | tristate "Freescale eDMA engine support" |
| 221 | depends on OF |
| 222 | select DMA_ENGINE |
| 223 | select DMA_VIRTUAL_CHANNELS |
| 224 | help |
| 225 | Support the Freescale eDMA engine with programmable channel |
| 226 | multiplexing capability for DMA request sources(slot). |
| 227 | This module can be found on Freescale Vybrid and LS-1 SoCs. |
| 228 | |
| 229 | config FSL_RAID |
| 230 | tristate "Freescale RAID engine Support" |
| 231 | depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 232 | select DMA_ENGINE |
| 233 | select DMA_ENGINE_RAID |
| 234 | ---help--- |
| 235 | Enable support for Freescale RAID Engine. RAID Engine is |
| 236 | available on some QorIQ SoCs (like P5020/P5040). It has |
| 237 | the capability to offload memcpy, xor and pq computation |
| 238 | for raid5/6. |
| 239 | |
| 240 | config IMG_MDC_DMA |
| 241 | tristate "IMG MDC support" |
| 242 | depends on MIPS || COMPILE_TEST |
| 243 | depends on MFD_SYSCON |
| 244 | select DMA_ENGINE |
| 245 | select DMA_VIRTUAL_CHANNELS |
| 246 | help |
| 247 | Enable support for the IMG multi-threaded DMA controller (MDC). |
| 248 | |
| 249 | config IMX_DMA |
| 250 | tristate "i.MX DMA support" |
| 251 | depends on ARCH_MXC |
| 252 | select DMA_ENGINE |
| 253 | help |
| 254 | Support the i.MX DMA engine. This engine is integrated into |
| 255 | Freescale i.MX1/21/27 chips. |
| 256 | |
| 257 | config IMX_SDMA |
| 258 | tristate "i.MX SDMA support" |
| 259 | depends on ARCH_MXC |
| 260 | select DMA_ENGINE |
| 261 | help |
| 262 | Support the i.MX SDMA engine. This engine is integrated into |
| 263 | Freescale i.MX25/31/35/51/53/6 chips. |
| 264 | |
| 265 | config INTEL_IDMA64 |
| 266 | tristate "Intel integrated DMA 64-bit support" |
| 267 | select DMA_ENGINE |
| 268 | select DMA_VIRTUAL_CHANNELS |
| 269 | help |
| 270 | Enable DMA support for Intel Low Power Subsystem such as found on |
| 271 | Intel Skylake PCH. |
| 272 | |
| 273 | config INTEL_IOATDMA |
| 274 | tristate "Intel I/OAT DMA support" |
| 275 | depends on PCI && X86_64 |
| 276 | select DMA_ENGINE |
| 277 | select DMA_ENGINE_RAID |
| 278 | select DCA |
| 279 | help |
| 280 | Enable support for the Intel(R) I/OAT DMA engine present |
| 281 | in recent Intel Xeon chipsets. |
| 282 | |
| 283 | Say Y here if you have such a chipset. |
| 284 | |
| 285 | If unsure, say N. |
| 286 | |
| 287 | config INTEL_IOP_ADMA |
| 288 | tristate "Intel IOP ADMA support" |
| 289 | depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX |
| 290 | select DMA_ENGINE |
| 291 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 292 | help |
| 293 | Enable support for the Intel(R) IOP Series RAID engines. |
| 294 | |
| 295 | config INTEL_MIC_X100_DMA |
| 296 | tristate "Intel MIC X100 DMA Driver" |
| 297 | depends on 64BIT && X86 && INTEL_MIC_BUS |
| 298 | select DMA_ENGINE |
| 299 | help |
| 300 | This enables DMA support for the Intel Many Integrated Core |
| 301 | (MIC) family of PCIe form factor coprocessor X100 devices that |
| 302 | run a 64 bit Linux OS. This driver will be used by both MIC |
| 303 | host and card drivers. |
| 304 | |
| 305 | If you are building host kernel with a MIC device or a card |
| 306 | kernel for a MIC device, then say M (recommended) or Y, else |
| 307 | say N. If unsure say N. |
| 308 | |
| 309 | More information about the Intel MIC family as well as the Linux |
| 310 | OS and tools for MIC to use with this driver are available from |
| 311 | <http://software.intel.com/en-us/mic-developer>. |
| 312 | |
| 313 | config K3_DMA |
| 314 | tristate "Hisilicon K3 DMA support" |
| 315 | depends on ARCH_HI3xxx || ARCH_HISI || COMPILE_TEST |
| 316 | select DMA_ENGINE |
| 317 | select DMA_VIRTUAL_CHANNELS |
| 318 | help |
| 319 | Support the DMA engine for Hisilicon K3 platform |
| 320 | devices. |
| 321 | |
| 322 | config LPC18XX_DMAMUX |
| 323 | bool "NXP LPC18xx/43xx DMA MUX for PL080" |
| 324 | depends on ARCH_LPC18XX || COMPILE_TEST |
| 325 | depends on OF && AMBA_PL08X |
| 326 | select MFD_SYSCON |
| 327 | help |
| 328 | Enable support for DMA on NXP LPC18xx/43xx platforms |
| 329 | with PL080 and multiplexed DMA request lines. |
| 330 | |
| 331 | config MMP_PDMA |
| 332 | bool "MMP PDMA support" |
| 333 | depends on ARCH_MMP || ARCH_PXA || COMPILE_TEST |
| 334 | select DMA_ENGINE |
| 335 | help |
| 336 | Support the MMP PDMA engine for PXA and MMP platform. |
| 337 | |
| 338 | config MMP_TDMA |
| 339 | bool "MMP Two-Channel DMA support" |
| 340 | depends on ARCH_MMP || COMPILE_TEST |
| 341 | select DMA_ENGINE |
| 342 | select MMP_SRAM if ARCH_MMP |
| 343 | select GENERIC_ALLOCATOR |
| 344 | help |
| 345 | Support the MMP Two-Channel DMA engine. |
| 346 | This engine used for MMP Audio DMA and pxa910 SQU. |
| 347 | It needs sram driver under mach-mmp. |
| 348 | |
| 349 | config MOXART_DMA |
| 350 | tristate "MOXART DMA support" |
| 351 | depends on ARCH_MOXART |
| 352 | select DMA_ENGINE |
| 353 | select DMA_VIRTUAL_CHANNELS |
| 354 | help |
| 355 | Enable support for the MOXA ART SoC DMA controller. |
| 356 | |
| 357 | Say Y here if you enabled MMP ADMA, otherwise say N. |
| 358 | |
| 359 | config MPC512X_DMA |
| 360 | tristate "Freescale MPC512x built-in DMA engine support" |
| 361 | depends on PPC_MPC512x || PPC_MPC831x |
| 362 | select DMA_ENGINE |
| 363 | ---help--- |
| 364 | Enable support for the Freescale MPC512x built-in DMA engine. |
| 365 | |
| 366 | config MV_XOR |
| 367 | bool "Marvell XOR engine support" |
| 368 | depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST |
| 369 | select DMA_ENGINE |
| 370 | select DMA_ENGINE_RAID |
| 371 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 372 | ---help--- |
| 373 | Enable support for the Marvell XOR engine. |
| 374 | |
| 375 | config MV_XOR_V2 |
| 376 | bool "Marvell XOR engine version 2 support " |
| 377 | depends on ARM64 |
| 378 | select DMA_ENGINE |
| 379 | select DMA_ENGINE_RAID |
| 380 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 381 | select GENERIC_MSI_IRQ_DOMAIN |
| 382 | ---help--- |
| 383 | Enable support for the Marvell version 2 XOR engine. |
| 384 | |
| 385 | This engine provides acceleration for copy, XOR and RAID6 |
| 386 | operations, and is available on Marvell Armada 7K and 8K |
| 387 | platforms. |
| 388 | |
| 389 | config MXS_DMA |
| 390 | bool "MXS DMA support" |
| 391 | depends on ARCH_MXS || ARCH_MXC || COMPILE_TEST |
| 392 | select STMP_DEVICE |
| 393 | select DMA_ENGINE |
| 394 | help |
| 395 | Support the MXS DMA engine. This engine including APBH-DMA |
| 396 | and APBX-DMA is integrated into some Freescale chips. |
| 397 | |
| 398 | config MX3_IPU |
| 399 | bool "MX3x Image Processing Unit support" |
| 400 | depends on ARCH_MXC |
| 401 | select DMA_ENGINE |
| 402 | default y |
| 403 | help |
| 404 | If you plan to use the Image Processing unit in the i.MX3x, say |
| 405 | Y here. If unsure, select Y. |
| 406 | |
| 407 | config MX3_IPU_IRQS |
| 408 | int "Number of dynamically mapped interrupts for IPU" |
| 409 | depends on MX3_IPU |
| 410 | range 2 137 |
| 411 | default 4 |
| 412 | help |
| 413 | Out of 137 interrupt sources on i.MX31 IPU only very few are used. |
| 414 | To avoid bloating the irq_desc[] array we allocate a sufficient |
| 415 | number of IRQ slots and map them dynamically to specific sources. |
| 416 | |
| 417 | config NBPFAXI_DMA |
| 418 | tristate "Renesas Type-AXI NBPF DMA support" |
| 419 | select DMA_ENGINE |
| 420 | depends on ARM || COMPILE_TEST |
| 421 | help |
| 422 | Support for "Type-AXI" NBPF DMA IPs from Renesas |
| 423 | |
| 424 | config PCH_DMA |
| 425 | tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA" |
| 426 | depends on PCI && (X86_32 || COMPILE_TEST) |
| 427 | select DMA_ENGINE |
| 428 | help |
| 429 | Enable support for Intel EG20T PCH DMA engine. |
| 430 | |
| 431 | This driver also can be used for LAPIS Semiconductor IOH(Input/ |
| 432 | Output Hub), ML7213, ML7223 and ML7831. |
| 433 | ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is |
| 434 | for MP(Media Phone) use and ML7831 IOH is for general purpose use. |
| 435 | ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. |
| 436 | ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. |
| 437 | |
| 438 | config PL330_DMA |
| 439 | tristate "DMA API Driver for PL330" |
| 440 | select DMA_ENGINE |
| 441 | depends on ARM_AMBA |
| 442 | help |
| 443 | Select if your platform has one or more PL330 DMACs. |
| 444 | You need to provide platform specific settings via |
| 445 | platform_data for a dma-pl330 device. |
| 446 | |
| 447 | config PXA_DMA |
| 448 | bool "PXA DMA support" |
| 449 | depends on (ARCH_MMP || ARCH_PXA) |
| 450 | select DMA_ENGINE |
| 451 | select DMA_VIRTUAL_CHANNELS |
| 452 | help |
| 453 | Support the DMA engine for PXA. It is also compatible with MMP PDMA |
| 454 | platform. The internal DMA IP of all PXA variants is supported, with |
| 455 | 16 to 32 channels for peripheral to memory or memory to memory |
| 456 | transfers. |
| 457 | |
| 458 | config SIRF_DMA |
| 459 | tristate "CSR SiRFprimaII/SiRFmarco DMA support" |
| 460 | depends on ARCH_SIRF |
| 461 | select DMA_ENGINE |
| 462 | help |
| 463 | Enable support for the CSR SiRFprimaII DMA engine. |
| 464 | |
| 465 | config STE_DMA40 |
| 466 | bool "ST-Ericsson DMA40 support" |
| 467 | depends on ARCH_U8500 |
| 468 | select DMA_ENGINE |
| 469 | help |
| 470 | Support for ST-Ericsson DMA40 controller |
| 471 | |
| 472 | config ST_FDMA |
| 473 | tristate "ST FDMA dmaengine support" |
| 474 | depends on ARCH_STI |
| 475 | depends on REMOTEPROC |
| 476 | select ST_SLIM_REMOTEPROC |
| 477 | select DMA_ENGINE |
| 478 | select DMA_VIRTUAL_CHANNELS |
| 479 | help |
| 480 | Enable support for ST FDMA controller. |
| 481 | It supports 16 independent DMA channels, accepts up to 32 DMA requests |
| 482 | |
| 483 | Say Y here if you have such a chipset. |
| 484 | If unsure, say N. |
| 485 | |
| 486 | config STM32_DMA |
| 487 | bool "STMicroelectronics STM32 DMA support" |
| 488 | depends on ARCH_STM32 || COMPILE_TEST |
| 489 | select DMA_ENGINE |
| 490 | select DMA_VIRTUAL_CHANNELS |
| 491 | help |
| 492 | Enable support for the on-chip DMA controller on STMicroelectronics |
| 493 | STM32 MCUs. |
| 494 | If you have a board based on such a MCU and wish to use DMA say Y |
| 495 | here. |
| 496 | |
| 497 | config S3C24XX_DMAC |
| 498 | bool "Samsung S3C24XX DMA support" |
| 499 | depends on ARCH_S3C24XX || COMPILE_TEST |
| 500 | select DMA_ENGINE |
| 501 | select DMA_VIRTUAL_CHANNELS |
| 502 | help |
| 503 | Support for the Samsung S3C24XX DMA controller driver. The |
| 504 | DMA controller is having multiple DMA channels which can be |
| 505 | configured for different peripherals like audio, UART, SPI. |
| 506 | The DMA controller can transfer data from memory to peripheral, |
| 507 | periphal to memory, periphal to periphal and memory to memory. |
| 508 | |
| 509 | config TXX9_DMAC |
| 510 | tristate "Toshiba TXx9 SoC DMA support" |
| 511 | depends on MACH_TX49XX || MACH_TX39XX |
| 512 | select DMA_ENGINE |
| 513 | help |
| 514 | Support the TXx9 SoC internal DMA controller. This can be |
| 515 | integrated in chips such as the Toshiba TX4927/38/39. |
| 516 | |
| 517 | config TEGRA20_APB_DMA |
| 518 | bool "NVIDIA Tegra20 APB DMA support" |
| 519 | depends on ARCH_TEGRA |
| 520 | select DMA_ENGINE |
| 521 | help |
| 522 | Support for the NVIDIA Tegra20 APB DMA controller driver. The |
| 523 | DMA controller is having multiple DMA channel which can be |
| 524 | configured for different peripherals like audio, UART, SPI, |
| 525 | I2C etc which is in APB bus. |
| 526 | This DMA controller transfers data from memory to peripheral fifo |
| 527 | or vice versa. It does not support memory to memory data transfer. |
| 528 | |
| 529 | config TEGRA210_ADMA |
| 530 | tristate "NVIDIA Tegra210 ADMA support" |
| 531 | depends on (ARCH_TEGRA_210_SOC || COMPILE_TEST) && PM_CLK |
| 532 | select DMA_ENGINE |
| 533 | select DMA_VIRTUAL_CHANNELS |
| 534 | help |
| 535 | Support for the NVIDIA Tegra210 ADMA controller driver. The |
| 536 | DMA controller has multiple DMA channels and is used to service |
| 537 | various audio clients in the Tegra210 audio processing engine |
| 538 | (APE). This DMA controller transfers data from memory to |
| 539 | peripheral and vice versa. It does not support memory to |
| 540 | memory data transfer. |
| 541 | |
| 542 | config TIMB_DMA |
| 543 | tristate "Timberdale FPGA DMA support" |
| 544 | depends on MFD_TIMBERDALE || COMPILE_TEST |
| 545 | select DMA_ENGINE |
| 546 | help |
| 547 | Enable support for the Timberdale FPGA DMA engine. |
| 548 | |
| 549 | config TI_CPPI41 |
| 550 | tristate "CPPI 4.1 DMA support" |
| 551 | depends on (ARCH_OMAP || ARCH_DAVINCI_DA8XX) |
| 552 | select DMA_ENGINE |
| 553 | help |
| 554 | The Communications Port Programming Interface (CPPI) 4.1 DMA engine |
| 555 | is currently used by the USB driver on AM335x and DA8xx platforms. |
| 556 | |
| 557 | config TI_DMA_CROSSBAR |
| 558 | bool |
| 559 | |
| 560 | config TI_EDMA |
| 561 | bool "TI EDMA support" |
| 562 | depends on ARCH_DAVINCI || ARCH_OMAP || ARCH_KEYSTONE || COMPILE_TEST |
| 563 | select DMA_ENGINE |
| 564 | select DMA_VIRTUAL_CHANNELS |
| 565 | select TI_DMA_CROSSBAR if (ARCH_OMAP || COMPILE_TEST) |
| 566 | default n |
| 567 | help |
| 568 | Enable support for the TI EDMA controller. This DMA |
| 569 | engine is found on TI DaVinci and AM33xx parts. |
| 570 | |
| 571 | config XGENE_DMA |
| 572 | tristate "APM X-Gene DMA support" |
| 573 | depends on ARCH_XGENE || COMPILE_TEST |
| 574 | select DMA_ENGINE |
| 575 | select DMA_ENGINE_RAID |
| 576 | select ASYNC_TX_ENABLE_CHANNEL_SWITCH |
| 577 | help |
| 578 | Enable support for the APM X-Gene SoC DMA engine. |
| 579 | |
| 580 | config XILINX_DMA |
| 581 | tristate "Xilinx AXI DMAS Engine" |
| 582 | depends on (ARCH_ZYNQ || MICROBLAZE || ARM64) |
| 583 | select DMA_ENGINE |
| 584 | help |
| 585 | Enable support for Xilinx AXI VDMA Soft IP. |
| 586 | |
| 587 | AXI VDMA engine provides high-bandwidth direct memory access |
| 588 | between memory and AXI4-Stream video type target |
| 589 | peripherals including peripherals which support AXI4- |
| 590 | Stream Video Protocol. It has two stream interfaces/ |
| 591 | channels, Memory Mapped to Stream (MM2S) and Stream to |
| 592 | Memory Mapped (S2MM) for the data transfers. |
| 593 | AXI CDMA engine provides high-bandwidth direct memory access |
| 594 | between a memory-mapped source address and a memory-mapped |
| 595 | destination address. |
| 596 | AXI DMA engine provides high-bandwidth one dimensional direct |
| 597 | memory access between memory and AXI4-Stream target peripherals. |
| 598 | |
| 599 | config XILINX_ZYNQMP_DMA |
| 600 | tristate "Xilinx ZynqMP DMA Engine" |
| 601 | depends on (ARCH_ZYNQ || MICROBLAZE || ARM64) |
| 602 | select DMA_ENGINE |
| 603 | help |
| 604 | Enable support for Xilinx ZynqMP DMA controller. |
| 605 | |
| 606 | config ZX_DMA |
| 607 | tristate "ZTE ZX DMA support" |
| 608 | depends on ARCH_ZX || COMPILE_TEST |
| 609 | select DMA_ENGINE |
| 610 | select DMA_VIRTUAL_CHANNELS |
| 611 | help |
| 612 | Support the DMA engine for ZTE ZX family platform devices. |
| 613 | |
| 614 | |
| 615 | # driver files |
| 616 | source "drivers/dma/bestcomm/Kconfig" |
| 617 | |
| 618 | source "drivers/dma/qcom/Kconfig" |
| 619 | |
| 620 | source "drivers/dma/dw/Kconfig" |
| 621 | |
| 622 | source "drivers/dma/hsu/Kconfig" |
| 623 | |
| 624 | source "drivers/dma/sh/Kconfig" |
| 625 | |
| 626 | # clients |
| 627 | comment "DMA Clients" |
| 628 | depends on DMA_ENGINE |
| 629 | |
| 630 | config ASYNC_TX_DMA |
| 631 | bool "Async_tx: Offload support for the async_tx api" |
| 632 | depends on DMA_ENGINE |
| 633 | help |
| 634 | This allows the async_tx api to take advantage of offload engines for |
| 635 | memcpy, memset, xor, and raid6 p+q operations. If your platform has |
| 636 | a dma engine that can perform raid operations and you have enabled |
| 637 | MD_RAID456 say Y. |
| 638 | |
| 639 | If unsure, say N. |
| 640 | |
| 641 | config DMATEST |
| 642 | tristate "DMA Test client" |
| 643 | depends on DMA_ENGINE |
| 644 | select DMA_ENGINE_RAID |
| 645 | help |
| 646 | Simple DMA test client. Say N unless you're debugging a |
| 647 | DMA Device driver. |
| 648 | |
| 649 | config DMA_ENGINE_RAID |
| 650 | bool |
| 651 | |
| 652 | endif |