* [PATCH] remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
@ 2018-04-17 19:44 Sibi Sankar
2018-04-17 21:47 ` Bjorn Andersson
0 siblings, 1 reply; 2+ messages in thread
From: Sibi Sankar @ 2018-04-17 19:44 UTC (permalink / raw)
To: bjorn.andersson; +Cc: linux-remoteproc, ohad, linux-arm-msm, Sibi Sankar
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.
Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
---
drivers/remoteproc/qcom_q6v5_pil.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/remoteproc/qcom_q6v5_pil.c b/drivers/remoteproc/qcom_q6v5_pil.c
index 8e70a627e0bb..296eb3f8b551 100644
--- a/drivers/remoteproc/qcom_q6v5_pil.c
+++ b/drivers/remoteproc/qcom_q6v5_pil.c
@@ -761,13 +761,12 @@ static int q6v5_start(struct rproc *rproc)
}
/* Assign MBA image access in DDR to q6 */
- xfermemop_ret = q6v5_xfer_mem_ownership(qproc, &qproc->mba_perm, true,
+ ret = q6v5_xfer_mem_ownership(qproc, &qproc->mba_perm, true,
qproc->mba_phys,
qproc->mba_size);
- if (xfermemop_ret) {
+ if (ret) {
dev_err(qproc->dev,
- "assigning Q6 access to mba memory failed: %d\n",
- xfermemop_ret);
+ "assigning Q6 access to mba memory failed: %d\n", ret);
goto disable_active_clks;
}
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
^ permalink raw reply related [flat|nested] 2+ messages in thread* Re: [PATCH] remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
2018-04-17 19:44 [PATCH] remoteproc: Prevent incorrect rproc state on xfer mem ownership failure Sibi Sankar
@ 2018-04-17 21:47 ` Bjorn Andersson
0 siblings, 0 replies; 2+ messages in thread
From: Bjorn Andersson @ 2018-04-17 21:47 UTC (permalink / raw)
To: Sibi Sankar; +Cc: linux-remoteproc, ohad, linux-arm-msm
On Tue 17 Apr 12:44 PDT 2018, Sibi Sankar wrote:
> 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.
>
Added Cc: stable@vger.kernel.org and applied, thanks.
Regards,
Bjorn
> Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
> ---
> drivers/remoteproc/qcom_q6v5_pil.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/remoteproc/qcom_q6v5_pil.c b/drivers/remoteproc/qcom_q6v5_pil.c
> index 8e70a627e0bb..296eb3f8b551 100644
> --- a/drivers/remoteproc/qcom_q6v5_pil.c
> +++ b/drivers/remoteproc/qcom_q6v5_pil.c
> @@ -761,13 +761,12 @@ static int q6v5_start(struct rproc *rproc)
> }
>
> /* Assign MBA image access in DDR to q6 */
> - xfermemop_ret = q6v5_xfer_mem_ownership(qproc, &qproc->mba_perm, true,
> + ret = q6v5_xfer_mem_ownership(qproc, &qproc->mba_perm, true,
> qproc->mba_phys,
> qproc->mba_size);
> - if (xfermemop_ret) {
> + if (ret) {
> dev_err(qproc->dev,
> - "assigning Q6 access to mba memory failed: %d\n",
> - xfermemop_ret);
> + "assigning Q6 access to mba memory failed: %d\n", ret);
> goto disable_active_clks;
> }
>
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-04-17 21:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-17 19:44 [PATCH] remoteproc: Prevent incorrect rproc state on xfer mem ownership failure Sibi Sankar
2018-04-17 21:47 ` Bjorn Andersson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.