summaryrefslogtreecommitdiff
path: root/.gitattributes
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2021-04-07 16:21:55 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2021-04-09 17:16:12 +0200
commitb989bc0f3cf24122ec700e66eb8ffb93432f18c5 (patch)
tree5a67d45e836c9533ea72bdc32c93f7734a457723 /.gitattributes
parent60943bbdb42e966aa4d50d587913721b95208fef (diff)
cpufreq: intel_pstate: Simplify intel_pstate_update_perf_limits()
Because pstate.max_freq is always equal to the product of pstate.max_pstate and pstate.scaling and, analogously, pstate.turbo_freq is always equal to the product of pstate.turbo_pstate and pstate.scaling, the result of the max_policy_perf computation in intel_pstate_update_perf_limits() is always equal to the quotient of policy_max and pstate.scaling, regardless of whether or not turbo is disabled. Analogously, the result of min_policy_perf in intel_pstate_update_perf_limits() is always equal to the quotient of policy_min and pstate.scaling. Accordingly, intel_pstate_update_perf_limits() need not check whether or not turbo is enabled at all and in order to compute max_policy_perf and min_policy_perf it can always divide policy_max and policy_min, respectively, by pstate.scaling. Make it do so. While at it, move the definition and initialization of the turbo_max local variable to the code branch using it. No intentional functional impact. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Tested-by: Chen Yu <yu.c.chen@intel.com>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions