Bluetooth: conn: Switch order of tx_notify & tx_queue
In case both conn->tx_notify and conn->tx_queue have data in them we should first process the notify queue and only then new outgoing packets. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
b56768b626
commit
baf4f0c912
1 changed files with 4 additions and 4 deletions
|
@ -1303,14 +1303,14 @@ int bt_conn_prepare_events(struct k_poll_event events[])
|
|||
k_poll_event_init(&events[ev_count],
|
||||
K_POLL_TYPE_FIFO_DATA_AVAILABLE,
|
||||
K_POLL_MODE_NOTIFY_ONLY,
|
||||
&conn->tx_queue);
|
||||
events[ev_count++].tag = BT_EVENT_CONN_TX_QUEUE;
|
||||
&conn->tx_notify);
|
||||
events[ev_count++].tag = BT_EVENT_CONN_TX_NOTIFY;
|
||||
|
||||
k_poll_event_init(&events[ev_count],
|
||||
K_POLL_TYPE_FIFO_DATA_AVAILABLE,
|
||||
K_POLL_MODE_NOTIFY_ONLY,
|
||||
&conn->tx_notify);
|
||||
events[ev_count++].tag = BT_EVENT_CONN_TX_NOTIFY;
|
||||
&conn->tx_queue);
|
||||
events[ev_count++].tag = BT_EVENT_CONN_TX_QUEUE;
|
||||
}
|
||||
|
||||
return ev_count;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue