Skip to content

drivers: timer: nrf_rtc_timer: Allow use of custom bit width #92025

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mstasiaknordic
Copy link
Contributor

Allowed use of counter bit width lower than hardware 24. In that case, PPI connection is established to trigger clear task once maximum value is reached.

@bjarki-andreasen
Copy link
Contributor

Out of curiosity, what usecases are there for artificially lowering the counters bit widht? Only effect I can think of is more frequent wakeups to account for rollover, which would be worse for power consumption :)

@mstasiaknordic mstasiaknordic force-pushed the rtc_custom_bitwidth branch 3 times, most recently from d40e414 to 35cf7eb Compare July 2, 2025 08:31
Allowed use of counter bit width lower than hardware 24.
In that case, PPI connection is established to trigger
clear task once maximum value is reached.

Signed-off-by: Michał Stasiak <michal.stasiak@nordicsemi.no>
Added overlay for the board.

Signed-off-by: Michał Stasiak <michal.stasiak@nordicsemi.no>
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants