From: sashiko-bot@kernel.org
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v2] ARM: dts: nxp/imx6: Drop unused .dtsi
Date: Thu, 05 Nov 2026 14:59:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-199279@kernel.org> (raw)
In-Reply-To: <20261105144920.2796623-2-robh@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] ARM: dts: imx6: Deleting Dwarf and Nymph .dtsi omitted by copy-paste in .dts
--
commit 22f4920daa7995325841819b6b25c37d2efd2b30
Author: Rob Herring (Arm) <robh@kernel.org>
ARM: dts: nxp/imx6: Drop unused .dtsi
This commit removes four i.MX6 device tree include files that are not
currently included by any in-tree device tree sources.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-dwarf.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-dwarf.dtsi
> deleted file mode 100644
> index 3a968782e854b..0000000000000
> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-dwarf.dtsi
> +++ /dev/null
> @@ -1,45 +0,0 @@
> -// SPDX-License-Identifier: GPL-2.0+ OR MIT
> -//
> -// Copyright 2017 NXP
> -
> -#include "imx6qdl-pico.dtsi"
[ ... ]
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-nymph.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-nymph.dtsi
> deleted file mode 100644
> index 3d56a42164482..0000000000000
> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-pico-nymph.dtsi
> +++ /dev/null
> @@ -1,54 +0,0 @@
> -// SPDX-License-Identifier: GPL-2.0+ OR MIT
> -
> -#include "imx6qdl-pico.dtsi"
[Severity: Medium]
Should imx6qdl-pico-dwarf.dtsi and imx6qdl-pico-nymph.dtsi be wired up to
their existing board device trees instead of being deleted?
Unlike the Kontron files, the corresponding board files for Dwarf and Nymph
already exist in the tree and are built by arch/arm/boot/dts/nxp/imx/Makefile
(imx6dl-pico-dwarf.dts, imx6q-pico-dwarf.dts, imx6dl-pico-nymph.dts, and
imx6q-pico-nymph.dts).
When commit 98670a0bb0ef ("ARM: dts: imx6qdl: Add imx6qdl-pico support")
added support for the Dwarf, Hobbit, Nymph, and Pi baseboards, a copy-paste
error left the Dwarf and Nymph .dts files including imx6qdl-pico-pi.dtsi:
arch/arm/boot/dts/nxp/imx/imx6dl-pico-dwarf.dts:
#include "imx6dl.dtsi"
#include "imx6qdl-pico-pi.dtsi"
/ {
model = "TechNexion PICO-IMX6 DualLite/Solo Board and Dwarf baseboard";
compatible = "technexion,imx6dl-pico-dwarf", "fsl,imx6dl";
};
arch/arm/boot/dts/nxp/imx/imx6dl-pico-nymph.dts:
#include "imx6dl.dtsi"
#include "imx6qdl-pico-pi.dtsi"
/ {
model = "TechNexion PICO-IMX6 DualLite/Solo Board and Nymph baseboard";
compatible = "technexion,imx6dl-pico-nymph", "fsl,imx6dl";
};
(and similarly in imx6q-pico-dwarf.dts and imx6q-pico-nymph.dts).
As a result, the Dwarf and Nymph board DTBs are currently built with the Pi
baseboard description (which disables HDMI and routes the LED to GPIO5_IO18)
rather than their own baseboard descriptions in imx6qdl-pico-dwarf.dtsi
(GPIO5_IO31 LED, mpl3115@60 on i2c1, and pca9554 io-expander@25 on i2c2) and
imx6qdl-pico-nymph.dtsi (GPIO5_IO31 LED, adc@52 on i2c1, pca9554
io-expander@25 on i2c2, ds1337 rtc@68 on i2c3, and PCIe enabled).
Would it make sense to keep imx6qdl-pico-dwarf.dtsi and
imx6qdl-pico-nymph.dtsi and update the four Dwarf and Nymph .dts files to
include them?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105144920.2796623-2-robh@kernel.org?part=1
next prev parent reply other threads:[~2026-11-05 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:49 [PATCH v2] ARM: dts: nxp/imx6: Drop unused .dtsi Rob Herring (Arm)
2026-11-05 14:59 ` sashiko-bot [this message]
2026-11-05 15:04 ` Rob Herring
2026-11-05 15:00 ` Marco Felsch
2026-11-05 15:06 ` Rob Herring
2026-11-05 15:09 ` Marco Felsch
2026-11-05 15:35 ` Marco Felsch
2026-11-05 16:41 ` Frank Li
2026-11-05 17:32 ` Marco Felsch
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=sashiko-outbox-199279@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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