Xiang Xiao 6d69439f58 Call xxx_timer_initialize from clock subsystem ... Call xxx_timer_initialize from clock subsystem to make timer ready for use as soon as possiblei and revert the workaround: commit 0863e771a9 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Apr 26 07:24:57 2019 -0600 Revert "sched/clock/clock_initialize.c: clock_inittime() needs to be done with CONFIG_SCHED_TICKLESS and clock_initialize should skip clock_inittime() for external RTC case since the RTC isn't ready yet." This reverts commit 2bc709d4b9. Commit 2bc709d4b9 was intended to handle the case where up_timer_gettime may not start from zero case. However, this change has the side-effect of breaking every implementation of tickless mode: After this change the tickless timer structures are used before they are initialized in clock_inittime(). Initialization happens later when up_initialize is called() when arm_timer_initialize(). Since the tickless mode timer is very special, one solution might be to 1. Rename xxx_timer_initialize to up_timer_initialize 2 Move up_timer_initialize to include/nuttx/arch.h 3. Call it from clock subsystem instead up_initialize Basically, this change make timer initialization almost same as rtc initialization(up_rtc_initialize). For now, however, we just need to revert the change.		2020-02-08 07:40:06 -06:00
..
drivers	boards/: Move more drivers directories at were placed too high in the hieararchy.	2019-08-24 14:42:14 -06:00
esp32-core	Call xxx_timer_initialize from clock subsystem	2020-02-08 07:40:06 -06:00