516cc280e0
If a port defines MICROPY_SOFT_TIMER_TICKS_MS then soft_timer assumes a SysTick back end, and provides a soft_timer_next variable that sets when the next call to soft_timer_handler() should occur. Otherwise, a port should provide soft_timer_get_ms() and soft_timer_schedule_at_ms() with appropriate semantics (see comments). Existing users of soft_timer should continue to work as they did. Signed-off-by: Damien George <damien@micropython.org> |
||
|---|---|---|
| .. | ||
| gchelper.h | ||
| gchelper_generic.c | ||
| gchelper_native.c | ||
| gchelper_thumb1.s | ||
| gchelper_thumb2.s | ||
| interrupt_char.c | ||
| interrupt_char.h | ||
| mpirq.c | ||
| mpirq.h | ||
| pyexec.c | ||
| pyexec.h | ||
| semihosting.c | ||
| semihosting.h | ||
| softtimer.c | ||
| softtimer.h | ||
| stdout_helpers.c | ||
| sys_stdio_mphal.c | ||