On 18-07-19, 08:46, Doug Smythies wrote: > On 2019.07.18 03:28 Viresh Kumar wrote: > > On 17-07-19, 23:26, Doug Smythies wrote: > >> This reverts commit ecd2884291261e3fddbc7651ee11a20d596bb514. > >> > >> The commit caused a regression whereby reducing the maximum > >> CPU clock frequency is ineffective while busy, and the CPU > >> clock remains unchanged. Once the system has experienced > >> some idle time, the new limit is implemented. > > > > Can you explain why this patch caused that issue ? I am sorry but I couldn't > > understand it from your email. How are we trying to reduce the frequency? Is > > clk_set_rate() getting called with that finally and not working ? > > The patch eliminates the "flag", UNIT_MAX, and it's related comment, > that was used to indicate if it was a limit change that causes the > subsequent execution of sugov_update_single.
I think I may have understood the root cause. Please try the patch I just sent as reply to this thread. Thanks. -- viresh
