Re: [PATCH] dmaengine: Driver for the AVR32 DMACA controller

[David Brownell <david-b@pacbell.net>]

On Tuesday 20 November 2007, Haavard Skinnemoen wrote:
> This patch depends on "DMA: Correct invalid assumptions in the Kconfig
> text" (without the part that adds AVR32 to the dependency list) and
> "DMAENGINE: Convert from class_device to device".

That regression fix still doesn't seem to be merged, or
even in the MM tree.

Here's a tweaked version of what Haavard sent.

- Dave

========	CUT HERE
From: Haavard Skinnemoen <hskinnemoen@atmel.com>

This patch corrects recently changed (and now invalid) Kconfig
descriptions for the DMA engine framework:

 - Non-Intel(R) hardware also has DMA engines;
 - DMA is used for more than memcpy and RAID offloading.
 
In fact, on most platforms memcpy and RAID aren't factors, and DMA
exists so that peripherals can transfer data to/from memory while
the CPU does other work.

Signed-off-by: Haavard Skinnemoen <hskinnemoen@atmel.com>
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
---
 drivers/dma/Kconfig |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

--- g26.orig/drivers/dma/Kconfig	2007-10-30 23:58:27.000000000 -0700
+++ g26/drivers/dma/Kconfig	2007-11-22 17:43:33.000000000 -0800
@@ -3,11 +3,13 @@
 #
 
 menuconfig DMADEVICES
-	bool "DMA Offload Engine support"
+	bool "DMA Engine support"
 	depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
 	help
-	  Intel(R) offload engines enable offloading memory copies in the
-	  network stack and RAID operations in the MD driver.
+	  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.
 
 if DMADEVICES