Jeenu Viswambharan 90a9213bfb SDEI: Unconditionally resume Secure if it was interrupted ... Secure world execution nearly always expect a controlled exit to Non-secure world. SDEI interrupts, although targets EL3, occur on behalf of Non-secure world, and may have higher priority than Secure world interrupts. Therefore they might preempt Secure execution, and yield execution to Non-secure SDEI handler. Upon completion of SDEI event handling (regardless of whether it's COPLETE or COMPLETE_AND_RESUME), we must resume Secure execution if it was preempted. Change-Id: I6edd991032588588427ba2fe6c3d7668f7080e3d Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>		2018-11-26 11:22:32 +00:00
..
sdei_dispatch.S	SDEI: Make dispatches synchronous	2018-06-21 16:15:23 +01:00
sdei_event.c	SDEI: MISRA fixes	2018-08-20 09:05:39 +01:00
sdei_intr_mgmt.c	SDEI: Unconditionally resume Secure if it was interrupted	2018-11-26 11:22:32 +00:00
sdei_main.c	SDEI: Mask events after CPU wakeup	2018-09-07 08:42:50 +01:00
sdei_private.h	sdei: include "context.h" to fix compilation errors	2018-10-30 17:07:39 -07:00
sdei_state.c	SDEI: MISRA fixes	2018-08-20 09:05:39 +01:00