Bluetooth: Controller: Stop following aux ptr if DATA_LEN_MAX is hit
If the aux scanner already has CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX advertising data, there is no point in following an aux ptr - instead flush the data and produce an incomplete report Signed-off-by: Troels Nilsson <trnn@demant.com>
This commit is contained in:
parent
bdeb62d116
commit
e0370f5439
1 changed files with 4 additions and 0 deletions
|
@ -537,6 +537,10 @@ void ull_scan_aux_setup(memq_link_t *link, struct node_rx_hdr *rx)
|
|||
|
||||
} else {
|
||||
aux->data_len += data_len;
|
||||
|
||||
if (aux->data_len >= CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX) {
|
||||
goto ull_scan_aux_rx_flush;
|
||||
}
|
||||
}
|
||||
|
||||
/* In sync context we can dispatch rx immediately, in scan context we
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue