RP2040: Remove incorrect assertion (#508)
After the xEventGroupWaitBits in vProtLockInternalSpinUnlockWithWait there was an assertion about pxYiledSpinLock being NULL, however when xEventGroupWaitBits returns, IRQs have been re-enabled and so it is no longer safe to assert on the state which is protected by IRQs being disabled. Co-authored-by: graham sanderson <graham.sanderson@raspeberryi.com>
This commit is contained in:
parent
d5771a7a60
commit
90d920466e
3
portable/ThirdParty/GCC/RP2040/port.c
vendored
3
portable/ThirdParty/GCC/RP2040/port.c
vendored
@ -742,9 +742,6 @@ __attribute__( ( weak ) ) void vPortSetupTimerInterrupt( void )
|
|||||||
ulYieldSpinLockSaveValue = ulSave;
|
ulYieldSpinLockSaveValue = ulSave;
|
||||||
xEventGroupWaitBits( xEventGroup, prvGetEventGroupBit(pxLock->spin_lock),
|
xEventGroupWaitBits( xEventGroup, prvGetEventGroupBit(pxLock->spin_lock),
|
||||||
pdTRUE, pdFALSE, portMAX_DELAY);
|
pdTRUE, pdFALSE, portMAX_DELAY);
|
||||||
/* sanity check that interrupts were disabled, then re-enabled during the call, which will have
|
|
||||||
* taken care of the yield */
|
|
||||||
configASSERT( pxYieldSpinLock == NULL);
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user