Re: [PATCH] cpufreq: conservative: Drop cached requested_freq

[Viresh Kumar]

On 12-03-26, 16:43, Rafael J. Wysocki wrote:
> But how exactly does policy->cur get out the limits?

>From the first email:

"Later, some frequency division strategies on our platform were triggered
and the actual frequency become 500MHz -- 1/4 of the OS distribution
frequency."


> I guess there's some notification from the firmware or similar that
> causes the limits to be updated, but the only way policy->cur can
> change is to still fall between the new limits AFAICS.

AFAIU, the limits (in the view of cpufreq core) doesn't change, just
the end hardware frequency changes without informing the cpufreq core.
And if someone tries to read cpuinfo_cur_freq, cpufreq core tries to
get everything in sync.

-- 
viresh