dejavudwh opened a new issue, #16265: URL: https://github.com/apache/nuttx/issues/16265
### Description From what I can see in the implementation, clock_nanosleep enters sleep via wd_start_abstick and is later woken up in wd_timer. However, wd_timer is triggered by the same timer that handles the OS tick. This means the actual precision of clock_nanosleep depends on the OS tick interval. Is my understanding correct? If so, I’m wondering why this approach was chosen. Why not use a separate timer to handle the wake-up, or, as in Linux, repurpose the timer originally used for the OS tick to be managed by hrtimer, and then emulate the OS tick based on that? Both approaches could help achieve higher precision to some extent. I might be missing something—please correct me if I’m wrong. ### Verification - [x] I have verified before submitting the report. -- 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. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
