From: Rasmus Villemoes <ravi@prevas.dk>
To: "Simon Glass" <sjg@chromium.org>
Cc: <u-boot@lists.denx.de>, "Neha Malcom Francis" <n-francis@ti.com>,
"Anshul Dalal" <anshuld@ti.com>, "Tom Rini" <trini@konsulko.com>
Subject: Re: [PATCH 6/6] k3-binman.dtsi: insert keyfile and distinguished name templates in all ti-secure(-rom) nodes
Date: Mon, 13 Jul 2026 16:53:17 +0200 [thread overview]
Message-ID: <87o6gbrleq.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <CAFLszTjzRQStvr-Vs=aOQ=BaMKBPFmtkPfNXKdh7XNsZ9hacSA@mail.gmail.com> (Simon Glass's message of "Mon, 13 Jul 2026 06:55:00 -0600")
On Mon, Jul 13 2026, "Simon Glass" <sjg@chromium.org> wrote:
> Hi Rasmus,
>
> On 2026-07-10T12:36:12, Rasmus Villemoes <ravi@prevas.dk> wrote:
>> k3-binman.dtsi: insert keyfile and distinguished name templates in all ti-secure(-rom) nodes
>>
>> 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 | 20 ++++++++++----------
>> 1 file changed, 10 insertions(+), 10 deletions(-)
>
>> k3-binman.dtsi: insert keyfile and distinguished name templates in all ti-secure(-rom) nodes
>
> I still see lots of custMpk.pem in .dtsi files after this series so
> I'm not sure of the exact mechanism for your claim in this series. I
> was expecting it to remove all of those?
Well, changing those are not needed for my immediate purpose, I only
need those in k3-binman.dtsi to be updated, as that is the only upstream
file I include. Yes, they should probably all be updated, but I didn't
want to pollute this series with tons of mechanical changes, that can be
done as a followup if and when this lands.
>> diff --git a/arch/arm/dts/k3-binman.dtsi b/arch/arm/dts/k3-binman.dtsi
>> @@ -330,8 +330,8 @@
>> ti-secure {
>> + insert-template = <&keyfile_template>, <&distinguished_name_template>;
>> content = <&u_boot_spl_nodtb>;
>> - keyfile = 'custMpk.pem';
>>
>> };
>
> Removing the keyfile property leaves a stray blank line before the
> closing brace. Please can you drop that while you are at it?
Of course.
Rasmus
next prev parent reply other threads:[~2026-07-13 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:36 [PATCH 0/6] k3-binman ergonomics Rasmus Villemoes
2026-07-10 12:36 ` [PATCH 1/6] binman: openssl: refactor creation of Distinguished Name section from dict Rasmus Villemoes
2026-07-13 12:40 ` Simon Glass
2026-07-14 5:29 ` Neha Malcom Francis
2026-07-10 12:36 ` [PATCH 2/6] binman: x509_cert: allow and parse distinguished-name subnode Rasmus Villemoes
2026-07-13 12:40 ` Simon Glass
2026-07-10 12:36 ` [PATCH 3/6] binman: x509: fix CN emitted for basic x509 certificates Rasmus Villemoes
2026-07-13 12:41 ` Simon Glass
2026-07-10 12:36 ` [PATCH 4/6] k3-binman.dtsi: add keyfile_template node Rasmus Villemoes
2026-07-13 12:41 ` Simon Glass
2026-07-10 12:36 ` [PATCH 5/6] k3-binman.dtsi: add empty distinguished_name_template Rasmus Villemoes
2026-07-13 12:41 ` Simon Glass
2026-07-10 12:36 ` [PATCH 6/6] k3-binman.dtsi: insert keyfile and distinguished name templates in all ti-secure(-rom) nodes Rasmus Villemoes
2026-07-13 12:55 ` Simon Glass
2026-07-13 14:53 ` Rasmus Villemoes [this message]
2026-07-13 15:18 ` Simon Glass
2026-07-13 12:19 ` [PATCH 0/6] k3-binman ergonomics Anshul Dalal
2026-07-13 12:54 ` Rasmus Villemoes
2026-07-14 5:36 ` Anshul Dalal
2026-07-13 12:56 ` [0/6] " Simon Glass
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=87o6gbrleq.fsf@rasmusvillemoes.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