Re: [PATCH] cpufreq: fix current freq check on policy update

[Pierre Ossman <pierre-list@ossman.eu>]

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

On Fri, 14 Feb 2014 17:14:34 +0530
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com> wrote:

> 
> So with that, I don't see how the KHz value can turn out to be zero!
> 

Very interesting. But I can tell you that it is indeed happening. With
my earlier patch (that checked the return value), I did have this in my
dmesg:

[  188.044175] cpufreq: updating policy for CPU 1
[  188.044177] cpufreq: Driver did not initialize current freq
[  188.044177] cpufreq: setting new policy for CPU 0: 1000000 - 2800000 kHz

I can sprinkle some more pr_debug:s in there if you want to trace it
further?

Note that this is with 3.12.9, not master.

Rgds
-- 
     -- Pierre Ossman

  WARNING: This correspondence is being monitored by FRA, a
  Swedish intelligence agency. Make sure your server uses
  encryption for SMTP traffic and consider using PGP for
  end-to-end encryption.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 230 bytes --]