Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org, ohad@wizery.com,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
Date: Tue, 17 Apr 2018 14:47:15 -0700	[thread overview]
Message-ID: <20180417214715.GE17344@builder> (raw)
In-Reply-To: <20180417194415.5155-1-sibis@codeaurora.org>

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
> 

      reply	other threads:[~2018-04-17 21:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180417214715.GE17344@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=sibis@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox