From: sashiko-bot@kernel.org
To: hongxing.zhu@oss.nxp.com
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
Frank.Li@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v1] arm64: dts: imx94: Add Root Port node and PERST property
Date: Thu, 04 Jun 2026 02:31:16 +0000 [thread overview]
Message-ID: <20260604023116.6AA981F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260604022420.120294-1-hongxing.zhu@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added Root Port PERST# properties incorrectly use `reset-gpio` instead of `reset-gpios`, causing the PCI core to silently ignore them, violating DT schema, and falling back to the deprecated legacy binding.
--
commit 10fdcd113cd4d5825e1430558167b9577d3cf633
Author: Richard Zhu <hongxing.zhu@oss.nxp.com>
arm64: dts: imx94: Add Root Port node and PERST property
This commit adds Root Port nodes to the i.MX943 PCIe controllers and attempts
to migrate the PERST reset property from the host bridge to these new Root
Port nodes.
> diff --git a/arch/arm64/boot/dts/freescale/imx943-evk.dts b/arch/arm64/boot/dts/freescale/imx943-evk.dts
> index 7cfd424689507..ed3abd3e76e56 100644
> --- a/arch/arm64/boot/dts/freescale/imx943-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx943-evk.dts
> @@ -1034,12 +1034,17 @@ &pcie0 {
[ ... ]
> + /* This property is deprecated, use reset-gpios from the Root Port node. */
> reset-gpio = <&pcal6416_i2c3_u46 3 GPIO_ACTIVE_LOW>;
> vpcie3v3aux-supply = <®_m2_wlan>;
> supports-clkreq;
> status = "okay";
> };
>
> +&pcie0_port0 {
> + reset-gpio = <&pcal6416_i2c3_u46 3 GPIO_ACTIVE_LOW>;
> +};
[Severity: Medium]
The commit message mentions adding the reset-gpios property, but is it
intended to use reset-gpio here instead?
The Linux PCI core function pci_host_common_parse_perst() explicitly parses
the Root Port's reset GPIO using of_property_present(np, "reset-gpios"),
which strictly checks for the plural form.
Because of this typo, will the Root Port's PERST GPIO be ignored, causing
the driver to fall back to imx_pcie_parse_legacy_binding() to parse the
deprecated legacy property left on the Host Bridge node? This appears to
defeat the migration effort and violate the PCI bus DT schema.
>
> &pcie0_ep {
[ ... ]
> @@ -1058,12 +1063,17 @@ &pcie1 {
[ ... ]
> + /* This property is deprecated, use reset-gpios from the Root Port node. */
> reset-gpio = <&pcal6416_i2c3_u46 1 GPIO_ACTIVE_LOW>;
> vpcie3v3aux-supply = <®_slot_pwr>;
> supports-clkreq;
> status = "okay";
> };
>
> +&pcie1_port0 {
> + reset-gpio = <&pcal6416_i2c3_u46 1 GPIO_ACTIVE_LOW>;
> +};
[Severity: Medium]
Does this also suffer from the same typo as the pcie0_port0 node?
Using reset-gpio instead of reset-gpios will likely cause this property
to be similarly ignored by the PCI core's Root Port parser.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260604022420.120294-1-hongxing.zhu@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-06-04 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 2:24 [PATCH v1] arm64: dts: imx94: Add Root Port node and PERST property hongxing.zhu
2026-06-04 2:31 ` sashiko-bot [this message]
2026-06-04 3:32 ` Sherry Sun
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=20260604023116.6AA981F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hongxing.zhu@oss.nxp.com \
--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