From: sashiko-bot@kernel.org
To: "Gopikrishna Garmidi" <gopikrishna.garmidi@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/5] arm64: dts: qcom: Add Kalambo SoC
Date: Mon, 27 Jul 2026 13:06:22 +0000 [thread overview]
Message-ID: <20260727130622.B5FA81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727-b4-kalambo-crd-v3-2-25280faceece@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Missing deletion of hardware blocks and thermal zones specific to the removed CPU cluster 0 (e.g., `bwmon_cluster0`, thermal zones), leading to a fatal SError and spurious thermal shutdowns.
--
--- Patch [2]: [PATCH v3 2/5] arm64: dts: qcom: Add Kalambo SoC ---
commit d6b5f610923793ce8197e8297bbc2ded9a915289
Author: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
arm64: dts: qcom: Add Kalambo SoC
This commit introduces support for the Qualcomm Kalambo SoC, which is
derived from Mahua but has CPU cluster 0 removed. It reassigns the surviving
cluster as cluster0 in the cpu-map and overrides memory offsets for imem.
> diff --git a/arch/arm64/boot/dts/qcom/kalambo.dtsi b/arch/arm64/boot/dts/qcom/kalambo.dtsi
> new file mode 100644
> index 0000000000000..4a68115a4286a
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/kalambo.dtsi
> @@ -0,0 +1,97 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> + */
> +
> +#include "mahua.dtsi"
> +
> +/delete-node/ &cluster0_pd;
> +/delete-node/ &cpu_map;
> +/delete-node/ &cpu0;
[Severity: High]
Does this also need to delete the associated bwmon_cluster0 node and the
cluster 0 thermal zones (like cpu-0-0-0-thermal and qmx-0-0-thermal)?
Because bwmon_cluster0 lacks a power domain dependency in the base device
tree, the icc-bwmon driver might unconditionally probe it. On Qualcomm SoCs,
attempting to map and access the MMIO registers of a physically removed
hardware block typically triggers a bus timeout and a fatal asynchronous
SError during boot.
Additionally, will leaving the cluster 0 thermal zones active cause them to
poll non-existent tsens sensors? If so, this could return garbage maximum
values and trigger an immediate emergency thermal shutdown.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727-b4-kalambo-crd-v3-0-25280faceece@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-27 13:06 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 [this message]
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
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=20260727130622.B5FA81F000E9@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