From: Francesco Dolcini <francesco@dolcini.it>
To: Suhaas Joshi <s-joshi@ti.com>
Cc: u-boot@lists.denx.de, vigneshr@ti.com, trini@konsulko.com,
n-francis@ti.com, s-tripathi1@ti.com, k-malarvizhi@ti.com,
kamlesh@ti.com, vishalm@ti.com
Subject: Re: [PATCH v2 0/5] Firewall ATF and OP-TEE memory regions in Sitara
Date: Wed, 21 Jan 2026 15:07:47 +0100 [thread overview]
Message-ID: <20260121140747.GA112150@francesco-nb> (raw)
In-Reply-To: <20260121054712.176939-1-s-joshi@ti.com>
Hello,
thanks for your patch
On Wed, Jan 21, 2026 at 11:17:07AM +0530, Suhaas Joshi wrote:
> This series starts by replacing the hard-coded addresses in firewall
> templates that are defined in k3-binman.dtsi, by Kconfigs. Using
> Kconfigs would make it easier for someone to move ATF and OP-TEE to
> another location, since they wouldn't have to fiddle with the firewall
> configs in the dtsi files.
>
> The rest of the commits in this series add firewall configs to each
> device's dtsi file.
If I understand correctly the change, you should change also the other
k3 boards, not just the TI one.
Francesco
next prev parent reply other threads:[~2026-01-21 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 5:47 [PATCH v2 0/5] Firewall ATF and OP-TEE memory regions in Sitara Suhaas Joshi
2026-01-21 5:47 ` [PATCH v2 1/5] arm: dts: k3-binman: Use configs for ATF/OPTEE addresses Suhaas Joshi
2026-01-21 5:47 ` [PATCH v2 2/5] arm: dts: k3-am625-binman: Configure firewall for ATF/OPTEE Suhaas Joshi
2026-01-21 5:47 ` [PATCH v2 3/5] arm: dts: k3-am62p-binman: " Suhaas Joshi
2026-01-21 5:47 ` [PATCH v2 4/5] arm: dts: k3-am62a-binman: " Suhaas Joshi
2026-01-21 5:47 ` [PATCH v2 5/5] arm: dts: k3-am64x-binman: " Suhaas Joshi
2026-01-21 14:07 ` Francesco Dolcini [this message]
2026-01-21 15:44 ` [PATCH v2 0/5] Firewall ATF and OP-TEE memory regions in Sitara Bryan Brattlof
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=20260121140747.GA112150@francesco-nb \
--to=francesco@dolcini.it \
--cc=k-malarvizhi@ti.com \
--cc=kamlesh@ti.com \
--cc=n-francis@ti.com \
--cc=s-joshi@ti.com \
--cc=s-tripathi1@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
/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