From: Rob Herring <robh@kernel.org>
To: Mukesh Ojha <mukesh.ojha@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] soc: qcom: pd-mapper: Add support for Hawi SoC
Date: Fri, 12 Jun 2026 17:15:14 -0500 [thread overview]
Message-ID: <20260612221514.GA1951714-robh@kernel.org> (raw)
In-Reply-To: <20260506110226.2256249-1-mukesh.ojha@oss.qualcomm.com>
On Wed, May 06, 2026 at 04:32:26PM +0530, Mukesh Ojha wrote:
> Hawi uses the same protection domain layout as Kaanapali, so reuse the
> kaanapali_domains table. Also add the missing adsp_ois_pd entry (OIS
> protection domain, instance_id 74) to kaanapali_domains, which is
> required by both Kaanapali and Hawi.
>
> Signed-off-by: Mukesh Ojha <mukesh.ojha@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 7bb14c20ab5d..b99718e25f2f 100644
> --- a/drivers/soc/qcom/qcom_pd_mapper.c
> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
> @@ -266,6 +266,12 @@ static const struct qcom_pdm_domain_data adsp_charger_pd = {
> .services = { NULL },
> };
>
> +static const struct qcom_pdm_domain_data adsp_ois_pd = {
> + .domain = "msm/adsp/ois_pd",
> + .instance_id = 74,
> + .services = { NULL, },
> +};
> +
> static const struct qcom_pdm_domain_data adsp_root_pd = {
> .domain = "msm/adsp/root_pd",
> .instance_id = 74,
> @@ -370,6 +376,7 @@ static const struct qcom_pdm_domain_data *glymur_domains[] = {
>
> static const struct qcom_pdm_domain_data *kaanapali_domains[] = {
> &adsp_audio_pd,
> + &adsp_ois_pd,
> &adsp_root_pd,
> &adsp_sensor_pd,
> &cdsp_root_pd,
> @@ -581,6 +588,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
> { .compatible = "qcom,eliza", .data = sm8550_domains, },
> { .compatible = "qcom,apq8096", .data = msm8996_domains, },
> { .compatible = "qcom,glymur", .data = glymur_domains, },
> + { .compatible = "qcom,hawi", .data = kaanapali_domains, },
This is not documented. I couldn't find any patch adding it. Please
submit one.
Rob
next prev parent reply other threads:[~2026-06-12 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 11:02 Mukesh Ojha
2026-05-13 19:08 ` Bjorn Andersson
2026-06-12 22:15 ` Rob Herring [this message]
2026-06-17 7:31 ` Mukesh Ojha
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=20260612221514.GA1951714-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@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
all inboxes | Powered by JetHome®