From: Zihuan Zhang <zhangzihuan@kylinos.cn>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J . wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>,
zhenglifeng <zhenglifeng1@huawei.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] cpufreq: Always enforce policy limits even without frequency table
Date: Mon, 8 Sep 2025 14:51:37 +0800 [thread overview]
Message-ID: <cbe36377-6f92-4913-8cd7-087e718af368@kylinos.cn> (raw)
In-Reply-To: <20250908061333.rwzq5dj4nxlav6x5@vireshk-i7>
在 2025/9/8 14:13, Viresh Kumar 写道:
> On 04-09-25, 13:48, Zihuan Zhang wrote:
>> I understand your point about the potential duplicate call to
>> cpufreq_verify_within_cpu_limits() for drivers with a valid freq-table.
>> However, in the third patch of this series, we removed the call to
>> cpufreq_generic_frequency_table_verify() from the table_verify path.
> Yeah, I missed that.
>
We are currently considering moving the check that ensures a driver
providing a freq_table also implements target_index() into the driver
registration path.
This way, freq_table.c no longer needs to defensively check for NULL
pointers.
Additionally, we are thinking about merging the two related APIs into a
single one. Do you think this is a good idea?
next prev parent reply other threads:[~2025-09-08 6:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 3:22 [PATCH v1 0/3] cpufreq: Clean up frequency table handling Zihuan Zhang
2025-09-04 3:22 ` [PATCH v1 1/3] cpufreq: Drop redundant freq_table parameter Zihuan Zhang
2025-09-04 13:31 ` Rafael J. Wysocki
2025-09-05 1:16 ` Zihuan Zhang
2025-09-04 3:22 ` [PATCH v1 2/3] cpufreq: Always enforce policy limits even without frequency table Zihuan Zhang
2025-09-04 4:48 ` Viresh Kumar
2025-09-04 5:23 ` Zihuan Zhang
2025-09-04 5:37 ` Viresh Kumar
2025-09-04 5:48 ` Zihuan Zhang
2025-09-08 6:13 ` Viresh Kumar
2025-09-08 6:51 ` Zihuan Zhang [this message]
2025-09-08 6:55 ` Viresh Kumar
2025-09-08 7:08 ` Zihuan Zhang
2025-09-08 7:19 ` Viresh Kumar
2025-09-08 7:36 ` Zihuan Zhang
2025-09-08 7:44 ` Viresh Kumar
2025-09-04 3:22 ` [PATCH v1 3/3] cpufreq: Make cpufreq_frequency_table_verify() internal Zihuan Zhang
2025-09-04 4:45 ` Viresh Kumar
2025-09-04 5:34 ` Zihuan Zhang
2025-09-08 6:46 ` Viresh Kumar
2025-09-04 4:24 ` [PATCH v1 0/3] cpufreq: Clean up frequency table handling Viresh Kumar
2025-09-04 4:36 ` Zihuan Zhang
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=cbe36377-6f92-4913-8cd7-087e718af368@kylinos.cn \
--to=zhangzihuan@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=viresh.kumar@linaro.org \
--cc=zhenglifeng1@huawei.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®