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)
committerRaspbian kernel package updater <root@raspbian.org>
Sun, 23 Jul 2017 02:55:17 +0000 (02:55 +0000)
commit41ce7bd910a8ca38b1dd9e9c6418e9332ff7354c
treee79dcf913478645a2302a96cd74812f2dff529c0
parentb66a0f599495a0b64ac3b7b158cdf488e8c910f7
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