Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jun Yan" <jerrysteve1101@gmail.com>
Cc: linux-amlogic@lists.infradead.org, neil.armstrong@linaro.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: amlogic: meson-axg: Disable pcie_phy node by default
Date: Wed, 17 Jun 2026 07:25:52 +0000	[thread overview]
Message-ID: <20260617072552.C0A441F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260617071604.635627-4-jerrysteve1101@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] The S400 board fails to enable the underlying `mipi_pcie_analog_dphy` required by `pcie_phy`, leaving PCIe broken and the deferred probe warning unresolved on this board.
--

commit 8447bc6097444b6a9914b09671ffb788547cd0fd
Author: Jun Yan <jerrysteve1101@gmail.com>

arm64: dts: amlogic: meson-axg: Disable pcie_phy node by default
    
This commit disables the pcie_phy node by default in the meson-axg base
devicetree to suppress a deferred probe warning on boards that do not use it.

> diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
> --- a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
[ ... ]
> @@ -328,6 +328,7 @@ pcie_phy: phy@ff644000 {
>  			phys = <&mipi_pcie_analog_dphy>;
>  			phy-names = "analog";
>  			#phy-cells = <0>;
> +			status = "disabled";
>  		};

[Severity: High]
This isn't a bug introduced by this patch, but does the S400 board fail to
enable the underlying mipi_pcie_analog_dphy required by pcie_phy?

Looking at arch/arm64/boot/dts/amlogic/meson-axg-s400.dts, the pcie_phy is
enabled:

&pcie_phy {
	status = "okay";
};

However, the analog PHY it depends on (mipi_pcie_analog_dphy) is disabled by
default in arch/arm64/boot/dts/amlogic/meson-axg.dtsi:

mipi_pcie_analog_dphy: phy {
	compatible = "amlogic,axg-mipi-pcie-analog-phy";
	#phy-cells = <0>;
	status = "disabled";
};

Since mipi_pcie_analog_dphy is never set to "okay" in the s400 board file,
won't pcie_phy continue to indefinitely defer its probe waiting for the
analog PHY, leaving PCIe broken on the S400 board?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260617071604.635627-1-jerrysteve1101@gmail.com?part=3

  reply	other threads:[~2026-06-17  7:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17  7:15 [PATCH v2 0/4] arm64: dts: amlogic: meson-axg: NAND fix and PCIe PHY adjustment Jun Yan
2026-06-17  7:15 ` [PATCH v2 1/4] arm64: dts: amlogic: meson-axg: Disable nfc node by default Jun Yan
2026-06-17  7:15 ` [PATCH v2 2/4] arm64: dts: amlogic: meson-axg: Add missing nand_rb0 pin to nand_all_pins Jun Yan
2026-06-17  7:15 ` [PATCH v2 3/4] arm64: dts: amlogic: meson-axg: Disable pcie_phy node by default Jun Yan
2026-06-17  7:25   ` sashiko-bot [this message]
2026-06-17  7:15 ` [PATCH v2 4/4] arm64: dts: amlogic: meson-axg-s400: Enable pcie_phy Jun Yan
2026-06-17  7:27   ` sashiko-bot
2026-06-17  7:30   ` Neil Armstrong
2026-06-17  8:15     ` Jun Yan

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=20260617072552.C0A441F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jerrysteve1101@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=neil.armstrong@linaro.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