From: sashiko-bot@kernel.org
To: "Wei Deng" <wei.deng@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector
Date: Thu, 09 Jul 2026 07:42:58 +0000 [thread overview]
Message-ID: <20260709074259.5FC0A1F00A3E@smtp.kernel.org> (raw)
In-Reply-To: <20260709-fix-hamoa-m2-w-disable2-v1-1-5e725091266a@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unused dummy fixed regulators `vreg_wcn_0p95` and `vreg_wcn_1p9` are left orphaned in the device tree.
--
--- Patch [1]: [PATCH 1/3] arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector ---
commit 3a5c700f021e92c47e3fa3997595501dd58c45d6
Author: Wei Deng <wei.deng@oss.qualcomm.com>
arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector
This commit describes the PCIe M.2 Mechanical Key E connector in the hamoa IoT
EVK device tree, linking it to the PCIe 4 Root Port. It replaces the specific
wcn7850-pmu and static BT nodes with chip-agnostic pwrseq-pcie-m2 driver
endpoints.
> diff --git a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> index 9fa86bb6438ec..41c2004f0ef67 100644
> --- a/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts
[ ... ]
> @@ -676,65 +714,6 @@ usb_1_ss0_sbu_mux: endpoint {
> };
> };
> };
> -
> - wcn7850-pmu {
> - compatible = "qcom,wcn7850-pmu";
> -
> - vdd-supply = <&vreg_wcn_0p95>;
> - vddio-supply = <&vreg_l15b_1p8>;
> - vddaon-supply = <&vreg_wcn_0p95>;
> - vdddig-supply = <&vreg_wcn_0p95>;
> - vddrfa1p2-supply = <&vreg_wcn_1p9>;
> - vddrfa1p8-supply = <&vreg_wcn_1p9>;
[Severity: Low]
Since the wcn7850-pmu node is removed here and the wifi@0 node is removed
below, their consumers are gone.
Should the corresponding fixed regulator definitions for vreg_wcn_0p95 and
vreg_wcn_1p9 also be removed from the device tree?
Leaving them behind might cause the regulator core to needlessly instantiate
these dummy regulators.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-fix-hamoa-m2-w-disable2-v1-0-5e725091266a@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-09 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:29 [PATCH 0/3] power: sequencing: pcie-m2: Enable USB/UART BT coexistence on Hamoa EVK Wei Deng
2026-07-09 7:29 ` [PATCH 1/3] arm64: dts: qcom: hamoa-iot-evk: Describe the PCIe M.2 Key E connector Wei Deng
2026-07-09 7:42 ` sashiko-bot [this message]
2026-07-09 7:44 ` Dmitry Baryshkov
2026-07-09 8:12 ` Wei Deng
2026-07-10 13:50 ` Konrad Dybcio
2026-07-09 7:29 ` [PATCH 2/3] power: sequencing: pcie-m2: Match WCN6855 and WCN7851 UART BT variants by subdevice ID Wei Deng
2026-07-09 7:39 ` sashiko-bot
2026-07-09 7:29 ` [PATCH 3/3] power: sequencing: pcie-m2: Deassert W_DISABLE2# when no UART serdev is created Wei Deng
2026-07-09 7:44 ` sashiko-bot
2026-07-09 7:56 ` Dmitry Baryshkov
2026-07-09 7:46 ` [PATCH 0/3] power: sequencing: pcie-m2: Enable USB/UART BT coexistence on Hamoa EVK Dmitry Baryshkov
2026-07-09 8:12 ` Wei Deng
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=20260709074259.5FC0A1F00A3E@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wei.deng@oss.qualcomm.com \
/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