From: Sreeshankar K <sreeshankar0910@gmail.com>
To: andersson@kernel.org, sboyd@kernel.org, bmasney+clk@redhat.com,
jbrunet+clk@baylibre.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, rafael@kernel.org, viresh.kumar@linaro.org,
konradybcio@kernel.org, tglx@kernel.org, ulfh@kernel.org
Cc: radu@rendec.net, abel.vesa@oss.qualcomm.com,
taniya.das@oss.qualcomm.com, danila@mainlining.org,
davidwronek@gmail.com, mani@kernel.org, robimarko@gmail.com,
linux@gurudas.dev, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Sreeshankar K <sreeshankar0910@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: [PATCH v7 02/12] soc: qcom: socinfo: Add SM7250 SoC ID
Date: Tue, 1 Sep 2026 06:43:47 +0000 [thread overview]
Message-ID: <20260901064357.20055-3-sreeshankar0910@gmail.com> (raw)
In-Reply-To: <20260901064357.20055-1-sreeshankar0910@gmail.com>
Add SoC ID for Qualcomm SM7250 SoC.
Signed-off-by: Sreeshankar K <sreeshankar0910@gmail.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
---
drivers/soc/qcom/socinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
index 1836e226a..63ee5cd56 100644
--- a/drivers/soc/qcom/socinfo.c
+++ b/drivers/soc/qcom/socinfo.c
@@ -450,6 +450,7 @@ static const struct soc_id soc_id[] = {
{ qcom_board_id(IPQ8172) },
{ qcom_board_id(IPQ8173) },
{ qcom_board_id(IPQ8174) },
+ { qcom_board_id(SM7250) },
{ qcom_board_id(IPQ6018) },
{ qcom_board_id(IPQ6028) },
{ qcom_board_id(SDM429W) },
--
2.43.0
next prev parent reply other threads:[~2026-09-01 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 6:43 [PATCH v7 00/12] Add initial support for Qualcomm SM7250 SoC Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 01/12] dt-bindings: arm: qcom,ids: Add SoC ID for SM7250 Sreeshankar K
2026-09-01 6:43 ` Sreeshankar K [this message]
2026-09-01 6:43 ` [PATCH v7 03/12] dt-bindings: clock: Add SM7250 global clock controller Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 04/12] clk: qcom: Add Global Clock Controller (GCC) driver for SM7250 Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 05/12] dt-bindings: clock: qcom,rpmhcc: Document RPMHCC compatible " Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 06/12] clk: qcom: rpmh: Add SM7250 rpmh clocks Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 07/12] dt-bindings: power: qcom,rpmhpd: Document RPMh power domain for SM7250 Sreeshankar K
2026-09-01 6:43 ` [PATCH v7 08/12] pmdomain: qcom: rpmhpd: Add RPMh power domains " Sreeshankar K
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=20260901064357.20055-3-sreeshankar0910@gmail.com \
--to=sreeshankar0910@gmail.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=danila@mainlining.org \
--cc=davidwronek@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jbrunet+clk@baylibre.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=mani@kernel.org \
--cc=radu@rendec.net \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
--cc=tglx@kernel.org \
--cc=ulfh@kernel.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.