| /trusted-firmware-a-3.6.0-3.5.0/docs/about/ |
| D | release-information.rst | 10 candidates will start appearing after this and only bug fixes or updates
13 created after code freeze if there are significant changes that need merging onto
65 after which it will be removed.
69 | | Date | after | …
80 after which it will be removed.
84 | | Date | after | …
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/components/spd/ |
| D | optee-dispatcher.rst | 11 platforms to use. There is also another technique that will load OP-TEE OS after
20 dm-verity. The SMC call to load OP-TEE is then invoked immediately after the
|
| /trusted-firmware-a-3.6.0-3.5.0/services/std_svc/sdei/ |
| D | sdei_main.c | 476 bool before, after; in sdei_event_enable() local
492 after = 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
532 after = 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.6.0-3.5.0/docs/process/ |
| D | platform-ports-policy.rst | 27 the release after which each one will be removed. When an interface is
28 deprecated, the page must be updated to indicate the release after which the
|
| D | faq.rst | 57 after the release, and then ``master`` will be fast-forwarded to ``integration``
72 but would be after the CI has been transitioned to `trustedfirmware.org`_.
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/components/ |
| D | arm-sip-service.rst | 61 of the entry point (physical address) at which execution should start, after
64 When execution starts at the supplied entry point after Execution State has been
272 On success, the read data is retrieved from the shared buffer after the
377 subsequent calls fail after a first initialization. The caller maps the same
|
| D | firmware-update.rst | 41 the second stage Bootloader after FWU has been done by ``Client`` and
70 ``Update Agent`` marks this update as accepted after further sanitisation
176 is permitted to request execution of a secure world FWU image (after
221 - INTERRUPTED: This is the state of a secure, executable image after it has
|
| D | romlib-design.rst | 17 2. Functions can be patched after they have been programmed into ROM.
|
| D | el3-spmc.rst | 92 and after the final reclaim has been completed.
361 In case of fragmented sharing, conversion of memory descriptors happens after last
471 - SPMC returns to normal world after interrupt handling is completed.
|
| D | secure-partition-manager-mm.rst | 594 instruction, to the instruction immediately after the call in the Secure
692 used after ``MM_SP_EVENT_COMPLETE_AARCH64``.
780 called from the Non-secure world. Also returned if it is used after
794 This function is only available at boot time. This interface is revoked after
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/plat/ |
| D | rockchip.rst | 54 So after successfully building TF-A just follow their build instructions
|
| D | rpi4.rst | 60 run after the SoC gets its power. The on-chip Boot ROM loads the next stage
|
| D | qti-msm8916.rst | 76 to the ``tz`` partition on the device. BL31 should be running after a reboot.
|
| D | stm32mp1.rst | 142 - | ``STM32MP_RECONFIGURE_CONSOLE``: to re-configure crash console (especially after BL2).
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/security_advisories/ |
| D | security-advisory-tfv-1.rst | 27 available after cold reset to support the Firmware Update (FWU) feature (also
110 /* Find out how much free trusted ram remains after BL1 load */
|
| D | security-advisory-tfv-3.rst | 45 The vulnerability primarily manifests itself after `Pull Request #662`_. Before
|
| D | security-advisory-tfv-10.rst | 21 | Fix Version | - `fd37982a19a4a291`_ "fix(auth): forbid junk after |
|
| /trusted-firmware-a-3.6.0-3.5.0/plat/nvidia/tegra/scat/ |
| D | bl31.scat | 134 * .rela.dyn needs to come after .data for the read-elf utility to parse
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/plat/marvell/armada/ |
| D | uart-booting.rst | 77 CZ.NIC mox-imager after successful download will start its own mini terminal (option ``-t``) to
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/perf/ |
| D | psci-performance-instr.rst | 110 captured after normal return from the PSCI SMC handler, or, if a low power state
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/components/fconf/ |
| D | index.rst | 95 after the io layer is initialized, as the |DTB| is stored on an external
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/getting_started/ |
| D | tools-build.rst | 8 this, use the ``OPENSSL_DIR`` variable after the ``make`` command to
|
| D | psci-lib-integration-guide.rst | 97 During cold/warm boot, after invoking appropriate PSCI library interfaces, it
146 to an appropriate state after boot and may choose to directly program the
238 need to be called by the primary CPU during the cold boot sequence after
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/ |
| D | porting-guide.rst | 1114 be invoked by BL31 after the power domain topology is initialized and can
1320 A platform may need to do additional initialization after reset. This function
1395 in case of DRTM implementation this function reset the system after
1571 BL1 implements the reset vector where execution starts from after a cold or
1651 for performing any remaining platform-specific setup that can occur after the
1722 BL1 calls this function after platform setup to identify the next image to be
1769 boot and FWU code path, after loading and authenticating the image.
1892 since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded.
1950 for given ``image_id``. This function is currently invoked in BL2 after
2053 since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded.
[all …]
|
| /trusted-firmware-a-3.6.0-3.5.0/docs/design/ |
| D | firmware-design.rst | 360 for platforms to take further action after image load. This function must
426 using the Boot Over MHU (BOM) protocol after being loaded in the trusted SRAM
592 cluster immediately after reset and before the data cache is enabled in the
730 entry-point, to be invoked by the CPU immediately after the reset handler.
959 populated for all of the OENs covered by a service after the service ``init()``
1299 actions very early after a CPU is released from reset in both the cold and warm
1457 warm boots, shortly after reset. Individual Errata workarounds are enabled as
1916 after SCP_BL2 has
1958 after SCP_BL2 has
2148 cache lines after these fields are written.
[all …]
|
