Re: [PATCH] cpufreq: flush any pending policy update work scheduled before freeing

From: Rafael J. Wysocki
Date: Fri Oct 18 2019 - 04:19:15 EST

On Fri, Oct 18, 2019 at 10:03 AM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> On 18-10-19, 09:32, Rafael J. Wysocki wrote:
> > Well, the policy is going away, so the governor has been stopped for
> > it already. Even if the limit is updated, it will not be used anyway,
> > so why bother with updating it?
> The hardware will be programmed to run on that frequency before the
> policy exits,

How exactly?

The policy is inactive, so refresh_frequency_limits() won't even run
cpufreq_set_policy() for it.

> so I will say it will be used and the constraint will be
> satisfied. And so I had that view.