From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: andersson@kernel.org, ulf.hansson@linaro.org, rafael@kernel.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH] rpmsg: core: Drop dev_pm_domain_detach() call
Date: Fri, 29 Aug 2025 10:35:59 -0600 [thread overview]
Message-ID: <aLHW7yBvEsAlYQoK@p14s> (raw)
In-Reply-To: <20250827101352.927542-1-claudiu.beznea.uj@bp.renesas.com>
On Wed, Aug 27, 2025 at 01:13:52PM +0300, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Starting with commit f99508074e78 ("PM: domains: Detach on
> device_unbind_cleanup()"), there is no longer a need to call
> dev_pm_domain_detach() in the bus remove function. The
> device_unbind_cleanup() function now handles this to avoid
> invoking devres cleanup handlers while the PM domain is
> powered off, which could otherwise lead to failures as
> described in the above-mentioned commit.
>
> Drop the explicit dev_pm_domain_detach() call and rely instead
> on the flags passed to dev_pm_domain_attach() to power off the
> domain.
>
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---
> drivers/rpmsg/rpmsg_core.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
Applied.
Thanks,
Mathieu
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
> index bece5e635ee9..5d661681a9b6 100644
> --- a/drivers/rpmsg/rpmsg_core.c
> +++ b/drivers/rpmsg/rpmsg_core.c
> @@ -479,7 +479,8 @@ static int rpmsg_dev_probe(struct device *dev)
> struct rpmsg_endpoint *ept = NULL;
> int err;
>
> - err = dev_pm_domain_attach(dev, PD_FLAG_ATTACH_POWER_ON);
> + err = dev_pm_domain_attach(dev, PD_FLAG_ATTACH_POWER_ON |
> + PD_FLAG_DETACH_POWER_OFF);
> if (err)
> goto out;
>
> @@ -538,8 +539,6 @@ static void rpmsg_dev_remove(struct device *dev)
> if (rpdrv->remove)
> rpdrv->remove(rpdev);
>
> - dev_pm_domain_detach(dev, true);
> -
> if (rpdev->ept)
> rpmsg_destroy_ept(rpdev->ept);
> }
> --
> 2.43.0
>
prev parent reply other threads:[~2025-08-29 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:13 [PATCH] rpmsg: core: Drop dev_pm_domain_detach() call Claudiu
2025-08-27 11:35 ` Ulf Hansson
2025-08-29 16:35 ` Mathieu Poirier [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=aLHW7yBvEsAlYQoK@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.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