Re: [PATCH v1] cpufreq: Return current frequency when frequency table is unavailable
From: Viresh Kumar
Date: Thu Aug 14 2025 - 05:42:30 EST
On 14-08-25, 17:24, Zihuan Zhang wrote:
> I just feel that it might not be ideal to set a frequency when the frequency
> table is unavailable.
>
> Perhaps adding a log or warning when the frequency table is missing could be
> a better approach.
There are a lot of drivers that don't provide a frequency table, i.e.
drivers with setpolicy() or target() callbacks. Only the
target_index() ones provide a freq table.
--
viresh