All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kathiravan Thirumoorthy" <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: ipq9650: add the PCIe support
Date: Tue, 14 Jul 2026 04:54:17 +0000	[thread overview]
Message-ID: <20260714045417.D34441F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714-ipq9650_pcie-v1-1-4197749d06bd@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The `gcc` node is missing the `#interconnect-cells = <1>;` property, which causes interconnect parsing for all PCIe controllers to fail.
--

--- Patch [1]: [PATCH 1/2] arm64: dts: qcom: ipq9650: add the PCIe support ---
commit 568f2d4c0bdec47be174d592deb75c6d379fe4dd
Author: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>

arm64: dts: qcom: ipq9650: add the PCIe support
    
IPQ9650 has 5 Gen3 PCIe controllers - PCIe0 and PCIe4 are single lane
and the remaining instances are dual lane. Add support for the same.

> diff --git a/arch/arm64/boot/dts/qcom/ipq9650.dtsi b/arch/arm64/boot/dts/qcom/ipq9650.dtsi
> index 3d3b317c6a3cc..8301a4090395e 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9650.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq9650.dtsi
[ ... ]
> @@ -216,11 +371,11 @@ gcc: clock-controller@1800000 {
>  			reg = <0x0 0x01800000 0x0 0x40000>;
>  			clocks = <&xo_board>,
>  				 <&sleep_clk>,
> -				 <0>,
> -				 <0>,
> -				 <0>,
> -				 <0>,
> -				 <0>,
> +				 <&pcie0_phy>,
> +				 <&pcie1_phy>,
> +				 <&pcie2_phy>,
> +				 <&pcie3_phy>,
> +				 <&pcie4_phy>,
>  				 <0>,
>  				 <0>;
>  			#clock-cells = <1>;

[Severity: High]
Does this gcc node need an #interconnect-cells = <1>; property?

The new PCIe nodes declare interconnects pointing to the gcc node.

When the PCIe controller driver attempts to acquire these interconnects
during probe via devm_of_icc_get(), the core interconnect code calls
of_parse_phandle_with_args().

If the target gcc node lacks the #interconnect-cells property, parsing
fails and returns -EINVAL. This will cause PCIe initialization to fail
entirely for all 5 controllers.

[ ... ]
> @@ -371,6 +526,506 @@ frame@f42d000 {
[ ... ]
> +		pcie3: pcie@30000000 {
> +			compatible = "qcom,pcie-ipq9650", "qcom,pcie-ipq9574";
[ ... ]
> +			interconnects = <&gcc MASTER_ANOC_PCIE3 &gcc SLAVE_ANOC_PCIE3>,
> +					<&gcc MASTER_CNOC_PCIE3 &gcc SLAVE_CNOC_PCIE3>;
> +			interconnect-names = "pcie-mem", "cpu-pcie";
> +
> +			status = "disabled";

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-ipq9650_pcie-v1-0-4197749d06bd@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-14  4:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  4:29 [PATCH 0/2] Add PCIe support for Qualcomm's IPQ9650 support Kathiravan Thirumoorthy
2026-07-14  4:29 ` [PATCH 1/2] arm64: dts: qcom: ipq9650: add the PCIe support Kathiravan Thirumoorthy
2026-07-14  4:54   ` sashiko-bot [this message]
2026-07-14  4:29 ` [PATCH 2/2] arm64: dts: qcom: ipq9650-rdp488: enable " Kathiravan Thirumoorthy

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=20260714045417.D34441F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@oss.qualcomm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.