Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kathiravan Thirumoorthy" <kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom,ids: add few more SOC IDs for IPQ5210 family
Date: Mon, 21 Sep 2026 07:00:15 +0000	[thread overview]
Message-ID: <20260921070015.D0D851F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921-ipq52xx_new_ids-v1-1-63d68a11bbff@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] cpufreq: qcom: kernel panic on boot due to missing SoC IDs in switch case
--

commit 0b99a8e575edc333a621cdaa6e2499570c73a001
Author: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>

dt-bindings: arm: qcom,ids: add few more SOC IDs for IPQ5210 family

QCF3211 and IPQ5211 are the new SoCs based on the IPQ5210 family. Add
the SoC IDs for the same.

> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
> index b63e4a0b8e545..f251d4c75612c 100644
> --- a/include/dt-bindings/arm/qcom,ids.h
> +++ b/include/dt-bindings/arm/qcom,ids.h
> @@ -317,6 +317,8 @@
>  #define QCOM_ID_IPQ9630			779
>  #define QCOM_ID_IPQ9640			780
>  #define QCOM_ID_IPQ9670			781
> +#define QCOM_ID_QCF3211			801
> +#define QCOM_ID_IPQ5211			802

[Severity: High]
Will adding these new SoC IDs cause a kernel panic during boot when using the
qcom-cpufreq-nvmem driver?

Because these new SoCs are based on the IPQ5210 family, they will likely match
the fallback compatible string in the device tree and load the driver.

During probe, the driver reads the actual SoC ID from SMEM, but these new IDs
are currently missing from the switch statement:

drivers/cpufreq/qcom-cpufreq-nvmem.c:qcom_cpufreq_kryo_name_version() {
    ...
	ret = qcom_smem_get_soc_id(&msm_id);
    ...
	switch (msm_id) {
    ...
	case QCOM_ID_IPQ5200:
	case QCOM_ID_IPQ5210:
	case QCOM_ID_QCF2200:
	case QCOM_ID_QCF3200:
	case QCOM_ID_QCF3210:
		drv->versions = (*speedbin == 0xcd) ? BIT(1) : BIT(0);
		break;
    ...
	default:
		BUG();
		break;
	}
    ...
}

Because QCOM_ID_QCF3211 and QCOM_ID_IPQ5211 are unhandled, execution will fall
through to the default case, triggering an unconditional BUG() and bringing
down the system during boot.

Should these new IDs be added to the IPQ5210 case block in the driver to
prevent the crash?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260921-ipq52xx_new_ids-v1-0-63d68a11bbff@oss.qualcomm.com?part=1

  reply	other threads:[~2026-09-21  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  6:51 [PATCH 0/2] Add few more SOC IDs for IPQ5210 family Kathiravan Thirumoorthy
2026-09-21  6:51 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: add " Kathiravan Thirumoorthy
2026-09-21  7:00   ` sashiko-bot [this message]
2026-09-21  6:51 ` [PATCH 2/2] soc: qcom: socinfo: " Kathiravan Thirumoorthy
2026-09-21  7:00   ` sashiko-bot

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=20260921070015.D0D851F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kathiravan.thirumoorthy@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