OSDN Git Service

cpufreq: Fix initialization of min and max frequency QoS requests
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 16 Dec 2021 19:32:15 +0000 (20:32 +0100)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Fri, 17 Dec 2021 15:45:53 +0000 (16:45 +0100)
commit521223d8b3ec078f670c7c35a1a04b1b2af07966
tree7f637d8e9a7ed48546d4c2bf0bd7492375965fdc
parentb6e6f8beec98ba7541213c506fe908517fdc52b8
cpufreq: Fix initialization of min and max frequency QoS requests

The min and max frequency QoS requests in the cpufreq core are
initialized to whatever the current min and max frequency values are
at the init time, but if any of these values change later (for
example, cpuinfo.max_freq is updated by the driver), these initial
request values will be limiting the CPU frequency unnecessarily
unless they are changed by user space via sysfs.

To address this, initialize min_freq_req and max_freq_req to
FREQ_QOS_MIN_DEFAULT_VALUE and FREQ_QOS_MAX_DEFAULT_VALUE,
respectively, so they don't really limit anything until user
space updates them.

Reported-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Tested-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/cpufreq.c