2 # DMA engine configuration
6 bool "DMA Engine support"
7 depends on !HIGHMEM64G && HAS_DMA
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.
21 tristate "Intel I/OAT DMA support"
26 Enable support for the Intel(R) I/OAT DMA engine present
27 in recent Intel Xeon chipsets.
29 Say Y here if you have such a chipset.
34 tristate "Intel IOP ADMA support"
35 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
39 Enable support for the Intel(R) IOP Series RAID engines.
42 tristate "Synopsys DesignWare AHB DMA support"
45 default y if CPU_AT32AP7000
47 Support the Synopsys DesignWare AHB DMA controller. This
48 can be integrated in chips such as the Atmel AT32ap7000.
51 bool "Freescale MPC85xx/MPC83xx DMA support"
55 Enable support for the Freescale DMA engine. Now, it support
56 MPC8560/40, MPC8555, MPC8548 and MPC8641 processors.
57 The MPC8349, MPC8360 is also supported.
60 bool "Marvell XOR engine support"
65 Enable support for the Marvell XOR engine.
74 bool "Network: TCP receive copy offload"
75 depends on DMA_ENGINE && NET
76 default (INTEL_IOATDMA || FSL_DMA)
78 This enables the use of DMA engines in the network stack to
79 offload receive copy-to-user operations, freeing CPU cycles.
81 Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
85 tristate "DMA Test client"
88 Simple DMA test client. Say N unless you're debugging a