From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@barebox.org>, barebox@lists.infradead.org
Subject: Re: [PATCH v2 5/5] pmdomain: add Rockchip power domain support
Date: Tue, 28 Oct 2025 10:48:11 +0100 [thread overview]
Message-ID: <aQCRW2k8IkHPTW_-@pengutronix.de> (raw)
In-Reply-To: <10308082-4d36-488f-b87c-9357e0e7125d@pengutronix.de>
On Tue, Oct 28, 2025 at 10:04:06AM +0100, Ahmad Fatoum wrote:
>
>
> On 10/28/25 9:57 AM, Sascha Hauer wrote:
> > On Mon, Oct 27, 2025 at 08:28:20PM +0100, Ahmad Fatoum wrote:
> >> +static int rockchip_pm_add_subdomain(struct rockchip_pmu *pmu,
> >> + struct device_node *parent)
> >> +{
> >> + struct device_node *np;
> >> +
> >> + for_each_child_of_node(parent, np)
> >> + return -ENOSYS;
> >> +
> >
> > I gave it a quick try on RK3588 and driver probe fails here. RK3588 has
> > several subdomains in its power controller.
>
> I need it on rk3566 though, otherwise the probe hangs. Should I drop the
> rk358x compatibles?
That leaves us with the warnings introduced with the last patch:
WARNING: dwc3 fc000000.usb@fc000000.of: power domain not found (ignoring)
WARNING: rockchip-dw-pcie a40c00000.pcie@fe180000.of: power domain not found (ignoring)
WARNING: rockchip-dw-pcie a41000000.pcie@fe190000.of: power domain not found (ignoring)
WARNING: dw_mmc fe2c0000.mmc@fe2c0000.of: power domain not found (ignoring)
WARNING: dwc3 fc400000.usb@fc400000.of: power domain not found (ignoring)
WARNING: rockchip-dw-pcie a40400000.pcie@fe160000.of: power domain not found (ignoring)
Maybe add a dummy driver where people can add their compatible to when
they encounter the warning knowing that their SoC doesn't need a power
domain driver?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-10-28 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 19:28 [PATCH v2 1/5] regulator: implement dev_of_regulator_get Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 2/5] pmdomain: look up pmdomain even if not have_genpd_providers Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 3/5] pmdomain: warn if deep probe enabled and driver missing Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 4/5] pmdomain: allow callback for when devices are attached Ahmad Fatoum
2025-10-27 19:28 ` [PATCH v2 5/5] pmdomain: add Rockchip power domain support Ahmad Fatoum
2025-10-28 8:57 ` Sascha Hauer
2025-10-28 9:04 ` Ahmad Fatoum
2025-10-28 9:48 ` Sascha Hauer [this message]
2025-10-28 10:41 ` Ahmad Fatoum
2025-10-28 10:46 ` Sascha Hauer
2025-10-28 11:01 ` Ahmad Fatoum
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=aQCRW2k8IkHPTW_-@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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