From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Stanislav Aleksandrov <lightofmysoul@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
Subject: Re: [PATCH] cpufreq: Add Halliday to cpufreq-dt-platdev blocklist
Date: Wed, 11 Nov 2026 14:48:57 +0800 [thread overview]
Message-ID: <07e6065f-d31a-47ce-87a8-dee76d545c18@oss.qualcomm.com> (raw)
In-Reply-To: <20261109-halliday-cpufreq-v1-1-d87a397396fd@gmail.com>
On 11/9/2026 8:30 AM, Stanislav Aleksandrov wrote:
> The Qualcomm Halliday platform uses the qcom-cpufreq-hw driver, so add
> it to the cpufreq-dt-platdev driver's blocklist.
Nit: It is better to use the "cpufreq: dt-platdev:" prefix in the
subject.
Link to the DT series:
https://lore.kernel.org/all/20261109-halliday-dts-v1-0-289114ab8197@gmail.com/#t
The code looks good to me:
Reviewed-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
>
> Signed-off-by: Stanislav Aleksandrov <lightofmysoul@gmail.com>
> ---
> This is part of the bring-up of the Qualcomm Halliday SoC (SXR2250P)
> in the Samsung Galaxy XR. The DT changes follow in a separate series.
>
> This work was made together with Claude, ChatGPT and Gemini.
> Reviewed and tested on my Galaxy XR, where cpufreq runs through
> qcom-cpufreq-hw.
> ---
> 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 bce4c87573a1..3d5709eaa08f 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -155,6 +155,7 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "nvidia,tegra234", },
>
> { .compatible = "qcom,apq8096", },
> + { .compatible = "qcom,halliday", },
> { .compatible = "qcom,milos", },
> { .compatible = "qcom,msm8909", },
> { .compatible = "qcom,msm8996", },
>
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20261108-halliday-cpufreq-1e9c3581e2b4
>
> Best regards,
> --
> Stanislav Aleksandrov <lightofmysoul@gmail.com>
>
>
--
Thx and BRs,
Zhongqiu Han
prev parent reply other threads:[~2026-11-11 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 0:30 Stanislav Aleksandrov
2026-11-11 6:48 ` Zhongqiu Han [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=07e6065f-d31a-47ce-87a8-dee76d545c18@oss.qualcomm.com \
--to=zhongqiu.han@oss.qualcomm.com \
--cc=lightofmysoul@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--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®