Message-ID: <9369989.DvuYhMxLoT@josua-pc>
Date: Sun, 4 Jan 2026 13:46:53 +0000
From: Josua Mayer <josua@...id-run.com>
To: Rob Herring <robh@...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>, Krzysztof Kozlowski <krzk@...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 Friday, 2 January 2026 16:43:35 IST Rob Herring wrote:
> On Thu, 01 Jan 2026 17:05:40 +0200, Josua Mayer wrote:
> > This patchset mainly adds description for 3 SolidRun boards:
> > - i.MX8MP Hummingboard IIoT
> > - SolidSense N8 Compact
> > - i.MX8MM Hummingboard Ripple
> > 
> > This includes dt bindings and a range of bug-fixes:
> > 
> > - dt bindings for the boards
> > - fix to dsi panel bindings referncing panel-common and adding port
> > 
> >   property
> > 
> > - cosmetic fix to some  solidrun imx8mp boards for regulator gpio
> > 
> >    polarity
> > 
> > - fix dsi hdmi bridge on hummingboard pulse
> > - compile dtbs with symbols to support overlays
> > - gpiod_set_value _can_sleep conversion for panel and touchscreen
> > 
> >    drivers
> > 
> > Open Questions:
> > 
> > - How to describe HX3 USB-2.0/3.0 Hub placed on a USB-2.0-only Bus
> > 
> >   (affects imx8mm-hummingboard-ripple.dts)
> > 
> > - Is "description for" implied not only on dt-bindings patches, but also
> > 
> >   dts? E.g. is this commit subject acceptable?:
> >   "arm64: dts: add solidrun solidsense-n8 board"
> > 
> > To: Rob Herring <robh@...nel.org>
> > To: Krzysztof Kozlowski <krzk+dt@...nel.org>
> > To: Conor Dooley <conor+dt@...nel.org>
> > To: Shawn Guo <shawnguo@...nel.org>
> > To: Sascha Hauer <s.hauer@...gutronix.de>
> > To: Pengutronix Kernel Team <kernel@...gutronix.de>
> > To: Fabio Estevam <festevam@...il.com>
> > Cc: devicetree@...r.kernel.org
> > Cc: linux-kernel@...r.kernel.org
> > Cc: imx@...ts.linux.dev
> > Cc: linux-arm-kernel@...ts.infradead.org
> > Signed-off-by: Josua Mayer <josua@...id-run.com>
> > 
> > Changes in v6:
> > - imx8mm-hb-ripple: sorted i2c devices by address;
> > 
> >   removed unnecessary newline.
> >   (Reported-by: Shawn Guo <shawnguo@...nel.org>)
> > 
> > - hb-iiot dts: sorted aliases alphabetically;
> > 
> >   fixed gpio flags for vmmc regulator;
> >   specified led@3 reg field in hexadecimal.
> >   (Reported-by: Shawn Guo <shawnguo@...nel.org>)
> > 
> > Changes in v5:
> > - rebased on v6.19-rc1
> > - dropped ilitek-ts patch already picked into input-next
> > - solidsense-n8 / imx8mm-sr-som: drop untested wake-on-lan support
> > - hb-iiot: disable software unsupported rtc timer irq
> > - hb-iiot: fix wrong pins selected for uart4
> > - Link to v4:
> > https://lore.kernel.org/r/20251201-imx8mp-hb-iiot-v4-0-53a4cd6c21bf@solid
> > -run.com
> > 
> > Changes in v4:
> > - dropped patches already picked into drm-misc-next
> > - ronbo panel: picked up reviewed-by tag
> > 
> >   (Reviewed-by: Neil Armstrong <neil.armstrong@...aro.org>)
> > 
> > - ilitek-ts: changed mdelay calls on reset path to fsleep
> > 
> >   (Note Dmitry requested msleep/usleep_range)
> >   (Reported-by: Dmitry Torokhov <dmitry.torokhov@...il.com>)
> > 
> > - changed hummingboard-iiot tpm irq type to level
> > - Link to v3:
> > https://lore.kernel.org/r/20251117-imx8mp-hb-iiot-v3-0-bf1a4cf5fa8e@solid
> > -run.com
> > 
> > Changes in v3:
> > - sinmplified language in gpiod_can_sleep patches.
> > 
> >   (Reported-By: Frank Li <Frank.li@....com>)
> > 
> > - collected ack on winstar lvds panel binding
> > 
> >   (Acked-by: Conor Dooley <conor.dooley@...rochip.com>)
> > 
> > - Link to v2:
> > https://lore.kernel.org/r/20251107-imx8mp-hb-iiot-v2-0-d8233ded999e@solid
> > -run.com
> > 
> > Changes in v2:
> > - fix spelling mistakes in commit descriptions.
> > 
> > - remove redundant "binding for" from subject:
> >   https://elixir.bootlin.com/linux/v6.17-rc3/source/Documentation/devicetr
> >   ee/bindings/submitting-patches.rst (Reported-by: Krzysztof Kozlowski
> >   <krzk@...nel.org>)
> > 
> > - remove one useless comment from imx8mm-sr-som.dtsi to fix long line
> > 
> >   warning.
> > 
> > - change ronbo panel binding to inherit panel-common and switch
> > 
> >   additionalProperties to unevaluatedProperties.
> >   (Reported-by: Krzysztof Kozlowski <krzk@...nel.org>)
> > 
> > - add dt binding for winstar lvds panel
> > - fix dtbs_check for dsi & lvds panel addons
> > - change n8 board dts comment-style in header
> > - collected ack on solidrun boards bindings patch (patch 1 in the series)
> > 
> >   (Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>)
> > 
> > - added standard led label property to hb-iiot multi-purpose leds
> > 
> >   ensuring consistent names in case lp5562 driver starts using it.
> > 
> > - Link to v1:
> > https://lore.kernel.org/r/20251027-imx8mp-hb-iiot-v1-0-683f86357818@solid
> > -run.com
> > 
> > ---
> > 
> > Josua Mayer (7):
> >       dt-bindings: arm: fsl: Add various solidrun i.mx8m boards
> >       arm64: dts: imx8mp-hummingboard-pulse/cubox-m: fix vmmc gpio
> >       polarity
> >       arm64: dts: imx8mp-hummingboard-pulse: fix mini-hdmi dsi port
> >       reference
> >       arm64: dts: imx8mp-sr-som: build dtbs with symbols for overlay
> >       support
> >       arm64: dts: add description for solidrun imx8mp hummingboard-iiot
> >       arm64: dts: add description for solidrun solidsense-n8 board
> >       arm64: dts: add description for solidrun i.mx8mm som and evb
> >  
> >  Documentation/devicetree/bindings/arm/fsl.yaml     |   9 +
> >  arch/arm64/boot/dts/freescale/Makefile             |  15 +
> >  .../dts/freescale/imx8mm-hummingboard-ripple.dts   | 335 ++++++++
> >  arch/arm64/boot/dts/freescale/imx8mm-sr-som.dtsi   | 393 ++++++++++
> >  .../dts/freescale/imx8mn-solidsense-n8-compact.dts | 851
> >  +++++++++++++++++++++ arch/arm64/boot/dts/freescale/imx8mp-cubox-m.dts  
> >  |   2 +-
> >  ...hummingboard-iiot-panel-dsi-WJ70N3TYJHMNG0.dtso |  69 ++
> >  ...ummingboard-iiot-panel-lvds-WF70A8SYJHLNGA.dtso | 105 +++
> >  .../imx8mp-hummingboard-iiot-rs485-a.dtso          |  18 +
> >  .../imx8mp-hummingboard-iiot-rs485-b.dtso          |  18 +
> >  .../dts/freescale/imx8mp-hummingboard-iiot.dts     | 719
> >  +++++++++++++++++
> >  .../imx8mp-hummingboard-pulse-common.dtsi          |   2 +-
> >  .../imx8mp-hummingboard-pulse-mini-hdmi.dtsi       |  11 +-
> >  13 files changed, 2538 insertions(+), 9 deletions(-)
> > 
> > ---
> > base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
> > change-id: 20251026-imx8mp-hb-iiot-525b03beea62
> > 
> > Best regards,
> > --
> > Josua Mayer <josua@...id-run.com>
> 
> My bot found new DTB warnings on the .dts files added or changed in this
> series.
> 
> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
> are fixed by another series. Ultimately, it is up to the platform
> maintainer whether these warnings are acceptable or not. No need to reply
> unless the platform maintainer has comments.
> 
> If you already ran DT checks and didn't see these error(s), then
> make sure dt-schema is up to date:
> 
>   pip3 install dtschema --upgrade
> 
> 
> 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.

Is there any advice what to do in this case?

Powered by blists - more mailing lists