From: Steven Price <steven.price@arm.com>
To: Etienne Carriere <etienne.carriere@linaro.org>,
linux-kernel@vger.kernel.org
Cc: lorenzo.pieralisi@arm.com, linux-arm-kernel@lists.infradead.org,
mark.rutland@arm.com, tglx@linutronix.de,
alexios.zavras@intel.com, will@kernel.org, maz@kernel.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 1/2] firmware: arm-smccc: define identifier for Arm SMCCC v1.2
Date: Thu, 14 May 2020 13:38:33 +0100 [thread overview]
Message-ID: <b8661499-6ecc-2adc-9ed6-b7c428a8aa35@arm.com> (raw)
In-Reply-To: <20200514082109.27573-1-etienne.carriere@linaro.org>
On 14/05/2020 09:21, Etienne Carriere wrote:
> Define identifier value reported by secure firmware when its
> supports Arm SMCCC specification v1.2.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
FYI Sudeep has already posted a patch to do this[1].
Steve
[1]
https://lore.kernel.org/linux-arm-kernel/20200430114814.14116-3-sudeep.holla@arm.com/
> ---
> include/linux/arm-smccc.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/arm-smccc.h b/include/linux/arm-smccc.h
> index 59494df0f55b..1cf221f3f07a 100644
> --- a/include/linux/arm-smccc.h
> +++ b/include/linux/arm-smccc.h
> @@ -56,6 +56,7 @@
>
> #define ARM_SMCCC_VERSION_1_0 0x10000
> #define ARM_SMCCC_VERSION_1_1 0x10001
> +#define ARM_SMCCC_VERSION_1_2 0x10002
>
> #define ARM_SMCCC_VERSION_FUNC_ID \
> ARM_SMCCC_CALL_VAL(ARM_SMCCC_FAST_CALL, \
>
next prev parent reply other threads:[~2020-05-14 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 8:21 [PATCH 1/2] firmware: arm-smccc: define identifier for Arm SMCCC v1.2 Etienne Carriere
2020-05-14 8:21 ` [PATCH 2/2] firmware: psci: support SMCCC v1.2 for SMCCC conduit Etienne Carriere
2020-05-14 14:24 ` Sudeep Holla
2020-05-14 14:56 ` Etienne Carriere
2020-05-15 9:24 ` Sudeep Holla
2020-05-14 12:38 ` Steven Price [this message]
2020-05-14 12:52 ` [PATCH 1/2] firmware: arm-smccc: define identifier for Arm SMCCC v1.2 Etienne Carriere
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=b8661499-6ecc-2adc-9ed6-b7c428a8aa35@arm.com \
--to=steven.price@arm.com \
--cc=alexios.zavras@intel.com \
--cc=etienne.carriere@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.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).