summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/sparc-us2e-cpufreq.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2013-10-29 18:56:06 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-10-31 00:11:08 +0100
commit7dbf694db6ac7c759599316d50d7050efcbd512a (patch)
treefe10dc555181b52a8fd567dcf819d5a447bb1f37 /drivers/cpufreq/sparc-us2e-cpufreq.c
parente0a261a207fb5bcbc6cc5db3b51a96d9cbe9b97e (diff)
downloadblackbird-op-linux-7dbf694db6ac7c759599316d50d7050efcbd512a.tar.gz
blackbird-op-linux-7dbf694db6ac7c759599316d50d7050efcbd512a.zip
cpufreq: distinguish drivers that do asynchronous notifications
There are few special cases like exynos5440 which doesn't send POSTCHANGE notification from their ->target() routine and call some kind of bottom halves for doing this work, work/tasklet/etc.. From which they finally send POSTCHANGE notification. Its better if we distinguish them from other cpufreq drivers in some way so that core can handle them specially. So this patch introduces another flag: CPUFREQ_ASYNC_NOTIFICATION, which will be set by such drivers. This also changes exynos5440-cpufreq.c and powernow-k8 in order to set this flag. Acked-by: Amit Daniel Kachhap <amit.daniel@samsung.com> Acked-by: Kukjin Kim <kgene.kim@samsung.com> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/sparc-us2e-cpufreq.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud