[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Sep 2022 13:23:57 -0600
From: Mathieu Poirier <mathieu.poirier@...aro.org>
To: Maria Yu <quic_aiquny@...cinc.com>
Cc: bjorn.andersson@...aro.org, linux-remoteproc@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
quic_clew@...cinc.com
Subject: Re: [PATCH v1] remoteproc: core: do pm relax when not first crash
Hi Maria,
On Fri, Sep 09, 2022 at 04:33:33PM +0800, Maria Yu wrote:
> Even if it is not first crash, need to relax the pm
> wakelock otherwise the device will stay awake.
>
The goal is exactly to keep the device awake...
> Signed-off-by: Maria Yu <quic_aiquny@...cinc.com>
> ---
> drivers/remoteproc/remoteproc_core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index e5279ed9a8d7..30078043e939 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -1956,6 +1956,7 @@ static void rproc_crash_handler_work(struct work_struct *work)
> if (rproc->state == RPROC_CRASHED || rproc->state == RPROC_OFFLINE) {
> /* handle only the first crash detected */
> mutex_unlock(&rproc->lock);
> + pm_relax(rproc->dev.parent);
If we are here it means that rproc_crash_handler_work() has already been called
_and_ that a recovery is in process. When the first crash handler completes
pm_relax() will be called and the device will go to sleep as expected.
Thanks,
Mathieu
> return;
> }
>
> --
> 2.7.4
>
Powered by blists - more mailing lists