From: Radu Rendec <rrendec@redhat.com>
To: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Lei Wang <quic_leiwan@quicinc.com>,
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>
Subject: [PATCH 2/2] soc: qcom: socinfo: Add SoC ID for SA8650P
Date: Fri, 20 Mar 2026 16:59:33 -0400 [thread overview]
Message-ID: <20260320205933.992852-3-rrendec@redhat.com> (raw)
In-Reply-To: <20260320205933.992852-1-rrendec@redhat.com>
From: Lei wang <quic_leiwan@quicinc.com>
Add SoC ID table entry for Qualcomm SA8650P.
Signed-off-by: Lei Wang <quic_leiwan@quicinc.com>
Signed-off-by: Radu Rendec <rrendec@redhat.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 003a2304d535c..01eae575afd27 100644
--- a/drivers/soc/qcom/socinfo.c
+++ b/drivers/soc/qcom/socinfo.c
@@ -488,6 +488,7 @@ static const struct soc_id soc_id[] = {
{ qcom_board_id(SM8475) },
{ qcom_board_id(SM8475P) },
{ qcom_board_id(SA8255P) },
+ { qcom_board_id(SA8650P) },
{ qcom_board_id(SA8775P) },
{ qcom_board_id(QRU1000) },
{ qcom_board_id(SM8475_2) },
--
2.53.0
next prev parent reply other threads:[~2026-03-20 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 20:59 [PATCH 0/2] Add Qualcomm SA8650P SoC to socinfo Radu Rendec
2026-03-20 20:59 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SA8650P Radu Rendec
2026-03-21 6:59 ` Dmitry Baryshkov
2026-03-21 10:03 ` Krzysztof Kozlowski
2026-03-21 15:12 ` Radu Rendec
2026-03-21 19:32 ` Krzysztof Kozlowski
2026-03-22 1:17 ` Radu Rendec
2026-03-20 20:59 ` Radu Rendec [this message]
2026-03-21 6:59 ` [PATCH 2/2] soc: qcom: socinfo: " Dmitry Baryshkov
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=20260320205933.992852-3-rrendec@redhat.com \
--to=rrendec@redhat.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=quic_leiwan@quicinc.com \
--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 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.