From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux@armlinux.org.uk, chentao@kylinos.cn,
claudiu.beznea.uj@bp.renesas.com, rmk+kernel@armlinux.org.uk,
jroedel@suse.de, lpieralisi@kernel.org, robin.murphy@arm.com,
rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amba: bus: Drop dev_pm_domain_detach() call
Date: Tue, 4 Nov 2025 16:04:45 +0200 [thread overview]
Message-ID: <a97b8fdd-4c6d-4191-b8c8-2277550a9810@tuxon.dev> (raw)
In-Reply-To: <CAPDyKFr1VJRS2hV4Yyx_sxwSLfc0cpH5-6Bh4iO7PvWeBXoxGA@mail.gmail.com>
Hi, Ulf,
On 8/27/25 14:35, Ulf Hansson wrote:
> On Wed, 27 Aug 2025 at 12:03, Claudiu <claudiu.beznea@tuxon.dev> 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>
>
> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
>
> If it helps, let me know if you want me to pick this up via my pmdomain tree.
This wasn't picked up so far. Could you please take it through your tree if
everything looks good?
Thank you,
Claudiu
>
> Kind regards
> Uffe
>
>
>> ---
>> drivers/amba/bus.c | 9 +++------
>> 1 file changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/amba/bus.c b/drivers/amba/bus.c
>> index 74e34a07ef72..952c45ca6e48 100644
>> --- a/drivers/amba/bus.c
>> +++ b/drivers/amba/bus.c
>> @@ -291,15 +291,14 @@ static int amba_probe(struct device *dev)
>> if (ret < 0)
>> break;
>>
>> - ret = dev_pm_domain_attach(dev, PD_FLAG_ATTACH_POWER_ON);
>> + ret = dev_pm_domain_attach(dev, PD_FLAG_ATTACH_POWER_ON |
>> + PD_FLAG_DETACH_POWER_OFF);
>> if (ret)
>> break;
>>
>> ret = amba_get_enable_pclk(pcdev);
>> - if (ret) {
>> - dev_pm_domain_detach(dev, true);
>> + if (ret)
>> break;
>> - }
>>
>> pm_runtime_get_noresume(dev);
>> pm_runtime_set_active(dev);
>> @@ -314,7 +313,6 @@ static int amba_probe(struct device *dev)
>> pm_runtime_put_noidle(dev);
>>
>> amba_put_disable_pclk(pcdev);
>> - dev_pm_domain_detach(dev, true);
>> } while (0);
>>
>> return ret;
>> @@ -336,7 +334,6 @@ static void amba_remove(struct device *dev)
>> pm_runtime_put_noidle(dev);
>>
>> amba_put_disable_pclk(pcdev);
>> - dev_pm_domain_detach(dev, true);
>> }
>>
>> static void amba_shutdown(struct device *dev)
>> --
>> 2.43.0
>>
>
>
next prev parent reply other threads:[~2025-11-04 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 10:03 Claudiu
2025-08-27 11:35 ` Ulf Hansson
2025-11-04 14:04 ` Claudiu Beznea [this message]
2025-11-10 12:23 ` Ulf Hansson
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=a97b8fdd-4c6d-4191-b8c8-2277550a9810@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=chentao@kylinos.cn \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robin.murphy@arm.com \
--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
all inboxes | Powered by JetHome®