d0958995a3
In the BAP Broadcast Sink implementation the sync request, the BIGInfo and the broadcast code can come in any other. Currently the btp_bap_broadcast_sink_bis_sync would reject the request if it came before the BIGInfo, but will now instead store the request and then apply it once the BIGInfo has been received, as there is not BIGInfo BTP event that the caller can use. Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| addr | ||
| adv | ||
| at | ||
| audio | ||
| bluetooth | ||
| bt_crypto | ||
| bt_crypto_ccm | ||
| buf | ||
| classic | ||
| common/testlib | ||
| controller | ||
| df | ||
| gap | ||
| gatt | ||
| hci | ||
| hci_codecs_info | ||
| hci_prop_evt | ||
| hci_uart_async | ||
| host | ||
| host_config_variants | ||
| host_long_adv_recv | ||
| init | ||
| l2cap | ||
| mesh | ||
| mesh_shell | ||
| qualification | ||
| shell | ||
| smp | ||
| tester | ||
| uuid | ||