commit e31d76fd1699427ad19acbebbf6f9c00b80772b8
author Jeenu Viswambharan <jeenu.viswambharan@arm.com> Wed Oct 18 14:30:53 2017 +0100
committer Jeenu Viswambharan <jeenu.viswambharan@arm.com> Mon Nov 26 11:22:32 2018 +0000
tree cc6f3c38f70b4b7a83ca16efe58e90a7a4b98663
parent 90a9213bfbb53366152f8030e4fc4b162c23ac04

docs: Add Exception Handling Framework documentation

Change-Id: I77d38758d18ba6dda1652b1b1e644fbfb14386cc
Signed-off-by: Jeenu Viswambharan <jeenu.viswambharan@arm.com>

docs/interrupt-framework-design.rst

diff --git a/docs/interrupt-framework-design.rst b/docs/interrupt-framework-design.rst
index b5c7d21..4247f1f 100644
--- a/docs/interrupt-framework-design.rst
+++ b/docs/interrupt-framework-design.rst
@@ -153,7 +153,10 @@
 
    However, when ``EL3_EXCEPTION_HANDLING`` is ``1``, this routing model is
    invalid as EL3 interrupts are unconditionally routed to EL3, and EL3
-   interrupts will always preempt Secure EL1/EL0 execution.
+   interrupts will always preempt Secure EL1/EL0 execution. See `exception
+   handling`__ documentation.
+
+   .. __: exception-handling.rst#interrupt-handling
 
 #. **CSS=0, TEL3=1**. Interrupt is routed to EL3 when execution is in
    Secure-EL1/Secure-EL0. This is a valid routing model as secure software