Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: conor+dt@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
	linux-pci@vger.kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH V4 7/7] arm64: dts: imx95: Move power supply properties to Root Port node
Date: Tue, 30 Jun 2026 06:23:47 +0000	[thread overview]
Message-ID: <20260630062347.7FE471F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630060710.3294811-8-sherry.sun@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing legacy power supply properties from the PCIe controller nodes breaks backwards compatibility for older kernels booting with the updated Device Tree.
--

commit 332f451afbc5374b9f81acdbad51ee15f1b90088
Author: Sherry Sun <sherry.sun@nxp.com>

arm64: dts: imx95: Move power supply properties to Root Port node

This commit moves power supply properties from the PCIe controller nodes to
the Root Port child nodes. This change is made to support the new PCI
pwrctrl framework.

> diff --git a/arch/arm64/boot/dts/freescale/imx95-15x15-evk.dts b/arch/arm64/boot/dts/freescale/imx95-15x15-evk.dts
> index 7d820a0f80b22..6aedcbbe915a5 100644
> --- a/arch/arm64/boot/dts/freescale/imx95-15x15-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx95-15x15-evk.dts
> @@ -555,8 +555,6 @@ &pcie0 {
>  	pinctrl-names = "default";
>  	/* This property is deprecated, use reset-gpios from the Root Port node. */
>  	reset-gpio = <&gpio5 13 GPIO_ACTIVE_LOW>;
> -	vpcie-supply = <&reg_m2_pwr>;
> -	vpcie3v3aux-supply = <&reg_m2_pwr>;

[Severity: High]
Does removing these legacy power supply properties break backwards
compatibility for older kernels booting with this updated Device Tree?

Since older kernels lack the pwrctrl framework to handle the new Root Port
properties, they rely on finding vpcie-supply and vpcie3v3aux-supply in the
PCIe host node. Without them, the legacy pci-imx6 driver silently skips
enabling the power regulators, and PCIe initialization will fail because the
slot remains unpowered.

The reset-gpio property was intentionally left to preserve backward
compatibility, but removing the power supplies appears to defeat that
effort. Keeping the legacy regulator properties (even if marked as
deprecated) should be safe, as the kernel regulator framework uses reference
counting and allows both the legacy driver and the new pwrctrl framework to
concurrently enable the same regulator without conflict.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260630060710.3294811-1-sherry.sun@oss.nxp.com?part=7

  reply	other threads:[~2026-06-30  6:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  6:07 [PATCH V4 0/7] PCI: imx6: Integrate pwrctrl API and update device trees Sherry Sun (OSS)
2026-06-30  6:07 ` [PATCH V4 1/7] arm: dts: imx6qdl-sabresd: Move power supply property to Root Port node Sherry Sun (OSS)
2026-06-30  6:27   ` sashiko-bot
2026-06-30  8:29     ` Sherry Sun
2026-06-30  6:07 ` [PATCH V4 2/7] arm: dts: imx6sx-sdb: " Sherry Sun (OSS)
2026-06-30  6:25   ` sashiko-bot
2026-06-30  8:29     ` Sherry Sun
2026-06-30  6:07 ` [PATCH V4 3/7] arm64: dts: imx8mm-evk: " Sherry Sun (OSS)
2026-06-30  6:12   ` sashiko-bot
2026-06-30  6:07 ` [PATCH V4 4/7] arm64: dts: imx8mp-evk: Move power supply properties " Sherry Sun (OSS)
2026-06-30  6:19   ` sashiko-bot
2026-06-30  8:34     ` Sherry Sun
2026-06-30  6:07 ` [PATCH V4 5/7] arm64: dts: imx8mq-evk: " Sherry Sun (OSS)
2026-06-30  6:20   ` sashiko-bot
2026-06-30  8:40     ` Sherry Sun
2026-06-30  6:07 ` [PATCH V4 6/7] arm64: dts: imx8dxl/qm/qxp: " Sherry Sun (OSS)
2026-06-30  6:24   ` sashiko-bot
2026-06-30  8:38     ` Sherry Sun
2026-06-30  6:07 ` [PATCH V4 7/7] arm64: dts: imx95: " Sherry Sun (OSS)
2026-06-30  6:23   ` sashiko-bot [this message]
2026-06-30  8:44     ` Sherry Sun
2026-06-30 15:31 ` [PATCH V4 0/7] PCI: imx6: Integrate pwrctrl API and update device trees Frank.Li
2026-06-30 15:52   ` Frank Li
2026-07-01  8:44     ` 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=20260630062347.7FE471F000E9@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