From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de, git@xilinx.com,
Ricardo Salveti <ricardo@foundries.io>
Subject: [PATCH 0/3] zynqmp: Add support for secure OS loading
Date: Mon, 31 May 2021 12:14:44 +0200 [thread overview]
Message-ID: <cover.1622456084.git.michal.simek@xilinx.com> (raw)
Hi,
this series is adding support for working with TEE in much easier and
flexible way.
TF-A can be placed to any location. When it is placed to DDR you should
enable DT support which reserve location where TF-A is
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/10131
The similar DT support can be added to secure OS but I haven't sent that
patches out in OPTEE case yet.
Thanks,
Michal
Michal Simek (3):
zynqmp: Do not place u-boot to reserved memory location
zynqmp: Generate u-boot.its also with TEE dynamically
zynqmp: Pass bl32 entry to TF-A via xilinx handoff structure
arch/arm/mach-zynqmp/handoff.c | 19 +++++++++---
arch/arm/mach-zynqmp/mkimage_fit_atf.sh | 41 ++++++++++++++++++++++++-
board/xilinx/zynqmp/zynqmp.c | 21 +++++++++++++
3 files changed, 75 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-31 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:14 Michal Simek [this message]
2021-05-31 10:14 ` [PATCH 1/3] zynqmp: Do not place u-boot to reserved memory location Michal Simek
2021-05-31 10:14 ` [PATCH 2/3] zynqmp: Generate u-boot.its also with TEE dynamically Michal Simek
2021-05-31 10:14 ` [PATCH 3/3] zynqmp: Pass bl32 entry to TF-A via xilinx handoff structure Michal Simek
2021-06-10 7:29 ` [PATCH 0/3] zynqmp: Add support for secure OS loading Michal Simek
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=cover.1622456084.git.michal.simek@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=git@xilinx.com \
--cc=ricardo@foundries.io \
--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