Bluetooth: Controller: Switch to controller-side RX thread
Since the controller already uses a thread for receiving data it makes sense to enable the BLUETOOTH_RECV_IS_RX_THREAD option. Change-Id: I927b20c1a0afaea8d000df28cc220a69ae817d59 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
533d544d95
commit
88b620550c
3 changed files with 2 additions and 10 deletions
|
@ -47,6 +47,7 @@ if BLUETOOTH_HCI
|
|||
|
||||
config BLUETOOTH_CONTROLLER
|
||||
bool "Bluetooth Controller"
|
||||
select BLUETOOTH_RECV_IS_RX_THREAD
|
||||
help
|
||||
Enables support for SoC native controller implementation.
|
||||
|
||||
|
|
|
@ -34,15 +34,6 @@ config BLUETOOTH_CONTROLLER_TX_BUFFER_SIZE
|
|||
Maximum is set to 16384 due to implementation limitations (use of
|
||||
uint16_t for size/length variables).
|
||||
|
||||
config BLUETOOTH_CONTROLLER_RX_STACK_SIZE
|
||||
int "Size of the receiving thread stack"
|
||||
default 512
|
||||
range 512 65536
|
||||
help
|
||||
Size of the receiving thread stack. This is the context from
|
||||
which all radio messages are encoded into HCI events or data
|
||||
before passing it to Bluetooth receiving thread.
|
||||
|
||||
comment "BLE Controller features"
|
||||
|
||||
config BLUETOOTH_CONTROLLER_LE_PING
|
||||
|
|
|
@ -75,7 +75,7 @@ static uint8_t MALIGN(4) _radio[LL_MEM_TOTAL];
|
|||
|
||||
static K_SEM_DEFINE(sem_recv, 0, UINT_MAX);
|
||||
static BT_STACK_NOINIT(recv_thread_stack,
|
||||
CONFIG_BLUETOOTH_CONTROLLER_RX_STACK_SIZE);
|
||||
CONFIG_BLUETOOTH_RX_STACK_SIZE);
|
||||
|
||||
K_MUTEX_DEFINE(mutex_rand);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue