dmaengine: remove arch dependency from DMADEVICES

The dependency is redundant since all drivers set their specific arch dependencies. The NET_DMA option is modified to be enabled only on platforms where it is known to have a positive effect. HAS_DMA is added as an explicit dependency for the DMADEVICES menu. Acked-by: Adrian Bunk <bunk@kernel.org> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

dmaengine: remove arch dependency from DMADEVICES
The dependency is redundant since all drivers set their specific arch dependencies. The NET_DMA option is modified to be enabled only on platforms where it is known to have a positive effect. HAS_DMA is added as an explicit dependency for the DMADEVICES menu. Acked-by: Adrian Bunk <bunk@kernel.org> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Dan Williams
1 parent 1099dc7924
Showing 1 changed file with 8 additions and 5 deletions Side-by-side Diff
drivers/dma/Kconfig
@@ -4,13 +4,14 @@
  
 menuconfig DMADEVICES
 	bool "DMA Engine support"
-	depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX || PPC
-	depends on !HIGHMEM64G
+	depends on !HIGHMEM64G && HAS_DMA
 	help
 	  DMA engines can do asynchronous data transfers without
 	  involving the host CPU.  Currently, this framework can be
 	  used to offload memory copies in the network stack and
-	  RAID operations in the MD driver.
+	  RAID operations in the MD driver.  This menu only presents
+	  DMA Device drivers supported by the configured arch, it may
+	  be empty in some cases.
  
 if DMADEVICES
  
  
@@ -55,11 +56,13 @@
 config NET_DMA
 	bool "Network: TCP receive copy offload"
 	depends on DMA_ENGINE && NET
+	default (INTEL_IOATDMA || FSL_DMA)
 	help
 	  This enables the use of DMA engines in the network stack to
 	  offload receive copy-to-user operations, freeing CPU cycles.
-	  Since this is the main user of the DMA engine, it should be enabled;
-	  say Y here.
+
+	  Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
+	  say N.
  
 endif
...	...	@@ -4,13 +4,14 @@
4	4
5	5	menuconfig DMADEVICES
6	6	bool "DMA Engine support"
7		- depends on (PCI && X86) \|\| ARCH_IOP32X \|\| ARCH_IOP33X \|\| ARCH_IOP13XX \|\| PPC
8		- depends on !HIGHMEM64G
	7	+ depends on !HIGHMEM64G && HAS_DMA
9	8	help
10	9	DMA engines can do asynchronous data transfers without
11	10	involving the host CPU. Currently, this framework can be
12	11	used to offload memory copies in the network stack and
13		- RAID operations in the MD driver.
	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.
14	15
15	16	if DMADEVICES
16	17
17	18
...	...	@@ -55,11 +56,13 @@
55	56	config NET_DMA
56	57	bool "Network: TCP receive copy offload"
57	58	depends on DMA_ENGINE && NET
	59	+ default (INTEL_IOATDMA \|\| FSL_DMA)
58	60	help
59	61	This enables the use of DMA engines in the network stack to
60	62	offload receive copy-to-user operations, freeing CPU cycles.
61		- Since this is the main user of the DMA engine, it should be enabled;
62		- say Y here.
	63	+
	64	+ Say Y here if you enabled INTEL_IOATDMA or FSL_DMA, otherwise
	65	+ say N.
63	66
64	67	endif