U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: E Shattow <e@freeshell.de>
Cc: u-boot@lists.u-boot-project.org, Yao Zi <me@ziyao.cc>,
	Tim Ouyang <tim609@andestech.com>,
	Leo Liang <leo.liang@sifive.com>, Tom Rini <trini@konsulko.com>,
	Michal Simek <michal.simek@amd.com>,
	Raymond Mao <raymond.mao@riscstar.com>,
	Hiago De Franco <hfranco@baylibre.com>,
	Junhui Liu <junhui.liu@pigmoral.tech>
Subject: Re: [PATCH v3 2/4] riscv: dts: spacemit: k3: add binman node
Date: Sat, 3 Oct 2026 10:14:27 +0000	[thread overview]
Message-ID: <20261003101427-GKA68132@kernel.org> (raw)
In-Reply-To: <2dcd6f21-ea10-4986-ae3c-fb81f5d768a4@freeshell.de>

Hi E Shattow,

Thanks for the suggestion

On 00:49 Sat 03 Oct     , E Shattow wrote:
> On 10/2/26 17:34, Yixun Lan wrote:
> > SpacemiT K3 follow the standard riscv binman layout, which has opensbi
> > and U-Boot proper, so include the common binman dtsi file.
> > 
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> > ---
> >  arch/riscv/dts/spacemit-k3-u-boot.dtsi | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/arch/riscv/dts/spacemit-k3-u-boot.dtsi b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
> > new file mode 100644
> > index 00000000000..f1c1c3ee6fd
> > --- /dev/null
> > +++ b/arch/riscv/dts/spacemit-k3-u-boot.dtsi
> > @@ -0,0 +1,6 @@
> > +// SPDX-License-Identifier: GPL-2.0+ OR MIT
> > +/*
> > + * Copyright (C) 2026 Yixun Lan <dlan@kernel.org>
> > + */
> > +
> > +#include "binman.dtsi"
> > 
> 
> Looks good to me. I suggest to introduce spacemit-k3-binman.dtsi now or
> later, may as well do it now?
> 
Yes, I thought about this as we introduced new SpacemiT image format..
I have no objection to do it now in this series

> See for example of how this looks in files
> starfive-visionfive2-binman.dtsi and starfive-visionfive2-u-boot.dtsi,
> it would be as follows:
> 
> arch/riscv/dts/spacemit-k3-binman.dtsi:
> ...copyright comment...
> +#include "binman.dtsi"
> +
> +
> 
> arch/riscv/dts/spacemit-k3-u-boot.dtsi:
> ...copyright comment...
> -#include "binman.dtsi"
> +
> +
> +#include "spacemit-k3-binman.dtsi"
> 
> With that,
> 
> Reviewed-by: E Shattow <e@freeshell.de>

-- 
Yixun Lan (dlan)

  reply	other threads:[~2026-10-03 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03  0:34 [PATCH v3 0/4] riscv: spacemit: Add support for K3 Pico-ITX board Yixun Lan
2026-10-03  0:34 ` [PATCH v3 1/4] board: spacemit: add SpacemiT K3 Pico-ITX Yixun Lan
2026-10-03 10:02   ` E Shattow
2026-10-03 11:08     ` Yixun Lan
2026-10-03 11:18       ` E Shattow
2026-10-03  0:34 ` [PATCH v3 2/4] riscv: dts: spacemit: k3: add binman node Yixun Lan
2026-10-03  7:49   ` E Shattow
2026-10-03 10:14     ` Yixun Lan [this message]
2026-10-03  0:34 ` [PATCH v3 3/4] configs: spacemit: Add K3 default configuration Yixun Lan
2026-10-03  8:04   ` E Shattow
2026-10-03  0:34 ` [PATCH v3 4/4] doc: spacemit: k3: Add Pico-ITX board Yixun Lan
2026-10-03 12:43   ` E Shattow
2026-10-04  1:39     ` Yixun Lan

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=20261003101427-GKA68132@kernel.org \
    --to=dlan@kernel.org \
    --cc=e@freeshell.de \
    --cc=hfranco@baylibre.com \
    --cc=junhui.liu@pigmoral.tech \
    --cc=leo.liang@sifive.com \
    --cc=me@ziyao.cc \
    --cc=michal.simek@amd.com \
    --cc=raymond.mao@riscstar.com \
    --cc=tim609@andestech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    /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