#
# DMA engine configuration
#

menu "DMA Engine support"

config DMA_ENGINE
	bool "Support for DMA engines"
	---help---
	  DMA engines offload copy operations from the CPU to dedicated
	  hardware, allowing the copies to happen asynchronously.

config NET_DMA
	bool "Use DMA engines in the network stack"
	depends on DMA_ENGINE
	---help---
	  Say Y to enable the use of DMA engines in the network stack to
	  offload receive copy-to-user operations, freeing CPU cycles.

config NET_DMA_EARLY
	bool "Do early DMA copies"
	depends on NET_DMA
	---help---
	  Enabling this will cause the network stack to start DMA copies
	  earlier. This can improve throughput, but this is also a more
	  invasive change, and can be unstable.

#
# DMA devices
#
config INTEL_CB
	tristate "Support for Intel Crystal Beach 1"
	depends on DMA_ENGINE
	---help---
	  Crystal Beach is the DMA engine in the Intel Blackford Northbridge.


config INTEL_CB_DMA_SIM
	bool "DMA softcopy"
	depends on INTEL_CB
	---help---
	  Enable this to simulate the presence of a CB device.

config INTEL_CB_DEBUG
	bool "Debug"
	depends on INTEL_CB
	---help---
	  Enable this to turn on some mostly obsolete debug messages.


config DMA_TESTCLIENT
	tristate "DMA test client"
	depends on DMA_ENGINE
	---help---
	  The CB test client driver performs a DMA-assisted memcpy on module
	  load, and prints the result when unloaded. It is pretty simple, but
	  maybe someday this will grow up into an actually useful test client.

endmenu
