From: Michal Simek <monstr@monstr.eu>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
Tomasz Figa <t.figa@samsung.com>,
Dave Martin <Dave.Martin@arm.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Kevin Hilman <khilman@linaro.org>,
gnurou@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH v7 1/5] ARM: add basic support for Trusted Foundations
Date: Tue, 08 Oct 2013 10:17:18 +0200 [thread overview]
Message-ID: <5253BF8E.4050802@monstr.eu> (raw)
In-Reply-To: <1380904635-18113-2-git-send-email-acourbot@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3398 bytes --]
Hi,
On 10/04/2013 06:37 PM, Alexandre Courbot wrote:
> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> can be invoked using the same SMC-based API on all supported
> platforms. This patch adds initial basic support for Trusted
> Foundations using the ARM firmware API. Current features are limited
> to the ability to boot secondary processors.
>
> Note: The API followed by Trusted Foundations does *not* follow the SMC
> calling conventions. It has nothing to do with PSCI neither and is only
> relevant to devices that use Trusted Foundations (like most Tegra-based
> retail devices).
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> Reviewed-by: Tomasz Figa <t.figa@samsung.com>
> Reviewed-by: Stephen Warren <swarren@nvidia.com>
> ---
> .../arm/firmware/tl,trusted-foundations.txt | 17 +++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> arch/arm/Kconfig | 2 +
> arch/arm/Makefile | 1 +
> arch/arm/firmware/Kconfig | 28 ++++++++
> arch/arm/firmware/Makefile | 1 +
> arch/arm/firmware/trusted_foundations.c | 77 ++++++++++++++++++++++
> arch/arm/include/asm/trusted_foundations.h | 64 ++++++++++++++++++
> 8 files changed, 191 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt
> create mode 100644 arch/arm/firmware/Kconfig
> create mode 100644 arch/arm/firmware/Makefile
> create mode 100644 arch/arm/firmware/trusted_foundations.c
> create mode 100644 arch/arm/include/asm/trusted_foundations.h
>
> diff --git a/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt b/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt
> new file mode 100644
> index 0000000..3954bbd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt
> @@ -0,0 +1,17 @@
> +Trusted Foundations
> +
> +Boards that use the Trusted Foundations secure monitor can signal its
> +presence by declaring a node compatible with "tl,trusted-foundations"
> +under the root node.
> +
> +Required properties:
> +- compatible : "tl,trusted-foundations"
> +- version-major : major version number of Trusted Foundations firmware
> +- version-minor: minor version number of Trusted Foundations firmware
> +
> +Example:
> + firmware {
> + compatible = "tl,trusted-foundations";
> + version-major = <2>;
> + version-minor = <8>;
> + };
This is just another example how to add sw description to dts.
I have briefly looked at tegra20.dtsi and there are IPs like timer, intc, etc
which are in the DTS without any bus.
Add this firmware node to the root is just +1 case to this mess
but IMHO will be good to have specific DT part which will be used for
this sw setting which are coming to DTS all the time.
Grant, Rob: Where is the proper location for these type of description?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-10-08 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 16:37 [PATCH v7 0/5] ARM: support for Trusted Foundations secure monito Alexandre Courbot
2013-10-04 16:37 ` [PATCH v7 1/5] ARM: add basic support for Trusted Foundations Alexandre Courbot
2013-10-07 18:16 ` Kevin Hilman
2013-10-07 19:28 ` Stephen Warren
2013-10-08 8:17 ` Michal Simek [this message]
2013-10-09 23:45 ` Olof Johansson
2013-10-10 5:18 ` Michal Simek
2013-10-09 23:47 ` Olof Johansson
2013-10-10 20:58 ` Alexandre Courbot
2013-10-10 21:14 ` Kevin Hilman
2013-10-10 22:22 ` Stephen Warren
2013-10-10 22:25 ` Olof Johansson
2013-10-10 22:28 ` Alexandre Courbot
2013-10-04 16:37 ` [PATCH v7 2/5] ARM: tegra: add " Alexandre Courbot
2013-10-04 16:37 ` [PATCH v7 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-10-04 16:37 ` [PATCH v7 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-10-04 16:37 ` [PATCH v7 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-10-06 18:11 ` [PATCH v7 0/5] ARM: support for Trusted Foundations secure monito Alex Courbot
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=5253BF8E.4050802@monstr.eu \
--to=monstr@monstr.eu \
--cc=Dave.Martin@arm.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
/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