Home
last modified time | relevance | path

Searched refs:SP (Results 1 – 25 of 27) sorted by relevance

12

/rk3399_ARM-atf/plat/imx/imx93/
H A Dtrdc_config.h19 { 0, 0, SP(RW) | SU(RW) | NP(RW) | NU(RW) },
21 { 1, 0, SP(RW) | SU(RW) | NP(RW) | NU(RW) },
22 { 1, 1, SP(RW) | SU(R) | NP(RW) | NU(R) },
23 { 1, 2, SP(RWX) | SU(RWX) | NP(RWX) | NU(RWX) },
54 { 0, 0, SP(RWX) | SU(RWX) | NP(RWX) | NU(RWX) },
55 { 0, 1, SP(R) | SU(0) | NP(R) | NU(0) },
66 { 0, 0, SP(RW) | SU(RW) | NP(RW) | NU(RW) },
68 { 1, 0, SP(RW) | SU(RW) | NP(RW) | NU(RW) },
99 { 0, 0, SP(RX) | SU(RX) | NP(RX) | NU(RX) },
101 { 1, 0, SP(RWX) | SU(RWX) | NP(RWX) | NU(RWX) },
[all …]
/rk3399_ARM-atf/plat/imx/imx8ulp/xrdc/
H A Dxrdc_config.h9 #define SP(X) ((X) << 9) macro
112 …{ 11, 0, 0x21170000, 0x10000, {0, 0, 1, 0, 0, 0, 0, 2}, {0xfff, SP(RW) | SU(RW) | NP(RW)} }, /* …
113 …{ 11, 1, 0x21180000, 0x10000, {0, 0, 1, 0, 0, 0, 0, 2}, {SP(RW) | SU(RW) | NP(RW) | NU(RW), SP(R…
114 …{ 12, 0, 0x2d400000, 0x100000, {0, 0, 0, 0, 0, 0, 0, 1}, {SP(RW) | SU(RW) | NP(RW) | NU(RW), 0} }…
/rk3399_ARM-atf/docs/components/
H A Del3-spmc.rst40 providing SP description. It is required when
46 - BL32 option is re-purposed to specify the S-EL1 TEE or SP image.
47 BL32 option can be omitted if using TF-A Test Secure Payload as SP.
145 Parsing SP partition manifests
148 SPMC consumes the SP manifest, as defined in `[7]`_.
149 SP manifest fields align with Hafnium SP manifest for easy porting.
166 Passing boot data to the SP
172 exchanged between SPMC and SP.
182 BLOB contains Boot Info Header, followed by SP Manifest contents.
184 The configuration of the boot protocol is done in the SP manifest. As defined by
[all …]
H A Dffa-manifest-binding.rst57 - Number of vCPUs that a VM or SP wants to instantiate.
157 - Specifies how secure interrupts are handled when the SP is in a waiting
158 state and is targeted by a secure interrupt, or when the SP attempts to
162 - 0x0: Proactively inject the VI and resume SP when handling a secure
163 interrupt and SP in the waiting state.
164 - 0x1: Only when a secure interrupt is fired while target SP in the
166 explicitly donate CPU cycles to the SP.
167 - 0x2: Only when the SP attempts to go back to the waiting state while
169 on the scheduler to explicitly donate CPU cycles to the SP.
H A Dsecure-partition-manager.rst19 | SP | Secure Partition |
86 - **SPMC_AT_EL3_SEL0_SP**: this option enables the support to load SEL0 SP
89 providing paths to SP binary images and manifests in DTS format
193 Sample TF-A build command line when the SPMC is located at EL3 and SEL0 SP is
H A Dsecure-partition-manager-mm.rst123 A working prototype of a SP has been implemented by re-purposing the EDK2 code
508 Signal completion of the last SP service request.
H A Dcontext-management-library.rst369 initialized through SPMD at EL3. Upon successful SP initialization, the SPD
/rk3399_ARM-atf/plat/arm/board/neoverse_rd/platform/rdv3/fdts/
H A Drdv3_spmc_sp_manifest.dts69 reg = /* Trusted DRAM for SPMC and SP */
71 /* Trusted DRAM for SP Heap*/
77 /* DRAM for SP NS mappings*/
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model_el3_spm.rst48 | DF1 | SP to SPMC communication. FF-A function invocation or |
98 - SP state.
101 - SP secrets (e.g. application keys).
151 | Assets | SP state |
189 | Assets | SP state |
282 | | - its own or another SP state by using an unusual |
288 | | SP sends a direct request to the normal world |
301 | Assets | SP state, SPMC state |
379 | Assets | SP secrets, SPMC secrets, SP state, SPMC state |
426 | Assets | SPMC or SP state |
[all …]
/rk3399_ARM-atf/plat/arm/board/fvp/fdts/
H A Doptee_sp_manifest.dts6 * This file is a Partition Manifest (PM) for a minimal Secure Partition (SP)
31 run-time-model = <1>; /* SP pre-emptible. */
H A Dfvp_cactus_sp_manifest.dts6 * This file is a Partition Manifest (PM) for a minimal Secure Partition (SP)
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-internals.rst23 - ``OPTEE_SP_FW_CONFIG``: DTC build flag to include OP-TEE as SP in
27 - ``TRUSTY_SP_FW_CONFIG``: DTC build flag to include Trusty as SP in
H A Dimage-terminology.rst74 Secure-EL1 Payload (SP): ``AP_BL32``
78 normal world. However, it may refer to a more abstract Secure-EL1 Payload (SP).
81 potentially multiple SPs and there is no concept of a primary SP, this
H A Dbuild-options.rst22 directory containing the SP source, relative to the ``bl32/``; the directory
50 SP nodes in tb_fw_config.
71 - ``BL2_ENABLE_SP_LOAD``: Boolean option to enable loading SP packages from the
1067 - ``SPMC_AT_EL3_SEL0_SP`` : Boolean option to enable SEL0 SP load support when
1148 internal-trusted-storage) as SP in tb_fw_config device tree.
/rk3399_ARM-atf/docs/
H A Dglobal_substitutions.txt58 .. |SP| replace:: :term:`SP`
H A Dglossary.rst214 SP
/rk3399_ARM-atf/docs/design/
H A Dinterrupt-framework-design.rst276 Secure Payload (SP) software which runs in Secure-EL1/Secure-EL0 and is
288 #. Secure Payload (SP). On a production system, the Secure Payload corresponds
409 be provided by the SP as the result of its initialisation. The SPD should
410 program the routing model only after SP initialisation has completed e.g. in the
415 could either be provided to the SPD service at build time or by the SP at
448 ``tsp_vectors`` in the SP which also includes the handler for Secure-EL1
511 TEL3=1**) where the SPD service will hand them to the SP. This is defined
514 The interrupt handling framework implemented by the SP should support one or
520 service at compile time, then the SP should pass this information to the SPD
535 synchronous interrupt handling model. The SP could implement this scenario
[all …]
/rk3399_ARM-atf/plat/arm/board/neoverse_rd/platform/rdn2/fdts/
H A Drdn2_stmm_sel0_manifest.dts100 * the SP image.
134 * Heap used by SP to allocate memory for DMA.
/rk3399_ARM-atf/docs/resources/diagrams/plantuml/
H A Dspm_dfd.puml67 spn [label="SP..." fillcolor="#ddffb3" height=1]
/rk3399_ARM-atf/fdts/
H A Dstmm_template.dts109 * Heap used by SP to allocate memory for DMA.
/rk3399_ARM-atf/include/drivers/nxp/trdc/
H A Dimx_trdc.h44 #define SP(X) ((X) << 12) macro
/rk3399_ARM-atf/docs/about/
H A Dfeatures.rst54 - A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP
/rk3399_ARM-atf/make_helpers/
H A Dconstraints.mk91 $(error SEL0 SP cannot be enabled without SPMC at EL3)
/rk3399_ARM-atf/docs/design_documents/
H A Dmeasured_boot_dtpm_poc.rst51 The drivers are located in TFA, and not in a |SP|, so that they may be used
/rk3399_ARM-atf/docs/process/
H A Dcoding-guidelines.rst283 - BL31 SPD discovers minor configuration problem with corresponding SP.

12