From: Icenowy Zheng <uwu@icenowy.me>
To: Yixun Lan <dlan@kernel.org>, Ulf Hansson <ulf.hansson@oss.qualcomm.com>
Cc: Ulf Hansson <ulfh@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH] pmdomain: core: connect consumer with supplier via device link
Date: Mon, 16 Nov 2026 15:46:59 +0800 [thread overview]
Message-ID: <b7d7ac2eee0e64aa7c267def5c2a8a022c7da425.camel@icenowy.me> (raw)
In-Reply-To: <20261116072442-GKA100890@kernel.org>
在 2026-11-16一的 07:24 +0000,Yixun Lan写道:
> Hi Ulf,
>
> On 12:33 Sat 14 Nov , Ulf Hansson wrote:
> > On Thu, Nov 12, 2026 at 8:45 AM Yixun Lan <dlan@kernel.org> wrote:
> > >
> > > Connect downstream Power Domain consumer with the supplier
> > > through
> > > the device link API, So when the pmdomain driver is unloaded or
> > > unbinded,
> > > the consumer can be automatically notified and purged gracefully.
> > >
> > > Signed-off-by: Yixun Lan <dlan@kernel.org>
> >
> > Can you check if the below commit that sits on my fixes branch
> > solves
> > this problem for you?
> >
> No, I've cherry-picked below commit and it does not solve my issue,
> it's a different problem.
>
> Problem here is the pm consumer side isn't aware pm driver is
> removed.
>
I do think it's just better to prevent PM drivers from being removed.
Thanks,
Icenowy
>
> > e279833a5362 pmdomain: core: Wait for device link removals before
> > dropping genpd->dev
> >
> > Kind regards
> > Uffe
> >
prev parent reply other threads:[~2026-11-16 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 7:45 Yixun Lan
2026-11-14 11:33 ` Ulf Hansson
2026-11-16 7:24 ` Yixun Lan
2026-11-16 7:46 ` Icenowy Zheng [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=b7d7ac2eee0e64aa7c267def5c2a8a022c7da425.camel@icenowy.me \
--to=uwu@icenowy.me \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=ulf.hansson@oss.qualcomm.com \
--cc=ulfh@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
all inboxes | Powered by JetHome®