Lines Matching refs:world

223 In general, each secure world TF image (BL1, BL2, BL31 and BL32) should be
242 - Internal secure world image state is inconsistent
248 Each secure world image may be provided by a different entity (for example, a
266 The secure world **must not** crash when supplied with bad data from an external
267 source. For example, data from the normal world or a hardware device. Similarly,
268 the secure world **must not** crash if it detects a non-critical problem within
275 - Secure world receives SMC from normal world with bad arguments.
276 - Secure world receives SMC from normal world at an unexpected time.
279 - Secure world receives recoverable error from hardware device. Retrying the
281 - Non-critical secure world service is not functioning correctly.
287 In some cases it may not be possible for the secure world to recover from an
312 - Secure world discovers that a critical hardware device is an unexpected and
314 - Secure world receives an unexpected and unrecoverable error from a critical
316 - Secure world discovers that it is running on unsupported hardware.
322 - Secure world continuously receives recoverable errors from a hardware device
328 If the secure world is waiting for a response from an external source (for
329 example, the normal world or a hardware device) which is critical for continued
336 - BL1 is waiting for the normal world to raise an SMC to proceed to the next
338 - A Trusted OS is waiting for a response from a proxy in the normal world that
340 - Secure world is waiting for a hardware response that is critical for continued