[GitHub] [incubator-nuttx] v01d opened a new issue #1704: enforce CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP for SCHED_TICKLESS without alarm

[GitBox <gi...@apache.org>]

v01d opened a new issue #1704:
URL: https://github.com/apache/incubator-nuttx/issues/1704


   Right now, up_timer_start() can be called with a delay that exceeds the maximum allowed one and this will fail silently. There is an option that limits maximum duration of sleeps but this should be always used unless SCHED_TICKLESS_ALARM is defined. This is currently being enforced in arch_timer.c/arch_alarm.c but it should be done already and not require user to select correct configuration (and in fact does not depend on arch_timer/arch_alarm).
   Also, CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP works via a global variable and would be better to implement via standard api call (up_timer_maxdelay?). This way, arch_timer/arch_alarm can implement this by invoking the underlying getmaxtimeout of the timer. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [incubator-nuttx] v01d closed issue #1704: enforce CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP for SCHED_TICKLESS without alarm

[GitBox <gi...@apache.org>]

v01d closed issue #1704:
URL: https://github.com/apache/incubator-nuttx/issues/1704


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org