| commit | 7249924e537816368c4a35afd97ab311f75a6368 | |
| author | Viresh Kumar <viresh.kumar@linaro.org> | |
| Wed, 31 Oct 2012 00:28:21 +0000 (31 01:28 +0100) | ||
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | |
| Wed, 14 Nov 2012 23:33:09 +0000 (15 00:33 +0100) | ||
| tree | a332ffc88c23988b4add2bab60705357a230b705 | treesnapshot (tar.gz zip) |
| parent | 5a1c022850ea5d64c2997bf9b89f5ae112d5ee4d | commitdiff |
cpufreq: Make sure target freq is within limits
__cpufreq_driver_target() must not pass target frequency beyond the
limits of current policy.
Today most of cpufreq platform drivers are doing this check in their
target routines. Why not move it to __cpufreq_driver_target()?
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
__cpufreq_driver_target() must not pass target frequency beyond the
limits of current policy.
Today most of cpufreq platform drivers are doing this check in their
target routines. Why not move it to __cpufreq_driver_target()?
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
| drivers/cpufreq/cpufreq.c | diffblobblamehistory |