Here is possible solutions I’ve tried:
I don’t think I understand the problem this is intended to be a solution to.
Which port are you using?
If you are using the Cortex-M port then an interrupt will unblock the task, so if the event you are waiting for comes from an interrupt (a reasonable assumption as the CPU is not running any code when it is in low power mode) then it will unblock in order to process the interrupt – and so not miss the event.
This is not a proper solution because this makes the tick count incorrect.
If you are using the Cortex-M port, or you have created your own following the examples, then the tick count will be corrected for whatever the time is when the suppress ticks and sleep function exits.
Thus I think this condition need a feature like wake lock that if some process acquire
wake lock then the system won’t enter sleep. Is there a elegant way to achieve this
feature without rewrite vPortSuppressTicksAndSleep or portTASK_FUNCTION()?
That is what the existing configPRESLEEP
PROCESSING macro allows you to do.