/trusted-firmware-a-latest/lib/libc/ |
D | strrchr.c | 38 char *save; in strrchr() local 42 for (save = NULL;; ++p) { in strrchr() 44 save = (char *)p; in strrchr() 46 return (save); in strrchr()
|
/trusted-firmware-a-latest/plat/rockchip/rk3399/drivers/gpio/ |
D | rk3399_gpio.c | 373 const struct gpio_save *save = &store_gpio[i - 2]; in plat_rockchip_restore_gpio() local 375 mmio_write_32(base + SWPORTA_DR, save->swporta_dr); in plat_rockchip_restore_gpio() 376 mmio_write_32(base + SWPORTA_DDR, save->swporta_ddr); in plat_rockchip_restore_gpio() 377 mmio_write_32(base + INTEN, save->inten); in plat_rockchip_restore_gpio() 378 mmio_write_32(base + INTMASK, save->intmask); in plat_rockchip_restore_gpio() 379 mmio_write_32(base + INTTYPE_LEVEL, save->inttype_level); in plat_rockchip_restore_gpio() 380 mmio_write_32(base + INT_POLARITY, save->int_polarity); in plat_rockchip_restore_gpio() 381 mmio_write_32(base + DEBOUNCE, save->debounce); in plat_rockchip_restore_gpio() 382 mmio_write_32(base + LS_SYNC, save->ls_sync); in plat_rockchip_restore_gpio()
|
/trusted-firmware-a-latest/docs/design_documents/ |
D | context_mgmt_rework.rst | 72 (4) **Allow more flexibility for Dispatchers to select feature set to save and restore** 74 The current functions for EL2 CPU context save and restore is a single 77 CPU features to select registers to save and restore. It also assumes that 80 world. The framework should cater for selective save and restore of CPU 84 save and restore routine corresponding to Arch feature. The memory allocation 126 some functionalities in EL3. The current sequence for context save and restore 135 a collection of EL3 and some other lower EL registers. The save and restore 139 Note2: The EL1 context save and restore can possibly be removed when switching 168 sysregs (`root_exc_context`) used by EL3. The save and restore
|
/trusted-firmware-a-latest/docs/security_advisories/ |
D | security-advisory-tfv-8.rst | 67 For this reason, TF-A does not save ``x0`` to ``x3`` in the CPU context on an 89 * Macro to save the General purpose registers (r0 - r12), the banked 92 * already saved. The `sp` must point to the `smc_ctx_t` to save to. 93 * Additionally, also save the 'pmcr' register as this is updated whilst
|
D | security-advisory-tfv-5.rst | 35 Since TF-A does not save and restore ``PMCR_EL0`` when switching between the
|
D | security-advisory-tfv-6.rst | 79 it needs to save/restore. Although the ``BPIALL`` instruction is not effective
|
/trusted-firmware-a-latest/docs/getting_started/ |
D | build-internals.rst | 10 - ``CTX_INCLUDE_EL2_REGS``: This boolean option provides context save/restore
|
D | build-options.rst | 85 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 99 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 106 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 279 register during EL2 context save/restore operations. ``FEAT_CSV2_2`` is an 292 Physical Offset register) during EL2 to EL3 context save/restore operations. 299 Read Trap Register) during EL2 to EL3 context save/restore operations. 306 well as adding HCRX_EL2 to the EL2 context save/restore operations. Its a 358 during EL2 context save/restore operations.``FEAT_VHE`` is a mandatory 365 well as adding TCR2_EL2 to the EL2 context save/restore operations. Its a 392 registers to the EL2 context save/restore operations. This flag can take [all …]
|
D | prerequisites.rst | 172 npm install --no-save
|
D | psci-lib-integration-guide.rst | 63 #. On receipt of an SMC, save the register context as per `SMCCC`_. 449 Typical bookkeeping during PSCI power management calls include save/restore
|
/trusted-firmware-a-latest/docs/components/ |
D | activity-monitors.rst | 10 sets up the |AMU| prior to its exit from EL3, and will save and restore
|
D | rmm-el3-comms-spec.rst | 14 invoked by RMM as well as the register save-restore convention when handling an 210 EL3 services expected by RMM at runtime as well as the register save and 487 RMM-EL3 world switch register save restore convention 491 specific to each world and will save and restore the registers 506 EL3 must save and restore the following as part of world switch: 510 EL3 will not save some registers as mentioned in the below list. It is the 524 case, RMM could choose to not save the incoming SVE context but must ensure
|
D | secure-partition-manager-mm.rst | 591 The SPM must save this syndrome information and use it to delegate the next
|
D | secure-partition-manager.rst | 153 ``SPMD_SPM_AT_SEL2`` is enabled. The context save/restore routine
|
/trusted-firmware-a-latest/fdts/ |
D | stm32mp15-ddr3-1x4Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:45:20
|
D | stm32mp15-ddr3-2x4Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:49:33
|
D | stm32mp15-ddr3-1x2Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:45:20
|
/trusted-firmware-a-latest/docs/plat/nxp/ |
D | nxp-ls-fuse-prov.rst | 144 -- User need to save the SRK key pair and OTPMK Key forever, to continue using this board.
|
/trusted-firmware-a-latest/docs/design/ |
D | interrupt-framework-design.rst | 126 state. This is a valid routing model as secure software in EL3 can save 573 handler which should save the SP state correctly and resume execution in 721 The SPD service must save the system register context of the current 742 exception level in the non-secure state. The former should save the SP context, 775 secure interrupt during ``yielding`` SMC processing, save the registers that 778 save any other secure context since the TSP is expected to preserve it 916 should save any Secure-EL1 system register context which is needed for resuming
|
D | auth-framework.rst | 272 Most platforms save the hash of the ROTPK, but some may save slightly different
|
/trusted-firmware-a-latest/docs/ |
D | change-log.md | 241 …- save BL32 image base and size in entry point info ([821b01f](https://review.trustedfirmware.org/… 495 …- save PAuth context when RME is enabled ([13cc1aa](https://review.trustedfirmware.org/plugins/git… 653 …- save BL32 image base and size in entry point info ([31dcf23](https://review.trustedfirmware.org/… 1228 …- run-time checks for mpam save/restore routines ([ed80440](https://review.trustedfirmware.org/plu… 1237 …- unconditionally save PMCR_EL0 ([1d6d680](https://review.trustedfirmware.org/plugins/gitiles/TF-A… 1543 …- do not save scr_el3 during EL3 entry ([e61713b](https://review.trustedfirmware.org/plugins/gitil… 2419 …- save boot auth status and partition info ([ab2b325](https://review.trustedfirmware.org/plugins/g… 3154 …- enable fpregs context save and restore ([18fa43f](https://review.trustedfirmware.org/plugins/git… 3429 …- add gic save and restore calls ([b40a467](https://review.trustedfirmware.org/plugins/gitiles/TF-… 3532 …- add support to save and restore fp regs ([15dd6f1](https://review.trustedfirmware.org/plugins/gi… [all …]
|
D | porting-guide.rst | 640 behaviour of the ``assert()`` function (for example, to save memory). 2751 case, the power domain is expected to save enough state so that it can resume 2767 ``gicv3_distif_save()`` helper to save the context of the GIC Distributor after
|
/trusted-firmware-a-latest/docs/threat_model/ |
D | threat_model.rst | 944 | | Build options are also provided to save/restore |
|