From: Mark Rutland <mark.rutland@arm•com>
To: Elliot Berman <eberman@codeaurora•org>
Cc: Trilok Soni <tsoni@codeaurora•org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm•com>,
David Collins <collinsd@codeaurora•org>,
linux-arm-msm@vger•kernel.org, linux-kernel@vger•kernel.org,
Bjorn Andersson <bjorn.andersson@linaro•org>,
Sudeep Holla <sudeep.holla@arm•com>,
Prasad Sodagudi <psodagud@codeaurora•org>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v3 1/3] dt: psci: Add arm,psci-sys-reset2-vendor-param property
Date: Fri, 20 Mar 2020 12:01:05 +0000 [thread overview]
Message-ID: <20200320120105.GA36658@C02TD0UTHF1T.local> (raw)
In-Reply-To: <1583435129-31356-2-git-send-email-eberman@codeaurora.org>
Hi Elliot,
On Thu, Mar 05, 2020 at 11:05:27AM -0800, Elliot Berman wrote:
> Some implementors of PSCI may wish to use a different reset type than
> SYSTEM_WARM_RESET. For instance, Qualcomm SoCs support an alternate
> reset_type which may be used in more warm reboot scenarios than
> SYSTEM_WARM_RESET permits (e.g. to reboot into recovery mode).
To be honest, I'm still confused by this series, and I think that these
patches indicate a larger problem that we cannot solve generally (e.g.
on other platofrms and/or with ACPI).
I think the underlying issue is whether the semantics for:
a) Linux's RESET_WARM and RESET_SOFT
b) PSCI's SYSTEM_RESET2 SYSTEM_WARM_RESET
... actually align in practice, which this series suggests is not the
case.
If those don't align, then I think that commit:
4302e381a870aafb ("firmware/psci: add support for SYSTEM_RESET2")
... is not actually reliable, and not something we can support by
default, and we should rethink the code introduce in that commit.
If (a) and (b) are supposed to align, and the behaviour on your platform
is an erratum, then I think we should treat it as such rather than
adding a property that is open to abuse.
Thoughts?
Thanks,
Mark.
>
> Reviewed-by: Sudeep Holla <sudeep.holla@arm•com>
> Signed-off-by: Elliot Berman <eberman@codeaurora•org>
> ---
> Documentation/devicetree/bindings/arm/psci.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/psci.yaml b/Documentation/devicetree/bindings/arm/psci.yaml
> index 8ef8542..1a9d2dd 100644
> --- a/Documentation/devicetree/bindings/arm/psci.yaml
> +++ b/Documentation/devicetree/bindings/arm/psci.yaml
> @@ -102,6 +102,13 @@ properties:
> [1] Kernel documentation - ARM idle states bindings
> Documentation/devicetree/bindings/arm/idle-states.txt
>
> + arm,psci-sys-reset2-vendor-param:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Vendor-specific reset type parameter to use for SYSTEM_RESET2 during
> + a warm or soft reboot. If no value is provided, then architectural
> + reset type SYSTEM_WARM_RESET is used.
> +
> "#power-domain-cells":
> description:
> The number of cells in a PM domain specifier as per binding in [3].
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-20 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 19:05 [PATCH v3 0/3] ARM PSCI: Add support for vendor-specific SYSTEM_RESET2 Elliot Berman
2020-03-05 19:05 ` [PATCH v3 1/3] dt: psci: Add arm, psci-sys-reset2-vendor-param property Elliot Berman
2020-03-20 12:01 ` Mark Rutland [this message]
2023-06-13 20:54 ` [PATCH v3 1/3] dt: psci: Add arm,psci-sys-reset2-vendor-param property Elliot Berman
2020-03-05 19:05 ` [PATCH v3 2/3] firmware: psci: Add support for dt-supplied SYSTEM_RESET2 type Elliot Berman
2020-03-20 12:04 ` Mark Rutland
2020-03-05 19:05 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250: Add vendor-specific PSCI system reset2 type Elliot Berman
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=20200320120105.GA36658@C02TD0UTHF1T.local \
--to=mark.rutland@arm$(echo .)com \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=collinsd@codeaurora$(echo .)org \
--cc=eberman@codeaurora$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lorenzo.pieralisi@arm$(echo .)com \
--cc=psodagud@codeaurora$(echo .)org \
--cc=sudeep.holla@arm$(echo .)com \
--cc=tsoni@codeaurora$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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