summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/exynos5440-cpufreq.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-02-07 18:01:31 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-03-09 16:40:53 +0300
commit2bb8d94fb03f808022c620f54b602a1e26d5cbac (patch)
tree9b73be310729f138d4c47e3e51b707144c85aa21 /drivers/cpufreq/exynos5440-cpufreq.c
parent9be4fd2c7723a3057b0b39676fe4c8d5fd7118a4 (diff)
downloadlinux-2bb8d94fb03f808022c620f54b602a1e26d5cbac.tar.xz
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>
Diffstat (limited to 'drivers/cpufreq/exynos5440-cpufreq.c')
0 files changed, 0 insertions, 0 deletions