From: sashiko-bot@kernel.org
To: "Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 18/18] arm64: dts: qcom: kodiak: Fix PCIe WAKE# GPIO polarity
Date: Thu, 17 Sep 2026 12:06:29 +0000 [thread overview]
Message-ID: <20260917120629.A67FD1F00899@smtp.kernel.org> (raw)
In-Reply-To: <20260917-root_port-v2-18-0d627d0856d5@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: undocumented addition of wake-gpios property to pcie1_port0
--
commit 6e97f1471613f8cea666aa46eb12ba3627dc0138
Author: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
arm64: dts: qcom: kodiak: Fix PCIe WAKE# GPIO polarity
This commit updates the polarity of the PCIe WAKE# GPIO across several
Qualcomm device trees to match the active-low requirement defined in the
PCIe Base Specification.
> diff --git a/arch/arm64/boot/dts/qcom/qcm6490-particle-tachyon.dts b/arch/arm64/boot/dts/qcom/qcm6490-particle-tachyon.dts
> index 5bb33a8a98304..509fc4941a029 100644
> --- a/arch/arm64/boot/dts/qcom/qcm6490-particle-tachyon.dts
> +++ b/arch/arm64/boot/dts/qcom/qcm6490-particle-tachyon.dts
[ ... ]
> @@ -579,6 +579,7 @@ &pcie1_phy {
>
> &pcie1_port0 {
> reset-gpios = <&tlmm 2 GPIO_ACTIVE_LOW>;
> + wake-gpios = <&tlmm 3 GPIO_ACTIVE_LOW>;
> };
[Severity: Medium]
The commit message states the intent is to fix the polarity of existing
wake-gpios properties by changing GPIO_ACTIVE_HIGH to GPIO_ACTIVE_LOW.
However, for &pcie1_port0 in this file, the wake-gpios property did not
exist previously and is being newly added.
Is this an accidental inclusion, or should the commit message be updated
to clarify that wake functionality is also being added for pcie1_port0
on this board?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917-root_port-v2-0-0d627d0856d5@oss.qualcomm.com?part=18
next prev parent reply other threads:[~2026-09-17 12:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:54 [PATCH v2 00/18] arm64: dts: qcom: Fix wake-gpios polarity Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 01/18] ARM: dts: qcom: sdx55: Fix PCIe WAKE# GPIO polarity Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 02/18] arm64: dts: qcom: msm8996: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 03/18] arm64: dts: qcom: sdm845: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 04/18] arm64: dts: qcom: sc8180x: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 05/18] arm64: dts: qcom: sm8150: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 06/18] arm64: dts: qcom: sm8250: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 07/18] arm64: dts: qcom: sm8350: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 08/18] arm64: dts: qcom: sm8450: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 09/18] arm64: dts: qcom: sm8550: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 10/18] arm64: dts: qcom: sm8650: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 11/18] arm64: dts: qcom: sm8750: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 12/18] arm64: dts: qcom: kaanapali: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 13/18] arm64: dts: qcom: sar2130p: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 14/18] arm64: dts: qcom: monaco: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 15/18] arm64: dts: qcom: lemans: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 16/18] arm64: dts: qcom: talos: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 17/18] arm64: dts: qcom: sa8540p-ride: " Krishna Chaitanya Chundru
2026-09-17 11:54 ` [PATCH v2 18/18] arm64: dts: qcom: kodiak: " Krishna Chaitanya Chundru
2026-09-17 12:06 ` sashiko-bot [this message]
2026-09-29 3:14 ` (subset) [PATCH v2 00/18] arm64: dts: qcom: Fix wake-gpios polarity Bjorn Andersson
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=20260917120629.A67FD1F00899@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