diff options
| author | Viresh Kumar <[email protected]> | 2019-03-12 10:27:18 +0530 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2019-03-12 09:45:56 +0100 |
| commit | faef080f6db5320011862f7baf1aa66d0851559f (patch) | |
| tree | b86f9f2c93fefe73d4cb7690bf8b0630bf27d390 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 55286a29389a1a30fb2ccc83ef9315809946b365 (diff) | |
PM / OPP: Update performance state when freq == old_freq
At boot up, CPUFreq core performs a sanity check to see if the system is
running at a frequency defined in the frequency table of the CPU. If so,
we try to find a valid frequency (lowest frequency greater than the
currently programmed frequency) from the table and set it. When the call
reaches dev_pm_opp_set_rate(), it calls _find_freq_ceil(opp_table,
&old_freq) to find the previously configured OPP and this call also
updates the old_freq. This eventually sets the old_freq == freq (new
target requested by cpufreq core) and we skip updating the performance
state in this case.
Fix this by also updating the performance state when the old_freq ==
freq.
Fixes: ca1b5d77b1c6 ("OPP: Configure all required OPPs")
Cc: v5.0 <[email protected]> # v5.0
Reported-by: Niklas Cassel <[email protected]>
Tested-by: Jorge Ramirez-Ortiz <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions