diff options
| author | Tim Sell <[email protected]> | 2016-06-10 21:48:08 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-08-15 20:44:24 +0200 |
| commit | 9ebab64952237f7b9b263d6dc0cdf31e83a2d5e7 (patch) | |
| tree | 98987dcb9aba3bdb27ab20e053fee6749f0dea96 /tools/perf/scripts/python | |
| parent | 83011b6cbe7c597c73b31c41021dc71f78dcef7b (diff) | |
staging: unisys: visorbus: use kernel timer instead of workqueue
A kernel timer is now used as the vehicle to periodically call the
channel_interrupt function of registered visor drivers, instead of a
workqueue.
This simplifies a lot of things by making periodic_work.c and
periodic_work.h no longer necessary. This change also means that the
channel_interrupt() callbacks registered by visor drivers (via
visorbus_register_visor_driver()) will now be called in atomic context
(i.e., canNOT sleep) rather than kernel thread context (CAN sleep).
Fortunately this did NOT necessitate any change to the existing
channel_interrupt() callbacks, because none of them ever perform any
operations that would be invalid in atomic context.
Signed-off-by: Tim Sell <[email protected]>
Signed-off-by: David Kershner <[email protected]>
Acked-By: Neil Horman <[email protected]>
Reviewed-by: Thomas Gleixner <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions