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.

To test this, I used `k3conf read|write <atf and optee addresses> <val>`. These 
operations were
disallowed when the patches of this series were applied, expectedly.

Changes v1 -> v2:
    * Removed some un-required empty lines in accordance with Neha's review.
    * Link to v1: 
https://lore.kernel.org/u-boot/[email protected]/

Suhaas Joshi (5):
  arm: dts: k3-binman: Use configs for ATF/OPTEE addresses
  arm: dts: k3-am625-binman: Configure firewall for ATF/OPTEE
  arm: dts: k3-am62p-binman: Configure firewall for ATF/OPTEE
  arm: dts: k3-am62a-binman: Configure firewall for ATF/OPTEE
  arm: dts: k3-am64x-binman: Configure firewall for ATF/OPTEE

 arch/arm/dts/k3-am625-sk-binman.dtsi | 29 +++++++++++++++++++++++++
 arch/arm/dts/k3-am62a-sk-binman.dtsi | 30 ++++++++++++++++++++++++++
 arch/arm/dts/k3-am62p-sk-binman.dtsi | 32 ++++++++++++++++++++++++++++
 arch/arm/dts/k3-am64x-binman.dtsi    | 31 +++++++++++++++++++++++++++
 arch/arm/dts/k3-binman.dtsi          |  8 +++----
 5 files changed, 126 insertions(+), 4 deletions(-)

-- 
2.34.1

Reply via email to