From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/7] Add FIT loadable custom processing
Date: Tue, 29 Nov 2016 16:33:19 -0600 [thread overview]
Message-ID: <20161129223326.3115-1-afd@ti.com> (raw)
Hello all,
To see the background on this see here[0].
As Simon suggested we are now using a linker list to keep any and all TEE
specific code out of common files as, unlike kernel, dtb, and ramdisk
TEE images may not be used by needed by all users.
The last 5 patches in this series are an example of how one can now add a
handler for an image type for their platform.
Thanks,
Andrew
[0] http://lists.denx.de/pipermail/u-boot/2016-November/272614.html
Changes from v2:
- Moved generic OP-TEE definitions to common location
- Check return value from SMC call
- Added patch to add OP-TEE node to kernel fdt, this was missing
from the last set to complete the working solution
Changes from v1:
- Added some additional documentation
- Last 4 patches are now the compleate working TEE loading solution for
our DRA7xx/AM57xx platforms, not just an example
Andrew F. Davis (5):
image: Add FIT image loadable section custom processing
image: Add Trusted Execution Environment image type
arm: omap5: Add OPTEE node to fdt
board: ti: dra7xx: add FIT image TEE processing
board: ti: am57xx: add FIT image TEE processing
Harinarayan Bhatta (2):
arm: omap5: Add function to make an SMC call on cpu1
arm: omap5: Add TEE loading support
arch/arm/include/asm/omap_common.h | 1 +
arch/arm/include/asm/omap_sec_common.h | 6 ++
arch/arm/mach-omap2/omap5/Makefile | 1 +
arch/arm/mach-omap2/omap5/fdt.c | 35 +++++++-
arch/arm/mach-omap2/omap5/sec-fxns.c | 108 +++++++++++++++++++++++++
arch/arm/mach-omap2/omap5/sec_entry_cpu1.S | 123 +++++++++++++++++++++++++++++
board/ti/am57xx/board.c | 7 ++
board/ti/dra7xx/evm.c | 7 ++
common/image.c | 34 ++++++++
doc/uImage.FIT/source_file_format.txt | 4 +-
include/image.h | 31 ++++++++
include/tee/optee.h | 30 +++++++
12 files changed, 385 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/mach-omap2/omap5/sec_entry_cpu1.S
create mode 100644 include/tee/optee.h
--
2.10.2
next reply other threads:[~2016-11-29 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 22:33 Andrew F. Davis [this message]
2016-11-29 22:33 ` [U-Boot] [PATCH v3 1/7] image: Add FIT image loadable section custom processing Andrew F. Davis
2016-12-04 1:05 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 2/7] image: Add Trusted Execution Environment image type Andrew F. Davis
2016-12-04 1:05 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 3/7] arm: omap5: Add function to make an SMC call on cpu1 Andrew F. Davis
2016-12-04 1:06 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 4/7] arm: omap5: Add TEE loading support Andrew F. Davis
2016-11-30 3:05 ` Tom Rini
2016-12-04 1:06 ` [U-Boot] [U-Boot,v3,4/7] " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 5/7] arm: omap5: Add OPTEE node to fdt Andrew F. Davis
2016-11-30 14:13 ` Tom Rini
2016-12-04 1:07 ` [U-Boot] [U-Boot,v3,5/7] " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 6/7] board: ti: dra7xx: add FIT image TEE processing Andrew F. Davis
2016-12-04 1:08 ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-11-29 22:33 ` [U-Boot] [PATCH v3 7/7] board: ti: am57xx: " Andrew F. Davis
2016-12-04 1:08 ` [U-Boot] [U-Boot, v3, " Tom Rini
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=20161129223326.3115-1-afd@ti.com \
--to=afd@ti.com \
--cc=u-boot@lists.denx.de \
/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