-
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
nanocoap: implement extended tokens (RFC 8974) #19487
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.
💪
3ffac49
to
3bc5a43
Compare
Unless there's any hurry, plz hold merging, I'd like to review.
|
fa56b4d
to
1ce7121
Compare
As this would needlessly add 348 bytes of ROM even when not used, I hid it behind a |
1ce7121
to
c01c470
Compare
bors merge |
19487: nanocoap: implement extended tokens (RFC 8974) r=benpicco a=benpicco 19781: cpu/nrf{53,9160}: add pwm support r=benpicco a=dylad ### Contribution description This PR moves the nRF52 PWM driver to `cpu/nrf5x_common` to allow nRF9160 and nRF53 to use this driver. IP is identical on these families. I didn't test on nRF9160DK and I didn't test if there is any regression on nRF52-based board as I don't have any so tests are welcome ! However it works fine on nRF53-based board. ### Testing procedure Flash the `tests/periph/pwm` test application on `nrf5340dk` or `nrf9160dk`. You can then use the `osci` command to make the onboard LEDs "breath". You can also attach an oscilloscope and/or logic analyzer to watch the signal. ### Issues/PRs references ~~Based on #19769~~ Co-authored-by: Benjamin Valentin <benpicco@beuth-hochschule.de> Co-authored-by: Dylan Laduranty <dylan.laduranty@mesotic.com>
Build failed (retrying...): |
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. |
Contribution description
RFC8974 allows for token length of up to 65804 Byte in order to store Client state in the token.
This is easy to implement in nanoCoAP, so let's give it a try.
Testing procedure
Currently no use case is associated with this, but I extended the unit test.
Maybe we should only enable this when a pseudo-module
nanocoap_token_ext
is used.Issues/PRs references