From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Cc: viresh.kumar@linaro.org, rafael@kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
umang.chheda@oss.qualcomm.com, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Add QCS8300 to cpufreq-dt-platdev blocklist
Date: Mon, 16 Mar 2026 21:11:00 +0530 [thread overview]
Message-ID: <20260316154100.5pt2nyli5nabvrm5@hu-mojha-hyd.qualcomm.com> (raw)
In-Reply-To: <20260316103752.289324-1-faruque.ansari@oss.qualcomm.com>
On Mon, Mar 16, 2026 at 04:07:52PM +0530, Faruque Ansari wrote:
> The Qualcomm QCS8300 platform uses the qcom-cpufreq-hw
> driver, so add it to the cpufreq-dt-platdev driver's blocklist.
>
> Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 25fd3b191b7e..ff1204c666b1 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -159,6 +159,7 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "qcom,qcm2290", },
> { .compatible = "qcom,qcm6490", },
> { .compatible = "qcom,qcs404", },
> + { .compatible = "qcom,qcs8300", },
Reviewed-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> { .compatible = "qcom,qdu1000", },
> { .compatible = "qcom,sa8155p" },
> { .compatible = "qcom,sa8540p" },
> --
> 2.34.1
>
--
-Mukesh Ojha
next prev parent reply other threads:[~2026-03-16 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 10:37 Faruque Ansari
2026-03-16 13:50 ` Dmitry Baryshkov
2026-03-16 15:41 ` Mukesh Ojha [this message]
2026-03-16 15:54 ` Konrad Dybcio
2026-03-17 8:51 ` Viresh Kumar
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=20260316154100.5pt2nyli5nabvrm5@hu-mojha-hyd.qualcomm.com \
--to=mukesh.ojha@oss.qualcomm.com \
--cc=faruque.ansari@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
--cc=viresh.kumar@linaro.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®