Messages in this thread | | | Date | Tue, 12 Jan 2016 16:54:09 +0530 | From | Viresh Kumar <> | Subject | Re: [RFC PATCH 18/19] cpufreq: remove transition_lock |
| |
On 11-01-16, 17:35, Juri Lelli wrote: > From: Michael Turquette <mturquette@baylibre.com> > > 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
| |