| /rk3399_ARM-atf/lib/libc/ |
| H A 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()
|
| /rk3399_ARM-atf/plat/rockchip/rk3399/drivers/gpio/ |
| H A 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()
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A 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
|
| H A D | security-advisory-tfv-5.rst | 35 Since TF-A does not save and restore ``PMCR_EL0`` when switching between the
|
| H A D | security-advisory-tfv-6.rst | 80 it needs to save/restore. Although the ``BPIALL`` instruction is not effective
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | activity-monitors.rst | 10 sets up the |AMU| prior to its exit from EL3, and will save and restore
|
| H A D | context-management-library.rst | 16 in TF-A, not the hardware, to save and restore register state. 28 security state and save enough EL3 metadata to be able to return to that exception 93 3. **Flexibility for Dispatchers to select desired feature set to save and restore** 97 feature set, and thereby save and restore the configuration associated with them. 155 #. ``context_mgmt.c`` : consists of core functions that setup, save and restore 161 #. ``context.S`` : consists of functions that save and restore some of the context 451 save and restore the Pauth registers during world switch. 453 lower exception levels of Secure and Realm worlds. In this scenario, we save the 569 context save operation is not required.
|
| H A D | rmm-el3-comms-spec.rst | 14 invoked by RMM as well as the register save-restore convention when handling an 218 EL3 services expected by RMM at runtime as well as the register save and 1045 RMM-EL3 world switch register save restore convention 1049 specific to each world and will save and restore the registers 1064 EL3 must save and restore the following as part of world switch: 1068 EL3 will not save some registers as mentioned in the below list. It is the 1082 case, RMM could choose to not save the incoming SVE context but must ensure
|
| H A D | secure-partition-manager.rst | 84 ``SPMD_SPM_AT_SEL2`` is enabled. The context save/restore routine
|
| H A D | secure-partition-manager-mm.rst | 591 The SPM must save this syndrome information and use it to delegate the next
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-internals.rst | 10 - ``CTX_INCLUDE_EL2_REGS``: This boolean option provides context save/restore
|
| H A D | build-options.rst | 86 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 100 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 111 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 315 register during EL2 context save/restore operations. ``FEAT_CSV2_2`` is an 341 Physical Offset register) during EL2 to EL3 context save/restore operations. 354 Read Trap Register) during EL2 to EL3 context save/restore operations. 361 during EL2 to EL3 context save/restore operations. 385 well as adding HCRX_EL2 to the EL2 context save/restore operations. Its a 464 during EL2 context save/restore operations.``FEAT_VHE`` is a mandatory 471 well as adding TCR2_EL2 to the EL2 context save/restore operations. Its a [all …]
|
| H A D | prerequisites.rst | 172 npm install --no-save
|
| /rk3399_ARM-atf/fdts/ |
| H A D | stm32mp15-ddr3-2x4Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:49:33
|
| H A D | stm32mp15-ddr3-1x4Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:45:20
|
| H A D | stm32mp15-ddr3-1x2Gb-1066-binG.dtsi | 15 * Save Date: 2020.02.20, save Time: 18:45:20
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 49 to save space and not overflow SYSRAM size, or else the platform won't build or boot.
|
| /rk3399_ARM-atf/docs/plat/nxp/ |
| H A D | nxp-ls-fuse-prov.rst | 144 -- User need to save the SRK key pair and OTPMK Key forever, to continue using this board.
|
| /rk3399_ARM-atf/docs/design/ |
| H A 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
|
| H A D | auth-framework.rst | 303 Most platforms save the hash of the ROTPK, but some may save slightly different
|
| H A D | firmware-design.rst | 1524 cores will powerdown and immediately power back up when this happens. To save on
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 1099 …- do not save SCR_EL3 on external aborts ([a202529](https://review.trustedfirmware.org/plugins/git… 2535 …- enable fp during fp save/restore ([5141de1](https://review.trustedfirmware.org/plugins/gitiles/T… 3428 …- add routines to save, restore sve state ([6d5319a](https://review.trustedfirmware.org/plugins/gi… 3635 …**See:** skip NS EL1 context save & restore operations ([2d960a1](https://review.trustedfirmware.o… 3667 …- save/restore DSU PMU register ([f99a69c](https://review.trustedfirmware.org/plugins/gitiles/TF-A… 3740 …- add save/restore DSU PMU register support ([b87d7ab](https://review.trustedfirmware.org/plugins/… 4337 …- skip NS EL1 context save & restore operations ([2d960a1](https://review.trustedfirmware.org/plug… 4388 …- save guarded control stack registers ([6aae3ac](https://review.trustedfirmware.org/plugins/gitil… 4389 …- update gic el2 sysregs save/restore mechanism ([937d6fd](https://review.trustedfirmware.org/plug… 4391 …- move EL1 save/restore routines into C ([59f8882](https://review.trustedfirmware.org/plugins/giti… [all …]
|
| H A D | porting-guide.rst | 640 behaviour of the ``assert()`` function (for example, to save memory). 3143 case, the power domain is expected to save enough state so that it can resume 3159 ``gicv3_distif_save()`` helper to save the context of the GIC Distributor after 3375 Typical bookkeeping during PSCI power management calls include save/restore
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model.rst | 1061 | | Build options are also provided to save/restore |
|