diff options
author | Viresh Kumar <viresh.kumar@linaro.org> | 2017-08-09 10:21:46 +0530 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-08-10 01:26:35 +0200 |
commit | 209887e6b974c22328487b55d0f390522b014b03 (patch) | |
tree | 2c8f238ef95b4ac26eb066db58509355fb8d2ea1 /fs/squashfs/squashfs.h | |
parent | d6344d4b5628052ccda104466e5e05b9c43d7b61 (diff) | |
download | talos-obmc-linux-209887e6b974c22328487b55d0f390522b014b03.tar.gz talos-obmc-linux-209887e6b974c22328487b55d0f390522b014b03.zip |
cpufreq: Return 0 from ->fast_switch() on errors
CPUFREQ_ENTRY_INVALID is a special symbol which is used to specify that
an entry in the cpufreq table is invalid. But using it outside of the
scope of the cpufreq table looks a bit incorrect.
We can represent an invalid frequency by writing it as 0 instead if we
need. Note that it is already done that way for the return value of the
->get() callback.
Lets do the same for ->fast_switch() and not use CPUFREQ_ENTRY_INVALID
outside of the scope of cpufreq table.
Also update the comment over cpufreq_driver_fast_switch() to clearly
mention what this returns.
None of the drivers return CPUFREQ_ENTRY_INVALID as of now from
->fast_switch() callback and so we don't need to update any of those.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'fs/squashfs/squashfs.h')
0 files changed, 0 insertions, 0 deletions