| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | deprecated.rst | 8 off period before deleting it or it can be deleted straight away. For later types
|
| D | rz-g2.rst | 71 reference tree [1] resets into EL1 before entering BL2 - see its
74 BL2 initializes DDR before determining the boot reason (cold or warm).
|
| D | rcar-gen3.rst | 71 reference tree [1] resets into EL1 before entering BL2 - see its
75 PMIC) before determining the boot reason (cold or warm).
|
| D | stm32mp1.rst | 147 - | ``STM32MP_EARLY_CONSOLE``: to enable early traces before clock driver is setup.
161 You need to build BL2, BL32 (SP_min or OP-TEE) and BL33 (U-Boot) before building FIP binary.
|
| D | rpi4.rst | 72 But before doing that, it will also load a "kernel" and the device tree into
|
| D | qti-msm8916.rst | 65 This image must be "signed" before flashing it, even if the board has secure
|
| /trusted-firmware-a-3.4.0/services/std_svc/sdei/ |
| D | sdei_main.c | 476 bool before, after; in sdei_event_enable() local
489 before = GET_EV_STATE(se, ENABLED); in sdei_event_enable()
498 if (is_map_bound(map) && (!before && after)) in sdei_event_enable()
516 bool before, after; in sdei_event_disable() local
529 before = GET_EV_STATE(se, ENABLED); in sdei_event_disable()
538 if (is_map_bound(map) && (before && !after)) in sdei_event_disable()
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/arm_fpga/ |
| D | index.rst | 48 putting its address into the x0 register before jumping to the entry
50 It defaults to 0x80070000, which is 64KB before the BL33 load address.
56 To avoid random garbage, there needs to be a "CMD:" signature before the
|
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | platform-interrupt-controller-API.rst | 90 inserts barrier to make memory updates visible before enabling interrupt, and
211 inserts barrier to make memory updates visible before raising SGI, then writes
252 inserts barrier to make memory updates visible before setting interrupt pending,
285 inserts to order memory updates before updating mask, then writes to the GIC
286 *Priority Mask Register*, and make sure memory updates are visible before
|
| D | exception-handling.rst | 387 priority level before returning to the |EHF|. Runtime firmware, upon exit
388 through an ``ERET``, resumes execution before the interrupt occurred.
424 priority before the call to ``ehf_activate_priority()``. Dispatchers
488 For the latter case above, dispatchers before |EHF| expect Non-secure interrupts
490 preempted error code before yielding to Non-secure world.
553 *deactivate* the priority level before returning to the |EHF|. See
574 was before.
|
| D | arm-sip-service.rst | 68 This call can only be made on the primary CPU, before any secondaries were
74 registers should not be expected to hold their values before the call was made.
|
| D | xlat-tables-lib-v2-design.rst | 194 added early on, before the translation tables are created and populated. They
247 added before ``init_xlat_tables()`` is called and ``init_xlat_tables()`` must be
271 successfully added before updating the translation context structure. If the
410 is deferred to the ``enable_mmu*()`` family of functions, just before the MMU is
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | platform-compatibility-policy.rst | 29 deprecated interfaces. Platforms are expected to migrate before the removal of
|
| D | security.rst | 30 remedy before it is made public. As such, please follow the disclosure plan
|
| D | faq.rst | 7 Often it is necessary to update your patch set before it is merged. Refer to the
|
| D | code-review-guidelines.rst | 14 before they are integrated in the source tree. Different people bring different
53 several rounds of reviews and rework before they get approved, especially
|
| D | contributing.rst | 171 Various CI Jobs are deployed which run tests on every patch before being
172 merged. So each of your patches go through a series of checks before they
237 configurations on every patch, before they are being passed to ``Coverity scan analysis``.
|
| /trusted-firmware-a-3.4.0/docs/security_advisories/ |
| D | security-advisory-tfv-1.rst | 16 | Affected | firmware update code executing before BL31 |
43 the cold boot path, before BL31 starts. Untrusted in this sense means code
|
| D | security-advisory-tfv-9.rst | 45 before any branch instruction is executed. This is sufficient to mitigate
|
| D | security-advisory-tfv-8.rst | 27 restore it before returning into the lower exception level software that called
|
| D | security-advisory-tfv-4.rst | 17 | Affected | firmware update code executing before BL31 |
|
| /trusted-firmware-a-3.4.0/docs/perf/ |
| D | psci-performance-juno.rst | 54 test to complete before proceeding to the next non-lead CPU. The lead CPU then
107 the lock before proceeding.
140 AP CPU to enter WFI before making the channel available to other CPUs, which
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | reset-design.rst | 105 reset vector base address, before the application processor is powered on.
155 zeroed before entering BL31.
|
| /trusted-firmware-a-3.4.0/docs/threat_model/ |
| D | threat_model.rst | 369 | | when the security check is produced before the time |
395 | Mitigations | Copy image to on-chip memory before authenticating |
476 | | problems before releasing the production |
610 | Mitigations | Validate SMC function ids and arguments before using |
668 | | sanitized before being used. These security checks |
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | tools-build.rst | 41 It is recommended to remove old artifacts before building the tool:
|
