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 00/10] Firewall ATF and OP-TEE memory regions in Sitara
Date: Tue, 27 Jan 2026 13:46:42 +0530 [thread overview]
Message-ID: <20260127081652.506357-1-s-joshi@ti.com> (raw)
This series starts by replacing hard-coded addresses in firewall templates that are defined in
k3-binman.dtsi, by Kconfigs. Using Kconfigs makes it easier for someone to move ATF and OP-TEE to
another location, since they wouldn't have to fiddle with the firewall configurations in dtsi files.
The rest of the commits in this series add firewall configs to each device's dtsi files.
I have only tested this patch series with TI boards. For non-TI Sitara boards, respective board
maintainers are requested to test the relevant patch and confirm whether it works.
To test this, I used `k3conf <read|write> <address> [<value>]`. Both of these operations were
disallowed, as expected.
Changes v2 -> v3
* Added configs in non-TI Sitara-based boards' dtsi files, as per Francesco's review.
* Link to v2: https://lore.kernel.org/u-boot/20260121054712.176939-1-s-joshi@ti.com/
Changes v1 -> v2
* Removed un-required empty lines in accordance with Neha's review.
* Link to v1: https://lore.kernel.org/u-boot/20260112093643.885903-1-s-joshi@ti.com/
Suhaas Joshi (10):
arm: dts: k3-binman: Use configs for ATF/OPTEE addresses
arm: dts: k3-am625-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am625-phycore-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am625-verdin-binman: Configure Firewall for ATF/OPTEE
arm: dts: k3-am62p-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am62p5-verdin-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am62a-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am62a-phycore-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am64x-binman: Configure firewall for ATF/OPTEE
arm: dts: k3-am642-phycore-binman: Configure firewall for ATF/OPTEE
arch/arm/dts/k3-am625-phycore-som-binman.dtsi | 30 +++++++++++++++++
arch/arm/dts/k3-am625-sk-binman.dtsi | 29 +++++++++++++++++
.../dts/k3-am625-verdin-wifi-dev-binman.dtsi | 30 +++++++++++++++++
arch/arm/dts/k3-am62a-phycore-som-binman.dtsi | 30 +++++++++++++++++
arch/arm/dts/k3-am62a-sk-binman.dtsi | 30 +++++++++++++++++
arch/arm/dts/k3-am62p-sk-binman.dtsi | 32 +++++++++++++++++++
.../dts/k3-am62p5-verdin-wifi-dev-binman.dtsi | 32 +++++++++++++++++++
arch/arm/dts/k3-am642-phycore-som-binman.dtsi | 31 ++++++++++++++++++
arch/arm/dts/k3-am64x-binman.dtsi | 31 ++++++++++++++++++
arch/arm/dts/k3-binman.dtsi | 8 ++---
10 files changed, 279 insertions(+), 4 deletions(-)
--
2.34.1
next reply other threads:[~2026-01-27 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:16 Suhaas Joshi [this message]
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 ` [PATCH v3 09/10] arm: dts: k3-am64x-binman: " Suhaas Joshi
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-1-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