Searched refs:nonsecure (Results 1 – 21 of 21) sorted by relevance
55 nonsecure-channels = <8 9 10 11 12>;64 nonsecure-channels = <0>;71 nonsecure-channels = <0>;
62 nonsecure-channels = <8 9 10 11 12>;72 nonsecure-channels = <0 2 3>;80 nonsecure-channels = <0 2 3>;
36 label = "image-0-nonsecure";44 label = "image-1-nonsecure";
47 label = "image-0-nonsecure";55 label = "image-1-nonsecure";
39 label = "image-0-nonsecure";49 label = "image-1-nonsecure";
17 label = "image-0-nonsecure";
54 label = "image-0-nonsecure";64 label = "image-1-nonsecure";
4 __TZ_WRAP_FUNC() is part of the nonsecure TrustZone API, but is itself6 of secure/nonsecure firmware.
57 label = "image-0-nonsecure";67 label = "image-1-nonsecure";
66 label = "image-0-nonsecure";74 label = "image-1-nonsecure";
43 label = "image-0-nonsecure";53 label = "image-1-nonsecure";
129 label = "image-0-nonsecure";137 label = "image-1-nonsecure";
337 label = "image-0-nonsecure";368 label = "image-1-nonsecure";
227 nonsecure-channels = <5 6>;
220 nonsecure-channels = <5 6>;
24 The sys_reboot call is routed to TF-M, since the nonsecure app is not allowed
563 each core has both a Secure and a Nonsecure domain. If *core A nonsecure* (A_NS) is the565 *core B nonsecure* (A_NS-B_NS). *B_NS* domain has one link, to *core B secure*
1348 * :github:`34570` - IPC samples running secure but configured nonsecure (AN521)
