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