Re: [PATCH AUTOSEL 5.2 190/249] cpufreq: Avoid calling cpufreq_verify_current_freq() from handle_update()

2019-07-21 Thread Sasha Levin
On Tue, Jul 16, 2019 at 11:25:00AM +0200, Rafael J. Wysocki wrote: On 7/15/2019 3:45 PM, Sasha Levin wrote: From: Viresh Kumar [ Upstream commit 70a59fde6e69d1d8579f84bf4555bfffb3ce452d ] On some occasions cpufreq_verify_current_freq() schedules a work whose callback is handle_update(), which

Re: [PATCH AUTOSEL 5.2 190/249] cpufreq: Avoid calling cpufreq_verify_current_freq() from handle_update()

2019-07-16 Thread Rafael J. Wysocki
On 7/15/2019 3:45 PM, Sasha Levin wrote: From: Viresh Kumar [ Upstream commit 70a59fde6e69d1d8579f84bf4555bfffb3ce452d ] On some occasions cpufreq_verify_current_freq() schedules a work whose callback is handle_update(), which further calls cpufreq_update_policy() which may end up calling cpuf

[PATCH AUTOSEL 5.2 190/249] cpufreq: Avoid calling cpufreq_verify_current_freq() from handle_update()

2019-07-15 Thread Sasha Levin
From: Viresh Kumar [ Upstream commit 70a59fde6e69d1d8579f84bf4555bfffb3ce452d ] On some occasions cpufreq_verify_current_freq() schedules a work whose callback is handle_update(), which further calls cpufreq_update_policy() which may end up calling cpufreq_verify_current_freq() again. On the ot