Lines Matching refs:to
9 This document describes how to enable an interrupt in TF-M. The target audiences
28 Partition Thread to have further data processing.
34 to scheduling.
40 The SLIH is deferred and subject to scheduling but all Secure Partition APIs are
43 Both the FLIH and the SLIH can be used by Secure Partitions which conform to
47 to Firmware Framework v1.0.
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.
59 - Granting the Secure Partition access permissions to the device of the
65 See also `Enabling the Interrupt Tests`_ on how to integrate them to platforms.
67 Binding an Interrupt to a Secure Partition
70 To bind an interrupt to a Secure Partition, you need to add an item to the
72 ``irqs`` is a list of Interrupt Request (IRQ) assigned to the Secure Partition.
74 Secure Partitions are not allowed to share IRQs with other Secure Partitions.
81 Here is an example manifest of Secure Partitions conform to Firmware Framework
110 The ``signal`` attribute is a symbolic name used by TF-M to identify which
112 It is also used by the Secure Partition to receive the interrupt signal by
128 Here is an example manifest of Secure Partitions conform to Firmware Framework
156 The ``name`` is used to construct the following two elements:
176 Granting Permissions to Devices for Secure Partitions
179 A secure partition shall be granted two parts of permissions to access a device.
181 codes to access the device.
186 You need to declare the MMIO region in the ``mmio_regions`` attributes in the
187 Secure Partition manifest, to enable the Secure Partition to access it.
192 A named region consists of a string ``name`` to describe the region.
212 It is a pointer to structure instance that usually includes the base address
214 required to set up permissions to the MMIO region.
231 To give permissions of devices drivers to Secure Partitions, it is recommended
232 to put the driver codes to the Partition's CMake library:
266 initialization. The function can be put in any source file that belongs to SPM,
267 for example a ``tfm_interrupts.c`` added to the ``tfm_spm`` CMake target.
288 But if you use the ``NVIC_SetPriority`` function provided by CMSIS to set
293 Targeting Interrupts to Secure
297 interrupts target to Secure State by setting the Interrupt Controller.
307 - ``p_pt`` - pointer to Partition runtime struct of the owner Partition
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.
332 The ``p_pt`` and ``p_ildi`` are the information passed to interrupt
363 In addition, you need to implement the following APIs of timer control:
370 to indicate that FLIH and SLIH interrupt tests are supported respectively.
385 Migrating to Firmware Framework v1.1
388 Please refer to ``Migrating Secure Partitions to version 1.1`` of FF-M v1.1 [1]_