Is any fast way exists to know wakeup reason when CPU exit from API POWER_EnterPowerDown() ?
Some power API ?
Or we should analyze pending interrupts from list of uint64_t wakeup_interrupts what were specified ?
Like you mentioned you should analyze pending interrupts in order to know what was.
Hi soledad !
I'm using POWER_EnterPowerDown() on secure side and it called from nonsecure RTOS scheduler hook.
Nonsecure interrupts are disabled but secure not.
GIntx interrupts processed on secure side and when I have exit after POWER_EnterPowerDown(), GINTx
already occurs after 343us ( like in spec) but exit happens after 450 us and GINTx is not pending any more.
It means I should disale all interrupts and they will be not processed so fast as expected.
may be some POWER API can remember reason of last exit ?
Unfortunately, none of the fslpower power functions, from fslpower API is capable to retrieve the wake-up source.
Best regards, Diego.
Retrieving data ...