summaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorGregory CLEMENT <gregory.clement@free-electrons.com>2016-04-29 09:49:06 +0200
committerVinod Koul <vinod.koul@intel.com>2016-05-03 12:27:47 +0530
commitdd130c652cb745e82b70cb71a3cf2dd876295e96 (patch)
treee4e8f99051df614ec14c8143e7e2cde78b0c4f06 /Kbuild
parentbc822e1251f908ab2560365d388f36afb9da255a (diff)
downloadlinux-dd130c652cb745e82b70cb71a3cf2dd876295e96.tar.gz
dmaengine: mv_xor: use SoC type instead of directly the operation mode
Currently the main difference between legacy XOR engine and newer one, is the way the engine modes are setup (either in the descriptor or through the controller registers). In order to be able to take into account new generation of the XOR engine for the ARM64 SoC, we need to identify them by type, and then depending to the type the engine setup will be selected. Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions