From: sashiko-bot@kernel.org
To: "Marek Vasut" <marex@nabladev.com>
Cc: robh@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v9 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Tue, 04 Aug 2026 17:46:04 +0000 [thread overview]
Message-ID: <20260804174604.D09141F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804162310.24374-7-marex@nabladev.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] DT Node Conflict / Duplicate Unit Address
--
--- Patch [7]: [PATCH v9 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio DTOs for Data Modul i.MX8M Mini and Plus eDM SBC ---
commit c5a51996123e2650a624a6ad09a9ec065dfa47f6
Author: Marek Vasut <marex@nabladev.com>
arm64: dts: imx8mm: imx8mp: Add FIO1-Audio DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
This commit adds Device Tree Overlays for the eDM-MOD-iMX8Mm-FIO1-Audio
feature connector expansion module. The module provides an SGTL5000 codec,
CAN, PWM, UARTs, and other IO for the Data Modul i.MX8M Mini and Plus
eDM SBCs.
> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso b/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso
> new file mode 100644
> index 0000000000000..88fa705ac2b67
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso
[ ... ]
> @@ -0,0 +1,79 @@
[ ... ]
> +&spba2 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + sai5clk: clock-controller@30050000 { /* SAI5 */
[Severity: Low]
Will this trigger unique_unit_address warnings during DT validation?
The base imx8mm.dtsi already defines an sai@30050000 node inside spba2.
Adding a sibling clock-controller@30050000 node creates two nodes with the
same unit address. Even though the base sai node is disabled, this violates
the DT specification that sibling nodes must have unique addresses.
Would it be better to override the existing &sai5 node directly, or
explicitly delete it first with /delete-node/ &sai5?
> + compatible = "fsl,imx8mm-sai-clock", "fsl,imx8mq-sai-clock";
[ ... ]
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso b/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso
> new file mode 100644
> index 0000000000000..4e2112355350f
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1-audio.dtso
[ ... ]
> @@ -0,0 +1,67 @@
[ ... ]
> +&spba5 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + sai5clk: clock-controller@30c50000 {
[Severity: Low]
Does this also conflict with the existing sai@30c50000 node in spba5
defined in the base imx8mp.dtsi?
Like the i.MX8MM overlay, this adds a clock-controller@30c50000 sibling
node that shares a unit address with the existing sai node.
Should this overlay override &sai5 directly or delete the existing node
first to avoid DT validation warnings?
> + compatible = "fsl,imx8mp-sai-clock", "fsl,imx8mq-sai-clock";
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260804162310.24374-1-marex@nabladev.com?part=7
prev parent reply other threads:[~2026-08-04 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 16:22 [PATCH v9 1/7] arm64: dts: imx8mp: Add DT label to SPBA5 bus Marek Vasut
2026-08-04 16:22 ` [PATCH v9 2/7] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-08-04 16:37 ` sashiko-bot
2026-08-04 16:22 ` [PATCH v9 3/7] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-08-04 16:42 ` sashiko-bot
2026-08-04 16:22 ` [PATCH v9 4/7] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-08-04 16:22 ` [PATCH v9 5/7] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-08-04 16:22 ` [PATCH v9 6/7] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-08-04 17:20 ` sashiko-bot
2026-08-04 16:22 ` [PATCH v9 7/7] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-08-04 17:46 ` sashiko-bot [this message]
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=20260804174604.D09141F000E9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox