Messages in this thread | | | Date | Sun, 11 Nov 2012 17:38:24 +0100 | From | Borislav Petkov <> | Subject | Re: [PATCH 3/6 v4] cpufreq: tolerate inexact values when collecting stats |
| |
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.
| |