diff options
author | Jeenu Viswambharan <jeenu.viswambharan@arm.com> | 2018-01-17 12:30:11 +0000 |
---|---|---|
committer | Jeenu Viswambharan <jeenu.viswambharan@arm.com> | 2018-06-21 16:15:23 +0100 |
commit | af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 (patch) | |
tree | 9e882f84a86afddca871e75a773fa5b6a7590eec /bl31/bl31.mk | |
parent | 6d769420b098f36717c99d4a6a2455fd6bd8fd23 (diff) | |
download | trusted-firmware-a-af2c9ecdf1b68c6243f6d23e26d0281d182d3b45.tar.gz |
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>
Diffstat (limited to 'bl31/bl31.mk')
0 files changed, 0 insertions, 0 deletions