Re: [RFC PATCH 18/19] cpufreq: remove transition_lock
From: Viresh Kumar
Date: Tue Jan 12 2016 - 06:24:20 EST
On 11-01-16, 17:35, Juri Lelli wrote:
> From: Michael Turquette <mturquette@xxxxxxxxxxxx>
>
> transition_lock was introduced to serialize cpufreq transition
> notifiers. Instead of using a different lock for protecting concurrent
> modifications of policy, it is better to require that callers of
> transition notifiers implement appropriate locking (this is already the
> case AFAICS). Removing transition_lock also simplifies current locking
> scheme.
So, are you saying that the reasoning mentioned in this patch are all
wrong?
commit 12478cf0c55e ("cpufreq: Make sure frequency transitions are
serialized")
--
viresh