| /rk3399_ARM-atf/docs/about/ |
| H A 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 87 after which it will be removed. 91 | | Date | after | … 102 after which it will be removed. 106 | | Date | after | …
|
| H A D | lts.rst | 186 it would make sense to leave at least a month after the November release and 330 after the Nov’22 release 413 considered as one "logical" fix. The version is incremented only after all these 415 will be merged to the affected LTS branches after completing the review process.
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A 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
|
| /rk3399_ARM-atf/services/std_svc/sdei/ |
| H A D | sdei_main.c | 474 bool before, after; in sdei_event_enable() local 490 after = GET_EV_STATE(se, ENABLED); in sdei_event_enable() 496 if (is_map_bound(map) && (!before && after)) in sdei_event_enable() 514 bool before, after; in sdei_event_disable() local 530 after = GET_EV_STATE(se, ENABLED); in sdei_event_disable() 536 if (is_map_bound(map) && (before && !after)) in sdei_event_disable()
|
| /rk3399_ARM-atf/docs/process/ |
| H A 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
|
| H A D | faq.rst | 57 after the release, and then ``master`` will be fast-forwarded to ``integration``
|
| H A D | code-review-guidelines.rst | 101 responding to active review comments after posting patch(es). In such a 123 along with the module(s) they look after.
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | arm-sip-service.rst | 62 of the entry point (physical address) at which execution should start, after 65 When execution starts at the supplied entry point after Execution State has been
|
| H A D | ven-el3-debugfs.rst | 182 On success, the read data is retrieved from the shared buffer after the 287 subsequent calls fail after a first initialization. The caller maps the same
|
| H A 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
|
| H A 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.
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | rockchip.rst | 57 So after successfully building TF-A just follow their build instructions
|
| H A D | s32g274a.rst | 26 upcoming S32G2 contributions. The execution will hang after the BL31 stage
|
| H A D | rpi4.rst | 60 run after the SoC gets its power. The on-chip Boot ROM loads the next stage
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A 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 */
|
| H A D | security-advisory-tfv-3.rst | 45 The vulnerability primarily manifests itself after `Pull Request #662`_. Before
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 57 - | ``STM32MP_RECONFIGURE_CONSOLE``: to re-configure crash console (especially after BL2).
|
| /rk3399_ARM-atf/plat/nvidia/tegra/scat/ |
| H A D | bl31.scat | 134 * .rela.dyn needs to come after .data for the read-elf utility to parse
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | msm8916.rst | 119 directly after BL31. For testing only, the port is primarily intended as 135 to the ``tz`` partition on the device. BL31 should be running after a reboot.
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | uart-booting.rst | 77 CZ.NIC mox-imager after successful download will start its own mini terminal (option ``-t``) to
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rdaspen.rst | 100 If it is not set, then ``BL33`` will be loaded directly after ``BL31``.
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-instr.rst | 111 captured after normal return from the PSCI SMC handler, or, if a low power state
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | dtpm_drivers.rst | 99 ``tpm_startup()`` only needs to be called once after startup, or if the system
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | index.rst | 95 after the io layer is initialized, as the |DTB| is stored on an external
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | console-framework.rst | 159 "boot" and "crash" states, this can be changed after registration using the 194 changed after registration using ``console_set_scope`` function, as per the platform
|