diff options
author | Michael Turquette <mturquette@baylibre.com> | 2015-07-07 19:24:20 +0100 |
---|---|---|
committer | Vincent Guittot <vincent.guittot@linaro.org> | 2015-07-27 17:59:42 +0200 |
commit | 6d23318179e499ed88ffca8c021212198347897d (patch) | |
tree | 30f7dec504639b93093f8e3a93fd28e2c73f2b32 /include/linux/dmi.h | |
parent | 0a5999b31a8b86cf507b15046ca8d4a4343ada53 (diff) |
cpufreq: introduce cpufreq_driver_might_sleep
Some architectures and platforms perform CPU frequency transitions
through a non-blocking method, while some might block or sleep. This
distinction is important when trying to change frequency from interrupt
context or in any other non-interruptable context, such as from the
Linux scheduler.
Describe this distinction with a cpufreq driver flag,
CPUFREQ_DRIVER_WILL_NOT_SLEEP. The default is to not have this flag set,
thus erring on the side of caution.
cpufreq_driver_might_sleep() is also introduced in this patch. Setting
the above flag will allow this function to return false.
Cc: Rafael J. Wysocki <rafael@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Michael Turquette <mturquette@baylibre.com>
Diffstat (limited to 'include/linux/dmi.h')
0 files changed, 0 insertions, 0 deletions