[nrf fromlist] drivers: timer: nrf_grtc_timer: Optimize to reduce reg… #3344
+62
−31
Conversation
This file contains hidden or 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
Contributor
Author
|
|
Contributor
Author
|
Removing |
Contributor
Author
|
It is another attempt to get those optimizations in after #3059 got reverted. It was reverted because it broke GRTC on cpusec which is not fixed. |
nordic-krch
force-pushed
the
ncs/grtc_opt
branch
from
47e8a67 to
1ad606f
Compare
kl-cruz
approved these changes
Oct 6, 2025
adamkondraciuk
approved these changes
Oct 6, 2025
nordic-krch
force-pushed
the
ncs/grtc_opt
branch
2 times, most recently
from
e811edb to
4ce6e81
Compare
…ister access Speed up execution of the interrupt handler and sys_clock_set_timeout(). Sys_clock_set_timeout() can be called in two scenarios: from previous timeout expiration handler or freely. If the former case fast path can be used since CC value in the GRTC register just expired and it can be used as a reference for CCADD setting. This is only a single register write so it's much faster. In the latter a longer procedure is applied which also happens in two variants. If value which is set in CC is further in the future (e.g. K_FOREVER was set before) then CC can be safely overwritten with a new value without a risk of triggering unexpected COMPARE event. If value in CC is earlier than the new CC value (if earlier timeout was aborted) then there is a risk of COMPARE event happening while it is being overwritten. That case requires long and safer procedure of setting CC. Update hal_nordic with changes in the nrfx_grtc driver which are needed for nrf_grtc_timer changes. Signed-off-by: Krzysztof Chruściński <[email protected]> (cherry picked from commit d6fb9384ebfbb46a3cb65213257a61651a76fd7c)
…20 PPR Adjusting CONFIG_SYS_CLOCK_TICKS_PER_SEC as core is to slow too run the test with the default system clock frequency. Signed-off-by: Paweł Pelikan <[email protected]> (cherry picked from commit fddce23e03021bfb6cac6e259c58b64ecc6b5775)
nordic-krch
force-pushed
the
ncs/grtc_opt
branch
from
4ce6e81 to
7085c5a
Compare
anangl
approved these changes
Nov 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
…ister access
Speed up execution of the interrupt handler and sys_clock_set_timeout(). Sys_clock_set_timeout() can be called in two scenarios: from previous timeout expiration handler or freely. If the former case fast path can be used since CC value in the GRTC register just expired and it can be used as a reference for CCADD setting. This is only a single register write so it's much faster. In the latter a longer procedure is applied which also happens in two variants. If value which is set in CC is further in the future (e.g. K_FOREVER was set before) then CC can be safely overwritten with a new value without a risk of triggering unexpected COMPARE event. If value in CC is earlier than the new CC value (if earlier timeout was aborted) then there is a risk of COMPARE event happening while it is being overwritten. That case requires long and safer procedure of setting CC.
Update hal_nordic with changes in the nrfx_grtc driver which are needed for nrf_grtc_timer changes.
Upstream PR #: 87944