mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 2/2] soc: qcom: pd-mapper: Add support for QCS8300
Date: Mon, 9 Feb 2026 18:49:26 +0530	[thread overview]
Message-ID: <3406d478-50fc-45a5-be06-713a9151e0d0@oss.qualcomm.com> (raw)
In-Reply-To: <onubc2qpbazy4kge5ynedl4imihcrj3btlo5aqvmxubk23t2hm@rasbihmw56gi>



On 2/9/2026 6:11 PM, Dmitry Baryshkov wrote:
> On Mon, Feb 09, 2026 at 04:59:47PM +0530, Mohammad Rafi Shaik wrote:
>> Add support for the Qualcomm QCS8300 SoC to the protection
>> domain mapper. QCS8300 share the same protection domain
>> configuration as SC8280XP, except 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 | 8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
>> index 8b899ec7f..32538e659 100644
>> --- a/drivers/soc/qcom/qcom_pd_mapper.c
>> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
>> @@ -413,6 +413,13 @@ static const struct qcom_pdm_domain_data *qcs404_domains[] = {
>>   	NULL,
>>   };
>>   
>> +static const struct qcom_pdm_domain_data *qcs8300_domains[] = {
>> +	&adsp_audio_pd,
>> +	&adsp_root_pd,
>> +	&cdsp_root_pd,
> 
> No PD for GPDSP?
> 

yes, There is no PD available for GPDSP in the Monaco linux‑firmware.

Thanks & Regards,
Rafi.

>> +	NULL,
>> +};
>> +
>>   static const struct qcom_pdm_domain_data *sa8775p_domains[] = {
>>   	&adsp_audio_pd,
>>   	&adsp_root_pd,
>> @@ -593,6 +600,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,qcs8300", .data = qcs8300_domains, },
>>   	{ .compatible = "qcom,sa8775p", .data = sa8775p_domains, },
>>   	{ .compatible = "qcom,sc7180", .data = sc7180_domains, },
>>   	{ .compatible = "qcom,sc7280", .data = sc7280_domains, },
>> -- 
>> 2.34.1
>>
> 


  reply	other threads:[~2026-02-09 13:19 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
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 [this message]
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=3406d478-50fc-45a5-be06-713a9151e0d0@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®