-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sched/clock: call up_timer_gettime() to get higher resolution #15139
Conversation
[Experimental Bot, please feedback here] No, this PR does not fully meet the NuttX requirements as described. While it provides a link to prior work and a brief explanation, it lacks crucial details. Here's what's missing:
The PR needs substantial improvement in providing specific details for each of the required sections to meet the NuttX guidelines. |
I have made similar changes before, but the problems are:
|
let us keep moving, @GUIDINGLI please fix the build break |
3b68ae6
to
d959d07
Compare
Signed-off-by: ligd <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
continue work of: apache#15139 Signed-off-by: chao an <[email protected]>
continue work of: apache#15139 Signed-off-by: chao an <[email protected]>
continue work of: #15139 Signed-off-by: chao an <[email protected]>
continue work of: apache#15139 Signed-off-by: chao an <[email protected]>
continue work of: #15139 Signed-off-by: chao an <[email protected]>
Summary
This is continue work of #15038
sched/clock: call up_timer_gettime() to get higher resolution
driver/timers: remove wall clock diff from lower half
Some SOC chipsets use global clock generator to unify the time of each MCU,
that means after MCUs is start-up, the timer will not start counting from 0.
this PR will record the wall timer of global timer and recalculate the ticks.
Impact
N/A
Testing
ci-check