Searched refs:expect (Results 1 – 14 of 14) sorted by relevance
| /rk3399_ARM-atf/plat/mediatek/drivers/apusys/mt8196/ |
| H A D | apusys_rv_pwr_ctrl.c | 19 static int wait_for_state_ready(uint32_t reg, uint32_t mask, uint32_t expect, in wait_for_state_ready() argument
24 while ((mmio_read_32(reg) & mask) != expect) { in wait_for_state_ready()
35 __func__, reg, mask, expect); in wait_for_state_ready()
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 9 which focuses on the most common configuration we expect to see. The other
19 features within the project, we have not reached that point yet. We expect
|
| /rk3399_ARM-atf/plat/mediatek/drivers/mtcmos/ |
| H A D | mtcmos.c | 38 uint32_t expect = is_set ? mask : 0; in mtcmos_wait_for_state() local
41 if ((mmio_read_32(reg) & mask) == expect) in mtcmos_wait_for_state()
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | rockchip.rst | 35 Rockchip SoCs expect TF-A's BL31 (AARCH64) or BL32 (AARCH32) to get
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-aemv8-base.rst | 94 BL32 image is only needed if BL31 has been built to expect a Secure-EL1
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-10.rst | 128 Only in the following 2 cases do we expect this vulnerability to be triggerable
|
| /rk3399_ARM-atf/docs/plat/arm/ |
| H A D | arm-build-options.rst | 60 in which case the platform is configured to expect NULL in the State-ID
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | exception-handling.rst | 149 EL3. As a result, S-EL1 software cannot expect to handle Non-secure
488 For the latter case above, dispatchers before |EHF| expect Non-secure interrupts
|
| H A D | ffa-manifest-binding.rst | 179 - Presence of this field indicates that the partition doesn't expect the
|
| H A D | xlat-tables-lib-v2-design.rst | 209 recommended to populate these structures by hand. Instead, wherever APIs expect
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | firmware-design.rst | 235 BL1 does not expect to receive any exceptions other than the SMC exception.
466 runtime. In the first 2 cases, we expect the Boot ROM to be able to
|
| H A D | cpu-specific-build-macros.rst | 1380 in a way most programmers expect, and will most probably result in a
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 408 we expect EL2 to be present. But in case of INIT_UNUSED_NS_EL2=1 ,
|
| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 1442 …- convert arm platforms to expect a wakeup ([da305ec](https://review.trustedfirmware.org/plugins/g…
12712 - Provided separate drivers for GICv3 and GICv2. These expect the entire
13215 builds a FIP by default and the FVP platform code expect to load a FIP from
|