All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Kamlesh Gurudasani <kamlesh@ti.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] add support for hs bootflows on am62 devices
Date: Thu, 16 Mar 2023 14:15:47 -0400	[thread overview]
Message-ID: <20230316181547.GL54321@bill-the-cat> (raw)
In-Reply-To: <87bkkt0ysl.fsf@kamlesh.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

On Thu, Mar 16, 2023 at 04:05:06PM +0530, Kamlesh Gurudasani wrote:
> Bryan Brattlof <bb@ti.com> writes:
> 
> > Hi Kamlesh!
> >
> > On March  2, 2023 thus sayeth kamlesh@ti.com:
> >> 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(-)
> >
> > Thanks for getting this fixed! Does TIFS drop the On Chip SRAM firewall 
> > completely once it's started? or only for the r5?
> >
> > Reviewed-by: Bryan Brattlof <bb@ti.com>
> >
> > ~Bryan
> Hi Tom,
> 
> Could you please review and merge this patches as these are bug fixes to
> get HS devices working.

Is this a regression fix vs v2023.01 or new feature support? Thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-03-16 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 14:10 [PATCH 0/2] add support for hs bootflows on am62 devices kamlesh
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 [this message]
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=20230316181547.GL54321@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=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.