public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Michael Walle" <mwalle@kernel.org>
To: "Neha Malcom Francis" <n-francis@ti.com>, <u-boot@lists.denx.de>,
	<trini@konsulko.com>, <sjg@chromium.org>,
	<alpernebiyasak@gmail.com>, <bb@ti.com>, <nm@ti.com>,
	<sumit.garg@linaro.org>
Cc: <michal.simek@amd.com>, <marex@denx.de>,
	<neil.armstrong@linaro.org>, <afd@ti.com>, <vigneshr@ti.com>,
	<kamlesh@ti.com>, <m-chawdhry@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 3/4] arm: dts: k3-*-binman.dtsi: Clean up and templatize boot binaries
Date: Tue, 26 Mar 2024 14:48:26 +0100	[thread overview]
Message-ID: <D03Q9AGO5ND9.1TJM3KSNA71WG@kernel.org> (raw)
In-Reply-To: <20240322131011.1029620-4-n-francis@ti.com>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Hi,

On Fri Mar 22, 2024 at 2:10 PM CET, Neha Malcom Francis wrote:
> Clean up templatized boot binaries for all K3 boards. This includes
> modifying the k3-binman.dtsi to use SPL_BOARD_DTB, BOARD_DESCRIPTION and
> UBOOT_BOARD_DESCRIPTION from the files that include it to further reuse
> code.
>
> All k3-<soc>-binman.dtsi will contain only templates. Only required boot
> binaries can be built from the templates in the boards' respective
> -u-boot.dtsi file (or k3-<board>-binman.dtsi if it exists). This allows
> clear distinction between the SoC common stuff vs. what is additionally
> needed to boot up a specific board.

I appreciate the cleanup. But as far as I can see, a board might
only have one device tree. How would that work if the uboot proper
must support multiple device trees?

Thanks,
-michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

  parent reply	other threads:[~2024-03-26 13:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 13:10 [PATCH 0/4] Cleanup K3 binman templating Neha Malcom Francis
2024-03-22 13:10 ` [PATCH 1/4] configs: j721e_sk: Move to separate defconfig for J721E SK board Neha Malcom Francis
2024-03-22 13:10 ` [PATCH 2/4] tools: binman: control.py: Delete template nodes after parsing Neha Malcom Francis
2024-03-22 13:10 ` [PATCH 3/4] arm: dts: k3-*-binman.dtsi: Clean up and templatize boot binaries Neha Malcom Francis
2024-03-23 16:07   ` Andrew Davis
2024-03-25  3:35     ` Neha Malcom Francis
2024-03-25  9:20   ` Manorit Chawdhry
2024-03-25 10:20     ` Neha Malcom Francis
2024-03-26 12:27   ` Nishanth Menon
2024-03-26 12:33     ` Neha Malcom Francis
2024-03-26 13:48   ` Michael Walle [this message]
2024-03-27  7:01     ` Neha Malcom Francis
2024-03-27 14:33       ` Michael Walle
2024-03-28 11:18         ` Neha Malcom Francis
2024-03-28 11:56           ` Michael Walle
2024-04-03  5:32             ` Neha Malcom Francis
2024-04-03 10:34               ` Manorit Chawdhry
2024-04-03 15:51                 ` Michael Walle
2024-04-04  8:04                   ` Matthias Schiffer
2024-04-04  9:10                     ` Neha Malcom Francis
2024-04-05  7:42                       ` Michael Walle
2024-04-12  3:03                         ` Neha Malcom Francis
2024-04-12 11:43                           ` Michael Walle
2024-03-22 13:10 ` [PATCH 4/4] arm: dts: k3-j721e: Move to OF_UPSTREAM Neha Malcom Francis
2024-03-26  6:37   ` Sumit Garg
2024-04-12 14:50 ` [PATCH 0/4] Cleanup K3 binman templating Tom Rini
2024-04-15 19:13   ` Neha Malcom Francis

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=D03Q9AGO5ND9.1TJM3KSNA71WG@kernel.org \
    --to=mwalle@kernel.org \
    --cc=afd@ti.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=bb@ti.com \
    --cc=kamlesh@ti.com \
    --cc=m-chawdhry@ti.com \
    --cc=marex@denx.de \
    --cc=michal.simek@amd.com \
    --cc=n-francis@ti.com \
    --cc=neil.armstrong@linaro.org \
    --cc=nm@ti.com \
    --cc=sjg@chromium.org \
    --cc=sumit.garg@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /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