From: Richard Acayan <mailingradian@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH 2/3] soc: qcom: socinfo: Add SDM670 SoC ID table entry
Date: Thu, 23 May 2024 21:20:26 -0400 [thread overview]
Message-ID: <20240524012023.318965-7-mailingradian@gmail.com> (raw)
In-Reply-To: <20240524012023.318965-5-mailingradian@gmail.com>
There is support for SDM670 already, but not recognized by the socinfo
driver. Add the table entry so SDM670 can be found in sysfs.
Signed-off-by: Richard Acayan <mailingradian@gmail.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 e8ff9819ac47..8817eb8c1f1c 100644
--- a/drivers/soc/qcom/socinfo.c
+++ b/drivers/soc/qcom/socinfo.c
@@ -347,6 +347,7 @@ static const struct soc_id soc_id[] = {
{ qcom_board_id(SDA630) },
{ qcom_board_id(MSM8905) },
{ qcom_board_id(SDX202) },
+ { qcom_board_id(SDM670) },
{ qcom_board_id(SDM450) },
{ qcom_board_id(SM8150) },
{ qcom_board_id(SDA845) },
--
2.45.1
next prev parent reply other threads:[~2024-05-24 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 1:20 [PATCH 0/3] SDM670 shared memory and socinfo Richard Acayan
2024-05-24 1:20 ` [PATCH 1/3] dt-bindings: arm: qcom,ids: Add SoC ID for SDM670 Richard Acayan
2024-05-24 15:25 ` Konrad Dybcio
2024-05-25 16:59 ` Krzysztof Kozlowski
2024-05-24 1:20 ` Richard Acayan [this message]
2024-05-24 15:25 ` [PATCH 2/3] soc: qcom: socinfo: Add SDM670 SoC ID table entry Konrad Dybcio
2024-05-24 1:20 ` [PATCH 3/3] arm64: dts: qcom: sdm670: add smem region Richard Acayan
2024-05-28 3:32 ` (subset) [PATCH 0/3] SDM670 shared memory and socinfo Bjorn Andersson
2024-05-28 14:13 ` Bjorn Andersson
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=20240524012023.318965-7-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@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