Re: [PATCH 0/2] allow cpufreq drivers to export flags

From: Viresh Kumar
Date: Wed Oct 08 2014 - 03:54:39 EST

On 8 October 2014 13:18, Mike Turquette <mturquette@xxxxxxxxxx> wrote:
> This series is partially in response to a discussion around DT bindings
> for CPUfreq drivers [0], but it is also needed for on-going work to
> integrate CPUfreq with the scheduler. In particular a scheduler-driven
> cpu frequency scaling policy would be well served to know if the
> underlying CPUfreq driver .target callback might sleep or block for a
> long time.
> [0]<fcb88cd21f31a467d2d49911c2505082837f72ea.1410323179.git.viresh.kumar@xxxxxxxxxx>

Firstly this link is broken and then the last comment I gave in Thomas's
thread was that he doesn't need this routine anymore. And so your scheduler
work is the only user of it.. And so probably we should get this included with
the scheduler patches only, isn't it? Just including them without any user
wouldn't benefit..

Or am I missing something ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at