Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kathiravan Thirumoorthy" <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: qcom: ipq9574: enable the PCIe support on RDP454
Date: Tue, 14 Jul 2026 05:01:33 +0000	[thread overview]
Message-ID: <20260714050133.D84BC1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260714-pcie_move_to_new_binding-v1-5-6bb25887a0dc@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Mismatched and unsafe default bias for the active-low PERST# (reset) pin on PCIe0, causing premature reset de-assertion.
--

--- Patch [5]: [PATCH 5/5] arm64: dts: qcom: ipq9574: enable the PCIe support on RDP454 ---
commit 52495aceaf771805ada229c324028601d793b505
Author: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>

arm64: dts: qcom: ipq9574: enable the PCIe support on RDP454

This commit enables the PCIe0 and PCIe2 instances on the IPQ9574 RDP454
board to connect QCN92xx Wi-Fi cards.

> diff --git a/arch/arm64/boot/dts/qcom/ipq9574-rdp454.dts b/arch/arm64/boot/dts/qcom/ipq9574-rdp454.dts
> index f2334b9e0ed49..146422aede7db 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574-rdp454.dts
> +++ b/arch/arm64/boot/dts/qcom/ipq9574-rdp454.dts

[ ... ]

> +	pcie0_default: pcie0-default-state {
> +		clkreq-n-pins {
> +			pins = "gpio22";
> +			function = "pcie0_clk";
> +			drive-strength = <6>;
> +			bias-pull-up;
> +		};
> +
> +		perst-n-pins {
> +			pins = "gpio23";
> +			function = "gpio";
> +			drive-strength = <8>;
> +			bias-pull-up;
                        ^^^^^^^^^^^^

[Severity: Medium]
Will this prematurely de-assert the reset for the QCN92xx Wi-Fi endpoint?

Because reset-gpios is active-low, configuring the default state with
bias-pull-up pulls the PERST# pin high before the PCIe host driver probes.
This can violate PCIe timing requirements if power and clocks are still
stabilizing, potentially causing link training failures or device
unresponsiveness.

Is it intentional that pcie0_default uses bias-pull-up here, while
pcie2_default correctly uses bias-pull-down for its perst-n-pins?

> +		};
> +
> +		wake-n-pins {
> +			pins = "gpio24";
> +			function = "pcie0_wake";
> +			drive-strength = <6>;
> +			bias-pull-up;
> +		};
> +	};
> +
> +	pcie2_default: pcie2-default-state {

[ ... ]

> +		perst-n-pins {
> +			pins = "gpio29";
> +			function = "gpio";
> +			drive-strength = <8>;
> +			bias-pull-down;
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-pcie_move_to_new_binding-v1-0-6bb25887a0dc@oss.qualcomm.com?part=5

      reply	other threads:[~2026-07-14  5:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  4:41 [PATCH 0/5] Switch PCIe node to new style of bindings for Qualcomm IPQ SoCs Kathiravan Thirumoorthy
2026-07-14  4:41 ` [PATCH 1/5] arm64: dts: qcom: ipq8074: move PCIe phys and PERST# to port node Kathiravan Thirumoorthy
2026-07-14  4:41 ` [PATCH 2/5] arm64: dts: qcom: ipq6018: move PCIe phys " Kathiravan Thirumoorthy
2026-07-14  4:41 ` [PATCH 3/5] arm64: dts: qcom: ipq5018: move PCIe phys and PERST# " Kathiravan Thirumoorthy
2026-07-14  4:41 ` [PATCH 4/5] arm64: dts: qcom: ipq9574: Add PCIe bridge node Kathiravan Thirumoorthy
2026-07-14  4:41 ` [PATCH 5/5] arm64: dts: qcom: ipq9574: enable the PCIe support on RDP454 Kathiravan Thirumoorthy
2026-07-14  5:01   ` 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=20260714050133.D84BC1F00A3A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox