Skip to content

call ble_gap_event_listener_call for every ble_gap_notify_tx_event#671

Merged
andrzej-kaczmarek merged 1 commit intoapache:masterfrom
HendrikVE:gap_event_listener_notify_tx
Nov 20, 2019
Merged

call ble_gap_event_listener_call for every ble_gap_notify_tx_event#671
andrzej-kaczmarek merged 1 commit intoapache:masterfrom
HendrikVE:gap_event_listener_notify_tx

Conversation

@HendrikVE
Copy link
Copy Markdown
Contributor

This PR adds a call to the listener for notify_tx only, but it might be desirable to also catch some other events.

As discussed on slack, it is needed to get the notification transmitted event with a listener
registered by ble_gap_event_listener_register to be able to chain ble notifications.
If there are two different modules on different application levels and both are using nimble, then it is not possible for the lower-level module to register a "feature-complete" callback via ble_gap_adv_start, because this function should only be called by the higher-level module, because it knows, when the application is ready for advertising.

Needed to get the notification transmitted event with a listener
registered by ble_gap_event_listener_register to be able to chain
ble notifications.
If there are two different modules on different application levels
and both are using nimble, then it is not possible for the
lower-level module to register a "feature-complete" callback via
ble_gap_adv_start, because this function should only be called
by the higher-level module, because it knows, when the application
is ready for advertising.
@andrzej-kaczmarek andrzej-kaczmarek merged commit c84464d into apache:master Nov 20, 2019
@HendrikVE HendrikVE deleted the gap_event_listener_notify_tx branch November 20, 2019 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants