Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gopikrishna Garmidi" <gopikrishna.garmidi@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/5] arm64: dts: qcom: Add Kalambo CRD
Date: Mon, 27 Jul 2026 12:59:16 +0000	[thread overview]
Message-ID: <20260727125916.AF1BF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727-b4-kalambo-crd-v3-3-25280faceece@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch leaves an orphaned PMIC endpoint and thermal zone by failing to delete the `spmi_bus1` node for PMIC D (`pmcx0102_d_e1`) and its associated thermal zone (`pmcx0102-d1-thermal`).
--

--- Patch [3]: [PATCH v3 3/5] arm64: dts: qcom: Add Kalambo CRD ---
commit 827c0ef9079fd542521c1496e341a245697bd21d
Author: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>

arm64: dts: qcom: Add Kalambo CRD
    
Introduce support for the CRD based on the Qualcomm Kalambo SoC, which is
pin-to-pin compatible with the Glymur CRD. The board description reuses the
common CRD layout and drops PMIC nodes that are not present on this design.

> diff --git a/arch/arm64/boot/dts/qcom/kalambo-crd.dts b/arch/arm64/boot/dts/qcom/kalambo-crd.dts
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/kalambo-crd.dts

[ ... ]

> +/delete-node/ &pmcx0102_d_e0;
> +/delete-node/ &pmcx0102_d0_thermal;

[Severity: Medium]
Should this also delete the e1 endpoint and d1 thermal zone for PMIC D?

The commit message notes that absent PMIC nodes are dropped, and PMIC D
is absent here. Since PMIC D spans both spmi_bus0 (e0) and spmi_bus1 (e1),
deleting only the e0 endpoint leaves the e1 endpoint active.

Will the SPMI driver attempt to probe the non-existent pmcx0102_d_e1 node
and generate bus timeouts or errors during boot? It appears that the
associated pmcx0102-d1-thermal zone may also need to be deleted (perhaps by
its full path if it lacks a label) to fully remove PMIC D from the tree.

> +/delete-node/ &pmh0104_i_e0;
> +/delete-node/ &pmh0104_i0_thermal;
> +/delete-node/ &pmh0104_j_e0;
> +/delete-node/ &pmh0104_j0_thermal;
> +
> +/ {
> +	model = "Qualcomm Technologies, Inc. Kalambo CRD";
> +	compatible = "qcom,kalambo-crd", "qcom,kalambo";
> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-b4-kalambo-crd-v3-0-25280faceece@oss.qualcomm.com?part=3

  reply	other threads:[~2026-07-27 12:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 12:51 [PATCH v3 0/5] arm64: dts: qcom: Add Kalambo SoC and CRD Gopikrishna Garmidi
2026-07-27 12:51 ` [PATCH v3 1/5] dt-bindings: arm: qcom: Document Kalambo SoC and board Gopikrishna Garmidi
2026-07-27 12:51 ` [PATCH v3 2/5] arm64: dts: qcom: Add Kalambo SoC Gopikrishna Garmidi
2026-07-27 13:06   ` sashiko-bot
2026-07-27 13:40   ` Konrad Dybcio
2026-07-27 13:58   ` Abel Vesa
2026-07-27 12:51 ` [PATCH v3 3/5] arm64: dts: qcom: Add Kalambo CRD Gopikrishna Garmidi
2026-07-27 12:59   ` sashiko-bot [this message]
2026-07-27 13:58   ` Abel Vesa
2026-07-27 12:51 ` [PATCH v3 4/5] firmware: qcom: scm: Allow QSEECOM on " Gopikrishna Garmidi
2026-07-27 12:51 ` [PATCH v3 5/5] soc: qcom: ubwc: Add Kalambo UBWC config Gopikrishna Garmidi

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=20260727125916.AF1BF1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gopikrishna.garmidi@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