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

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Removing `vpcie-supply` from the host controller node breaks DT backward compatibility, as older kernels will fail to enable the regulator and initialize PCIe.
- [Low] Adding `vpcie3v3-supply` to the Root Port node without updating the corresponding binding schema causes `dtbs_check` validation failures.
--

commit 9019771c92c02473e9f2657166c7dc76a65b606d
Author: Sherry Sun <sherry.sun@nxp.com>

arm: dts: imx6sx-sdb: Move power supply property to Root Port node

Move the power supply property from the PCIe controller node to the Root
Port child node to support the new PCI pwrctrl framework.

> diff --git a/arch/arm/boot/dts/nxp/imx/imx6sx-sdb.dtsi b/arch/arm/boot/dts/nxp/imx/imx6sx-sdb.dtsi
> index 338de4d144b2a..41a69fe83be85 100644
> --- a/arch/arm/boot/dts/nxp/imx/imx6sx-sdb.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/imx6sx-sdb.dtsi
> @@ -284,12 +284,12 @@ &pcie {
>  	pinctrl-0 = <&pinctrl_pcie>;
>  	/* This property is deprecated, use reset-gpios from the Root Port node. */
>  	reset-gpio = <&gpio2 0 GPIO_ACTIVE_LOW>;
> -	vpcie-supply = <&reg_pcie_gpio>;

[Severity: High]
Does removing this property break device tree backward compatibility for
older kernels?

Older kernels using the pci-imx6.c driver expect the vpcie-supply property
in the host controller node to find and enable the regulator. If this is
removed instead of being left as a deprecated fallback (similar to the
reset-gpio property above), will PCIe initialization fail on older kernels
booted with this new device tree?

>  	status = "okay";
>  };
>  
>  &pcie_port0 {
>  	reset-gpios = <&gpio2 0 GPIO_ACTIVE_LOW>;
> +	vpcie3v3-supply = <&reg_pcie_gpio>;

[Severity: Low]
Does adding this property to the Root Port node without a corresponding
schema update cause dtbs_check validation failures?

The fsl,imx6q-pcie.yaml binding schema defines the root port node with
unevaluatedProperties: false, but it does not appear to document the newly
added vpcie3v3-supply property.

[ ... ]

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

  reply	other threads:[~2026-06-30  6:25 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 [this message]
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
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=20260630062509.B01751F000E9@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