Bluetooth: controller: split: Fix incorrect mayfly caller id
Fix incorrect ticker/mayfly user id used in scheduling the abort of a radio event. Incorrect use of thread context as the caller caused the abort function to be scheduled from thread context while being called from ULL high context level in reality. This could cause corruption of mayfly scheduling. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
This commit is contained in:
parent
848015854a
commit
8d8d6a7608
1 changed files with 1 additions and 1 deletions
|
@ -896,7 +896,7 @@ void ll_radio_state_abort(void)
|
|||
static struct mayfly mfy = {0, 0, &link, NULL, lll_disable};
|
||||
u32_t ret;
|
||||
|
||||
ret = mayfly_enqueue(TICKER_USER_ID_THREAD, TICKER_USER_ID_LLL, 0,
|
||||
ret = mayfly_enqueue(TICKER_USER_ID_ULL_HIGH, TICKER_USER_ID_LLL, 0,
|
||||
&mfy);
|
||||
LL_ASSERT(!ret);
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue