remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
authorSibi Sankar <sibis@codeaurora.org>
Tue, 17 Apr 2018 19:44:15 +0000 (01:14 +0530)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 3 Jul 2018 09:27:06 +0000 (11:27 +0200)
commita9eb2d03252e476735de7ff9752ec6ed16ad7025
tree8caaa293995a27f5a026ff67e7d44e34d514aa15
parent0c8d1ee930ae452f036669f7462e3efd3fb770ef
remoteproc: Prevent incorrect rproc state on xfer mem ownership failure

commit 2724807f7f70a6a3e67b3f6bf921cc77ed39c8a1 upstream.

Any failure in the secure call for transferring mem ownership of mba
region to Q6 would result in reporting that the remoteproc device
is running. This is because the previous q6v5_clk_enable would have
been a success. Prevent this by updating variable 'ret' accordingly.

Cc: stable@vger.kernel.org
Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/remoteproc/qcom_q6v5_pil.c