From: Alexandre Courbot <acourbot@nvidia.com>
To: 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>,
Linus Walleij <linus.walleij@linaro.org>
Cc: gnurou@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Alexandre Courbot <acourbot@nvidia.com>
Subject: [PATCH v6 0/5] ARM: support for Trusted Foundations secure monitor
Date: Sun, 15 Sep 2013 18:40:23 +0900 [thread overview]
Message-ID: <1379238028-7960-1-git-send-email-acourbot@nvidia.com> (raw)
Sixth attempt at the support for Trusted Foundations, which allows many
Tegra-based (and quite possibly other) devices sold on the market to boot and
be used with an upstream kernel.
v5 did not receive many comments on the code itself, so I hope this means
the patch set is converging well. Most remarks were about the lack of clarity
about what Trusted Foundations is and how it fits with respect to SMC calling
conventions and the PSCI standard (spoiler: it does not fit).
Change against v5:
- added a no-op of_register_trusted_foundations() for the case where neither
Trusted Foundations nor device tree support are enabled
- made it clear in the commit message and source file that TF does not follow
the SMC calling convention, is totally independant of PSIC and only matters
to devices that come with a bootloader that enables it.
Alexandre Courbot (5):
ARM: add basic support for Trusted Foundations
ARM: tegra: add support for Trusted Foundations
ARM: tegra: split setting of CPU reset handler
ARM: tegra: set CPU reset handler with firmware op
ARM: tegra: support Trusted Foundations by default
.../arm/firmware/tl,trusted-foundations.txt | 17 +++++
Documentation/devicetree/bindings/arm/tegra.txt | 5 ++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/Kconfig | 2 +
arch/arm/Makefile | 1 +
arch/arm/configs/tegra_defconfig | 1 +
arch/arm/firmware/Kconfig | 28 ++++++++
arch/arm/firmware/Makefile | 1 +
arch/arm/firmware/trusted_foundations.c | 79 ++++++++++++++++++++++
arch/arm/include/asm/trusted_foundations.h | 70 +++++++++++++++++++
arch/arm/mach-tegra/Kconfig | 1 +
arch/arm/mach-tegra/common.c | 2 +
arch/arm/mach-tegra/reset.c | 40 ++++++++---
13 files changed, 237 insertions(+), 11 deletions(-)
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
--
1.8.4
next reply other threads:[~2013-09-15 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 9:40 Alexandre Courbot [this message]
2013-09-15 9:40 ` [PATCH v6 1/5] ARM: add basic support for Trusted Foundations Alexandre Courbot
[not found] ` <1379238028-7960-2-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-09-16 16:50 ` Stephen Warren
[not found] ` <523736DE.1050201-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-17 3:28 ` Alexandre Courbot
2013-09-19 20:49 ` Kevin Hilman
[not found] ` <87d2o4edus.fsf-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-09-23 20:37 ` Alexandre Courbot
[not found] ` <1379238028-7960-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-09-15 9:40 ` [PATCH v6 2/5] ARM: tegra: add " Alexandre Courbot
2013-09-15 9:40 ` [PATCH v6 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-09-15 9:40 ` [PATCH v6 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-09-15 9:40 ` [PATCH v6 5/5] ARM: tegra: support Trusted Foundations by default 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=1379238028-7960-1-git-send-email-acourbot@nvidia.com \
--to=acourbot@nvidia.com \
--cc=Dave.Martin@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=khilman@linaro.org \
--cc=linus.walleij@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=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;
as well as URLs for NNTP newsgroup(s).