Skip to content
Commit 5d7d6e0a authored by Prasad Sodagudi's avatar Prasad Sodagudi
Browse files

clockevents: Update clockevents device next_event



Usually clockevent device's next_event is updated in
clockevents_program_event() and next_event indicates
the next timer event on that cpu. Whenever there are
no timers on a CPU, corresponding clockevent device
is going into ONESHOT_STOPPED state but clockevent
device next_event is not updated, because
clockevents_program_event() not called.

As next_event is not updated properly, resulting in spurious
wakeups, so update the clockevent device next_event
with proper value(KTIME_MAX) to avoid spurious wakeups.

Change-Id: I942e884583097c52da52a80bee31d4823173d520
Signed-off-by: default avatarPrasad Sodagudi <psodagud@codeaurora.org>
parent 3fafba6f
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment