From: sashiko-bot@kernel.org
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 05/18] arm64: dts: qcom: sm8150: Fix PCIe wake GPIO polarity
Date: Thu, 21 May 2026 13:42:49 +0000 [thread overview]
Message-ID: <20260521134250.137A21F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260521-wake-v1-5-d822567be258@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The dt-binding examples for Qualcomm PCIe controllers are not updated to reflect the `wake-gpios` polarity change.
--
commit ceea67812f2db3dd214265d1322e7b8e9c36e293
Author: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
arm64: dts: qcom: sm8150: Fix PCIe wake GPIO polarity
The PCIe WAKE# signal is active-low as defined in the PCIe Base
Specification. Fix the wake-gpios polarity by using GPIO_ACTIVE_LOW
instead of GPIO_ACTIVE_HIGH.
> diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> index 0e101096209ab..8da494de4308a 100644
> --- a/arch/arm64/boot/dts/qcom/sm8150.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8150.dtsi
> @@ -1905,7 +1905,7 @@ pcie0: pcie@1c00000 {
> phy-names = "pciephy";
>
> perst-gpios = <&tlmm 35 GPIO_ACTIVE_HIGH>;
> - wake-gpios = <&tlmm 37 GPIO_ACTIVE_HIGH>;
> + wake-gpios = <&tlmm 37 GPIO_ACTIVE_LOW>;
[Severity: Low]
Should the dt-binding example for this controller be updated to reflect the
polarity change?
The example in Documentation/devicetree/bindings/pci/qcom,pcie-sm8150.yaml
still instructs developers to use GPIO_ACTIVE_HIGH for wake-gpios. Leaving
the documentation with the old polarity risks propagating the incorrect
configuration to new board designs.
>
> pinctrl-names = "default";
> pinctrl-0 = <&pcie0_default_state>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260521-wake-v1-0-d822567be258@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-05-21 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:06 [PATCH 00/18] arm64: dts: qcom: Fix PCIe wake GPIO polarity Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 01/18] ARM: dts: qcom: sdx55: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 02/18] arm64: dts: qcom: msm8996: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 03/18] arm64: dts: qcom: sdm845: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 04/18] arm64: dts: qcom: sc8180x: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 05/18] arm64: dts: qcom: sm8150: " Krishna Chaitanya Chundru
2026-05-21 13:42 ` sashiko-bot [this message]
2026-05-21 13:06 ` [PATCH 06/18] arm64: dts: qcom: sm8250: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 07/18] arm64: dts: qcom: sm8350: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 08/18] arm64: dts: qcom: sm8450: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 09/18] arm64: dts: qcom: sm8550: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 10/18] arm64: dts: qcom: sm8650: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 11/18] arm64: dts: qcom: sm8750: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 12/18] arm64: dts: qcom: kaanapali: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 13/18] arm64: dts: qcom: sar2130p: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 14/18] arm64: dts: qcom: monaco: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 15/18] arm64: dts: qcom: lemans: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 16/18] arm64: dts: qcom: sa8540p-ride: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 17/18] arm64: dts: qcom: kodiak: " Krishna Chaitanya Chundru
2026-05-21 13:06 ` [PATCH 18/18] arm64: dts: qcom: talos: " Krishna Chaitanya Chundru
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=20260521134250.137A21F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krishna.chundru@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