Home
last modified time | relevance | path

Searched refs:was (Results 1 – 25 of 33) sorted by relevance

12

/trusted-firmware-a-3.4.0/docs/plat/
Dqti-msm8916.rst96 INFO: BL31: cortex_a53: CPU workaround for 819472 was applied
97 INFO: BL31: cortex_a53: CPU workaround for 824069 was applied
98 INFO: BL31: cortex_a53: CPU workaround for 826319 was applied
99 INFO: BL31: cortex_a53: CPU workaround for 827319 was applied
100 INFO: BL31: cortex_a53: CPU workaround for 835769 was applied
101 INFO: BL31: cortex_a53: CPU workaround for disable_non_temporal_hint was applied
102 INFO: BL31: cortex_a53: CPU workaround for 843419 was applied
103 INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied
Dqti.rst37 is picked. qtiseclib with stub implementation doesn't boot device. This was
Dintel-stratix10.rst90 WARNING: BL31: cortex_a53: CPU workaround for 855873 was missing!
/trusted-firmware-a-3.4.0/
Ddco.txt17 (a) The contribution was created in whole or in part by me and I
29 (c) The contribution was provided directly to me by some other
/trusted-firmware-a-3.4.0/lib/zlib/
Dinflate.h124 unsigned was; /* initial length of match */ member
Dinflate.c1101 state->was = state->length;
1551 (state->mode == MATCH ? state->was - state->length : 0));
/trusted-firmware-a-3.4.0/docs/security_advisories/
Dsecurity-advisory-tfv-4.rst52 #678`_ was merged (on 18 August 2016). However, the upstream code was not
53 vulnerable until `Pull Request #939`_ was merged (on 22 May 2017), which
55 then, the ``check_uptr_overflow()`` macro was not used in AArch32 code.
Dsecurity-advisory-tfv-5.rst51 whereas the EL3 was fixed in the later commits.
/trusted-firmware-a-3.4.0/docs/getting_started/
Dimage-terminology.rst22 - Previously, the format for 3rd level images had 2 forms; ``BL3`` was either
24 subscript number, depending on whether rich text formatting was available.
25 This was confusing and often the dash gets omitted in practice. Therefore the
113 This image was previously abbreviated as ``BL0`` but in some systems, the SCP
125 This image was previously abbreviated as BL3-0 but from the SCP's point of view,
/trusted-firmware-a-3.4.0/docs/components/
Dsecure-partition-manager-mm.rst182 ``e29efeb1b4``, in which the port for FVP was introduced.
507 was made to signal either completion of Secure Partition initialisation or
525 Zero or a positive value indicates that the event was handled successfully.
526 The values depend upon the original event that was delegated to the Secure
529 - ``SUCCESS`` : Used to indicate that the Secure Partition was initialised
530 or a runtime request was handled successfully.
552 - ``NOT_SUPPORTED``: Function was called from the Non-secure world.
588 completion of a request that was delegated to it by the SPM.
596 system register values when the call was made.
691 function was called from the Non-secure world. Also returned if it is
[all …]
Drmm-el3-comms-spec.rst231 ``E_RMM_BAD_ADDR``,The value of an address used as argument was invalid,-2
234 ``E_RMM_INVAL``,The value of an argument was invalid,-5
Darm-sip-service.rst74 registers should not be expected to hold their values before the call was made.
Dras.rst97 The probe handler must return a non-zero value if an error was detected, or 0
Dsdei.rst19 was executing with exceptions masked. The list of SDEI events available to the
Dsecure-partition-manager.rst1100 - ``FFA_MSG_WAIT`` ABI if it was in WAITING state.
1101 - ``FFA_RUN`` ABI if its was in BLOCKED state.
1107 If normal world execution was preempted by secure interrupt, SPMC uses
1110 context was preempted by a secure interrupt to be handled by execution context
/trusted-firmware-a-3.4.0/drivers/renesas/common/ddr/ddr_b/
Dboot_init_dram_config.c2005 #error Invalid value was set to RCAR_DRAM_MEMRANK in ddr_rank_judge()
/trusted-firmware-a-3.4.0/docs/design/
Dinterrupt-framework-design.rst325 exception level when the interrupt was generated. A value of ``1`` means
326 that it was in the non-secure state. A value of ``0`` indicates that it was
328 interrupt was generated and routed as per the routing model specified
693 #. Validating the interrupt. This involves ensuring that the interrupt was
697 the interrupt was taken from to determine this. If the interrupt is not
710 if the security state of the execution context where the interrupt was
752 exception level and the security state from where the Secure-EL1 interrupt was
774 ``TSP_HANDLE_SEL1_INTR_AND_RETURN``. If the TSP was preempted earlier by a non
845 handling Secure-EL1 interrupts that triggered while execution was in the normal
885 #. Checks whether the TSP needs a resume i.e check if it was preempted. It
[all …]
/trusted-firmware-a-3.4.0/docs/perf/
Dpsci-performance-juno.rst38 When using the debug build of TF, there was no noticeable difference in the
42 framework was used because the results in the debug build became skewed; the
/trusted-firmware-a-3.4.0/docs/design_documents/
Dmeasured_boot_poc.rst37 needed to test that the Event Log was properly created. One of these images will
42 for convenience. As the fTPM service used is an OP-TEE TA, it was easy to add
50 Support to interfacing with Measured Boot was added to version 3.9.0 of
60 reference implementation from Microsoft. The service was updated in order
Dcontext_mgmt_rework.rst15 in EL3 firmware. The original design of the library was done keeping in
/trusted-firmware-a-3.4.0/docs/process/
Dcommit-style.rst19 - How was it tested?
/trusted-firmware-a-3.4.0/docs/plat/nxp/
Dnxp-ls-fuse-prov.rst28 - At U-Boot prompt, verify that SNVS register - HPSR, whether OTPMK was written, already:
/trusted-firmware-a-3.4.0/docs/plat/marvell/armada/
Dporting.rst123 The porting layer for PHY was introduced in TF-A. There is one file
/trusted-firmware-a-3.4.0/make_helpers/
Dbuild_macros.mk222 …$(if $(wildcard $(value $(_V))),,$$$$(error '$(_V)=$(value $(_V))' was specified, but '$(value $(_…
/trusted-firmware-a-3.4.0/docs/threat_model/
Dthreat_model_spm.rst618 | | or to allocate a bitmap for a VM that was not |
620 | | creating the possibility for a channel that was not|

12