From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/7] AM65x HS device support
Date: Wed, 13 Feb 2019 12:37:05 -0600 [thread overview]
Message-ID: <20190213183712.7087-1-afd@ti.com> (raw)
Hello all,
This series brings up HS device support on the AM65x platform. Support
for HS on K3 family devices is a bit different than previous devices
but for the most part all that has been abstracted into the SECDEV
package, allowing for a rather straight forward implementation here.
Thanks,
Andrew
Andrew F. Davis (7):
arm: K3: Avoid use of MCU_PSRAM0 before SYSFW is loaded
firmware: ti_sci: Add support for firewall management
firmware: ti_sci: Modify auth_boot TI-SCI API to match new version
arm: mach-k3: Add secure device support
arm: mach-k3: Add secure device build support
configs: Add a config for AM65x High Security EVM
doc: Update info on using K3 secure devices
MAINTAINERS | 4 +
arch/arm/Kconfig | 2 +-
arch/arm/mach-k3/Makefile | 1 +
arch/arm/mach-k3/am6_init.c | 8 +-
arch/arm/mach-k3/config.mk | 25 +++
arch/arm/mach-k3/config_secure.mk | 44 ++++
arch/arm/mach-k3/include/mach/am6_hardware.h | 3 -
arch/arm/mach-k3/security.c | 63 ++++++
configs/am65x_hs_evm_a53_defconfig | 74 +++++++
configs/am65x_hs_evm_r5_defconfig | 90 +++++++++
doc/README.ti-secure | 20 +-
drivers/firmware/ti_sci.c | 202 ++++++++++++++++++-
drivers/firmware/ti_sci.h | 139 ++++++++++++-
include/linux/soc/ti/ti_sci_protocol.h | 68 ++++++-
tools/k3_fit_atf.sh | 8 +-
15 files changed, 722 insertions(+), 29 deletions(-)
create mode 100644 arch/arm/mach-k3/config_secure.mk
create mode 100644 arch/arm/mach-k3/security.c
create mode 100644 configs/am65x_hs_evm_a53_defconfig
create mode 100644 configs/am65x_hs_evm_r5_defconfig
--
2.19.1
next reply other threads:[~2019-02-13 18:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:37 Andrew F. Davis [this message]
2019-02-13 18:37 ` [U-Boot] [PATCH 1/7] arm: K3: Avoid use of MCU_PSRAM0 before SYSFW is loaded Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 21:16 ` Andrew F. Davis
2019-02-14 3:32 ` Lokesh Vutla
2019-02-14 21:51 ` Andrew F. Davis
2019-02-18 4:40 ` Lokesh Vutla
2019-02-13 18:37 ` [U-Boot] [PATCH 2/7] firmware: ti_sci: Add support for firewall management Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-14 3:43 ` Lokesh Vutla
2019-02-13 18:37 ` [U-Boot] [PATCH 3/7] firmware: ti_sci: Modify auth_boot TI-SCI API to match new version Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 4/7] arm: mach-k3: Add secure device support Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 5/7] arm: mach-k3: Add secure device build support Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 21:20 ` Andrew F. Davis
2019-02-14 3:46 ` Lokesh Vutla
2019-02-14 22:55 ` Andrew F. Davis
2019-02-15 12:13 ` Lokesh Vutla
2019-02-16 22:18 ` Tom Rini
2019-02-18 13:05 ` Andrew F. Davis
2019-02-13 18:37 ` [U-Boot] [PATCH 6/7] configs: Add a config for AM65x High Security EVM Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 7/7] doc: Update info on using K3 secure devices Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 21:12 ` [U-Boot] [PATCH 0/7] AM65x HS device support Andreas Dannenberg
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=20190213183712.7087-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