Lines Matching refs:from
98 overridden from the command line or by the platform makefile (although it may be
155 used (Banned) or are discouraged from use and must be used with care (Caution).
267 The secure world **must not** crash when supplied with bad data from an external
268 source. For example, data from the normal world or a hardware device. Similarly,
270 itself or the system. It must make every effort to recover from the problem by
276 - Secure world receives SMC from normal world with bad arguments.
277 - Secure world receives SMC from normal world at an unexpected time.
278 - BL31 receives SMC from BL32 with bad arguments.
279 - BL31 receives SMC from BL32 at unexpected time.
280 - Secure world receives recoverable error from hardware device. Retrying the
288 In some cases it may not be possible for the secure world to recover from an
309 - BL32 receives an unexpected SMC response from BL31 that it is unable to
310 recover from.
315 - Secure world receives an unexpected and unrecoverable error from a critical
323 - Secure world continuously receives recoverable errors from a hardware device
329 If the secure world is waiting for a response from an external source (for
333 the system from executing in this state indefinitely.
339 - A Trusted OS is waiting for a response from a proxy in the normal world that
358 compiler from making optimizations. There are legitimate uses for them,
399 includes pointers to types that are abstracted away from the known API and
415 - Use ``ssize_t`` when returning the ``sizeof()`` something from a function that