From: Kevin Hilman <khilman@baylibre.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "cristian.marussi@arm.com" <cristian.marussi@arm.com>,
"souvik.chakravarty@arm.com" <souvik.chakravarty@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
Dhruva Gole <d-gole@ti.com>, Sebin Francis <sebin.francis@ti.com>
Subject: Re: mixing SCMI and PSCI power domain hierarchy
Date: Fri, 25 Apr 2025 07:39:34 -0700 [thread overview]
Message-ID: <7hmsc4s3tl.fsf@baylibre.com> (raw)
In-Reply-To: <CAPDyKFo_P129sVirHHYjOQT+QUmpymcRJme9obzKJeRgO7B-1A@mail.gmail.com>
Ulf Hansson <ulf.hansson@linaro.org> writes:
[...]
>> Anyways, curious what you think. I quite like this solution because it
>> solves two fairly big limitations in the SCMI PM domain implementaion
>> that exist today with one relatively simple solution.
>
> Well, I am not the one to convince in regards to DT bindings. Putting
> the DT bindings aside, I think your extensions for the SCMI Power
> Domain to support parent-domains makes perfect sense to me!
>
> In regards to the DT bindings (again, I am not the expert here), but
> maybe we could try to extend the current way we describe parent
> domains instead of inventing something entirely new. Could the below
> work?
>
> scmi_pds: protocol@11 {
> reg = <0x11>;
> #power-domain-cells = <1>;
> power-domains = <&MAIN_PD>, <&WKUP_PD>; // a list of phandles
> power-domains-child-ids = <15>, <19> ; // a list of indexes
> corresponding to the list of phandles above
Yeah, this is probably better. I'm not crazy about introducing novel
DT bindings either. I will make a PoC of this approach.
The catch with either approach is that it will be a long list. e.g. on
the TI AM62L, there are 50+ SCMI IDs.
> The above said, I have also discussed this with Vincent and we thought
> it was a good idea to bring up the topic at the next monthly public
> SCMI call.
>
> It would be great if you could join, but let's see if we can find a
> reasonable slot as the current is in the middle of the night for you.
> Vincent will reach out to you as he is the one hosting the call.
Sounds great, thanks!
Kevin
next prev parent reply other threads:[~2025-04-25 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 23:31 mixing SCMI and PSCI power domain hierarchy Kevin Hilman
2025-04-10 13:07 ` Ulf Hansson
2025-04-16 0:22 ` Kevin Hilman
2025-04-16 13:22 ` Ulf Hansson
2025-04-16 16:34 ` Kevin Hilman
2025-04-16 19:28 ` Kevin Hilman
2025-04-25 10:48 ` Ulf Hansson
2025-04-16 23:57 ` Kevin Hilman
2025-04-25 11:08 ` Ulf Hansson
2025-04-25 14:39 ` Kevin Hilman [this message]
2025-05-16 12:36 ` Ulf Hansson
2025-05-28 20:09 ` Kevin Hilman
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=7hmsc4s3tl.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=d-gole@ti.com \
--cc=sebin.francis@ti.com \
--cc=souvik.chakravarty@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.