From: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Subject: Re: [PATCH v5] remoteproc: Add device awake calls in rproc boot and shutdown path
Date: Thu, 22 May 2025 12:16:41 +0530 [thread overview]
Message-ID: <fde458da-5f44-7947-f746-270b9ecf2991@quicinc.com> (raw)
In-Reply-To: <cf3fffda-8d88-b962-398d-d038cd10b981@quicinc.com>
Gentle Reminder
On 5/19/2025 10:54 AM, Souradeep Chowdhury wrote:
> Gentle Reminder
>
>
> On 5/14/2025 1:03 PM, Souradeep Chowdhury wrote:
>> Gentle Reminder
>>
>>
>> On 4/8/2025 4:13 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 an user stops and starts rproc by using the sysfs
>>> interface, then on pm suspension the firmware fails to load as the
>>> request_firmware call under adsp_load relies on usermodehelper
>>> process which gets freezed on pm suspension. Add device awake calls
>>> to fix this.
>>>
>>> Signed-off-by: Souradeep Chowdhury <quic_schowdhu@quicinc.com>
>>> Reviewed-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
>>> ---
>>> Changes in v5
>>>
>>> *Added more details to commit description
>>>
>>> Changes in v4
>>>
>>> *Remove stability from mailing list
>>> *Remove the extra tab in v3
>>> *Change the commit description
>>>
>>> drivers/remoteproc/remoteproc_core.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/remoteproc/remoteproc_core.c
>>> b/drivers/remoteproc/remoteproc_core.c
>>> index c2cf0d277729..5d6c4e694b4c 100644
>>> --- a/drivers/remoteproc/remoteproc_core.c
>>> +++ b/drivers/remoteproc/remoteproc_core.c
>>> @@ -1917,6 +1917,7 @@ int rproc_boot(struct rproc *rproc)
>>> 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);
>>
>
next prev parent reply other threads:[~2025-05-22 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 10:43 Souradeep Chowdhury
2025-04-23 6:26 ` Souradeep Chowdhury
2025-05-14 7:33 ` Souradeep Chowdhury
2025-05-19 5:24 ` Souradeep Chowdhury
2025-05-22 6:46 ` Souradeep Chowdhury [this message]
2025-06-17 13:14 ` Bjorn Andersson
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=fde458da-5f44-7947-f746-270b9ecf2991@quicinc.com \
--to=quic_schowdhu@quicinc.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®