Re: [PATCH v9 1/5] cpufreq: Allow arch_freq_get_on_cpu to return an error

Viresh Kumar
2025-01-24T03:33:36Z

On 23-01-25, 22:45, Beata Michalska wrote:
> That would mean we are opting for presenting '0' value (whatever that means)
> instead of trying alternative ways of getting 'current' frequency ?
> This is still the scaling_cur_freq.

A return value of 0 should typically mean something went wrong
somewhere and didn't return the right value to us.

- For the print message, I think we should just print the value
instead of UNKNOWN. Let the user / developer decide what to do with
it.

- As for trying other mechanism to find the frequency now, maybe you
are right and looking for an alternate way is the right way to go.
And that would be consistent with existing behavior too.

--
viresh