linux-kernel - Re: [PATCH v5 0/7] arm64: dts: add description for solidrun imx8mp hummingboard-iiot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1943543.tdWV9SEqCh@josua-pc>
Date: Mon, 5 Jan 2026 07:31:08 +0000
From: Josua Mayer <josua@...id-run.com>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>
CC: "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, Shawn Guo <shawnguo@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"imx@...ts.linux.dev" <imx@...ts.linux.dev>, Pengutronix Kernel Team
	<kernel@...gutronix.de>, Sascha Hauer <s.hauer@...gutronix.de>, Fabio Estevam
	<festevam@...il.com>
Subject: Re: [PATCH v5 0/7] arm64: dts: add description for solidrun imx8mp
 hummingboard-iiot

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@...id-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