From: Bhupesh Sharma <bhupesh.sharma@linaro.org>
To: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: agross@kernel.org, bhupesh.sharma@linaro.org,
bhupesh.linux@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski@linaro.org,
andersson@kernel.org, konrad.dybcio@somainline.org,
a39.skl@gmail.com
Subject: [PATCH 0/4] Add SoC ID support for a few more Qualcomm SoCs
Date: Thu, 1 Dec 2022 19:46:15 +0530 [thread overview]
Message-ID: <20221201141619.2462705-1-bhupesh.sharma@linaro.org> (raw)
This patchset adds SoC IDs for Qualcomm SM8150, SA8155,
SM6115 / SM4250 (and variants) SoCs to the socinfo driver and dt-bindings.
Bhupesh Sharma (4):
dt-bindings: arm: qcom,ids: Add SoC IDs for SM8150 and SA8155
soc: qcom: socinfo: Add SM8150 and SA8155 SoC IDs to the soc_id table
dt-bindings: arm: qcom,ids: Add SoC IDs for SM6115 / SM4250 and
variants
soc: qcom: socinfo: Add SM6115 / SM4250 SoC IDs to the soc_id table
drivers/soc/qcom/socinfo.c | 6 ++++++
include/dt-bindings/arm/qcom,ids.h | 6 ++++++
2 files changed, 12 insertions(+)
--
2.38.1
next reply other threads:[~2022-12-01 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 14:16 Bhupesh Sharma [this message]
2022-12-01 14:16 ` [PATCH 1/4] dt-bindings: arm: qcom,ids: Add SoC IDs for SM8150 and SA8155 Bhupesh Sharma
2022-12-01 14:20 ` Konrad Dybcio
2022-12-01 14:20 ` Krzysztof Kozlowski
2022-12-01 14:16 ` [PATCH 2/4] soc: qcom: socinfo: Add SM8150 and SA8155 SoC IDs to the soc_id table Bhupesh Sharma
2022-12-01 14:20 ` Konrad Dybcio
2022-12-01 14:16 ` [PATCH 3/4] dt-bindings: arm: qcom,ids: Add SoC IDs for SM6115 / SM4250 and variants Bhupesh Sharma
2022-12-01 14:20 ` Konrad Dybcio
2022-12-01 14:22 ` Krzysztof Kozlowski
2022-12-01 14:16 ` [PATCH 4/4] soc: qcom: socinfo: Add SM6115 / SM4250 SoC IDs to the soc_id table Bhupesh Sharma
2022-12-01 14:21 ` Konrad Dybcio
2022-12-06 18:18 ` [PATCH 0/4] Add SoC ID support for a few more Qualcomm SoCs 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=20221201141619.2462705-1-bhupesh.sharma@linaro.org \
--to=bhupesh.sharma@linaro.org \
--cc=a39.skl@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).