diff options
author | John Tsichritzis <john.tsichritzis@arm.com> | 2019-05-28 11:53:58 +0000 |
---|---|---|
committer | TrustedFirmware Code Review <review@review.trustedfirmware.org> | 2019-05-28 11:53:58 +0000 |
commit | 89a4d269146c90e944ea36d4afb39b27d82b23e2 (patch) | |
tree | 9d9931b4515026e0030bf4841897c2513171906e /docs/components/sdei.rst | |
parent | 508a48bb32bd205e40c6203b0551c9e2f289257d (diff) | |
parent | 566d15e84aefb63f33933934059e024008ae70ad (diff) |
Merge "Fix documentation links" into integration
Diffstat (limited to 'docs/components/sdei.rst')
-rw-r--r-- | docs/components/sdei.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/components/sdei.rst b/docs/components/sdei.rst index 845a2955..6d0e1563 100644 --- a/docs/components/sdei.rst +++ b/docs/components/sdei.rst @@ -41,7 +41,7 @@ execute the registered handler [10]. The client terminates its execution with original EL2 execution [13]. Note that the SDEI interrupt remains active until the client handler completes, at which point EL3 does EOI [12]. -Other than events bound to interrupts (as depicted in the sequence above, SDEI +Other than events bound to interrupts, as depicted in the sequence above, SDEI events can be explicitly dispatched in response to other exceptions, for example, upon receiving an *SError* or *Synchronous External Abort*. See `Explicit dispatch of events`_. @@ -370,3 +370,4 @@ implemented in assembly, following a similar pattern as below: .. _SDEI specification: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf .. _SDEI porting requirements: ../getting_started/porting-guide.rst#sdei-porting-requirements +.. _Software Delegated Exception Interface: `SDEI specification`_ |