Re: [PATCH 1/3] dt-bindings: power: domain-idle-state: Add system-state

From: Sudeep Holla

Date: Tue Oct 06 2026 - 05:12:23 EST


On Mon, Oct 05, 2026 at 08:59:42PM +0530, Maulik Shah wrote:
> Some domain idle states require system-wide coordination and are not
> applicable while the platform is up and running.
>
> Add a boolean system-state property to describe these states.
>
> Assisted-by: Codex:GPT-6
> Signed-off-by: Maulik Shah <maulik.shah@xxxxxxxxxxxxxxxx>
> ---
> .../devicetree/bindings/power/domain-idle-state.yaml | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/power/domain-idle-state.yaml b/Documentation/devicetree/bindings/power/domain-idle-state.yaml
> index 4dd4f59bbbec..35dab3cd6aed 100644
> --- a/Documentation/devicetree/bindings/power/domain-idle-state.yaml
> +++ b/Documentation/devicetree/bindings/power/domain-idle-state.yaml
> @@ -45,6 +45,12 @@ patternProperties:
> state will yield power benefits, after overcoming the overhead while
> entering the idle state.
>
> + system-state:
> + description:
> + When present, this state requires system-wide coordination and is
> + not applicable while the platform is up and running.
> + type: boolean
> +

I would rather have a system wide QoS latency setting either h/w specific
or it can be purely software policy that tells all these states to be off
for normal CPU idle path.

> arm,psci-suspend-param:
> $ref: /schemas/types.yaml#/definitions/uint32
> description: |
> @@ -77,5 +83,13 @@ examples:
> exit-latency-us = <40>;
> min-residency-us = <80>;
> };
> +
> + domain_power_off: domain-power-off {
> + compatible = "domain-idle-state";
> + entry-latency-us = <100>;
> + exit-latency-us = <200>;
> + min-residency-us = <1000>;

Please provide some realistic values. I understand this is just example
but way-off for a system level state. See your own platform values for
reference.

--
Regards,
Sudeep