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

[Beata Michalska]

On Wed, Jan 22, 2025 at 11:42:50AM +0530, Viresh Kumar wrote:
> On 21-01-25, 16:14, Beata Michalska wrote:
> > Theoretically speaking - it should, though what would 0 actually
> > represent then ?
> 
> 0 won't be a failure, that's clear, since errors are represented
> differently now. I am not sure what 0 frequency would mean and it can
> be left as an architecture specific value, which is a corner case I am
> not sure will ever occur.
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.

---
BR
Beata
> 
> -- 
> viresh