Skip to content

Conversation

@nordic-segl
Copy link
Contributor

…alculation

max_stddev calculation was previously patched to be more at least 1 system clock cycle to cover for platforms that use higher frequency system clock (32kHz). On that platform (nRF52) system clock frequency was the same as tick frequency but on nRF54x that is no longer true. Initially, the intention was to use 1 system tick and not cycle. Fixing it now.

(cherry picked from commit 26fe43d)

…alculation

max_stddev calculation was previously patched to be more at least
1 system clock cycle to cover for platforms that use higher frequency
system clock (32kHz). On that platform (nRF52) system clock frequency
was the same as tick frequency but on nRF54x that is no longer true.
Initially, the intention was to use 1 system tick and not cycle.
Fixing it now.

Signed-off-by: Krzysztof Chruściński <[email protected]>
(cherry picked from commit 26fe43d)
@nordic-segl
Copy link
Contributor Author

@nordic-segl
Copy link
Contributor Author

Fixes one test that is currently in the quarantine

09:35:32  INFO    - 1/1 [email protected]/nrf54h20/cpurad tests/kernel/timer/timer_behavior/kernel.timer.timer PASSED (device: 1051164192, 34.676s <zephyr>)
- scenarios:
    - kernel.timer.timer
  platforms:
    - [email protected]/nrf54h20/cpurad
  comment: "https://github.com/zephyrproject-rtos/zephyr/issues/88491"

@nordic-segl nordic-segl requested a review from nordic-krch July 23, 2025 07:38
@rlubos rlubos merged commit ef52a5e into nrfconnect:main Jul 23, 2025
26 of 27 checks passed
@nordic-segl nordic-segl deleted the timer_behavior_max_stddev branch July 23, 2025 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants