From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
arm-scmi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC v5 1/2] pmdomain: core: support domain hierarchy via power-domain-map
Date: Tue, 03 Feb 2026 15:12:53 -0800 [thread overview]
Message-ID: <7hjywtzaiy.fsf@baylibre.com> (raw)
In-Reply-To: <20260127151735.GA1699112-robh@kernel.org>
Rob Herring <robh@kernel.org> writes:
> On Thu, Jan 22, 2026 at 05:14:00PM -0800, Kevin Hilman (TI) wrote:
>> Add of_genpd_[add|remove]_subdomain_map() helper functions to support
>> hierarchical PM domains defined by using power-domains-map
>
> power-domain-map. No 's'.
>
>> property (c.f. nexus node maps in DT spec, section 2.5.1).
>>
>> This enables PM domain providers with #power-domain-cells > 0 to
>> establish subdomain relationships via the power-domain-map property,
>> which was not previously possible.
>>
>> These new helper functions:
>> - uses an OF helper to iterate to over entries in power-domain-map
>> - For each mapped entry: extracts child specifier, resolves parent phandle,
>> extracts parent specifier args, and establishes subdomain relationship
>> - Calls genpd_[add|remove]_subdomain() with proper gpd_list_lock mutex protection
>>
>> Example from k3-am62l.dtsi:
>>
>> scmi_pds: protocol@11 {
>> #power-domain-cells = <1>;
>> power-domain-map = <15 &MAIN_PD>, /* TIMER0 */
>> <19 &WKUP_PD>; /* WKUP_TIMER0 */
>> };
>>
>> MAIN_PD: power-controller-main {
>> #power-domain-cells = <0>;
>> };
>>
>> WKUP_PD: power-controller-main {
>> #power-domain-cells = <0>;
>> };
>>
>> This allows SCMI power domain 15 to become a subdomain of MAIN_PD, and
>> domain 19 to become a subdomain of WKUP_PD.
>
> One concern I have here is generally *-map is transparent meaning when
> you lookup <&scmi_pds 15>, &MAIN_PD is returned as the provider. It's
> also possible to have a map point to another map until you get to the
> final provider. The only way we have to support both behaviors is the
> consumer has to specify (i.e. with of_parse_phandle_with_args_map() vs.
> of_parse_phandle_with_args()), but the consumer shouldn't really know
> this detail.
>
> Maybe a transparent map of power-domains would never make sense. IDK. If
> so, then there's not really any issue since the pmdomain core handles
> everyone the same way.
I don't really know enough about potential usage of maps to know if
there's ever a usecase for transparent maps. However, the problem I'm
trying to solve is less about transparent maps, and more about
describing hierarchy in a situation where "leaf" domains of the same
type (e.g. SCMI) can have different parent domains.
When I first proposed this[1], I didn't use a map, but you suggested I
try using a map[2]. So I'm not sure if I misunderstood what you
proposed, or if now that you see it implemented, you're second guessing if
the map is the right approach.
Kevin
[1] https://lore.kernel.org/r/20250528-pmdomain-hierarchy-onecell-v1-1-851780700c68@baylibre.com
[2] https://lore.kernel.org/r/20250528203532.GA704342-robh@kernel.org
next prev parent reply other threads:[~2026-02-03 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 1:13 [PATCH RFC v5 0/2] pmdomain: core: add support for domain hierarchies in DT Kevin Hilman (TI)
2026-01-23 1:14 ` [PATCH RFC v5 1/2] pmdomain: core: support domain hierarchy via power-domain-map Kevin Hilman (TI)
2026-01-27 15:17 ` Rob Herring
2026-02-03 23:12 ` Kevin Hilman [this message]
2026-02-19 10:29 ` Geert Uytterhoeven
2026-02-24 23:11 ` Kevin Hilman
2026-03-03 17:09 ` Ulf Hansson
2026-03-09 22:24 ` Kevin Hilman
2026-01-23 1:14 ` [PATCH RFC v5 2/2] pmdomain: arm_scmi: add support for domain hierarchies Kevin Hilman (TI)
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=7hjywtzaiy.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@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