Increase STM32 default deep sleep latency to 4ms #11767
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (required)
Recent measurements have shown that the total wake-up latency can be more
than the 3ms initially set. It was measured as 3,7ms on DISCO_L475VG_IOT01A
target and 3,1ms on NUCLEO_L073RZ target. So set it to 4ms to be on the
safe side.
Summary of change (What the change is for and why)
The change better reflects the reality of the actual latency and will allows mbed-os OS to schedule
more precisely the wake-up timings.
Documentation (Details of any document updates required)
No specific documentation update needed.
Pull request type (required)
Test results (required)
Note that this patch actually will fix the initial issue raised in #11545
Reviewers (optional)
@jeromecoutant @ABOSTM @TuomoHautamaki @kjbracey-arm