From: "J. Neuschäfer" <j.ne@posteo.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: j.ne@posteo.net, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] powerpc: dts: Build devicetrees of enabled platforms
Date: Wed, 04 Mar 2026 13:47:08 +0000 [thread overview]
Message-ID: <aag32bMA9aiEbSIP@probook> (raw)
In-Reply-To: <CAMuHMdXZYuDn5RRFFUp7kXFDn_fMZuqHbXmSJie4ofEv8NxXfw@mail.gmail.com>
On Tue, Mar 03, 2026 at 10:34:26PM +0100, Geert Uytterhoeven wrote:
> Hi J,
>
> On Tue, 3 Mar 2026 at 16:56, J. Neuschäfer via B4 Relay
> <devnull+j.ne.posteo.net@kernel.org> wrote:
> > From: "J. Neuschäfer" <j.ne@posteo.net>
> >
> > Follow the same approach as other architectures such as Arm or RISC-V,
> > and build devicetrees based on platforms selected in Kconfig. This makes
> > it unnecessary to use CONFIG_OF_ALL_DTBS on PowerPC in order to build
> > DTB files.
> >
> > This makes it easier to use other build and test infrastructure such as
> > `make dtbs_check`, and is a first step towards generating FIT images
> > that include all the relevant DTBs with `make image.fit`.
> >
> > Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
>
> Thanks for your patch!
>
> > --- a/arch/powerpc/boot/dts/Makefile
> > +++ b/arch/powerpc/boot/dts/Makefile
> > @@ -3,3 +3,158 @@
> > subdir-y += fsl
> >
> > dtb-$(CONFIG_OF_ALL_DTBS) := $(patsubst $(src)/%.dts,%.dtb, $(wildcard $(src)/*.dts))
> > +
> > +# PPC44x platforms
> > +dtb-$(CONFIG_PPC44x_SIMPLE) += \
> > + arches.dtb \
[...]
> > + icon.dtb
> > +dtb-$(CONFIG_EBONY) += \
> > + ebony.dtb
>
> This fits on a single line (many more below)
>
> [...]
>
> > +# MPC5200 platforms
> > +dtb-$(CONFIG_PPC_MPC5200_SIMPLE) += \
[...]
> > + tqm5200.dtb \
> > + uc101.dtb
>
> Even when it wouldn't fit on a single line, having separate
>
> dtb-$(CONFIG_FOO) += bar1.dtb
> dtb-$(CONFIG_FOO) += bar2.dtb
>
> lines not only makes it a little bit shorter, but avoids the churn of
> adding a backslash to the previous line when adding new entries.
Sounds good, I'll do that for v2.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
prev parent reply other threads:[~2026-03-04 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:55 [PATCH RESEND] powerpc: dts: Build devicetrees of enabled platforms J. Neuschäfer via B4 Relay
2026-03-03 21:34 ` Geert Uytterhoeven
2026-03-04 13:47 ` J. Neuschäfer [this message]
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=aag32bMA9aiEbSIP@probook \
--to=j.ne@posteo.net \
--cc=chleroy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=robh@kernel.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