From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH 0/9] Add support for secure boot on Keystone2 SoCs
Date: Fri, 24 Feb 2017 06:59:37 -0600 [thread overview]
Message-ID: <20170224125946.7500-1-afd@ti.com> (raw)
Hello all,
This series adds support for secure Keystone2 K2E and K2HK devices,
much of the work is borrowed from the OMAP style devices as the
secure workings are very similar, allowing minimal changes for
this support addition.
Thanks,
Andrew
Changes for resend:
- Fixup patch authorship
Andrew F. Davis (1):
defconfig: k2hk_hs_evm: Add k2hk_hs_evm_defconfig
Madan Srinivas (5):
image: Fixes build warning with CONFIG_FIT_IMAGE_POST_PROCESS
arm: mach-omap2: Add secure image name common to OMAP and keystone
ARM: Keystone2: Build secure images for K2
doc: Updates info on using Keystone2 secure devices
Kconfig: Adds SYS_TEXT_BASE config option for Keystone2
Vitaly Andrianov (3):
arm: mach-keystone: Implements FIT post-processing call for keystone
SoCs
arm: mach-omap2: Enable Kconfig support for K2 HS devices
defconfig: k2e_hs_evm: Add k2e_hs_evm_defconfig
Kconfig | 2 +-
arch/arm/mach-keystone/config.mk | 6 ++
arch/arm/mach-keystone/mon.c | 73 ++++++++++++++++++++++
arch/arm/mach-omap2/Kconfig | 2 +-
arch/arm/mach-omap2/config_secure.mk | 6 ++
configs/k2e_evm_defconfig | 1 +
.../{k2e_evm_defconfig => k2e_hs_evm_defconfig} | 15 ++---
configs/k2g_evm_defconfig | 1 +
configs/k2hk_evm_defconfig | 1 +
.../{k2hk_evm_defconfig => k2hk_hs_evm_defconfig} | 13 ++--
configs/k2l_evm_defconfig | 1 +
doc/README.ti-secure | 20 ++++++
include/image.h | 3 +-
13 files changed, 122 insertions(+), 22 deletions(-)
copy configs/{k2e_evm_defconfig => k2e_hs_evm_defconfig} (78%)
copy configs/{k2hk_evm_defconfig => k2hk_hs_evm_defconfig} (80%)
--
2.11.0
next reply other threads:[~2017-02-24 12:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 12:59 Andrew F. Davis [this message]
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 1/9] image: Fixes build warning with CONFIG_FIT_IMAGE_POST_PROCESS Andrew F. Davis
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 2/9] arm: mach-keystone: Implements FIT post-processing call for keystone SoCs Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 3/9] arm: mach-omap2: Enable Kconfig support for K2 HS devices Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 4/9] arm: mach-omap2: Add secure image name common to OMAP and keystone Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 5/9] ARM: Keystone2: Build secure images for K2 Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 6/9] doc: Updates info on using Keystone2 secure devices Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 7/9] Kconfig: Adds SYS_TEXT_BASE config option for Keystone2 Andrew F. Davis
2017-02-27 15:18 ` Tom Rini
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 8/9] defconfig: k2e_hs_evm: Add k2e_hs_evm_defconfig Andrew F. Davis
2017-02-27 15:19 ` Tom Rini
2017-02-28 17:47 ` Andrew F. Davis
2017-02-28 17:58 ` Tom Rini
2017-03-03 4:53 ` Simon Glass
2017-02-24 12:59 ` [U-Boot] [RESEND PATCH 9/9] defconfig: k2hk_hs_evm: Add k2hk_hs_evm_defconfig Andrew F. Davis
2017-02-27 15:19 ` 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=20170224125946.7500-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