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 ? > A consequence is that any thermal throttling monitoring > and control based on max freq limits fail to respond > in a timely manor, if at all, to a thermal temperature > trip on a busy system. -- viresh
