From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tomasz Figa <tomasz.figa@gmail.com>,
Dave Martin <Dave.Martin@arm.com>, Joseph Lo <josephl@nvidia.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
gnurou@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] ARM: add basic Trusted Foundations support
Date: Wed, 14 Aug 2013 15:35:49 -0600 [thread overview]
Message-ID: <520BF835.5080309@wwwdotorg.org> (raw)
In-Reply-To: <1376360992-1508-2-git-send-email-acourbot@nvidia.com>
On 08/12/2013 08:29 PM, Alexandre Courbot wrote:
> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> can be invoked using a consistent 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.
> diff --git a/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt b/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt
> +Trusted Foundations
> +
> +Boards that use the Trusted Foundations secure monitor can signal its
> +presence by declaring a node compatible with "tl,trusted-foundations"
> +(the name and location of the node does not matter).
> +
> +Required properties:
> +- compatible : "tl,trusted-foundations"
> +- version : Must contain the version number string of the Trusted Foundation
> + firmware.
Can the version be queried at run-time from the firmware itself?
If not, I wonder if we shouldn't instead encode the version number into
the compatible value.
Some comments on the exact format of the version property would be
useful; from the example I assume it's "%02d.%02d" % (major_ver, minor_ver)?
> diff --git a/arch/arm/firmware/Kconfig b/arch/arm/firmware/Kconfig
> +config ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
> + bool
Shouldn't that be "config ARCH_SUPPORTS_FIRMWARE", since presumably in
the future there will be more entries in the menu, and hence we want the
menu to appear if any of those entries are useful?
> +
> +menu "Firmware options"
> + depends on ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
Or perhaps that comment is more appropriate for that "depends".
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/5] ARM: add basic Trusted Foundations support
Date: Wed, 14 Aug 2013 15:35:49 -0600 [thread overview]
Message-ID: <520BF835.5080309@wwwdotorg.org> (raw)
In-Reply-To: <1376360992-1508-2-git-send-email-acourbot@nvidia.com>
On 08/12/2013 08:29 PM, Alexandre Courbot wrote:
> Trusted Foundations is a TrustZone-based secure monitor for ARM that
> can be invoked using a consistent 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.
> diff --git a/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt b/Documentation/devicetree/bindings/arm/firmware/tl,trusted-foundations.txt
> +Trusted Foundations
> +
> +Boards that use the Trusted Foundations secure monitor can signal its
> +presence by declaring a node compatible with "tl,trusted-foundations"
> +(the name and location of the node does not matter).
> +
> +Required properties:
> +- compatible : "tl,trusted-foundations"
> +- version : Must contain the version number string of the Trusted Foundation
> + firmware.
Can the version be queried at run-time from the firmware itself?
If not, I wonder if we shouldn't instead encode the version number into
the compatible value.
Some comments on the exact format of the version property would be
useful; from the example I assume it's "%02d.%02d" % (major_ver, minor_ver)?
> diff --git a/arch/arm/firmware/Kconfig b/arch/arm/firmware/Kconfig
> +config ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
> + bool
Shouldn't that be "config ARCH_SUPPORTS_FIRMWARE", since presumably in
the future there will be more entries in the menu, and hence we want the
menu to appear if any of those entries are useful?
> +
> +menu "Firmware options"
> + depends on ARCH_SUPPORTS_TRUSTED_FOUNDATIONS
Or perhaps that comment is more appropriate for that "depends".
next prev parent reply other threads:[~2013-08-14 21:35 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 2:29 [PATCH v3 0/5] ARM: tegra: support for Trusted Foundations Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` [PATCH v3 1/5] ARM: add basic Trusted Foundations support Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-14 21:35 ` Stephen Warren [this message]
2013-08-14 21:35 ` Stephen Warren
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
[not found] ` <CAAVeFuJ9tgXRf+QZRK5K8O2X=mKxUZtFgTsB06r4huQrDwZx2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-19 15:56 ` Stephen Warren
2013-08-19 15:56 ` Stephen Warren
2013-08-19 15:56 ` Stephen Warren
2013-08-15 11:52 ` Dave Martin
2013-08-15 11:52 ` Dave Martin
2013-08-15 11:52 ` Dave Martin
[not found] ` <20130815115227.GC2562-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-15 22:02 ` Stephen Warren
2013-08-15 22:02 ` Stephen Warren
2013-08-15 22:02 ` Stephen Warren
2013-08-16 13:23 ` Dave Martin
2013-08-16 13:23 ` Dave Martin
[not found] ` <20130816132326.GC2909-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-08-18 8:38 ` Alexandre Courbot
2013-08-18 8:38 ` Alexandre Courbot
2013-08-18 8:38 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
[not found] ` <1376360992-1508-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-13 2:29 ` [PATCH v3 2/5] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-14 21:38 ` Stephen Warren
2013-08-14 21:38 ` Stephen Warren
[not found] ` <520BF8BD.7050706-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
2013-08-13 2:29 ` [PATCH v3 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` [PATCH v3 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
[not found] ` <1376360992-1508-5-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-14 21:40 ` Stephen Warren
2013-08-14 21:40 ` Stephen Warren
2013-08-14 21:40 ` Stephen Warren
2013-08-18 8:37 ` Alexandre Courbot
2013-08-18 8:37 ` Alexandre Courbot
2013-08-13 2:29 ` [PATCH v3 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-08-13 2:29 ` Alexandre Courbot
2013-08-13 2:29 ` Alexandre 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=520BF835.5080309@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Dave.Martin@arm.com \
--cc=acourbot@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=josephl@nvidia.com \
--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=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.