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