-
Notifications
You must be signed in to change notification settings - Fork 2k
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
boards/nrf9160dk: use all available CC timer channels #19771
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I once broke a board config by adding all available CC timer channels here because I failed to notice that one is used to implement timer_read()
. It would be nice if you could add a comment to prevent others from doing the same mistake.
I'm not insisting, though. If you agree, please squash at will and feel free to kick bors.
Signed-off-by: Dylan Laduranty <[email protected]>
6b7b76f
to
ff076fa
Compare
Comment added :) bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
Thanks for the review ! |
Contribution description
nRF9160
has 6 CC per timer.You can
grep -ra "CC_NUM" cpu/nrf9160
to check it.So let's use all available CC.
Testing procedure
You can run
tests/periph/timer
to see the new CC.Issues/PRs references
None.