docs/components/sdei.rst

18 client receives the event notification at the registered handler even when it
20 client are specific to the platform [#std-event]_. See also `Determining client
25 The following figure depicts a general sequence involving SDEI client executing
31 As part of initialisation, the SDEI client binds a Non-secure interrupt [1], and
32 the SDEI dispatcher returns a platform dynamic event number [2]. The client then
34 events on the current PE [7]. This sequence is typical of an SDEI client, but it
39 execute the registered handler [10]. The client terminates its execution with
42 the client handler completes, at which point EL3 does EOI [12].
116 on the platform. The list of events made available to the client, along with
193 Determining client EL
196 The SDEI specification requires that the *physical* SDEI client executes in the
233 As part of initialisation, the SDEI client registers a handler for a platform
242 dispatch an event [10] (which the client had already registered for [1]). The
244 requested event is dispatched to the client (assuming all the conditions are
253 -  SDEI events must be unmasked on the PE. I.e. the client must have called
291 -  The call will block until the SDEI client completes the event (i.e. when the
292    client calls either ``SDEI_EVENT_COMPLETE`` or ``SDEI_COMPLETE_AND_RESUME``).
365 Considering a Non-secure client is involved in SDEI state management, there exists
366 some security considerations which needs to be taken care of in both client and EL3
372 A bound event is an SDEI event that corresponds to a client interrupt.
374 an SDEI event with a client interrupt. There is a possibility that a rogue
375 client can request an invalid interrupt to be bound. This may potentially
379 by client is architecturally valid, Non-secure client should also ensure the
385 For a given event source, if the events are generated continuously, then NS client
386 may be unusable. To mitigate against this, the Non-secure client must have
390 This may result in unusable Non-secure client.
395 For a dispatched event, it is the client's responsibility to ensure that the
397 ``SDEI_EVENT_COMPLETE`` or ``SDEI_EVENT_COMPLETE_AND_RESUME``. If the client
399 in the client and potentially end up in unusable PE.