-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Backport v2.9-nRF54H20-branch] pm: Fix to use abs time with policy event funcs #22255
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
[Backport v2.9-nRF54H20-branch] pm: Fix to use abs time with policy event funcs #22255
Conversation
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f6f0fbd8fbb88b13dbf2986d14ebc09b765fd96d more detailssdk-nrf:
zephyr:
Github labels
List of changed files detected by CI (10)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR here. |
Update sdk-zephyr with fixes in PM policy events. Signed-off-by: Krzysztof Chruściński <[email protected]>
Use the new MPSL PM API where event registration and low latency request are handled separately. Signed-off-by: Knut Eldhuset <[email protected]> (cherry picked from commit 233a9e7)
Update pm policy event usage after API was changed from using relative time in cycles to absolute time in ticks. Signed-off-by: Knut Eldhuset <[email protected]> (cherry picked from commit f320b75)
8484cf1
to
f6f0fbd
Compare
cc493a3
into
nrfconnect:v2.9-nRF54H20-branch
Use absolute 64 bit timing values in PM policy events.