From: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Jingyi Wang <jingyi.wang@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,
aiqun.yu@oss.qualcomm.com, tingwei.zhang@oss.qualcomm.com,
trilok.soni@oss.qualcomm.com, yijie.yang@oss.qualcomm.com
Subject: Re: [PATCH] soc: qcom: pd-mapper: Add Kaanapali compatible
Date: Wed, 1 Oct 2025 19:59:09 +0530 [thread overview]
Message-ID: <b2eda648-9c2e-423d-8068-3ff95e741d70@oss.qualcomm.com> (raw)
In-Reply-To: <6f8583e8-2a73-4795-8eb8-5f1b763b36eb@oss.qualcomm.com>
On 9/25/2025 2:24 PM, Konrad Dybcio wrote:
> On 9/25/25 1:58 AM, Jingyi Wang wrote:
>> From: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
>>
>> Add support for the Qualcomm Kaanapali SoC to the protection
>> domain mapper. Kaanapali shares the same protection domain
>> configuration as SM8550, so reuse the existing SM8550 domain data.
>>
>> Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
>> Signed-off-by: Jingyi Wang <jingyi.wang@oss.qualcomm.com>
>> ---
>> 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 6384f271953d..bb2eeb955106 100644
>> --- a/drivers/soc/qcom/qcom_pd_mapper.c
>> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
>> @@ -552,6 +552,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
>> { .compatible = "qcom,apq8074", .data = NULL, },
>> { .compatible = "qcom,apq8084", .data = NULL, },
>> { .compatible = "qcom,apq8096", .data = msm8996_domains, },
>> + { .compatible = "qcom,kaanapali", .data = sm8550_domains, },
> Doesn't e.g. 'msm/adsp/charger_pd' need adjustments with the move to
> SoCCP?
Yes, Thanks for pointing it, Will create a new domain entry for
Kaanapali and
remove the charger_pd. Will update in next patch.
Thanks,
Prasad
>
> Konrad
prev parent reply other threads:[~2025-10-01 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 23:58 [PATCH] soc: qcom: pd-mapper: Add Kaanapali compatible Jingyi Wang
2025-09-25 2:22 ` Dmitry Baryshkov
2025-09-25 8:54 ` Konrad Dybcio
2025-10-01 14:29 ` Prasad Kumpatla [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=b2eda648-9c2e-423d-8068-3ff95e741d70@oss.qualcomm.com \
--to=prasad.kumpatla@oss.qualcomm.com \
--cc=aiqun.yu@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
--cc=trilok.soni@oss.qualcomm.com \
--cc=yijie.yang@oss.qualcomm.com \
/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