public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Suhaas Joshi <s-joshi@ti.com>
To: <u-boot@lists.denx.de>
Cc: <vigneshr@ti.com>, <trini@konsulko.com>, <n-francis@ti.com>,
	<s-tripathi1@ti.com>, <k-malarvizhi@ti.com>, <kamlesh@ti.com>,
	<vishalm@ti.com>, <d.schultz@phytec.de>, <w.egorov@phytec.de>,
	<francesco.dolcini@toradex.com>, <ggiordano@phytec.com>
Subject: [PATCH v3 09/10] arm: dts: k3-am64x-binman: Configure firewall for ATF/OPTEE
Date: Tue, 27 Jan 2026 13:46:51 +0530	[thread overview]
Message-ID: <20260127081652.506357-10-s-joshi@ti.com> (raw)
In-Reply-To: <20260127081652.506357-1-s-joshi@ti.com>

Add firewall configurations to protect ATF and OP-TEE memory regions
from non-secure reads and writes in AM64x.

Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
---
 arch/arm/dts/k3-am64x-binman.dtsi | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/arch/arm/dts/k3-am64x-binman.dtsi b/arch/arm/dts/k3-am64x-binman.dtsi
index 32e47a3f688..f3c7f2c939d 100644
--- a/arch/arm/dts/k3-am64x-binman.dtsi
+++ b/arch/arm/dts/k3-am64x-binman.dtsi
@@ -139,6 +139,37 @@
 			#address-cells = <1>;
 
 			images {
+				atf {
+					ti-secure {
+						auth-in-place = <0xa02>;
+
+						firewall-24-5 {
+							insert-template = <&firewall_armv8_atf_fg>;
+							id = <24>;
+							region = <5>;
+						};
+					};
+				};
+
+				tee {
+					ti-secure {
+						auth-in-place = <0xa02>;
+
+						firewall-1-0 {
+							insert-template = <&firewall_bg_3>;
+							id = <1>;
+							region = <0>;
+						};
+
+
+						firewall-1-1 {
+							insert-template = <&firewall_armv8_optee_fg>;
+							id = <1>;
+							region = <1>;
+						};
+					};
+				};
+
 				dm {
 					blob-ext {
 						filename = "/dev/null";
-- 
2.34.1


  parent reply	other threads:[~2026-01-27 13:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  8:16 [PATCH v3 00/10] Firewall ATF and OP-TEE memory regions in Sitara Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 01/10] arm: dts: k3-binman: Use configs for ATF/OPTEE addresses Suhaas Joshi
2026-01-27 16:01   ` Andrew Davis
2026-01-27  8:16 ` [PATCH v3 02/10] arm: dts: k3-am625-binman: Configure firewall for ATF/OPTEE Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 03/10] arm: dts: k3-am625-phycore-binman: " Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 04/10] arm: dts: k3-am625-verdin-binman: Configure Firewall " Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 05/10] arm: dts: k3-am62p-binman: Configure firewall " Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 06/10] arm: dts: k3-am62p5-verdin-binman: " Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 07/10] arm: dts: k3-am62a-binman: " Suhaas Joshi
2026-01-27  8:16 ` [PATCH v3 08/10] arm: dts: k3-am62a-phycore-binman: " Suhaas Joshi
2026-01-27  8:16 ` Suhaas Joshi [this message]
2026-01-27  8:16 ` [PATCH v3 10/10] arm: dts: k3-am642-phycore-binman: " Suhaas Joshi
2026-02-08  0:27 ` [PATCH v3 00/10] Firewall ATF and OP-TEE memory regions in Sitara Tom Rini

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=20260127081652.506357-10-s-joshi@ti.com \
    --to=s-joshi@ti.com \
    --cc=d.schultz@phytec.de \
    --cc=francesco.dolcini@toradex.com \
    --cc=ggiordano@phytec.com \
    --cc=k-malarvizhi@ti.com \
    --cc=kamlesh@ti.com \
    --cc=n-francis@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 \
    --cc=w.egorov@phytec.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