From: sashiko-bot@kernel.org
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org, Frank.Li@kernel.org, robh@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH V5 1/7] arm: dts: imx6qdl-sabresd: Add power supply property to Root Port node
Date: Wed, 01 Jul 2026 11:04:21 +0000 [thread overview]
Message-ID: <20260701110422.438D01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260701105234.198987-2-sherry.sun@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Missing error check for pwrseq_power_on() in slot_pwrctrl_power_on() leads to potential kernel panic.
--
commit 4b51e513820a111cd03554e7f701a9ce808be27b
Author: Sherry Sun <sherry.sun@nxp.com>
arm: dts: imx6qdl-sabresd: Add power supply property to Root Port node
This commit adds the power supply property to the Root Port child node to
support the new PCI pwrctrl framework. The legacy power supply property is
retained for backward compatibility.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
> index fe9046c03ddd6..60fe0f973668b 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
> @@ -756,12 +756,14 @@ &pcie {
> pinctrl-0 = <&pinctrl_pcie>;
> /* This property is deprecated, use reset-gpios from the Root Port node. */
> reset-gpio = <&gpio7 12 GPIO_ACTIVE_LOW>;
> + /* This property is deprecated, use power supply from the Root Port node. */
> vpcie-supply = <®_pcie>;
> status = "okay";
> };
>
> &pcie_port0 {
> reset-gpios = <&gpio7 12 GPIO_ACTIVE_LOW>;
> + vpcie3v3-supply = <®_pcie>;
[Severity: High]
This is a pre-existing issue, but does enabling the pwrctrl framework here
expose a regression where error checks are missing in the core code?
Looking at drivers/pci/pwrctrl/generic.c:slot_pwrctrl_power_on(), it drops
the error code from pwrseq_power_on() and unconditionally returns 0:
drivers/pci/pwrctrl/generic.c:slot_pwrctrl_power_on() {
...
if (slot->pwrseq) {
pwrseq_power_on(slot->pwrseq);
return 0;
}
...
}
If the power sequencer fails to power on the slot, the PCI subsystem is
falsely notified that the slot is ready. The PCI core will then enumerate
the bus and attempt to access the configuration space of the unpowered
device.
On ARM/ARM64 platforms, couldn't accessing unpowered PCIe registers result
in a synchronous external abort (SError) and an immediate kernel panic?
> };
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701105234.198987-1-sherry.sun@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-07-01 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 10:52 [PATCH V5 0/7]PCI: imx6: Integrate pwrctrl API and update device trees Sherry Sun (OSS)
2026-07-01 10:52 ` [PATCH V5 1/7] arm: dts: imx6qdl-sabresd: Add power supply property to Root Port node Sherry Sun (OSS)
2026-07-01 11:04 ` sashiko-bot [this message]
2026-07-01 10:52 ` [PATCH V5 2/7] arm: dts: imx6sx-sdb: " Sherry Sun (OSS)
2026-07-01 11:10 ` sashiko-bot
2026-07-01 10:52 ` [PATCH V5 3/7] arm64: dts: imx8mm-evk: " Sherry Sun (OSS)
2026-07-01 10:56 ` sashiko-bot
2026-07-01 10:52 ` [PATCH V5 4/7] arm64: dts: imx8mp-evk: Add power supply properties " Sherry Sun (OSS)
2026-07-01 11:02 ` sashiko-bot
2026-07-01 10:52 ` [PATCH V5 5/7] arm64: dts: imx8mq-evk: " Sherry Sun (OSS)
2026-07-01 11:01 ` sashiko-bot
2026-07-01 10:52 ` [PATCH V5 6/7] arm64: dts: imx8dxl/qm/qxp: " Sherry Sun (OSS)
2026-07-01 10:57 ` sashiko-bot
2026-07-01 10:52 ` [PATCH V5 7/7] arm64: dts: imx95: Move " Sherry Sun (OSS)
2026-07-01 11:06 ` 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=20260701110422.438D01F000E9@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=linux-pci@vger.kernel.org \
--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