| /trusted-firmware-a-latest/docs/resources/diagrams/plantuml/ |
| D | io_arm_class_diagram.puml | 72 .. io_dev_funcs_t interface ..
78 .. io_dev_funcs_t interface ..
82 interface io_driver {
86 .. io_dev_connector_t interface ..
89 .. io_dev_funcs_t interface ..
|
| /trusted-firmware-a-latest/docs/process/ |
| D | platform-ports-policy.rst | 16 platform compatibility, which means the previous interface needs to be deprecated
17 and a new interface introduced to replace it. In case the migration to the new
18 interface is trivial, the contributor of the change is expected to make good
19 effort to migrate the upstream platforms to the new interface.
27 the release after which each one will be removed. When an interface is
29 interface will be removed. This must be at least 1 full release cycle in future.
30 For non-trivial interface changes, an email should be sent out to the `TF-A
33 the deprecated interface.
38 If a platform, driver or library interface is no longer maintained, it is best
|
| D | security.rst | 49 | |TFV-2| | Enabled secure self-hosted invasive debug interface can allow |
|
| /trusted-firmware-a-latest/docs/threat_model/ |
| D | threat_model_rss_interface.rst | 1 Threat Model for RSS - AP interface
14 The scope of this threat model only includes the interface between the RSS and
23 it includes the RSS and highlights the interface between the AP and the RSS
24 cores. The interface description only focuses on the AP-RSS interface the rest
47 - ID 11: The access to the communication interface between AP and RSS is
49 interface to NSCode can allow malicious code to interact with RSS and
|
| D | threat_model_fvp_r.rst | 78 through the external debug and trace interface.
93 - ID 15: Improper handling of input data received over a UART interface may
|
| D | threat_model.rst | 70 | | informative messages over a UART interface. |
72 | | | Also, characters can be read from a UART interface. |
78 | | with TF-A through SMC call interface and/or shared |
82 | | with TF-A through SMC call interface and/or shared |
368 | | debug and trace interface** |
489 | | interface** |
579 | | a UART interface may allow an attacker to tamper |
621 | | UART interface(s). |
1038 | | debug interface signals, i.e. Secure world event |
|
| D | threat_model_arm_cca.rst | 113 | | TF-A through SMC call interface and/or shared |
155 | | | code or access otherwise restricted HW interface. |
|
| /trusted-firmware-a-latest/docs/components/ |
| D | debugfs-design.rst | 18 interface (`Notes on the Plan 9 Kernel Source`_ and
30 9p interface
67 This interface is embedded into the BL31 run-time payload when selected by build
68 options. The interface multiplexes drivers or emulated "files":
77 SMC interface
84 for a description of the SMC interface.
97 - In order to setup the shared buffer, the component consuming the interface
112 The SMC interface is accessible from an NS environment, that is:
|
| D | arm-sip-service.rst | 20 - DebugFS interface
91 DebugFS interface
94 The optional DebugFS interface is accessed through an SMC SiP service. Refer
405 Returns the debugfs interface version if implemented in TF-A.
421 w0 == SMC_UNK if interface is not implemented
423 uint32_t w1: On success, debugfs interface version, 32 bits
|
| D | rmm-el3-comms-spec.rst | 1 RMM-EL3 Communication interface
4 This document defines the communication interface between RMM and EL3.
5 There are two parts in this interface: the boot interface and the runtime
6 interface.
9 R-EL2 for the first time after boot. The cold boot interface defines the ABI
10 for the cold boot path and the warm boot interface defines the same for the
13 The RMM-EL3 runtime interface defines the ABI for EL3 services which can be
26 RMM-EL3 runtime interface.
173 warm boot by any PE should not enter RMM using the warm boot interface.
209 This section defines the RMM-EL3 runtime interface which specifies the ABI for
[all …]
|
| D | secure-partition-manager-mm.rst | 10 (MM) interface.
33 other interfaces (e.g. ACPI TCG TPM interface, UEFI runtime variable service).
84 - Implement a standard interface that is used for initialising a Secure
89 - Implement a standard interface that is used by a Secure Partition to fulfil
92 - Implement a standard interface that is used by the Non-secure world for
149 TF-A exports a porting interface that enables a platform to specify the system
151 However, this interface is under development and it may change as new features
182 interface defined in the `Management Mode Interface Specification`_ (*Arm DEN
304 corresponding interface.
309 The Secure Partition provides an Event Management interface that is used by the
[all …]
|
| D | el3-spmc.rst | 320 This is a mandatory interface for secure partitions participating in direct request
337 FFA_ID_GET interface, and records it. The SPMC can also query the SPMD ID using
338 the FFA_SPM_ID_GET interface at the secure physical FF-A instance.
340 Secure partitions call this interface at the virtual FF-A instance, to which
396 The FFA_SECONDARY_EP_REGISTER interface is to be used by a secure partition
428 - the FFA_MSG_SEND_DIRECT_REQ interface.
429 - the FFA_RUN interface.
467 - Interrupt is forwarded to SP using FFA_INTERRUPT interface.
470 SPMC using FFA_MSG_WAIT interface.
|
| D | secure-partition-manager.rst | 560 - the FFA_MSG_SEND_DIRECT_REQ interface.
561 - the FFA_RUN interface.
592 to explicitly invoke the ``FFA_RXTX_MAP`` interface. The memory referred
678 `FFA_SECONDARY_EP_REGISTER`_ interface (SMC invocation from the SPMC to the SPMD
740 deployed in NWd, the Hypervisor or OS kernel must invoke the interface
745 permissions. Permissions are provided by invoking the interface
862 synchronization (through FFA_RX_ACQUIRE interface), and to permit SPs to send
923 This is a mandatory interface for secure partitions consisting in direct request
937 Hence, this interface is not to be issued by secure partitions.
969 has been retrieved by this interface. The count is incremented and decremented
[all …]
|
| D | firmware-update.rst | 11 IHI 0093), which defines a standard firmware interface for installing firmware
148 #. Export a BL1 SMC interface to interoperate with other FWU images executing
150 #. Export a platform interface to provide FWU common code with the information
152 :ref:`Porting Guide` for details of this interface.
|
| /trusted-firmware-a-latest/docs/security_advisories/ |
| D | security-advisory-tfv-2.rst | 5 | Title | Enabled secure self-hosted invasive debug interface can |
44 interface. Therefore this issue only exists for AArch32 Secure EL1 code when
45 secure privileged invasive debug is enabled by the authentication interface, at
|
| D | security-advisory-tfv-1.rst | 26 Generic Trusted Firmware (TF) BL1 code contains an SMC interface that is briefly
31 example, BL31 on AArch64 systems), the FWU SMC interface is replaced by the EL3
32 Runtime SMC interface. Platforms may choose how much of this FWU functionality
|
| /trusted-firmware-a-latest/plat/arm/board/tc/ |
| D | platform_test.mk | 85 PLAT_INCLUDES += -I$(TF_M_EXTRAS_PATH)/partitions/measured_boot/interface/include \
86 -I$(TF_M_EXTRAS_PATH)/partitions/delegated_attestation/interface/include \
|
| /trusted-firmware-a-latest/drivers/arm/tzc/ |
| D | tzc_dmc500.c | 54 #define DMC_INST_SI_BASE(instance, interface) \ argument
55 (DMC_INST_BASE_ADDR(instance) + IFACE_OFFSET(interface))
|
| /trusted-firmware-a-latest/plat/st/common/include/ |
| D | stm32mp_common.h | 125 void stm32_get_boot_interface(uint32_t *interface, uint32_t *instance);
|
| /trusted-firmware-a-latest/docs/getting_started/ |
| D | psci-lib-integration-guide.rst | 4 This document describes the PSCI library interface with a focus on how to
8 interface appropriately. **EL3 Runtime Software** refers to software executing
15 of the PSCI library. The description of PSCI library interface and its
19 Generic call sequence for PSCI Library interface (AArch32)
55 #. Call ``psci_warmboot_entrypoint()`` in Monitor mode. This interface
66 the appropriate arguments and call the ``psci_smc_handler()`` interface.
169 Further requirements for each interface can be found in the interface
181 any other interface to the PSCI library. It takes ``lib_args``, a const pointer
198 runtime. Prior to calling the ``psci_setup()`` interface, the platform setup for
199 cold boot must have completed. Major actions performed by this interface are:
[all …]
|
| /trusted-firmware-a-latest/plat/st/common/ |
| D | stm32mp_common.c | 365 void stm32_get_boot_interface(uint32_t *interface, uint32_t *instance) in stm32_get_boot_interface() argument
378 *interface = (itf & BOOT_ITF_MASK) >> BOOT_ITF_SHIFT; in stm32_get_boot_interface()
|
| /trusted-firmware-a-latest/ |
| D | readme.rst | 10 TF-A implements Arm interface standards, including:
|
| /trusted-firmware-a-latest/docs/about/ |
| D | features.rst | 37 - A generic |SCMI| driver to interface with conforming power controllers, for
100 - Support for Errata management firmware interface.
|
| /trusted-firmware-a-latest/docs/plat/ |
| D | rcar-gen3.rst | 52 SD card host interface,
74 BL2 initializes DDR (and on some platforms i2c to interface to the
|
| /trusted-firmware-a-latest/docs/ |
| D | glossary.rst | 74 Errata management firmware interface
|
