Lines Matching refs:states

12 software running in various security states (Secure/Non-Secure/Realm).
14 are not banked per world. When moving between the security states it is the
21 saving and restoring of register states across the worlds.
33 security states (Non-Secure, Secure, Realm). Each world must have its
34 configuration of system registers independent of other security states to access
37 If the CPU switches across security states (for example: from Non-secure to Secure
51 unauthorized access or data corruption between the different security states.
69 RME isolates EL3 from all other Security states and moves it into its own security
71 trusted from software in Non-secure, Secure, and Realm states.
101 TF-A supports four states for feature enablement at EL3, to make them available
156    context for different security states alongside high level feature enablement
179    utilisation across the security states.
592 …oper.arm.com/documentation/102418/0101/TrustZone-in-the-processor/Switching-between-Security-states
593 .. _Security States with RME: https://developer.arm.com/documentation/den0126/0100/Security-states