-
Notifications
You must be signed in to change notification settings - Fork 3k
Make event queue use RTOS tick count #6693
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
Conversation
FYI @kivaisan |
Event queue was using its own Timer or LowPowerTimer objects to derive millisecond tick counts. This is unnecessary in RTOS builds, where the RTOS is maintaining a tick count. It also makes more sense to use the actual RTOS tick count, as the values are being used to compute tick timeouts for RTOS calls. Computing these RTOS tick delays with a separate timer could conceivably lead to rounding errors. Fixes: ARMmbed#5378
@@ -23,7 +23,7 @@ | |||
"value": 256 | |||
}, | |||
"use-lowpower-timer-ticker": { | |||
"help": "Enable use of low power timer and ticker classes. May reduce the accuracy of the event queue.", | |||
"help": "Enable use of low power timer and ticker classes in non-RTOS builds. May reduce the accuracy of the event queue. In RTOS builds, the RTOS tick count is used, and this configuration option has no effect.", |
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.
So is there a "lowpower timer" option for the RTOS? (@bulislaw?)
If so we should probably note that here
@MikeDK fyi |
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.
Looks good to me
/morph build |
Build : SUCCESSBuild number : 1851 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1495 |
Test : SUCCESSBuild number : 1659 |
Description
Event queue was using its own
Timer
orLowPowerTimer
objects to derive millisecond tick counts. This is unnecessary in RTOS builds, where the RTOS is maintaining a tick count.It also makes more sense to use the actual RTOS tick count, as the values are being used to compute tick timeouts for RTOS calls. Computing these RTOS tick delays with a separate timer could conceivably lead to rounding errors.
Fixes: #5378
See also: #6653 and #6698
Pull request type
[ ] Fix
[X] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change