From: Josua Mayer <josua@solid-run.com>
To: Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v5 0/7] arm64: dts: add description for solidrun imx8mp hummingboard-iiot
Date: Mon, 5 Jan 2026 07:31:08 +0000 [thread overview]
Message-ID: <1943543.tdWV9SEqCh@josua-pc> (raw)
In-Reply-To: <6e1d7e2e-9585-4b4e-8c82-004a613bdb39@kernel.org>
On Monday, 5 January 2026 9:12:12 IST Krzysztof Kozlowski wrote:
> On 04/01/2026 14:46, Josua Mayer wrote:
> > On Friday, 2 January 2026 16:43:35 IST Rob Herring wrote:
> >> This patch series was applied (using b4) to base:
> >> Base: 8f0b4cce4481fb22653697cced8d0d04027cb1e8 (use --merge-base to
> >>
> >> override)
> >>
> >> If this is not the correct base, please add 'base-commit' tag
> >> (or use b4 which does this automatically)
> >>
> >> New warnings running 'make CHECK_DTBS=y for
> >> arch/arm64/boot/dts/freescale/'
> >> for 20260101-imx8mp-hb-iiot-v5-0-b369b2e0c07f@solid-run.com:
> >>
> >> scripts/Makefile.dtbs:20: .dtbo is not applied to any base:
> >> imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0.dtbo
> >> imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA.dtbo
> >> imx8mp-hummingboard-iiot-rs485-a.dtbo
> >> imx8mp-hummingboard-iiot-rs485-b.dtbo
> >
> > These overlays are not applied to anything on purpose,
> > as we don't want to create a dtb for each possible combination.
In particular we want bootloader to load individual addons,
rather than a named dtb with a preapplied combination.
>
> But we want to validate applying DTB.
Reasonable.
>
> > Is there any advice what to do in this case?
>
> If you don't want to follow upstream rules, I think we cannot take that
> code, so don't upstream code...
My question is more technical nature.
Is it okay to add a few concatenated dtb names covering all overlays? I.e.:
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0-rs485-a.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA-rs485-b.dtb
Perhaps one dtb for each overlay?
imx8mp-hummingboard-iiot-rs485-a.dtb
imx8mp-hummingboard-iiot-rs485-b.dtb
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA5.dtb
Or should we create all valid combinations?:
imx8mp-hummingboard-iiot-rs485-a.dtb
imx8mp-hummingboard-iiot-rs485-b.dtb
imx8mp-hummingboard-iiot-rs485-a-rs485-b.dtb
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0.dtb
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0-rs485-a.dtb
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0-rs485-b.dtb
imx8mp-hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0-rs485-a-rs485-b.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA5.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA5-rs485-a.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA5-rs485-b.dtb
imx8mp-hummingboard-iiot-panel-lvds-WF70A8SYJHLNGA5-rs485-a-rs485-b.dtb
Note lvds and dsi are not currently combined due to HW design issues.
sincerely
Josua Mayer
next prev parent reply other threads:[~2026-01-05 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 15:05 [PATCH v5 0/7] arm64: dts: add description for solidrun imx8mp hummingboard-iiot Josua Mayer
2026-01-01 15:05 ` [PATCH v5 1/7] dt-bindings: arm: fsl: Add various solidrun i.mx8m boards Josua Mayer
2026-01-01 15:05 ` [PATCH v5 2/7] arm64: dts: imx8mp-hummingboard-pulse/cubox-m: fix vmmc gpio polarity Josua Mayer
2026-01-01 15:05 ` [PATCH v5 3/7] arm64: dts: imx8mp-hummingboard-pulse: fix mini-hdmi dsi port reference Josua Mayer
2026-01-01 15:05 ` [PATCH v5 4/7] arm64: dts: imx8mp-sr-som: build dtbs with symbols for overlay support Josua Mayer
2026-01-01 15:05 ` [PATCH v5 5/7] arm64: dts: add description for solidrun imx8mp hummingboard-iiot Josua Mayer
2026-01-01 15:05 ` [PATCH v5 6/7] arm64: dts: add description for solidrun solidsense-n8 board Josua Mayer
2026-01-01 15:05 ` [PATCH v5 7/7] arm64: dts: add description for solidrun i.mx8mm som and evb Josua Mayer
2026-01-02 14:43 ` [PATCH v5 0/7] arm64: dts: add description for solidrun imx8mp hummingboard-iiot Rob Herring
2026-01-04 13:46 ` Josua Mayer
2026-01-05 7:12 ` Krzysztof Kozlowski
2026-01-05 7:31 ` Josua Mayer [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-21 11:28 Josua Mayer
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=1943543.tdWV9SEqCh@josua-pc \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).