From: sashiko-bot@kernel.org
To: "Marek Vasut" <marex@nabladev.com>
Cc: Frank.Li@kernel.org, imx@lists.linux.dev, conor+dt@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 3/7] arm64: dts: imx8mm: imx8mp: Add legacy board DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Mon, 27 Jul 2026 20:14:18 +0000 [thread overview]
Message-ID: <20260727201418.A2B831F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727195244.78199-3-marex@nabladev.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Chaining overlays in a multi-dtb rule fails at build time because preceding overlays do not export `__symbols__` for subsequent overlays to resolve their `__fixups__`.
--
--- Patch [3]: [PATCH v6 3/7] arm64: dts: imx8mm: imx8mp: Add legacy board DTOs for Data Modul i.MX8M Mini and Plus eDM SBC ---
commit 68e606cc871d4844f2966698d1f9194823c8f933
Author: Marek Vasut <marex@nabladev.com>
arm64: dts: imx8mm: imx8mp: Add legacy board DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
This patch adds legacy board revision compatibility DT overlays for both
i.MX8M Mini and Plus eDM SBC boards. It includes adjustments to support
these legacy board revisions.
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index 9da078bb6380b..c3de54507aae0 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
[ ... ]
> @@ -344,6 +350,24 @@ imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-mi1010z1t-1cp11-dtbs := \
> imx8mp-data-modul-edm-sbc.dtb \
> imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-mi1010z1t-1cp11.dtbo
>
> +imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-rev900-dtbs := \
> + imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-rev900.dtb \
> + imx8mp-data-modul-edm-sbc-overlay-edm-mod-imx8mm-lvds-g070y2-l01.dtbo \
> + imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-rev900.dtbo
[Severity: Low]
Does this multi-dtb rule cause an fdtoverlay failure at build time?
Because the Kbuild system compiles .dtbo files without the -@ flag unless
explicitly requested, the first overlay (...lvds-g070y2-l01.dtbo) does not
export __symbols__ for the subsequent overlay (...lvds-rev900.dtbo) to resolve
its __fixups__ against.
[ ... ]
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-rev900.dtso b/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-rev900.dtso
> new file mode 100644
> index 0000000000000..427585b78e45d
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-sbc-imx8mp-lvds-rev900.dtso
[ ... ]
> +®_panel_bl_supply {
> + status = "disabled";
> +};
[Severity: Low]
Will this label reference fail to resolve during the build since it relies
on the preceding overlay in the chain which does not have symbols enabled?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727195244.78199-1-marex@nabladev.com?part=3
next prev parent reply other threads:[~2026-07-27 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 19:52 [PATCH v6 1/7] arm64: dts: imx8mp: Add DT label to SPBA5 bus Marek Vasut
2026-07-27 19:52 ` [PATCH v6 2/7] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-07-27 20:07 ` sashiko-bot
2026-07-27 19:52 ` [PATCH v6 3/7] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-07-27 20:14 ` sashiko-bot [this message]
2026-07-27 19:52 ` [PATCH v6 4/7] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-07-27 19:52 ` [PATCH v6 5/7] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-07-27 19:52 ` [PATCH v6 6/7] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-07-27 19:52 ` [PATCH v6 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-07-27 20:08 ` sashiko-bot
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=20260727201418.A2B831F000E9@smtp.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=marex@nabladev.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.