Lines Matching refs:SPs
227 TF-A is the bootlader for the Hafnium and SPs in the secure world. TF-A
229 by (1). Thus BL2 loads SPs payloads independently.
230 SPs may be signed by different parties (SiP, OEM/ODM, TOS vendor, etc.).
233 ability to upgrade SPs in the field.
348 - The *hypervisor* node describes SPs. *is_ffa_partition* boolean
367 Loading of SPs
391 if SPs originate from different parties.
427 - Pinned MP SPs: an Execution Context id matches a physical PE id. MP
428 SPs must implement the same number of ECs as the number of PEs in the
432 - Migratable UP SPs: a single execution context can run and be migrated
486 method to passing boot data to SPs (not currently implemented).
512 core linear id is N, the 1:1 mapping requires MP SPs are launched using
543 be relayed by SPMC to one or more registered SPs on need basis
570 SPs are always scheduled from the NWd, this paradigm did not change from legacy
640 messaging is allowed to SPs. Thus mailbox usage is restricted to implementing
666 - FF-A id with bit 15 set refer to secure world SPs
821 SPs may need to be notified about specific PM events.
823 - SPs might register PM events to the SPMC
824 - On SPMD to SPMC notification, a limited range of SPs may be notified
826 - This assumes the mentioned SPs supports managed exit.