Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: robh@kernel.org, devicetree@vger.kernel.org, Frank.Li@kernel.org,
	conor+dt@kernel.org, linux-pci@vger.kernel.org,
	imx@lists.linux.dev
Subject: Re: [PATCH V5 7/7] arm64: dts: imx95: Move power supply properties to Root Port node
Date: Wed, 01 Jul 2026 11:06:59 +0000	[thread overview]
Message-ID: <20260701110700.5E1B81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260701105234.198987-8-sherry.sun@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The transition to the new PCI pwrctrl framework is incomplete across the i.MX95 platform. Several other i.MX95 board definitions were omitted from this migration and still retain the legacy `vpcie-supply` property in the host controller node instead of moving them to the Root Port child nodes.
--

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

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

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

> Move the power supply properties from the PCIe controller nodes to the
> Root Port child nodes to support the new PCI pwrctrl framework.
> 
> Since i.MX95 is the new platform that under development phase, it should
> be fine to simply move the power supply properties.

[Severity: Low]
Are there other i.MX95 boards that should be included in this migration?

The transition to the new PCI pwrctrl framework appears incomplete across the
i.MX95 platform. Several other i.MX95 board definitions were omitted from this
migration and still retain the legacy vpcie-supply property in the host
controller node instead of moving them to the Root Port child nodes.

For example, arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts retains the
legacy power supply property in the host controller node:

&pcie0 {
    ...
    vpcie-supply = <&reg_m2_mkey_pwr>;
    ...
};

Similar omissions appear in arch/arm64/boot/dts/freescale/imx95-19x19-frdm-pro.dts:

&pcie0 {
    ...
    vpcie-supply = <&reg_m2_mkey_1_pwr>;
    ...
};

And in arch/arm64/boot/dts/freescale/imx95-19x19-verdin-evk.dts:

&pcie0 {
    ...
    vpcie-supply = <&reg_pcie0>;
    ...
};

Should these boards also be updated to ensure consistent power management
behavior across the i.MX95 platform and allow future cleanup of the legacy
code?

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

      reply	other threads:[~2026-07-01 11:07 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
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 [this message]

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=20260701110700.5E1B81F000E9@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