public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Komal Bajaj <komal.bajaj@oss.qualcomm.com>
Subject: [PATCH 0/2] arm64: qcom: Add SoC ID for Shikra IoT variants
Date: Tue, 28 Apr 2026 14:47:45 +0530	[thread overview]
Message-ID: <20260428-shikra-socid-v1-0-6ff16bad5ea2@oss.qualcomm.com> (raw)

This is the initial posting for upstreaming Qualcomm Shikra SoC.
There are three variants, distinguished by their respective SoC IDs -
- CQ2390M: Shikra Retail with modem
- CQ2390S: Shikra Retail without modem
- IQ2390S: Shikra Industrial without modem

This serial adds the corresponding SoC IDs to enable proper
identification of these variants in the kernel.

Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
---
Komal Bajaj (2):
      dt-bindings: arm: qcom,ids: Add SoC ID for Shikra IoT variants
      soc: qcom: socinfo: Add SoC ID for Shikra IoT variants

 drivers/soc/qcom/socinfo.c         | 3 +++
 include/dt-bindings/arm/qcom,ids.h | 3 +++
 2 files changed, 6 insertions(+)
---
base-commit: 39704f00f747aba3144289870b5fd8ac230a9aaf
change-id: 20260428-shikra-socid-a27ae38cb7e3

Best regards,
-- 
Komal Bajaj <komal.bajaj@oss.qualcomm.com>


             reply	other threads:[~2026-04-28  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  9:17 Komal Bajaj [this message]
2026-04-28  9:17 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for Shikra IoT variants Komal Bajaj
2026-04-28  9:39   ` Konrad Dybcio
2026-04-30  9:38   ` Krzysztof Kozlowski
2026-04-28  9:17 ` [PATCH 2/2] soc: qcom: socinfo: " Komal Bajaj
2026-04-28  9:41   ` Konrad Dybcio
2026-04-30  9:38   ` Krzysztof Kozlowski

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=20260428-shikra-socid-v1-0-6ff16bad5ea2@oss.qualcomm.com \
    --to=komal.bajaj@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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