On 14-08-25, 16:52, Zihuan Zhang wrote:
In cases where the CPU frequency table (freq_table) is not available,Is there a real problem you are facing ? Or a code that path can do
the __resolve_freq() function will now return the current frequency
(policy->cur) instead of the requested target frequency. This ensures
that the system doesn't return an invalid or uninitialized frequency
value when frequency scaling is not supported or not initialized.
This change improves the stability of the frequency scaling logic when
the CPU frequency table is not populated, preventing errors related
to unavailable frequency tables.
some harm ? I think this patch may end up breaking users.