From: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: pd-mapper: Add support for the Qualcomm Shikra SoC
Date: Tue, 20 Oct 2026 13:05:35 +0530 [thread overview]
Message-ID: <d1ef564c-2031-477b-b318-426d472b80e6@oss.qualcomm.com> (raw)
In-Reply-To: <014f65d8-702f-4b45-8037-8c416ea8c858@oss.qualcomm.com>
On 7/28/2026 3:43 PM, Konrad Dybcio wrote:
> On 7/28/26 11:52 AM, Anurag Pateriya wrote:
>> Add support for the Qualcomm Shikra SoC to the protection domain mapper.
>>
>> All Shikra SoC variants (CQM, CQS, IQS) share the same protection
>> domain requirements: mpss_wlan_pd.
>>
>> Signed-off-by: Anurag Pateriya <anurag.pateriya@oss.qualcomm.com>
>> ---
>
> I understand the audio domains are lacking since there is no more
> ADSP, but mpss_wlan_pd? cdsp_root_pd?
>
> Konrad
Yes. I need to add cdsp_root_pd and mpss_root_pd
I will add it in v2.
For mpss, I already added mpss_wlan_pd. Mpss_root_pd share the same
instance_id = 180 but register distinct domain paths (msm/modem/wlan_pd
vs msm/modem/root_pd).
Clients subscribing to msm/modem/root_pd restart notifications require
an explicit entry.
I will add mpss_root_pd to ensure complete coverage, consistent with
other SoCs.
Thanks,
Anurag
prev parent reply other threads:[~2026-10-20 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:52 Anurag Pateriya
2026-07-28 10:13 ` Konrad Dybcio
2026-10-20 7:35 ` Anurag Pateriya [this message]
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=d1ef564c-2031-477b-b318-426d472b80e6@oss.qualcomm.com \
--to=anurag.pateriya@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@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®