Searched hist:af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 (Results 1 – 4 of 4) sorted by relevance
| /rk3399_ARM-atf/include/services/ |
| H A D | sdei.h | af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 Wed Jan 17 12:30:11 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|
| /rk3399_ARM-atf/services/std_svc/sdei/ |
| H A D | sdei_private.h | af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 Wed Jan 17 12:30:11 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|
| H A D | sdei_main.c | af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 Wed Jan 17 12:30:11 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|
| H A D | sdei_intr_mgmt.c | af2c9ecdf1b68c6243f6d23e26d0281d182d3b45 Wed Jan 17 12:30:11 UTC 2018 Jeenu Viswambharan <jeenu.viswambharan@arm.com> 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>
|