Lines Matching refs:interrupt

9 This document describes how to enable an interrupt in TF-M. The target audiences
20 TF-M supports the two interrupt handling models defined by FF-M:
24   In this model, the interrupt handling is carried out immediately when the
25   interrupt exception happens.
27   The interrupt handling can optionally set an interrupt signal for the Secure
32   In this model, the interrupt handling is deferred after the interrupt
36 The FLIH supports handling an interrupt in a bounded time, but very limited APIs
49 Please refer to chapter 6.2 of FF-M v1.1 [1]_ for more details on the interrupt
56 To enable an interrupt, you need to do the following:
58 - Binding the interrupt to a Secure Partition.
60   interrupt.
61 - Initializing the interrupt.
62 - Integrating the interrupt handling function
70 To bind an interrupt to a Secure Partition, you need to add an item to the
103   The ``source`` is a string that identifies the interrupt source.
111   interrupt is asserted.
112   It is also used by the Secure Partition to receive the interrupt signal by
113   calling ``psa_wait`` for interrupt handling.
122 The interrupt handling model is SLIH by default as it is the only supported one
158   - the interrupt signal symbol: ``{{name}}_SIGNAL``, the equivalent of
170   The ``handling`` attribute specifies the interrupt handling model and must
244 Platforms must define an interrupt initialization function for each Secure
245 interrupt.
269 The initialization of an interrupt must include:
272 - ensuring that the interrupt targets the Secure State.
273 - saving the interrupt information
282 For example if the number of configurable priority of your interrupt controller
286 Note that these are not the values set into the interrupt controllers.
308 - ``p_ildi`` - pointer to ``irq_load_info_t`` struct of the interrupt
313 The easiest way is to save them in global variables for each interrupt.
326 TF-M provides an interrupt handling entry for Secure interrupts:
332 The ``p_pt`` and ``p_ildi`` are the information passed to interrupt
335 Platforms should call this entry function in the interrupt handlers held in
336 Vector Table with the information saved by the interrupt initialization
338 If the information is saved as global variables, then the interrupt handlers can
359   FLIH interrupt test and SLIH interrupt test share the same timer
370 to indicate that FLIH and SLIH interrupt tests are supported respectively.
373   interrupt tests
375   interrupt tests
377 The following configurations control SLIH and FLIH interrupt tests: