dmaengine: mv_xor_v2: enable XOR engine after its configuration
authorHanna Hawa <hannah@marvell.com>
Fri, 5 May 2017 09:57:47 +0000 (11:57 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 14 Jun 2017 13:05:57 +0000 (15:05 +0200)
commit0d0918504a96d406d1a8beedab47bfb93c01ee67
treeb6004141a0c77d6ecba0a6ce64d8984e88af83e6
parente2a092eab8a5b0390e48c04b5d35c85d1c8900be
dmaengine: mv_xor_v2: enable XOR engine after its configuration

commit ab2c5f0a77fe49bdb6e307b397496373cb47d2c2 upstream.

The engine was enabled prior to its configuration, which isn't
correct. This patch relocates the activation of the XOR engine, to be
after the configuration of the XOR engine.

Fixes: 19a340b1a820 ("dmaengine: mv_xor_v2: new driver")
Signed-off-by: Hanna Hawa <hannah@marvell.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/dma/mv_xor_v2.c