From: Sudeep Holla <sudeep.holla@arm.com>
To: Jacky Bai <ping.bai@nxp.com>
Cc: <rafael@kernel.org>, <viresh.kumar@linaro.org>,
<ilia.lin@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>,
<tiny.windzz@gmail.com>, <wens@csie.org>,
<jernej.skrabec@gmail.com>, <samuel@sholland.org>,
<matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>,
<linux-pm@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-sunxi@lists.linux.dev>,
<linux-mediatek@lists.infradead.org>, <imx@lists.linux.dev>
Subject: Re: [PATCH] cpufreq: Init cpufreq only for present CPUs
Date: Mon, 10 Mar 2025 10:19:48 +0000 [thread overview]
Message-ID: <Z868xB3_3NhMsa7R@bogus> (raw)
In-Reply-To: <20250310071640.3140435-1-ping.bai@nxp.com>
On Mon, Mar 10, 2025 at 03:16:40PM +0800, Jacky Bai wrote:
> for_each_possible_cpu() is currently used to initialize cpufreq
> in below cpufreq drivers:
> drivers/cpufreq/cpufreq-dt.c
> drivers/cpufreq/mediatek-cpufreq-hw.c
> drivers/cpufreq/mediatek-cpufreq.c
> drivers/cpufreq/qcom-cpufreq-nvmem.c
> drivers/cpufreq/sun50i-cpufreq-nvmem.c
>
Again how did you just narrow down to the list above ? Is that just a
random pick ? As I suggested with corresponding cpuidle changes, please
look into the details in side the for_each_possible_cpu() loop and then
decide if it applies or not.
For me, it applied to the below files as well at the least.
drivers/cpufreq/mvebu-cpufreq.c
drivers/cpufreq/qcom-cpufreq-hw.c
drivers/cpufreq/scmi-cpufreq.c
drivers/cpufreq/scpi-cpufreq.c
drivers/cpufreq/virtual-cpufreq.c
Please check everything thoroughly as I just looked at these briefly.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-03-10 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:16 [PATCH] cpufreq: Init cpufreq only for present CPUs Jacky Bai
2025-03-10 10:19 ` Sudeep Holla [this message]
2025-03-10 10:56 ` Jacky Bai
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=Z868xB3_3NhMsa7R@bogus \
--to=sudeep.holla@arm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ilia.lin@kernel.org \
--cc=imx@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=ping.bai@nxp.com \
--cc=rafael@kernel.org \
--cc=samuel@sholland.org \
--cc=tiny.windzz@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.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