Lines Matching full:world

13  * with an instance of OP-TEE running in secure world.
17  * 2. Requests from normal world
18  * 3. Requests from secure world, Remote Procedure Call (RPC), handled by
107  * Secure and normal world communicates pointers as physical address
108  * instead of the virtual address. This is because secure and normal world
109  * have completely independent memory mapping. Normal world can even have a
112  * structure to secure world.
135  * Value parameters are passed unchecked between normal and secure world.
220  * Part 2 - requests from normal world
248  * Used by non-secure world to figure out which Trusted OS is installed.
263  * Used by non-secure world to figure out which version of the Trusted OS
319  * Part 3 - Requests from secure world, RPC
358  * Wait queue primitive, helper for secure world to implement a wait queue.
360  * If secure world need to wait for a secure world mutex it issues a sleep
361  * request instead of spinning in secure world. Conversely is a wakeup
362  * request issued when a secure world mutex with a thread waiting thread is
434  *					with the secure world