dmaengine: driver for the ARM PL080/PL081 PrimeCells v5
[deliverable/linux.git] / drivers / dma / Kconfig
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_DISABLE_CHANNEL_SWITCH
50 bool
51
52 config 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
60 config 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_CHANNEL_SWITCH
66 select ASYNC_TX_DISABLE_PQ_VAL_DMA
67 select ASYNC_TX_DISABLE_XOR_VAL_DMA
68 help
69 Enable support for the Intel(R) I/OAT DMA engine present
70 in recent Intel Xeon chipsets.
71
72 Say Y here if you have such a chipset.
73
74 If unsure, say N.
75
76 config INTEL_IOP_ADMA
77 tristate "Intel IOP ADMA support"
78 depends on ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
79 select DMA_ENGINE
80 help
81 Enable support for the Intel(R) IOP Series RAID engines.
82
83 config DW_DMAC
84 tristate "Synopsys DesignWare AHB DMA support"
85 depends on AVR32
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
92 config 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
100 config FSL_DMA
101 tristate "Freescale Elo and Elo Plus DMA support"
102 depends on FSL_SOC
103 select DMA_ENGINE
104 ---help---
105 Enable support for the Freescale Elo and Elo Plus DMA controllers.
106 The Elo is the DMA controller on some 82xx and 83xx parts, and the
107 Elo Plus is the DMA controller on 85xx and 86xx parts.
108
109 config MPC512X_DMA
110 tristate "Freescale MPC512x built-in DMA engine support"
111 depends on PPC_MPC512x
112 select DMA_ENGINE
113 ---help---
114 Enable support for the Freescale MPC512x built-in DMA engine.
115
116 config MV_XOR
117 bool "Marvell XOR engine support"
118 depends on PLAT_ORION
119 select DMA_ENGINE
120 ---help---
121 Enable support for the Marvell XOR engine.
122
123 config MX3_IPU
124 bool "MX3x Image Processing Unit support"
125 depends on ARCH_MX3
126 select DMA_ENGINE
127 default y
128 help
129 If you plan to use the Image Processing unit in the i.MX3x, say
130 Y here. If unsure, select Y.
131
132 config MX3_IPU_IRQS
133 int "Number of dynamically mapped interrupts for IPU"
134 depends on MX3_IPU
135 range 2 137
136 default 4
137 help
138 Out of 137 interrupt sources on i.MX31 IPU only very few are used.
139 To avoid bloating the irq_desc[] array we allocate a sufficient
140 number of IRQ slots and map them dynamically to specific sources.
141
142 config TXX9_DMAC
143 tristate "Toshiba TXx9 SoC DMA support"
144 depends on MACH_TX49XX || MACH_TX39XX
145 select DMA_ENGINE
146 help
147 Support the TXx9 SoC internal DMA controller. This can be
148 integrated in chips such as the Toshiba TX4927/38/39.
149
150 config SH_DMAE
151 tristate "Renesas SuperH DMAC support"
152 depends on (SUPERH && SH_DMA) || (ARM && ARCH_SHMOBILE)
153 depends on !SH_DMA_API
154 select DMA_ENGINE
155 help
156 Enable support for the Renesas SuperH DMA controllers.
157
158 config COH901318
159 bool "ST-Ericsson COH901318 DMA support"
160 select DMA_ENGINE
161 depends on ARCH_U300
162 help
163 Enable support for ST-Ericsson COH 901 318 DMA.
164
165 config STE_DMA40
166 bool "ST-Ericsson DMA40 support"
167 depends on ARCH_U8500
168 select DMA_ENGINE
169 help
170 Support for ST-Ericsson DMA40 controller
171
172 config AMCC_PPC440SPE_ADMA
173 tristate "AMCC PPC440SPe ADMA support"
174 depends on 440SPe || 440SP
175 select DMA_ENGINE
176 select ARCH_HAS_ASYNC_TX_FIND_CHANNEL
177 help
178 Enable support for the AMCC PPC440SPe RAID engines.
179
180 config TIMB_DMA
181 tristate "Timberdale FPGA DMA support"
182 depends on MFD_TIMBERDALE || HAS_IOMEM
183 select DMA_ENGINE
184 help
185 Enable support for the Timberdale FPGA DMA engine.
186
187 config ARCH_HAS_ASYNC_TX_FIND_CHANNEL
188 bool
189
190 config PL330_DMA
191 tristate "DMA API Driver for PL330"
192 select DMA_ENGINE
193 depends on PL330
194 help
195 Select if your platform has one or more PL330 DMACs.
196 You need to provide platform specific settings via
197 platform_data for a dma-pl330 device.
198
199 config PCH_DMA
200 tristate "Topcliff PCH DMA support"
201 depends on PCI && X86
202 select DMA_ENGINE
203 help
204 Enable support for the Topcliff PCH DMA engine.
205
206 config DMA_ENGINE
207 bool
208
209 comment "DMA Clients"
210 depends on DMA_ENGINE
211
212 config NET_DMA
213 bool "Network: TCP receive copy offload"
214 depends on DMA_ENGINE && NET
215 default (INTEL_IOATDMA || FSL_DMA)
216 help
217 This enables the use of DMA engines in the network stack to
218 offload receive copy-to-user operations, freeing CPU cycles.
219
220 Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
221 say N.
222
223 config ASYNC_TX_DMA
224 bool "Async_tx: Offload support for the async_tx api"
225 depends on DMA_ENGINE
226 help
227 This allows the async_tx api to take advantage of offload engines for
228 memcpy, memset, xor, and raid6 p+q operations. If your platform has
229 a dma engine that can perform raid operations and you have enabled
230 MD_RAID456 say Y.
231
232 If unsure, say N.
233
234 config DMATEST
235 tristate "DMA Test client"
236 depends on DMA_ENGINE
237 help
238 Simple DMA test client. Say N unless you're debugging a
239 DMA Device driver.
240
241 endif
This page took 0.036034 seconds and 5 git commands to generate.