Bluetooth: Controller: Fix filtering data status for Periodic report
Fix missing implementation to use correct data status when detecting duplicate Periodic Advertising Report data. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
This commit is contained in:
parent
5829863460
commit
88bc1d790c
1 changed files with 7 additions and 4 deletions
|
@ -6381,20 +6381,23 @@ no_ext_hdr:
|
|||
} else if (IS_ENABLED(CONFIG_BT_CTLR_SYNC_PERIODIC_ADI_SUPPORT) &&
|
||||
adi) {
|
||||
const struct ll_sync_set *sync = HDR_LLL2ULL(ftr->param);
|
||||
uint8_t data_status;
|
||||
|
||||
data_status = (aux_ptr) ?
|
||||
BT_HCI_LE_ADV_EVT_TYPE_DATA_STATUS_PARTIAL :
|
||||
BT_HCI_LE_ADV_EVT_TYPE_DATA_STATUS_COMPLETE;
|
||||
|
||||
/* FIXME: Use correct data status else chain PDU report will
|
||||
* be filtered out.
|
||||
*/
|
||||
accept = ftr->sync_rx_enabled &&
|
||||
(!sync->nodups ||
|
||||
!dup_found(PDU_ADV_TYPE_EXT_IND,
|
||||
sync->peer_id_addr_type,
|
||||
sync->peer_id_addr,
|
||||
DUP_EXT_ADV_MODE_PERIODIC,
|
||||
adi, 0U));
|
||||
adi, data_status));
|
||||
#endif /* CONFIG_BT_CTLR_DUP_FILTER_LEN > 0 &&
|
||||
* CONFIG_BT_CTLR_SYNC_PERIODIC_ADI_SUPPORT
|
||||
*/
|
||||
|
||||
} else {
|
||||
accept = ftr->sync_rx_enabled;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue