Bluetooth: controller: Fix cond. mayfly priority check
When the controller is configured to have its worker and job be run at different interrupt priority, check for mayfly priority being equal was incorrect. Fixed by conditionally compiling the correct check of mayfly priority level. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
This commit is contained in:
parent
9dc7975b76
commit
88dba0dd35
1 changed files with 4 additions and 0 deletions
|
@ -106,11 +106,15 @@ u32_t mayfly_is_enabled(u8_t caller_id, u8_t callee_id)
|
|||
|
||||
u32_t mayfly_prio_is_equal(u8_t caller_id, u8_t callee_id)
|
||||
{
|
||||
#if (RADIO_TICKER_USER_ID_WORKER_PRIO == RADIO_TICKER_USER_ID_JOB_PRIO)
|
||||
return (caller_id == callee_id) ||
|
||||
((caller_id == MAYFLY_CALL_ID_0) &&
|
||||
(callee_id == MAYFLY_CALL_ID_1)) ||
|
||||
((caller_id == MAYFLY_CALL_ID_1) &&
|
||||
(callee_id == MAYFLY_CALL_ID_0));
|
||||
#else
|
||||
return caller_id == callee_id;
|
||||
#endif
|
||||
}
|
||||
|
||||
void mayfly_pend(u8_t caller_id, u8_t callee_id)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue