-
Notifications
You must be signed in to change notification settings - Fork 3k
Nuvoton: Enlarge LPTICKER_DELAY_TICKS for safe #11021
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
Nuvoton: Enlarge LPTICKER_DELAY_TICKS for safe #11021
Conversation
On Nuvoton targets, lp_ticker_set_interrupt(...) needs around 3 lp-ticker ticks to take effect. It may miss when current tick and match tick are very close (see hal/LowPowerTickerWrapper.cpp). Enlarge LPTICKER_DELAY_TICKS to 4 from 3 to address this boundary case.
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.
On Nuvoton targets, lp_ticker_set_interrupt(...) needs around 3 lp-ticker ticks to take effect. It may miss when current tick and match tick are very close (see hal/LowPowerTickerWrapper.cpp). Enlarge LPTICKER_DELAY_TICKS to 4 from 3 to address this boundary case.
👍 what I asked in your earlier PR for deepsleep , this one to be there as well
Any update? |
Ci started |
Test run: FAILEDSummary: 2 of 11 test jobs failed Failed test jobs:
|
CI restarted |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
Tracking issue for exporters failure: #11209 |
CI restarted |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
On Nuvoton targets,
lp_ticker_set_interrupt(...)
needs around 3 lp-ticker ticks to take effect. It may miss when current tick and match tick are very close (see hal/LowPowerTickerWrapper.cpp). This PR enlargesLPTICKER_DELAY_TICKS
to 4 from 3 to address this boundary case.Pull request type