From: Sudeep Holla <sudeep.holla@arm.com>
To: Elliot Berman <eberman@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Trilok Soni <tsoni@codeaurora.org>,
Prasad Sodagudi <psodagud@codeaurora.org>,
David Collins <collinsd@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v2 2/3] firmware: psci: Add support for dt-supplied SYSTEM_RESET2 type
Date: Wed, 26 Feb 2020 11:59:12 +0000 [thread overview]
Message-ID: <20200226115912.GC8613@bogus> (raw)
In-Reply-To: <1d7fecf8-3a7f-57e5-5c13-73de89d52aa2@codeaurora.org>
On Tue, Feb 25, 2020 at 05:37:53PM -0800, Elliot Berman wrote:
[...]
> Alternatively, I could rename the DT property to
> "arm,psci-sys-reset2-vendor-param"
Yes much better.
> and then always set the 31st bit so that it is impossible to provide an
> invalid architectural reset type in DT.
>
Indeed this is what I was expecting and hence raised issue here. So that
one can't make use of architectural ID space just by adding param in DT.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-02-26 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 20:57 [PATCH v2 0/3] ARM PSCI: Add support for vendor-specific SYSTEM_RESET2 Elliot Berman
2020-02-24 20:57 ` [PATCH v2 1/3] dt: psci: Add arm,psci-sys-reset2-type property Elliot Berman
2020-02-25 10:55 ` Sudeep Holla
2020-02-26 12:09 ` Mark Rutland
2020-02-27 0:44 ` Elliot Berman
2020-02-24 20:57 ` [PATCH v2 2/3] firmware: psci: Add support for dt-supplied SYSTEM_RESET2 type Elliot Berman
2020-02-25 11:03 ` Sudeep Holla
2020-02-26 1:37 ` Elliot Berman
2020-02-26 11:59 ` Sudeep Holla [this message]
2020-02-26 12:02 ` Sudeep Holla
2020-02-26 12:10 ` Mark Rutland
2020-02-24 20:57 ` [PATCH v2 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=20200226115912.GC8613@bogus \
--to=sudeep.holla@arm.com \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=eberman@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=psodagud@codeaurora.org \
--cc=tsoni@codeaurora.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;
as well as URLs for NNTP newsgroup(s).