From: Alexandre Courbot <acourbot@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tomasz Figa <tomasz.figa@gmail.com>,
Dave Martin <Dave.Martin@arm.com>
Cc: gnurou@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>
Subject: [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations
Date: Thu, 29 Aug 2013 18:57:43 +0900 [thread overview]
Message-ID: <1377770268-14014-1-git-send-email-acourbot@nvidia.com> (raw)
New version revised according to comments received for v3. Hopefully
it will be good enough to be merged.
Changes since v3:
- Added of_register_trusted_foundations() function to avoid duplicate
device tree parsing code in arch files
- Added ability to initialize Trusted Foundations through platform data
- Changed TF version number to integers
- Refactored Kconfig menu for more clarity
A few requests could not reasonably be implemented:
TF version probing at runtime (requested by Dave) seems impossible
unfortunately. TF just does not provide an interface that allows such
queries. In the downstream Tegra kernel the TF version is
even hardcoded into the kernel.
Use of a firmware_op instance for non-firmware behavior (requested by
Stephen) would make it necessary to have a dedicated non-firmware
registration function that takes implementations from various different
files and would require these implementations to be exported. Checking
the return code of call_firmware_op() at call sites seems to be easier
to handle and is how current users of firmware_ops do.
Alexandre Courbot (5):
ARM: add basic Trusted Foundations support
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 | 26 +++++++
arch/arm/firmware/Makefile | 1 +
arch/arm/firmware/trusted_foundations.c | 83 ++++++++++++++++++++++
arch/arm/include/asm/trusted_foundations.h | 48 +++++++++++++
arch/arm/mach-tegra/Kconfig | 1 +
arch/arm/mach-tegra/common.c | 2 +
arch/arm/mach-tegra/reset.c | 40 ++++++++---
13 files changed, 217 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-08-29 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 9:57 Alexandre Courbot [this message]
2013-08-29 9:57 ` [PATCH v4 1/5] ARM: add basic Trusted Foundations support Alexandre Courbot
[not found] ` <1377770268-14014-2-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-08-30 8:20 ` Tomasz Figa
2013-09-02 7:28 ` Alexandre Courbot
[not found] ` <CAAVeFuJ=z-29gp9=caQaxRGCiOQSnPLfafia3eCgWAUuny3GBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-03 18:36 ` Stephen Warren
2013-09-03 18:40 ` Stephen Warren
2013-08-29 9:57 ` [PATCH v4 2/5] ARM: tegra: add support for Trusted Foundations Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 3/5] ARM: tegra: split setting of CPU reset handler Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 4/5] ARM: tegra: set CPU reset handler with firmware op Alexandre Courbot
2013-08-29 9:57 ` [PATCH v4 5/5] ARM: tegra: support Trusted Foundations by default Alexandre Courbot
2013-08-30 8:23 ` [PATCH v4 0/5] ARM: tegra: support for Trusted Foundations Tomasz Figa
2013-09-03 18:42 ` Stephen Warren
[not found] ` <52262D8F.9060706-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-04 2:31 ` Alex Courbot
2013-09-04 18:25 ` Stephen Warren
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=1377770268-14014-1-git-send-email-acourbot@nvidia.com \
--to=acourbot@nvidia.com \
--cc=Dave.Martin@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.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=swarren@wwwdotorg.org \
--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 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).