From: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] soc: qcom: pd-mapper: Add support for SA8775P
Date: Mon, 9 Feb 2026 19:09:06 +0530 [thread overview]
Message-ID: <a46bf66c-8f88-44c9-afe8-78dc91bd50e2@oss.qualcomm.com> (raw)
In-Reply-To: <x4muzue44tizvlrhtrmat6f2rdlqkzwuuo6l4553lgrewlsr4a@n24bqtl6jn6s>
On 2/9/2026 6:10 PM, Dmitry Baryshkov wrote:
> On Mon, Feb 09, 2026 at 04:59:46PM +0530, Mohammad Rafi Shaik wrote:
>> Add support for the Qualcomm SA8775P SoC to the protection
>> domain mapper. SA8775P share the same protection domain
>> configuration as SC8280XP with an additional gpdsp domain,
>> except for charger_pd.
>>
>> Add an entry to the kernel, to avoid the need for userspace
>> to provide this service.
>>
>> Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
>> ---
>> drivers/soc/qcom/qcom_pd_mapper.c | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
>> index 1bcbe6968..8b899ec7f 100644
>> --- a/drivers/soc/qcom/qcom_pd_mapper.c
>> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
>> @@ -305,6 +305,18 @@ static const struct qcom_pdm_domain_data cdsp_root_pd = {
>> .services = { NULL },
>> };
>>
>> +static const struct qcom_pdm_domain_data gpdsp_root_pd = {
>> + .domain = "msm/gpdsp/root_pd",
>> + .instance_id = 192,
>> + .services = { NULL },
>> +};
>> +
>> +static const struct qcom_pdm_domain_data gpdsp1_root_pd = {
>> + .domain = "msm/gpdsp1/root_pd",
>> + .instance_id = 241,
>> + .services = { NULL },
>> +};
>> +
>> static const struct qcom_pdm_domain_data slpi_root_pd = {
>> .domain = "msm/slpi/root_pd",
>> .instance_id = 90,
>> @@ -401,6 +413,15 @@ static const struct qcom_pdm_domain_data *qcs404_domains[] = {
>> NULL,
>> };
>>
>> +static const struct qcom_pdm_domain_data *sa8775p_domains[] = {
>> + &adsp_audio_pd,
>> + &adsp_root_pd,
>> + &cdsp_root_pd,
>
> Is there no separate PD for CDSP1? What is the difference between CDSP
> and CDSP1?
>
Yes, there is no dedicated PD entry for CDSP1 in the linux‑firmware,
In the device tree, there is no functional change in CDSP, only the base
address is different.
Thanks & Regards,
Rafi.
>> + &gpdsp_root_pd,
>> + &gpdsp1_root_pd,
>> + NULL,
>> +};
>> +
>> static const struct qcom_pdm_domain_data *sc7180_domains[] = {
>> &adsp_audio_pd,
>> &adsp_root_pd_pdr,
>> @@ -572,6 +593,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
>> { .compatible = "qcom,qcm2290", .data = qcm2290_domains, },
>> { .compatible = "qcom,qcm6490", .data = sc7280_domains, },
>> { .compatible = "qcom,qcs404", .data = qcs404_domains, },
>> + { .compatible = "qcom,sa8775p", .data = sa8775p_domains, },
>> { .compatible = "qcom,sc7180", .data = sc7180_domains, },
>> { .compatible = "qcom,sc7280", .data = sc7280_domains, },
>> { .compatible = "qcom,sc8180x", .data = sc8180x_domains, },
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2026-02-09 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 11:29 [PATCH v3 0/2] soc: qcom: pd-mapper: Add support for SA8775P and QCS8300 Mohammad Rafi Shaik
2026-02-09 11:29 ` [PATCH v3 1/2] soc: qcom: pd-mapper: Add support for SA8775P Mohammad Rafi Shaik
2026-02-09 12:40 ` Dmitry Baryshkov
2026-02-09 13:39 ` Mohammad Rafi Shaik [this message]
2026-02-09 14:18 ` Dmitry Baryshkov
2026-02-10 6:13 ` Mohammad Rafi Shaik
2026-02-09 11:29 ` [PATCH v3 2/2] soc: qcom: pd-mapper: Add support for QCS8300 Mohammad Rafi Shaik
2026-02-09 12:41 ` Dmitry Baryshkov
2026-02-09 13:19 ` Mohammad Rafi Shaik
2026-02-09 14:19 ` 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=a46bf66c-8f88-44c9-afe8-78dc91bd50e2@oss.qualcomm.com \
--to=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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®