From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Ahmad Fatoum <a.fatoum@barebox.org>,
barebox@lists.infradead.org,
Alexander Shiyan <eagle.alexander923@gmail.com>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH v2 5/5] pmdomain: add Rockchip power domain support
Date: Tue, 28 Oct 2025 12:01:12 +0100 [thread overview]
Message-ID: <38b64506-cd65-4024-8e0d-b8925a96d9b4@pengutronix.de> (raw)
In-Reply-To: <aQCfFOfYug9S7Hd-@pengutronix.de>
Hi Sascha,
On 10/28/25 11:46 AM, Sascha Hauer wrote:
> On Tue, Oct 28, 2025 at 11:41:47AM +0100, Ahmad Fatoum wrote:
>> Hi,
>>
>> On 10/28/25 10:48 AM, Sascha Hauer wrote:
>>> 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)
>>
>> Is PCIe working right now?
>
> Not this particular port which still has a missing phy, but generally
> yes. The Rock5t has ethernet connected to PCIe.
>
>>
>>> 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?
>>
>> Are you sure the power domains are indeed unneeded?
>
> No, I am not, but currently it seems all power domains we need are
> turned on.
>
> If it's more convenient for you you could of course still add power
> domain support for RK3588 ;)
Not intending to anytime soon, sorry.
> Having a dummy driver might turn out useful for other SoCs, I am not
> sure how many SoCs we have which lack a power domain driver, but have
> power domains in specified in the device tree.
Yes, absolutely. I'd prefer people actually familiar with the hardware
adding matches to the dummy driver though...
I will do this for v3. Can 1, 2 and 4 already go to next?
Thanks,
Ahmad
>
> 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 |
prev parent reply other threads:[~2025-10-28 11:01 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
2025-10-28 10:41 ` Ahmad Fatoum
2025-10-28 10:46 ` Sascha Hauer
2025-10-28 11:01 ` Ahmad Fatoum [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=38b64506-cd65-4024-8e0d-b8925a96d9b4@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
--cc=m.tretter@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/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