From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCHv2] ARM: dts: marvell: armada-388: use onnn,pca9655 compatible
Date: Mon, 07 Sep 2026 01:12:43 +0000 [thread overview]
Message-ID: <20260907011244.7EF5B1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907005933.230766-1-rosenp@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Replacing 'nxp,pca9555' entirely with 'onnn,pca9655' removes the fallback string, breaking device tree ABI backward compatibility.
- [Low] The newly introduced compatible string 'onnn,pca9655' is not documented in the device tree bindings, which will cause a schema validation failure.
--
commit c8f9a287a2365f46a814726f590cf6561513d0de
Author: Rosen Penev <rosenp@gmail.com>
ARM: dts: marvell: armada-388: use onnn,pca9655 compatible
This patch updates the GPIO expander compatible string in the Armada 388
ClearFog and Helios4 device trees from nxp,pca9555 to onnn,pca9655, and
removes a stale comment about I2C matching limitations.
> diff --git a/arch/arm/boot/dts/marvell/armada-388-clearfog.dtsi b/arch/arm/boot/dts/marvell/armada-388-clearfog.dtsi
> index f8a06ae4a3c91..4a61e9d1a2c0d 100644
> --- a/arch/arm/boot/dts/marvell/armada-388-clearfog.dtsi
> +++ b/arch/arm/boot/dts/marvell/armada-388-clearfog.dtsi
> @@ -131,12 +131,7 @@ &i2c0 {
> * 15-SFP_MOD_DEF0
> */
> expander0: gpio-expander@20 {
> - /*
> - * This is how it should be:
> - * compatible = "onnn,pca9655", "nxp,pca9555";
> - * but you can't do this because of the way I2C works.
> - */
> - compatible = "nxp,pca9555";
> + compatible = "onnn,pca9655";
[Severity: High]
Does replacing nxp,pca9555 entirely with onnn,pca9655 break backward
compatibility for older kernels booting with this new device tree blob?
Older kernels lacking onnn,pca9655 in their OF match table might fail to
probe the expander0 GPIO expander, breaking features like USB3 power and
SFP modules.
Would it be safer to provide a fallback list to maintain the device tree
ABI, such as: compatible = "onnn,pca9655", "nxp,pca9555"; ?
[Severity: Low]
Is the onnn,pca9655 compatible string documented in the device tree
bindings?
Running make dtbs_check with schema validation enabled might fail if
this string is not listed in the gpio-pca95xx bindings.
> gpio-controller;
> #gpio-cells = <2>;
> reg = <0x20>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260907005933.230766-1-rosenp@gmail.com?part=1
next prev parent reply other threads:[~2026-09-07 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 0:59 [PATCHv2] ARM: dts: marvell: armada-388: use onnn,pca9655 compatible Rosen Penev
2026-09-07 1:12 ` sashiko-bot [this message]
2026-09-07 1:19 ` Rosen Penev
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 6:04 Rosen Penev
2026-09-08 6:12 ` 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=20260907011244.7EF5B1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--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