-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
introduce NRF and BLE drivers #4448
Conversation
|
601953e
to
87610cc
Compare
// If the message is already sent or the id is not found, it does nothing and | ||
// returns false If the message is queued, it will be removed from the queue If | ||
// the message is being sent, it will be sent. The callback will not be called. | ||
bool nrf_abort_msg(int32_t id); |
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.
Aborting messages introduces a bunch of complexity into the queue code, where are we even going to use it?
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.
Probably will when going to low power modes, there will also be other services that might need that. cc also @cepetr
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.
nothing else from me
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.
utACK
f5a0f84
to
aac111f
Compare
ed61578
to
a2622a6
Compare
[no changelog]
[no changelog]
[no changelog]
[no changelog]
a2622a6
to
d4bf0e8
Compare
This PR introduces NRF driver, responsible for handling communication with NRF, and BLE driver, which provides interface for using BLE via the NRF.