Lines Matching full:world

31 A common system design will place the ``Update Agent`` in the Secure-world
32 while the ``Client`` executes in the Normal-world.
33 The `PSA FW update specification`_ provides ABIs meant for a Normal-world
69 and also if the system successfully booted the Normal-world image then
71 checking at Normal-world.
81 as authentication failure or non-fuctionality of Normal-world software then the
119 This document describes the secure world FWU design. It is beyond its scope to
120 describe how normal world FWU images should operate. To implement normal world
129 some parts of FWU to be implemented in other secure and normal world images.
138    -  Context switching between the normal and secure world during the FWU
141 -  Other secure world FWU images handle platform initialization required by
143 -  Normal world FWU images handle loading of firmware images from external
175 -  Executable or non-executable image. This indicates whether the normal world
176    is permitted to request execution of a secure world FWU image (after
177    authentication). Secure world certificates and non-AP images are examples
222    requested BL1 to resume normal world execution.
281         if (normal world caller) synchronous exception
309         if (secure world caller) return -EPERM
335 Once the SMC is handled, BL1 returns from exception to the normal world caller.
356         if (secure world caller)
359         else // normal world caller
392         if (secure world caller) return -EPERM
398 ``image_id``, in the other security world to the caller. The current
399 implementation only supports normal world callers initiating execution of a
400 secure world image.
402 BL1 saves the normal world caller's context, sets the secure image state to
419         if (normal world caller and no INTERRUPTED secure image) return -EPERM
421 This SMC resumes execution in the other security world while there is a secure
424 For normal world callers, BL1 sets the previously interrupted secure image state
425 to EXECUTED. For secure world callers, BL1 sets the previously executing secure
426 image state to INTERRUPTED. In either case, BL1 saves the calling world's
427 context, restores the resuming world's context and returns from exception into
428 the resuming world. If the call is successful then the caller provided
429 ``image_param`` is returned to the resumed world, otherwise an error code is
445         if (normal world caller) return -EPERM
450 restores the normal world context and returns from exception into the normal
451 world.
483         if (secure world caller) return -EPERM