From: Quentin Schulz <quentin.schulz@cherry.de>
To: Chaoyi Chen <chaoyi.chen@rock-chips.com>,
Frank Zhang <rmxpzlb@gmail.com>
Cc: ulf.hansson@linaro.org, heiko@sntech.de,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pmdomain:rockchip: Fix init genpd as GENPD_STATE_ON before regulator ready
Date: Fri, 12 Dec 2025 13:19:21 +0100 [thread overview]
Message-ID: <51f5109f-66dc-4ec5-9f1f-91085f2fc6c2@cherry.de> (raw)
In-Reply-To: <27dff4a5-1e9d-458d-936a-941c3f10c139@rock-chips.com>
Hi Chaoyi, Frank,
On 12/8/25 4:17 AM, Chaoyi Chen wrote:
> On 12/5/2025 2:47 PM, Frank Zhang wrote:
>> RK3588_PD_NPU initialize as GENPD_STATE_ON before regulator ready.
>> rknn_iommu initlized success and suspend RK3588_PD_NPU. When rocket
>> driver register, it will resume rknn_iommu.
>>
>> If regulator is still not ready at this point, rknn_iommu resume fail,
>> pm runtime status will be error: -EPROBE_DEFER.
>>
>> This patch check regulator when pmdomain init, if regulator is not ready
>> or not enabled, power off pmdomain. Consumer device can power on it's
>> pmdomain after regulator ready
>>
>> Signed-off-by: Frank Zhang <rmxpzlb@gmail.com>
>> ---
>> drivers/pmdomain/rockchip/pm-domains.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/pmdomain/rockchip/pm-domains.c b/drivers/pmdomain/rockchip/pm-domains.c
>> index 1955c6d453e4..bc69f5d840e6 100644
>> --- a/drivers/pmdomain/rockchip/pm-domains.c
>> +++ b/drivers/pmdomain/rockchip/pm-domains.c
>> @@ -659,6 +659,11 @@ static int rockchip_pd_power(struct rockchip_pm_domain *pd, bool power_on)
>> return ret;
>> }
>>
>> +static bool rockchip_pd_regulator_is_enabled(struct rockchip_pm_domain *pd)
>> +{
>> + return IS_ERR_OR_NULL(pd->supply) ? false : regulator_is_enabled(pd->supply);
>> +}
>> +
>> static int rockchip_pd_regulator_disable(struct rockchip_pm_domain *pd)
>> {
>> return IS_ERR_OR_NULL(pd->supply) ? 0 : regulator_disable(pd->supply);
>> @@ -861,6 +866,15 @@ static int rockchip_pm_add_one_domain(struct rockchip_pmu *pmu,
>> pd->genpd.name = pd->info->name;
>> else
>> pd->genpd.name = kbasename(node->full_name);
>> +
>> + if (pd->info->need_regulator) {
>> + if (IS_ERR_OR_NULL(pd->supply))
>> + pd->supply = devm_of_regulator_get(pmu->dev, pd->node, "domain");
>> +
>> + if (!rockchip_pd_regulator_is_enabled(pd))
>> + rockchip_pd_power(pd, false);
>> + }
>> +
>> pd->genpd.power_off = rockchip_pd_power_off;
>> pd->genpd.power_on = rockchip_pd_power_on;
>> pd->genpd.attach_dev = rockchip_pd_attach_dev;
>>
>
> @Quentin, Could you please try this patch? This should resolve the
> problem you're currently facing where the NPU fails to work in
> built-in module.
>
Thanks for the heads up, Chaoyi!
I tested that for a few hours with a bootloop script (700+) and seems
like I couldn't reproduce the issue 4 reported in
https://lore.kernel.org/linux-rockchip/0b20d760-ad4f-41c0-b733-39db10d6cc41@cherry.de/
when building wih DRM_ACCEL_ROCKET=y.
So:
Tested-by: Quentin Schulz <quentin.schulz@cherry.de> # NPU on RK3588 Jaguar
@Frank, please add me in Cc if there's a v2 so I can recheck if you want.
Thanks for having a look!
Cheers,
Quentin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-12-12 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 6:47 [PATCH] pmdomain:rockchip: Fix init genpd as GENPD_STATE_ON before regulator ready Frank Zhang
2025-12-08 3:17 ` Chaoyi Chen
2025-12-12 12:19 ` Quentin Schulz [this message]
2025-12-09 13:12 ` Sebastian Reichel
2025-12-09 15:04 ` rmxpzlb
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=51f5109f-66dc-4ec5-9f1f-91085f2fc6c2@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=chaoyi.chen@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rmxpzlb@gmail.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