Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH v1] remoteproc: Add device awake calls in rproc boot and shutdown path
Date: Thu, 13 Mar 2025 11:03:46 +0100	[thread overview]
Message-ID: <2025031340-crux-nectar-b62c@gregkh> (raw)
In-Reply-To: <ec46a72f-f31b-c306-e57d-9bb7f58b24a2@quicinc.com>

On Thu, Mar 13, 2025 at 02:42:10PM +0530, Souradeep Chowdhury wrote:
> Gentle Reminder.
> 
> 
> On 3/3/2025 2:38 PM, Souradeep Chowdhury wrote:
> > Add device awake calls in case of rproc boot and rproc shutdown path.
> > Currently, device awake call is only present in the recovery path
> > of remoteproc. If a user stops and starts rproc by using the sysfs
> > interface, then on pm suspension the firmware loading fails. Keep the
> > device awake in such a case just like it is done for the recovery path.
> > 
> > Signed-off-by: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
> > ---
> >   drivers/remoteproc/remoteproc_core.c | 6 +++++-
> >   1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> > index c2cf0d277729..908a7b8f6c7e 100644
> > --- a/drivers/remoteproc/remoteproc_core.c
> > +++ b/drivers/remoteproc/remoteproc_core.c
> > @@ -1916,7 +1916,8 @@ int rproc_boot(struct rproc *rproc)
> >   		pr_err("invalid rproc handle\n");
> >   		return -EINVAL;
> >   	}
> > -
> > +	
> > +	pm_stay_awake(rproc->dev.parent);
> >   	dev = &rproc->dev;
> >   	ret = mutex_lock_interruptible(&rproc->lock);
> > @@ -1961,6 +1962,7 @@ int rproc_boot(struct rproc *rproc)
> >   		atomic_dec(&rproc->power);
> >   unlock_mutex:
> >   	mutex_unlock(&rproc->lock);
> > +	pm_relax(rproc->dev.parent);
> >   	return ret;
> >   }
> >   EXPORT_SYMBOL(rproc_boot);
> > @@ -1991,6 +1993,7 @@ int rproc_shutdown(struct rproc *rproc)
> >   	struct device *dev = &rproc->dev;
> >   	int ret = 0;
> > +	pm_stay_awake(rproc->dev.parent);
> >   	ret = mutex_lock_interruptible(&rproc->lock);
> >   	if (ret) {
> >   		dev_err(dev, "can't lock rproc %s: %d\n", rproc->name, ret);
> > @@ -2027,6 +2030,7 @@ int rproc_shutdown(struct rproc *rproc)
> >   	rproc->table_ptr = NULL;
> >   out:
> >   	mutex_unlock(&rproc->lock);
> > +	pm_relax(rproc->dev.parent);
> >   	return ret;
> >   }
> >   EXPORT_SYMBOL(rproc_shutdown);
> 
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2025-03-13 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  9:08 [PATCH v1] remoteproc: Add device awake calls in rproc boot and shutdown path Souradeep Chowdhury
2025-03-03  9:10 ` kernel test robot
2025-03-13  9:12 ` Souradeep Chowdhury
2025-03-13 10:03   ` Greg KH [this message]
2025-03-17  6:45     ` Souradeep Chowdhury

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=2025031340-crux-nectar-b62c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andersson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=quic_schowdhu@quicinc.com \
    --cc=stable@vger.kernel.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