From 6d05dd07f59ef21dc81a299e865cdee1fc1d3f8e Mon Sep 17 00:00:00 2001 From: Kevin O'Connor Date: Mon, 27 Mar 2017 16:38:01 -0400 Subject: sched: Move timer dispatch loop to board code Rename sched_timer_kick() to sched_timer_dispatch() and move its loop into its callers in the board code. This eliminates the need to export timer_try_set_next() from the board code. Signed-off-by: Kevin O'Connor --- docs/Code_Overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/Code_Overview.md') diff --git a/docs/Code_Overview.md b/docs/Code_Overview.md index ee640457..8b1ca06c 100644 --- a/docs/Code_Overview.md +++ b/docs/Code_Overview.md @@ -58,9 +58,9 @@ Timer functions are scheduled by calling sched_add_timer() (located in **src/sched.c**). The scheduler code will arrange for the given function to be called at the requested clock time. Timer interrupts are initially handled in an architecture specific interrupt handler -(eg, **src/avr/timer.c**), but this just calls sched_timer_kick() -located in **src/sched.c**. The timer interrupt leads to execution of -schedule timer functions. Timer functions always run with interrupts +(eg, **src/avr/timer.c**) which calls sched_timer_dispatch() located +in **src/sched.c**. The timer interrupt leads to execution of schedule +timer functions. Timer functions always run with interrupts disabled. The timer functions should always complete within a few micro-seconds. At completion of the timer event, the function may choose to reschedule itself. -- cgit v1.2.3-70-g09d2