You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2020/09/05 16:30:14 UTC

[GitHub] [incubator-nuttx] patacongo edited a comment on pull request #1705: nRF52: refactor system timer handling; support tickless and nontickless using RTC/systick

patacongo edited a comment on pull request #1705:
URL: https://github.com/apache/incubator-nuttx/pull/1705#issuecomment-687632464


   > 
   > 
   > Also, if you look at stm32_oneshot.c, you will find that when the timer expires it is stopped. So I don't really understand how you can use the counter to provide up_timer_gettime after it the "alarm" expires on arch_alarm.c. I feel there's something wrong here.
   
   Of course, it if reset and fired again it wouldn't be a one shot.  The one shot timer was created to support tickless mode operation for the two timer case:  https://cwiki.apache.org/confluence/display/NUTTX/Tickless+OS
   
   The one shot is also used internally to support CPU load measurements with entropy: https://cwiki.apache.org/confluence/display/NUTTX/Oneshot+Timers+and+CPU+Load+Measurement
   
   I don't know all implementations, but normally the oneshot interface is built on top of the timer interface.


----------------------------------------------------------------
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