From: sashiko-bot@kernel.org
To: "Marek Vasut" <marex@nabladev.com>
Cc: Frank.Li@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v5 5/6] arm64: dts: imx8mm: imx8mp: Add FIO1 DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
Date: Thu, 16 Jul 2026 06:13:37 +0000 [thread overview]
Message-ID: <20260716061338.179F61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260716055751.279033-5-marex@nabladev.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Device Tree node collision and potential I2C address conflict on `io-expander@20`.
--
--- Patch [5]: [PATCH v5 5/6] arm64: dts: imx8mm: imx8mp: Add FIO1 DTOs for Data Modul i.MX8M Mini and Plus eDM SBC ---
commit b8816aeaca7378ddfdc8544c5eb07a316a35281c
Author: Marek Vasut <marex@nabladev.com>
Subject: arm64: dts: imx8mm: imx8mp: Add FIO1 DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
This patch adds a Device Tree overlay for the eDM-MOD-iMX8Mm-FIO1 feature
connector expansion module. It provides additional UARTs, CAN, PWM Beeper,
I2C, SPI, and GPIO breakout for the Data Modul i.MX8M Mini and Plus eDM SBC.
> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1.dtsi b/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1.dtsi
> new file mode 100644
> index 0000000000000..7851ca73ccd8e
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-edm-mod-imx8mm-fio1.dtsi
[ ... ]
> +&i2c_feature { /* Feature connector I2C */
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gpio_feature: io-expander@20 {
> + compatible = "nxp,pca9554";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_gpio_expander>;
> + reg = <0x20>;
[Severity: High]
Will this overlay conflict with the baseboard when applied to the i.MX8MP?
The i.MX8MP baseboard (arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc.dts)
unconditionally defines an LVDS IO expander on the same I2C bus:
gpiolvds: io-expander@20 {
compatible = "nxp,pca9554";
reg = <0x20>;
...
};
When this overlay is applied, won't gpio_feature: io-expander@20 merge into
gpiolvds: io-expander@20 and silently overwrite properties like gpio-line-names
and interrupt assignments, breaking both configurations?
Additionally, if both the baseboard LVDS PCA9554 and the FIO1 expansion
module PCA9554 are physically present, will they cause a hardware collision
on the I2C bus at address 0x20 and fail to probe?
> + #gpio-cells = <2>;
> + gpio-controller;
> + #interrupt-cells = <2>;
> + interrupt-controller;
> + interrupt-parent = <&gpio4>;
> + interrupts = <27 IRQ_TYPE_LEVEL_LOW>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260716055751.279033-1-marex@nabladev.com?part=5
next prev parent reply other threads:[~2026-07-16 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 5:56 [PATCH v5 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS DTOs for Data Modul i.MX8M Mini and Plus eDM SBC Marek Vasut
2026-07-16 5:56 ` [PATCH v5 2/6] arm64: dts: imx8mm: imx8mp: Add legacy board " Marek Vasut
2026-07-16 6:14 ` sashiko-bot
2026-07-16 5:56 ` [PATCH v5 3/6] arm64: dts: imx8mm: imx8mp: Add HDMI " Marek Vasut
2026-07-16 5:56 ` [PATCH v5 4/6] arm64: dts: imx8mm: imx8mp: Add CM " Marek Vasut
2026-07-16 6:08 ` sashiko-bot
2026-07-16 5:56 ` [PATCH v5 5/6] arm64: dts: imx8mm: imx8mp: Add FIO1 " Marek Vasut
2026-07-16 6:13 ` sashiko-bot [this message]
2026-07-16 5:56 ` [PATCH v5 6/6] arm64: dts: imx8mm: imx8mp: Add FIO1-Audio " Marek Vasut
2026-07-16 6:23 ` sashiko-bot
2026-07-16 6:10 ` [PATCH v5 1/6] arm64: dts: imx8mm: imx8mp: Add LVDS " 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=20260716061338.179F61F000E9@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