From: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>
Subject: [PATCH] soc: qcom: pd-mapper: Add support for SM6125
Date: Wed, 28 Oct 2026 21:20:41 +0100 [thread overview]
Message-ID: <20261028-sm6125-pd-mapper-v1-1-af9a645b4b8a@mainlining.org> (raw)
Add support for the Qualcomm SM6125 SoC to the protection
domain mapper. SM6125 shares the same protection domain
configuration as SM6115.
Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
---
drivers/soc/qcom/qcom_pd_mapper.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
index 64ca99d7fad9..c1b7438541da 100644
--- a/drivers/soc/qcom/qcom_pd_mapper.c
+++ b/drivers/soc/qcom/qcom_pd_mapper.c
@@ -652,6 +652,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
{ .compatible = "qcom,sdm845", .data = sdm845_domains, },
{ .compatible = "qcom,sm4250", .data = sm6115_domains, },
{ .compatible = "qcom,sm6115", .data = sm6115_domains, },
+ { .compatible = "qcom,sm6125", .data = sm6115_domains, },
{ .compatible = "qcom,sm6350", .data = sm6350_domains, },
{ .compatible = "qcom,sm7150", .data = sm7150_domains, },
{ .compatible = "qcom,sm7225", .data = sm6350_domains, },
---
base-commit: 151a134a4e6ec66f69db8750c66006f5207f7a9d
change-id: 20261028-sm6125-pd-mapper-4fe25c92a547
Best regards,
--
Barnabás Czémán <barnabas.czeman@mainlining.org>
next reply other threads:[~2026-10-28 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 20:20 Barnabás Czémán [this message]
2026-10-29 8:12 ` Konrad Dybcio
2026-10-29 8:35 ` Abel Vesa
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=20261028-sm6125-pd-mapper-v1-1-af9a645b4b8a@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®