cpufreq: governor: Use common mutex for dbs_data protection
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Sun, 7 Feb 2016 15:01:31 +0000 (16:01 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 9 Mar 2016 13:40:53 +0000 (14:40 +0100)
commit2bb8d94fb03f808022c620f54b602a1e26d5cbac
tree9b73be310729f138d4c47e3e51b707144c85aa21
parent9be4fd2c7723a3057b0b39676fe4c8d5fd7118a4
cpufreq: governor: Use common mutex for dbs_data protection

Every governor relying on the common code in cpufreq_governor.c
has to provide its own mutex in struct common_dbs_data.  However,
there actually is no need to have a separate mutex per governor
for this purpose, they may be using the same global mutex just
fine.  Accordingly, introduce a single common mutex for that and
drop the mutex field from struct common_dbs_data.

That at least will ensure that the mutex is always present and
initialized regardless of what the particular governors do.

Another benefit is that the common code does not need a pointer to
a governor-related structure to get to the mutex which sometimes
helps.

Finally, it makes the code generally easier to follow.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Saravana Kannan <skannan@codeaurora.org>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/cpufreq/cpufreq_conservative.c
drivers/cpufreq/cpufreq_governor.c
drivers/cpufreq/cpufreq_governor.h
drivers/cpufreq/cpufreq_ondemand.c
This page took 0.02556 seconds and 5 git commands to generate.