The cpufreq_schedutil governor keeps a cache of the last raw frequency that was mapped to a supported device frequency. If the next request for a frequency matches the cached value, the policy's next_freq value is reused. But there are paths that can update the raw cached value without updating the next_freq value, and there are paths that can set the next_freq value without setting the raw cached value. On those paths, the cached value must be reset. The case that has been observed is when a frequency request reaches sugov_update_commit but is then rejected by to the sugov_up_down_rate_limit check. Bug: 116279565 Change-Id: I7c585339a04ff1732054d6e5b36a57e2d41266aa Signed-off-by: John Dias <joaodias@google.com> Signed-off-by: Miguel de Dios <migueldedios@google.com> Signed-off-by: Alexander Winkowski <dereference23@outlook.com>fourteen
parent
aa6676efa5
commit
977116cf8b
Loading…
Reference in new issue