path: root/docs/firmware-design.rst
diff options
authorDimitris Papastamos <dimitris.papastamos@arm.com>2017-10-13 15:27:58 +0100
committerDimitris Papastamos <dimitris.papastamos@arm.com>2017-10-31 10:33:27 +0000
commit17b4c0dd0a12b1c306057b71182e25a69807ff89 (patch)
tree552b91e5814b9e41f46e392cf712ad07f5e42d2b /docs/firmware-design.rst
parenta2ef56af183155465df8ed7577854cebec7522d9 (diff)
aarch64: Add PubSub events to capture security state transitions
Add events that trigger before entry to normal/secure world. The events trigger after the normal/secure context has been restored. Similarly add events that trigger after leaving normal/secure world. The events trigger after the normal/secure context has been saved. Change-Id: I1b48a7ea005d56b1f25e2b5313d77e67d2f02bc5 Signed-off-by: Dimitris Papastamos <dimitris.papastamos@arm.com>
Diffstat (limited to 'docs/firmware-design.rst')
1 files changed, 6 insertions, 16 deletions
diff --git a/docs/firmware-design.rst b/docs/firmware-design.rst
index 853e390115..7cc197096b 100644
--- a/docs/firmware-design.rst
+++ b/docs/firmware-design.rst
@@ -2309,6 +2309,12 @@ PE only; it won't cause handlers to execute on a different PE.
Note that publishing an event on a PE blocks until all the subscribed handlers
finish executing on the PE.
+ARM Trusted Firmware generic code publishes and subscribes to some events
+within. Platform ports are discouraged from subscribing to them. These events
+may be withdrawn, renamed, or have their semantics altered in the future.
+Platforms may however register, publish, and subscribe to platform-specific
Publish and Subscribe Example
@@ -2339,22 +2345,6 @@ implement:
SUBSCRIBE_TO_EVENT(foo, foo_handler);
-Available Events
-ARM Trusted Firmware core makes some events available by default. They're listed
-below, along with information as to when they're published, and the arguments
-passed to subscribed handlers.
-Other EL3 components that are conditionally compiled in may make their own
-events available, but aren't documented here.
-- ``psci_cpu_on_finish``
- - When: Published on a PE after it's finished its power-up sequence.
- - Argument: ``NULL``.
Performance Measurement Framework