Searched refs:after (Results 1 – 25 of 38) sorted by relevance
12
| /trusted-firmware-a-3.4.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
61 Release version after which it will be removed.
65 | | Date | after | …
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | platform-compatibility-policy.rst | 24 the release after which each one will be removed. When an interface is
25 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`_.
|
| D | code-review-guidelines.rst | 94 along with the module(s) they look after.
|
| /trusted-firmware-a-3.4.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.4.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 | romlib-design.rst | 17 2. Functions can be patched after they have been programmed into ROM.
|
| D | firmware-update.rst | 80 is permitted to request execution of a secure world FWU image (after
125 - INTERRUPTED: This is the state of a secure, executable image after it has
|
| D | rmm-el3-comms-spec.rst | 9 R-EL2 for the first time after boot. The cold boot interface defines the ABI
110 operations are performed after the Boot Manifest is populated.
|
| 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
|
| D | platform-interrupt-controller-API.rst | 18 servicing. This must be be called only after an interrupt has already been
|
| D | ras.rst | 180 handled when they occur, but only after the exceptions are unmasked again.
|
| /trusted-firmware-a-3.4.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.
|
| /trusted-firmware-a-3.4.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
|
| /trusted-firmware-a-3.4.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.4.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.4.0/docs/getting_started/ |
| D | porting-guide.rst | 829 be invoked by BL31 after the power domain topology is initialized and can
1035 A platform may need to do additional initialization after reset. This function
1256 BL1 implements the reset vector where execution starts from after a cold or
1336 for performing any remaining platform-specific setup that can occur after the
1407 BL1 calls this function after platform setup to identify the next image to be
1454 boot and FWU code path, after loading and authenticating the image.
1577 since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded.
1635 for given ``image_id``. This function is currently invoked in BL2 after
1702 since the later ``bl2_platform_setup`` must be done after SCP_BL2 is loaded.
2257 the hardware after ``plat_trng_setup`` function is called. This value must
[all …]
|
| 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.4.0/docs/design/ |
| D | firmware-design.rst | 361 for platforms to take further action after image load. This function must
427 using the Boot Over MHU (BOM) protocol after being loaded in the trusted SRAM
593 cluster immediately after reset and before the data cache is enabled in the
731 entry-point, to be invoked by the CPU immediately after the reset handler.
960 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
1891 after SCP_BL2 has
1928 after SCP_BL2 has
2118 cache lines after these fields are written.
[all …]
|
| D | interrupt-framework-design.rst | 410 program the routing model only after SP initialisation has completed e.g. in the
414 after receiving an interrupt from the EL3 runtime firmware. This information
873 #. ``SMC_PREEMPTED`` is set in x0 and return to non secure state after
876 The Normal World is expected to resume the TSP after the ``yielding`` SMC
913 In the synchronous model, it should begin handling a Secure-EL1 interrupt after
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/juno/ |
| D | index.rst | 231 The Juno board should suspend to RAM and then wakeup after 10 seconds due to
|
| /trusted-firmware-a-3.4.0/docs/design_documents/ |
| D | measured_boot_poc.rst | 99 this: ``<fvp-project>/Foundation_Platformpkg``. In the end, after cloning
183 For this PoC, nothing loaded after BL33 and NT_FW_CONFIG is recorded
|
12
