From: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx> Certain firmware implementations (such as the ones found on Qualcomm SoCs between roughly 2015 and 2023) expose an S3-like S2RAM state through the CPU_SUSPEND call, as opposed to exposing PSCIv1.0's optional PSCI_SYSTEM_SUSPEND. This really doesn't work well with the model where we associate all calls to CPU_SUSPEND with cpuidle. Allow specifying a single special CPU_SUSPEND suspend parameter value that is to be treated just like SYSTEM_SUSPEND from the OS's point of view. Signed-off-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxxxxxxxx> --- Documentation/devicetree/bindings/arm/psci.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/psci.yaml b/Documentation/devicetree/bindings/arm/psci.yaml index cbb012e217ab80c1ca88e611e7acc06c6d56fad0..a6901878697c8e1ec1cbfed62298ae3bc58f2501 100644 --- a/Documentation/devicetree/bindings/arm/psci.yaml +++ b/Documentation/devicetree/bindings/arm/psci.yaml @@ -98,6 +98,12 @@ properties: [1] Kernel documentation - ARM idle states bindings Documentation/devicetree/bindings/cpu/idle-states.yaml + arm,psci-s2ram-param: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + power_state parameter denoting the S2RAM/S3-like system suspend state + maxItems: 1 + patternProperties: "^power-domain-": $ref: /schemas/power/power-domain.yaml# -- 2.47.0