{"push_id":705388780,"size":2,"distinct_size":2,"ref":"refs/heads/lp5.1","head":"a7ff3a74b38eb2f0ec251db7f3d7de3d67e6ab7d","before":"2132f130fb12d8e0329f18d628eb653c3f0b1dc6","commits":[{"sha":"bd72108d1f32b0befe741f4ea131c24292e48095","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Record hispeed_validated_time in timer function\n\nChange 0cd554ae585f5ccbb95056e049a8fec0f0742dce\n(cpufreq: interactive: Exercise hispeed settings at a policy level)\nintroduced policy level hispeed settings. The change is correct in\ngeneral, but it sets hispeed_validate_time after actual frequency\nchange has completed. Waking up speedchange task and setting\nfrequency takes non-trival amount of time. This period is not accounted\nfor in above_hispeed_delay, resulting in additional delays when\nramping up frequency. Frequency switch latency varies a lot\ndepending on beginning and end frequency, and thus it cannot be easily\ncompensated by user setting above_hispeed_delay.\n\nRecord a local hispeed_validated_time in every CPU's timer function.\nCluster hispeed_validated_time is the local hispeed_validated_time of\nCPUs voting for the highest frequency.\n\nChange-Id: Id8ae547fe3a70f8710f60b6e2125954111b7a2b6\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/AICP/kernel_google_msm/commits/bd72108d1f32b0befe741f4ea131c24292e48095"},{"sha":"a7ff3a74b38eb2f0ec251db7f3d7de3d67e6ab7d","author":{"email":"0e192bfc10239b7cf88fa9a9633350ffa6e30867@gmail.com","name":"doc HD"},"message":"Merge \"cpufreq: interactive: Record hispeed_validated_time in timer function\" into lp5.1","distinct":true,"url":"https://api.github.com/repos/AICP/kernel_google_msm/commits/a7ff3a74b38eb2f0ec251db7f3d7de3d67e6ab7d"}]}