Re: [PATCH 3/6 v4] cpufreq: tolerate inexact values when collecting stats

Borislav Petkov
2012-11-11T16:38:24Z

On Wed, Nov 07, 2012 at 12:32:43PM -0600, Mark Langsdorf wrote:
> When collecting stats, if a frequency doesn't match the table, go through
> the table again with both the search frequency and table values shifted
> left by 10 bits.

Why would that second pass succeed?

And why is this in generic code (I'm assuming this is a Calxeda-specific
case)?

--
Regards/Gruss,
Boris.