From: Rasmus Villemoes <ravi@prevas.dk>
To: u-boot@lists.denx.de
Cc: Neha Malcom Francis <n-francis@ti.com>,
Anshul Dalal <anshuld@ti.com>, Simon Glass <sjg@chromium.org>,
Tom Rini <trini@konsulko.com>, Rasmus Villemoes <ravi@prevas.dk>
Subject: [PATCH v2 6/7] k3-binman.dtsi: insert keyfile and distinguished name templates in all ti-secure(-rom) nodes
Date: Fri, 17 Jul 2026 15:58:23 +0200 [thread overview]
Message-ID: <20260717135824.2142135-7-ravi@prevas.dk> (raw)
In-Reply-To: <20260717135824.2142135-1-ravi@prevas.dk>
This should not make any functional difference, and downstream boards
that already override the keyfile property via an explicit .dtsi
fragment for each node will continue to have precedence over the value
coming from the template. But this makes it much more ergonomic to
have the keyfile and distinguished-name have consistent values
throughout, because one only has to override the values in the
templates and not each and every individual node.
Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
---
arch/arm/dts/k3-binman.dtsi | 21 ++++++++++-----------
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/arch/arm/dts/k3-binman.dtsi b/arch/arm/dts/k3-binman.dtsi
index 2c9e5b619b7..797c271bdeb 100644
--- a/arch/arm/dts/k3-binman.dtsi
+++ b/arch/arm/dts/k3-binman.dtsi
@@ -150,8 +150,8 @@
arch = "arm";
compression = "none";
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&board_cfg>;
- keyfile = "custMpk.pem";
};
board_cfg: board-cfg {
filename = "board-cfg.bin";
@@ -165,8 +165,8 @@
arch = "arm";
compression = "none";
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&pm_cfg>;
- keyfile = "custMpk.pem";
};
pm_cfg: pm-cfg {
filename = "pm-cfg.bin";
@@ -179,8 +179,8 @@
arch = "arm";
compression = "none";
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&rm_cfg>;
- keyfile = "custMpk.pem";
};
rm_cfg: rm-cfg {
filename = "rm-cfg.bin";
@@ -193,8 +193,8 @@
arch = "arm";
compression = "none";
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&sec_cfg>;
- keyfile = "custMpk.pem";
};
sec_cfg: sec-cfg {
filename = "sec-cfg.bin";
@@ -287,8 +287,8 @@
load = <CONFIG_K3_ATF_LOAD_ADDR>;
entry = <CONFIG_K3_ATF_LOAD_ADDR>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&atf>;
- keyfile = "custMpk.pem";
};
atf: atf-bl31 {
};
@@ -303,8 +303,8 @@
load = <CONFIG_K3_OPTEE_LOAD_ADDR>;
entry = <CONFIG_K3_OPTEE_LOAD_ADDR>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&tee>;
- keyfile = "custMpk.pem";
};
tee: tee-os {
optional;
@@ -330,9 +330,8 @@
load = <CONFIG_SPL_TEXT_BASE>;
entry = <CONFIG_SPL_TEXT_BASE>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&u_boot_spl_nodtb>;
- keyfile = "custMpk.pem";
-
};
u_boot_spl_nodtb: blob-ext {
filename = "spl/u-boot-spl-nodtb.bin";
@@ -419,8 +418,8 @@
compression = "none";
load = <CONFIG_TEXT_BASE>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&u_boot_nodtb>;
- keyfile = "custMpk.pem";
};
u_boot_nodtb: u-boot-nodtb {
};
@@ -521,8 +520,8 @@
load = <CONFIG_K3_ATF_LOAD_ADDR>;
entry = <CONFIG_K3_ATF_LOAD_ADDR>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&atf_falcon>;
- keyfile = "custMpk.pem";
};
atf_falcon: atf-bl31 {
};
@@ -536,8 +535,8 @@
load = <CONFIG_K3_OPTEE_LOAD_ADDR>;
entry = <CONFIG_K3_OPTEE_LOAD_ADDR>;
ti-secure {
+ insert-template = <&keyfile_template>, <&distinguished_name_template>;
content = <&tee_falcon>;
- keyfile = "custMpk.pem";
};
tee_falcon: tee-os {
optional;
--
2.55.0
next prev parent reply other threads:[~2026-07-17 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:58 [PATCH v2 0/7] k3-binman ergonomics Rasmus Villemoes
2026-07-17 13:58 ` [PATCH v2 1/7] binman: openssl: refactor creation of Distinguished Name section from dict Rasmus Villemoes
2026-07-17 13:58 ` [PATCH v2 2/7] binman: x509_cert: allow and parse distinguished-name subnode Rasmus Villemoes
2026-07-17 13:58 ` [PATCH v2 3/7] binman: x509: fix CN emitted for basic x509 certificates Rasmus Villemoes
2026-07-17 13:58 ` [PATCH v2 4/7] k3-binman.dtsi: add keyfile_template node Rasmus Villemoes
2026-07-17 13:58 ` [PATCH v2 5/7] k3-binman.dtsi: add empty distinguished_name_template Rasmus Villemoes
2026-07-17 13:58 ` Rasmus Villemoes [this message]
2026-07-17 13:58 ` [PATCH v2 7/7] doc: k3.rst: describe use of keyname and distinguished_name binman templates Rasmus Villemoes
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=20260717135824.2142135-7-ravi@prevas.dk \
--to=ravi@prevas.dk \
--cc=anshuld@ti.com \
--cc=n-francis@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox