Bluetooth: Call bt_recv from priority higher that TX thread.
A build assert in dummy.c lists the following requirement: [...] receive thread priority shall be higher than the Bluetooth Host's Tx and the Controller's receive thread priority. This is required in order to dispatch Number of Completed Packets event before any new data arrives on a connection to the Host threads. The drivers uses a priority that is equal to the Host TX thread, and since they don't use the CONFIG define that is only available to the controller then this BUILD_ASSERT will not catch the requirement. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
This commit is contained in:
parent
9247e8bc44
commit
9ac8dcf5a7
7 changed files with 14 additions and 17 deletions
|
@ -494,7 +494,7 @@ static int bt_ipm_open(void)
|
|||
k_thread_create(&ipm_rx_thread_data, ipm_rx_stack,
|
||||
K_KERNEL_STACK_SIZEOF(ipm_rx_stack),
|
||||
(k_thread_entry_t)bt_ipm_rx_thread, NULL, NULL, NULL,
|
||||
K_PRIO_COOP(CONFIG_BT_RX_PRIO - 1),
|
||||
K_PRIO_COOP(CONFIG_BT_DRIVER_RX_HIGH_PRIO),
|
||||
0, K_NO_WAIT);
|
||||
|
||||
/* Take BLE out of reset */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue