Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 6d4f5879 authored by Haavard Skinnemoen's avatar Haavard Skinnemoen Committed by Linus Torvalds
Browse files

dmaengine: correct invalid assumptions in the Kconfig text 



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: default avatarHaavard Skinnemoen <hskinnemoen@atmel.com>
Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent e593f070

drivers/dma/Kconfig

+5 −3
Original line number Diff line number Diff line
@@ -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