summaryrefslogtreecommitdiffstats
path: root/crypto/aead.c
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>2016-11-22 01:33:20 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-11-22 02:31:49 +0100
commitd5dd33d9de0d50db7f3ba221f9c4e4f74e61a69d (patch)
treee7c131c80841832c05f352d66a6321b521ba425c /crypto/aead.c
parentcpufreq: intel_pstate: round up min_perf limits (diff)
downloadlinux-d5dd33d9de0d50db7f3ba221f9c4e4f74e61a69d.tar.xz
linux-d5dd33d9de0d50db7f3ba221f9c4e4f74e61a69d.zip
cpufreq: intel_pstate: increase precision of performance limits
Even with round up of limits->min_perf and limits->max_perf, in some cases resultant performance is 100 MHz less than the desired. For example when the maximum frequency is 3.50 GHz, setting scaling_min_frequency to 2.3 GHz always results in 2.2 GHz minimum. Currently the fixed floating point operation uses 8 bit precision for calculating limits->min_perf and limits->max_perf. For some operations in this driver the 14 bit precision is used. Using the 14 bit precision also for calculating limits->min_perf and limits->max_perf, addresses this issue. Introduced fp_ext_toint() equivalent to fp_toint() and int_ext_tofp() equivalent to int_tofp() with 14 bit precision. Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'crypto/aead.c')
0 files changed, 0 insertions, 0 deletions