bluetooth: fast_pair: fmdn: add uptime workaround to the clock module #21023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
changelog-entry-required
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: f878f9af22af2c41472accd3edd23602c6e1776d more detailssdk-nrf:
Github labels
List of changed files detected by CI (2)Outputs:ToolchainVersion: 4ffa2202d5 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
kapi-no
force-pushed
the
fmdn_clock_nrf54l_uptime_workaround
branch
from
9c4583f to
3298145
Compare
mkapala-nordic
approved these changes
Mar 19, 2025
|
You can find the documentation preview for this PR here. |
MarekPieta
approved these changes
Mar 19, 2025
Added the kernel uptime workaround to the clock module in the FMDN extension that is part of the Fast Pair library. Applied the workaround for the kernel uptime persistence after a system reset. The FMDN clock module assumes that the kernel uptime starts from zero after the system reboot. Activated the workaround only for devices from the nRF54L series that use the GRTC timer as the system clock source (the default configuration). For this configuration, the kernel uptime persists after a system reset if the reset reason is of a specific type, such as a software reset (for example, triggered by the sys_reboot API). Ref: NCSDK-32268 Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
kapi-no
force-pushed
the
fmdn_clock_nrf54l_uptime_workaround
branch
from
3298145 to
f878f9a
Compare
|
MarekPieta
approved these changes
Mar 20, 2025
nordicjm
approved these changes
Mar 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added the kernel uptime workaround to the clock module in the FMDN extension that is part of the Fast Pair library.
Applied the workaround for the kernel uptime persistence after a system reset. The FMDN clock module assumes that the kernel uptime starts from zero after the system reboot.
Activated the workaround only for devices from the nRF54L series that use the GRTC timer as the system clock source (the default configuration). For this configuration, the kernel uptime persists after a system reset if the reset reason is of a specific type, such as a software reset (for example, triggered by the sys_reboot API).
Ref: NCSDK-32268
The following items are planned as a follow-up PR: