Ken, thanks for the reply.

 

My take on that is that instead of adding overhead to ISR, ISR should be executed fast.

For ISRs we should publish clear guidelines that explain potential side effects of ISR execution.

 

These guidelines should advocate that ISR is kept short, and workload is off-loaded to thread execution.

How this is exactly done in secure side needs to be defined, as the RTOS (on non-secure side) might inconsistent and not be available.

 

What would be really good is to have typical ISR routines that execute in secure side.  This would better allow us to judge what is really needed. I believe most of them are small anyway.

 

Reinhard

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.