Searched refs:messages (Results 1 – 18 of 18) sorted by relevance
26 power-management-messages = <0x7>;
4 When writing commit messages, please think carefully about the purpose and scope8 keep a more accurate changelog. You may use Markdown in commit messages.29 To briefly summarize, commit messages are expected to be of the form:94 in the :ref:`prerequisites <Prerequisites>` guide to validate commit messages
40 runtime messages or not. ``-1`` (default) disables the option, any other value65 By default, all boot stages print messages to the dedicated UART debug port.
183 The payload then makes them wait in another waitloop listening from messages231 enables the default UART (currently UART1) for runtime messages.
120 - Bit[2]: partition can send and receive indirect messages193 - power-management-messages195 - Specifies which power management messages a partition subscribes to.203 - vm-availability-messages205 - Specifies which VM availability messages a partition subscribes to. A set
163 power-management-messages = <0x7>;
41 power-management-messages = <0>;
51 * Having different consoles for Boot and Runtime messages52 * Having a single console for both Runtime and Boot messages268 messages to all consoles marked with the RUNTIME flag. BOOT is the default294 messages on the active console.
1828 this is also used for the MHU payload when passing messages to and from the
97 | | print diagnostic error messages and ensure they do |
99 - Information exchange between endpoints (partition messages).333 | | messages between an endpoint and the SPMC may be |
73 | | informative messages over a UART interface. |
2001 const struct phy_msg *messages; in lookup_msg() local2005 messages = messages_2d; in lookup_msg()2008 messages = messages_1d; in lookup_msg()2012 if (messages[i].index == index) { in lookup_msg()2013 ptr = messages[i].msg; in lookup_msg()
102 messages. Note that this option can only be used if the UART is reserved in
60 messages. Data is copied from/to these buffers to/from the channel registers.65 could be useful in the case of long messages because transaction time is less
492 - **CFG_TEE_TA_LOG_LEVEL**: Defines the log level used for the debug messages.
408 …- parse and report VM availability messages ([ce299f9](https://review.trustedfirmware.org/plugins/…2056 …- update debug messages to appropriate class ([a550aeb](https://review.trustedfirmware.org/plugins…4409 …- unify logging messages ([b99926e](https://review.trustedfirmware.org/plugins/gitiles/TF-A/truste…7848 …- add support for FF-A power mgmt. messages in the EL3 SPMC ([59bd2ad](https://review.trustedfirmw…8288 …- correct types in messages ([43bbdca](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tru…8344 …- correct messages with image_id ([e4c77db](https://review.trustedfirmware.org/plugins/gitiles/TF-…8412 …- correct image_id type in messages ([cec2fb2](https://review.trustedfirmware.org/plugins/gitiles/…8416 …- correct parent_node type in messages ([b9338ee](https://review.trustedfirmware.org/plugins/gitil…8428 …- correct some messages ([a211fde](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted…8447 …- correct types in messages ([6e86b46](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tru…[all …]
149 description = "Validate configuration and produce human readable error messages."