On Tue, Jul 06, 2021 at 02:07:41PM +0530, Viresh Kumar wrote:

On 06-07-21, 09:12, Vincent Donnefort wrote:

quoted

Of course, I can implement this instead of a cpufreq_policy flag in v4.

Why should this ever be a policy flag and not governor's flag ?

I was referring to how letting know a driver which registers ->target() that we
want or not inefficient frequencies. My proposal was to rely on a
cpufreq_policy's flag that the driver can read. 

-- 
viresh