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_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 49config ASYNC_TX_ENABLE_CHANNEL_SWITCH 50 bool 51 52config AMBA_PL08X 53 bool "ARM PrimeCell PL080 or PL081 support" 54 depends on ARM_AMBA && EXPERIMENTAL 55 select DMA_ENGINE 56 help 57 Platform has a PL08x DMAC device 58 which can provide DMA engine support 59 60config INTEL_IOATDMA 61 tristate "Intel I/OAT DMA support" 62 depends on PCI && X86 63 select DMA_ENGINE 64 select DCA 65 select ASYNC_TX_DISABLE_PQ_VAL_DMA 66 select ASYNC_TX_DISABLE_XOR_VAL_DMA 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 75config 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 83config DW_DMAC 84 tristate "Synopsys DesignWare AHB DMA support" 85 depends on HAVE_CLK 86 select DMA_ENGINE 87 default y if CPU_AT32AP7000 88 help 89 Support the Synopsys DesignWare AHB DMA controller. This 90 can be integrated in chips such as the Atmel AT32ap7000. 91 92config AT_HDMAC 93 tristate "Atmel AHB DMA support" 94 depends on ARCH_AT91SAM9RL || ARCH_AT91SAM9G45 95 select DMA_ENGINE 96 help 97 Support the Atmel AHB DMA controller. This can be integrated in 98 chips such as the Atmel AT91SAM9RL. 99 100config FSL_DMA 101 tristate "Freescale Elo and Elo Plus DMA support" 102 depends on FSL_SOC 103 select DMA_ENGINE 104 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 105 ---help--- 106 Enable support for the Freescale Elo and Elo Plus DMA controllers. 107 The Elo is the DMA controller on some 82xx and 83xx parts, and the 108 Elo Plus is the DMA controller on 85xx and 86xx parts. 109 110config MPC512X_DMA 111 tristate "Freescale MPC512x built-in DMA engine support" 112 depends on PPC_MPC512x || PPC_MPC831x 113 select DMA_ENGINE 114 ---help--- 115 Enable support for the Freescale MPC512x built-in DMA engine. 116 117config MV_XOR 118 bool "Marvell XOR engine support" 119 depends on PLAT_ORION 120 select DMA_ENGINE 121 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 122 ---help--- 123 Enable support for the Marvell XOR engine. 124 125config MX3_IPU 126 bool "MX3x Image Processing Unit support" 127 depends on ARCH_MXC 128 select DMA_ENGINE 129 default y 130 help 131 If you plan to use the Image Processing unit in the i.MX3x, say 132 Y here. If unsure, select Y. 133 134config MX3_IPU_IRQS 135 int "Number of dynamically mapped interrupts for IPU" 136 depends on MX3_IPU 137 range 2 137 138 default 4 139 help 140 Out of 137 interrupt sources on i.MX31 IPU only very few are used. 141 To avoid bloating the irq_desc[] array we allocate a sufficient 142 number of IRQ slots and map them dynamically to specific sources. 143 144config TXX9_DMAC 145 tristate "Toshiba TXx9 SoC DMA support" 146 depends on MACH_TX49XX || MACH_TX39XX 147 select DMA_ENGINE 148 help 149 Support the TXx9 SoC internal DMA controller. This can be 150 integrated in chips such as the Toshiba TX4927/38/39. 151 152config SH_DMAE 153 tristate "Renesas SuperH DMAC support" 154 depends on (SUPERH && SH_DMA) || (ARM && ARCH_SHMOBILE) 155 depends on !SH_DMA_API 156 select DMA_ENGINE 157 help 158 Enable support for the Renesas SuperH DMA controllers. 159 160config COH901318 161 bool "ST-Ericsson COH901318 DMA support" 162 select DMA_ENGINE 163 depends on ARCH_U300 164 help 165 Enable support for ST-Ericsson COH 901 318 DMA. 166 167config STE_DMA40 168 bool "ST-Ericsson DMA40 support" 169 depends on ARCH_U8500 170 select DMA_ENGINE 171 help 172 Support for ST-Ericsson DMA40 controller 173 174config AMCC_PPC440SPE_ADMA 175 tristate "AMCC PPC440SPe ADMA support" 176 depends on 440SPe || 440SP 177 select DMA_ENGINE 178 select ARCH_HAS_ASYNC_TX_FIND_CHANNEL 179 select ASYNC_TX_ENABLE_CHANNEL_SWITCH 180 help 181 Enable support for the AMCC PPC440SPe RAID engines. 182 183config TIMB_DMA 184 tristate "Timberdale FPGA DMA support" 185 depends on MFD_TIMBERDALE || HAS_IOMEM 186 select DMA_ENGINE 187 help 188 Enable support for the Timberdale FPGA DMA engine. 189 190config SIRF_DMA 191 tristate "CSR SiRFprimaII DMA support" 192 depends on ARCH_PRIMA2 193 select DMA_ENGINE 194 help 195 Enable support for the CSR SiRFprimaII DMA engine. 196 197config ARCH_HAS_ASYNC_TX_FIND_CHANNEL 198 bool 199 200config PL330_DMA 201 tristate "DMA API Driver for PL330" 202 select DMA_ENGINE 203 depends on ARM_AMBA 204 help 205 Select if your platform has one or more PL330 DMACs. 206 You need to provide platform specific settings via 207 platform_data for a dma-pl330 device. 208 209config PCH_DMA 210 tristate "Intel EG20T PCH / LAPIS Semicon IOH(ML7213/ML7223/ML7831) DMA" 211 depends on PCI && X86 212 select DMA_ENGINE 213 help 214 Enable support for Intel EG20T PCH DMA engine. 215 216 This driver also can be used for LAPIS Semiconductor IOH(Input/ 217 Output Hub), ML7213, ML7223 and ML7831. 218 ML7213 IOH is for IVI(In-Vehicle Infotainment) use, ML7223 IOH is 219 for MP(Media Phone) use and ML7831 IOH is for general purpose use. 220 ML7213/ML7223/ML7831 is companion chip for Intel Atom E6xx series. 221 ML7213/ML7223/ML7831 is completely compatible for Intel EG20T PCH. 222 223config IMX_SDMA 224 tristate "i.MX SDMA support" 225 depends on ARCH_MXC 226 select DMA_ENGINE 227 help 228 Support the i.MX SDMA engine. This engine is integrated into 229 Freescale i.MX25/31/35/51/53 chips. 230 231config IMX_DMA 232 tristate "i.MX DMA support" 233 depends on ARCH_MXC 234 select DMA_ENGINE 235 help 236 Support the i.MX DMA engine. This engine is integrated into 237 Freescale i.MX1/21/27 chips. 238 239config MXS_DMA 240 bool "MXS DMA support" 241 depends on SOC_IMX23 || SOC_IMX28 242 select DMA_ENGINE 243 help 244 Support the MXS DMA engine. This engine including APBH-DMA 245 and APBX-DMA is integrated into Freescale i.MX23/28 chips. 246 247config EP93XX_DMA 248 bool "Cirrus Logic EP93xx DMA support" 249 depends on ARCH_EP93XX 250 select DMA_ENGINE 251 help 252 Enable support for the Cirrus Logic EP93xx M2P/M2M DMA controller. 253 254config DMA_SA11X0 255 tristate "SA-11x0 DMA support" 256 depends on ARCH_SA1100 257 select DMA_ENGINE 258 help 259 Support the DMA engine found on Intel StrongARM SA-1100 and 260 SA-1110 SoCs. This DMA engine can only be used with on-chip 261 devices. 262 263config DMA_ENGINE 264 bool 265 266comment "DMA Clients" 267 depends on DMA_ENGINE 268 269config NET_DMA 270 bool "Network: TCP receive copy offload" 271 depends on DMA_ENGINE && NET 272 default (INTEL_IOATDMA || FSL_DMA) 273 help 274 This enables the use of DMA engines in the network stack to 275 offload receive copy-to-user operations, freeing CPU cycles. 276 277 Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise 278 say N. 279 280config ASYNC_TX_DMA 281 bool "Async_tx: Offload support for the async_tx api" 282 depends on DMA_ENGINE 283 help 284 This allows the async_tx api to take advantage of offload engines for 285 memcpy, memset, xor, and raid6 p+q operations. If your platform has 286 a dma engine that can perform raid operations and you have enabled 287 MD_RAID456 say Y. 288 289 If unsure, say N. 290 291config DMATEST 292 tristate "DMA Test client" 293 depends on DMA_ENGINE 294 help 295 Simple DMA test client. Say N unless you're debugging a 296 DMA Device driver. 297 298endif 299