From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Le Qi <le.qi@oss.qualcomm.com>,
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,
kernel@oss.qualcomm.com
Subject: Re: [PATCH v1] arm64: qcom: pd-mapper: Add QCS615 power domain mappings
Date: Tue, 27 Jan 2026 11:24:56 +0100 [thread overview]
Message-ID: <1507ca50-52c6-4b60-a0ee-06e873bb509e@oss.qualcomm.com> (raw)
In-Reply-To: <aa4f73a0-9342-4b02-aff6-df88abf836db@oss.qualcomm.com>
On 1/27/26 9:03 AM, Le Qi wrote:
> On 1/24/2026 4:03 AM, Dmitry Baryshkov wrote:
>> On Thu, Jan 22, 2026 at 01:07:45PM +0100, Konrad Dybcio wrote:
>>> On 1/22/26 12:13 PM, Le Qi wrote:
>>>> Add the QCS615 domain table to the in-kernel pd-mapper so that audio
>>>> subsystems no longer rely on the userspace pd-mapper daemon.
>>>> This enables proper initialization of ADSP and CDSP domains directly
>>>> from the kernel.
>>>>
>>>> Signed-off-by: Le Qi <le.qi@oss.qualcomm.com>
>>>> ---
>>>> drivers/soc/qcom/qcom_pd_mapper.c | 9 +++++++++
>>>> 1 file changed, 9 insertions(+)
>>>>
>>>> diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
>>>> index 1bcbe69688d2..884a2db9bb08 100644
>>>> --- a/drivers/soc/qcom/qcom_pd_mapper.c
>>>> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
>>>> @@ -401,6 +401,14 @@ static const struct qcom_pdm_domain_data *qcs404_domains[] = {
>>>> NULL,
>>>> };
>>>> +static const struct qcom_pdm_domain_data *qcs615_domains[] = {
>>>> + &adsp_audio_pd,
>>>> + &adsp_root_pd,
>>>> + &adsp_sensor_pd,
>>>> + &cdsp_root_pd,
>>>> + NULL,
>>>> +};
>>>
>>> No modem_xyz?
>>
>> There definitely should be mpss_root_pd / mpss_wlan_pd, otherwise modem
>> will not load WiFi firmware.
>>
>
> Hi Konrad and Dmitry, This board does not contain an MPSS. WiFi is handled by an independent WLAN module, which has its own internal PMU and is already supported.
Please describe the full set for Talos-with-modem, the "S" variant
will work too, since any "extra" domains will simply remain inactive
Konrad
prev parent reply other threads:[~2026-01-27 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 11:13 [PATCH v1] arm64: qcom: pd-mapper: Add QCS615 power domain mappings Le Qi
2026-01-22 12:07 ` Konrad Dybcio
2026-01-23 20:03 ` Dmitry Baryshkov
2026-01-27 8:03 ` Le Qi
2026-01-27 10:24 ` Konrad Dybcio [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=1507ca50-52c6-4b60-a0ee-06e873bb509e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kernel@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=le.qi@oss.qualcomm.com \
--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