| /rk3399_ARM-atf/drivers/arm/gicv5/ |
| H A D | gicv5_main.c | 22 static inline bool probe_component(uintptr_t base_addr, uint8_t component) in probe_component() argument
26 if (EXTRACT(IRI_AIDR_COMPONENT, aidr) != component) { in probe_component()
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | activity-monitors.rst | 6 Unit (|AMU|), an optional non-invasive component for monitoring core events
|
| H A D | debugfs-design.rst | 11 higher SW layers such as a non-secure component. Such component can be the
97 - In order to setup the shared buffer, the component consuming the interface
|
| H A D | secure-partition-manager.rst | 51 The SPM is split into a dispatcher and a core component (respectively SPMD and
58 - The same SPMD component is used for both S-EL1 and S-EL2 SPMC configurations.
75 - **SPD=spmd**: this option selects the SPMD component to relay the FF-A
|
| H A D | ven-el3-debugfs.rst | 5 to the component documentation for details.
|
| H A D | el3-spmc.rst | 34 - **SPD=spmd**: this option selects the SPMD component to relay the FF-A
333 Returns the FF-A ID allocated to an SPM component which can be one of SPMD
409 - The Hypervisor or OS kernel is the component initiating PSCI service calls.
|
| H A D | realm-management-extension.rst | 5 FEAT_RME (or RME for short) is an Armv9-A extension and is one component of the
|
| H A D | sdei.rst | 239 EL3 [7]. EL3 performs a first-level triage of the event, and a RAS component
280 - The caller of the API is a component running in EL3; for example, a RAS
|
| H A D | context-management-library.rst | 86 Each world (Non-Secure, Secure, and Realm) should have their separate component
292 component found in the Secure and Realm worlds. Instead, the PSCI library at EL3
352 configurations with TFTF component at NS-EL2.
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | msm8916.rst | 62 component (usually SBL) and that it is capable of running in EL2/HYP mode.
111 * ``BL31_BASE``: Base address for the BL31 firmware component. Must point to
114 * ``BL32_BASE``: Base address for the BL32 firmware component.
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_el3_spm.rst | 15 component (SPMC) within the EL3 firmware.
32 and SPMC component at EL3. The SPMD mostly acts as a relayer/pass-through between
212 | | Additionally a software component residing in the |
221 | | This component checks the sender/receiver fields |
224 | | A similar component can exist in the OS kernel |
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | commit-style.rst | 103 to be deprecated, and should be avoided. If you are adding a new component that
126 component (e.g. ``marvell-comphy-3700``, ``rcar3-drivers``, ``a3720-uart``).
|
| H A D | contributing.rst | 329 component that contains all the actual code will not be accepted.
|
| H A D | coding-guidelines.rst | 184 The `libc` component in the codebase will not add support for the banned APIs.
|
| /rk3399_ARM-atf/fdts/ |
| H A D | rtsm_ve-motherboard.dtsi | 8 * Motherboard component
|
| /rk3399_ARM-atf/docs/ |
| H A D | index.rst | 74 design of portions of the software that involve more than one component, such
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | porting.rst | 85 The DDR code is part of the BLE component, which is an extension of ARM Trusted
|
| H A D | build.rst | 431 This component is usually included in the Linux host packages.
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-specific-configs.rst | 55 On Foundation FVP, there is no flash loader component and the EL3 payload
|
| /rk3399_ARM-atf/docs/plat/arm/ |
| H A D | arm-build-options.rst | 108 only for the BL2 component, and it is disabled by default.
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 270 following components of software running in EL3 and Secure-EL1. Each component is
273 #. EL3 Runtime Firmware. This component is common to all ports of TF-A.
300 This section describes in detail the role of each software component (see
309 This component declares the following prototype for a handler of an interrupt type.
614 This section describes in detail the role of each software component (see
|
| H A D | auth-framework.rst | 147 In Diagram 1, each component is responsible for one or more of these operations.
454 extents of each component. The platform will have to implement the
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 6 line and are not to be modified in any component makefiles. Note that the
20 - ``AARCH32_SP`` : Choose the AArch32 Secure Payload component to be built as
643 component of the option ``-fstack-protector-$ENABLE_STACK_PROTECTOR``.
1051 - ``SPD``: Choose a Secure Payload Dispatcher component to be built into TF-A.
1067 component runs at the EL3 exception level. The default value is ``0`` (
1082 component runs at the S-EL2 exception level provided by the ``FEAT_SEL2``
1084 disabled (0) it indicates the SPMC component runs at the S-EL1 execution
|
| H A D | rt-svc-writers-guide.rst | 8 Firmware component of Trusted Firmware-A (TF-A), BL31.
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 32 A brief description of each component is provided below.
106 description of each component and where they are sourced from.
|