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:
Vinayak Kariappa Chettimada 2019-10-03 17:49:27 +05:30 committed by Carles Cufí
commit 8d8d6a7608

View file

@ -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);
}