All of lore.kernel.org
 help / color / mirror / Atom feed
From: <kamlesh@ti.com>
To: <u-boot@lists.denx.de>
Cc: Kamlesh Gurudasani <kamlesh@ti.com>
Subject: [PATCH 0/2] add support for hs bootflows on am62 devices
Date: Thu, 2 Mar 2023 19:40:45 +0530	[thread overview]
Message-ID: <20230302141047.3175114-1-kamlesh@ti.com> (raw)

From: Kamlesh Gurudasani <kamlesh@ti.com>

Add support for high security bootflow on am62 devices.

On HS devices, ROM and TIFS will protect the RAM regions with
firewalls. This means the wakeup domain's SPL will need to move the
stack and heap to HSM RAM to ensure it stays within its allotted
memory regions.

Kamlesh Gurudasani (2):
  arm: mach-k3: am62: move scratch board area to HSM RAM
  configs: am62: move stack and heap to HSM RAM

 arch/arm/mach-k3/include/mach/am62_hardware.h |  3 +--
 configs/am62x_evm_r5_defconfig                | 16 +++++++++++-----
 2 files changed, 12 insertions(+), 7 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-03-02 14:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:10 kamlesh [this message]
2023-03-02 14:10 ` [PATCH 1/2] arm: mach-k3: am62: move scratch board area to HSM RAM kamlesh
2023-03-22 18:03   ` Tom Rini
2023-03-02 14:10 ` [PATCH 2/2] configs: am62: move stack and heap " kamlesh
2023-03-22 18:03   ` Tom Rini
2023-03-03  1:21 ` [PATCH 0/2] add support for hs bootflows on am62 devices Bryan Brattlof
2023-03-03  9:09   ` Kamlesh Gurudasani
2023-03-16 10:35   ` Kamlesh Gurudasani
2023-03-16 18:15     ` Tom Rini
2023-03-17  8:51       ` [EXTERNAL] " Kamlesh Gurudasani
2023-03-17 14:37         ` Tom Rini
2023-03-20  8:34           ` Kamlesh Gurudasani
  -- strict thread matches above, loose matches on Subject: below --
2023-03-02 14:07 Kamlesh.Gurudasani.kamlesh
     [not found] <20230302135043.3174988-1-kamlesh@ti.com>
2023-03-02 14:02 ` Kamlesh Gurudasani

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=20230302141047.3175114-1-kamlesh@ti.com \
    --to=kamlesh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.