Searched refs:taskYIELD (Results 1 – 19 of 19) sorted by relevance
178 taskYIELD(); in vTickISR()
179 taskYIELD(); in vPortTickISR()
186 taskYIELD(); in vTickISR()
352 taskYIELD(); in vTickISR()
402 taskYIELD(); in vTickISR()
396 taskYIELD(); in vTickISR()
563 taskYIELD(); in vTickISR()
226 taskYIELD(); in vTickISR()
584 taskYIELD(); in vTickISR()
71 ; SWI interrupt is generated by a call to taskYIELD() or portYIELD().
227 taskYIELD(); in vTickISR()
247 taskYIELD(); in vTickISR()
263 taskYIELD(); in prvTickISR()
426 taskYIELD(); in vPortTickISR()
309 taskYIELD(); in prvTickISR()
586 taskYIELD(); in vTickISR()
201 #define taskYIELD() portYIELD() macro
3514 taskYIELD(); in portTASK_FUNCTION()3531 taskYIELD(); in portTASK_FUNCTION()
1238 the Blocked state, or explicitly calls taskYIELD(). This differs from1245 Blocked state or task A calls taskYIELD(). [If configUSE_PREEMPTION is not3178 + Calls to taskYIELD() during ISR's have been replaced by calling the
