Re: [PATCH 2/2] cpufreq: make sure frequency transitions are serialized

On 12 September 2013 15:40, Viresh Kumar viresh.kumar@linaro.org wrote:

Some part of this patch was pushed in mainline earlier but was then removed due to loopholes in the patch. Those are now fixed and this patch is tested by the people who reported these problems.

Whenever we are changing frequency of a cpu, we are calling PRECHANGE and POSTCHANGE notifiers. They must be serialized. i.e. PRECHANGE or POSTCHANGE shouldn't be called twice contiguously. Also, calls to cpufreq_driver_target() or cpufreq_driver->target() must also be serialized. Following examples show why this is important:

Adding:

Tested-by: Stephen Warren swarren@nvidia.com

Picked from the other thread..