SDEI: Allow platforms to define explicit events
authorJeenu Viswambharan <jeenu.viswambharan@arm.com>
Wed, 17 Jan 2018 12:30:11 +0000 (12:30 +0000)
committerJeenu Viswambharan <jeenu.viswambharan@arm.com>
Thu, 21 Jun 2018 15:15:23 +0000 (16:15 +0100)
commitaf2c9ecdf1b68c6243f6d23e26d0281d182d3b45
tree9e882f84a86afddca871e75a773fa5b6a7590eec
parent6d769420b098f36717c99d4a6a2455fd6bd8fd23
SDEI: Allow platforms to define explicit events

The current macros only allow to define dynamic and statically-bound
SDEI events. However, there ought be a mechanism to define SDEI events
that are explicitly dispatched; i.e., events that are dispatched as a
result of a previous secure interrupt or other exception

This patch introduces SDEI_EXPLICIT_EVENT() macro to define an explicit
event. They must be placed under private mappings. Only the priority
flags are allowed to be additionally specified.

Documentation updated.

Change-Id: I2e12f5571381195d6234c9dfbd5904608ad41db3
Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>
docs/sdei.rst
include/services/sdei.h
services/std_svc/sdei/sdei_intr_mgmt.c
services/std_svc/sdei/sdei_main.c
services/std_svc/sdei/sdei_private.h