Lines Matching refs:levels

95 priority levels as applicable for the Secure software stack. It then assigns the
96 dispatchers to one or more priority levels. The dispatchers then register
97 handlers for the priority levels at runtime. A dispatcher can register handlers
100 .. __: `Partitioning priority levels`_
132 stack—priority levels stack up in strictly increasing fashion, and need to be
135 `Transition of priority levels`_.
166 interrupts into distinct priority levels. A dispatcher that chooses to receive
167 interrupts can then *own* one or more priority levels, and register interrupt
171 Dispatchers are assigned interrupt priority levels in two steps:
173 .. _Partitioning priority levels:
175 Partitioning priority levels
196    security states must implement at least 32 priority levels; i.e., at least 5
210 The platform expresses the chosen priority levels by declaring an array of
232 The text in `Partitioning priority levels`_ only describes how the platform
233 expresses the required levels of priority. It however doesn't choose interrupts
240 `Partitioning priority levels`_ section above.
248 Dispatchers register handlers for their priority levels through the following
261 If a dispatcher owns more than one priority levels, it has to call the API for
283 example, expects the platform to allocate two different priority levels—
285 same handler to handle both levels.
431 .. __: `Transition of priority levels`_
433 Transition of priority levels
513    individual dispatchers, as described in `Partitioning priority levels`_.
583 As mentioned in `Partitioning priority levels`_, interrupts targeting distinct
584 dispatchers fall in distinct priority levels. Because they're routed via the