Searched refs:events (Results 1 – 7 of 7) sorted by relevance
19 if (ctx->events & SPU_EVENT_RAMACCERR) { in spu_dump_context()23 if (ctx->events & SPU_EVENT_PERIPHACCERR) { in spu_dump_context()27 if (ctx->events & SPU_EVENT_FLASHACCERR) { in spu_dump_context()34 nrf_exc_info.events = spu_events_get(); in nrf_exception_info_store_context()
13 uint32_t events; member
70 uint32_t events = 0; in spu_events_get() local73 events |= SPU_EVENT_RAMACCERR; in spu_events_get()76 events |= SPU_EVENT_FLASHACCERR; in spu_events_get()79 events |= SPU_EVENT_PERIPHACCERR; in spu_events_get()82 return events; in spu_events_get()
13 TF-M enabled systems need to be able to handle asynchronous events (interrupts)
676 - It has a message loop, keep waiting for RPC events.677 - It converts received RPC events into FF-M API call to target services.
44 …events}if(bC){bD=bA[bv];if(bD==null){bD=bA[b.camelCase(bv)]}}else{bD=bA}return bD},removeData:func…
560 | | the critical events, such as the access to critical data. |