From: Tom Rini <trini@konsulko.com>
To: kamlesh@ti.com
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 2/2] configs: am62: move stack and heap to HSM RAM
Date: Wed, 22 Mar 2023 14:03:11 -0400 [thread overview]
Message-ID: <20230322180311.GM8135@bill-the-cat> (raw)
In-Reply-To: <20230302141047.3175114-3-kamlesh@ti.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Thu, Mar 02, 2023 at 07:40:47PM +0530, kamlesh@ti.com wrote:
> From: Kamlesh Gurudasani <kamlesh@ti.com>
>
> On high security devices, ROM enables firewalls to protect the OCSRAM
> region access during bootup. Only after TIFS has started (and had
> time to disable the OCSRAM firewall region) will we have write access to
> the region.
>
> This means we will need to move the stack & heap from OCSRAM to HSM RAM
> and reduce the size of BSS and the SPL to allow it to fit properly.
>
> To protect us from overflowing our ~256k of HSM SRAM, add limits and
> check during the wakeup SPL build.
>
> Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-03-22 18:03 UTC|newest]
Thread overview: 12+ 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 [this message]
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
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=20230322180311.GM8135@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.