Re: [PATCH] cpufreq: Initialize the governor again while restoring policy

On 10 July 2015 at 05:35, Rafael J. Wysocki rjw@rjwysocki.net wrote:

...

• Because governors matched, we skip governor initialization and return after calling __cpufreq_governor(CPUFREQ_GOV_LIMITS).

But this sounds fragile in principle. What's the benefit from skipping the governor initialization in that case?

So this is the case where we have changed some property of the governor, and the governor is already initialised. We need to exit the earlier governor and initialize the new one only when the governor is actually switched.