summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-06-19 10:16:55 +0530
committerMarek Szyprowski <m.szyprowski@samsung.com>2014-05-15 07:28:19 +0200
commitbcb417719f20d732f54fc87c99d05b8f246ef889 (patch)
tree2a7fa5740573bb4d7d53b41b0ecf16587858e21a /include
parent45b5bbeed46077b367057075ae607f1e7034402b (diff)
downloadlinux-3.10-bcb417719f20d732f54fc87c99d05b8f246ef889.tar.gz
linux-3.10-bcb417719f20d732f54fc87c99d05b8f246ef889.tar.bz2
linux-3.10-bcb417719f20d732f54fc87c99d05b8f246ef889.zip
cpufreq: make sure frequency transitions are serialized
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. This can happen due to bugs in users of __cpufreq_driver_target() or actual cpufreq drivers who are sending these notifiers. This patch adds some protection against this. Now, we keep track of the last transaction and see if something went wrong. Change-Id: I0f5465bd515c431ae2d3711d065f70aacec7e978 Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include')
-rw-r--r--include/linux/cpufreq.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
index 9791c329c3e..e3da73bbcf0 100644
--- a/include/linux/cpufreq.h
+++ b/include/linux/cpufreq.h
@@ -121,6 +121,7 @@ struct cpufreq_policy {
struct list_head policy_list;
struct kobject kobj;
struct completion kobj_unregister;
+ bool transition_ongoing; /* Tracks transition status */
};
#define CPUFREQ_ADJUST (0)