Lines Matching full:message

3  * System Control and Management Interface (SCMI) Message Protocol
39  * struct scmi_msg_resp_prot_version - Response for a message
48  * Response to a generic message with message type SCMI_MSG_VERSION
56  * struct scmi_msg - Message(Tx/Rx) structure
67  * struct scmi_msg_hdr - Message(Tx/Rx) header
69  * @id: The identifier of the message being sent
70  * @protocol_id: The identifier of the protocol used to send @id message
71  * @type: The SCMI type for this message
72  * @seq: The token to identify the message. When a message returns, the
73  *	platform returns the whole message header unmodified including the
89  * struct scmi_xfer - Structure representing a message flow
92  * @hdr: Transmit message header
93  * @tx: Transmit message
94  * @rx: Receive message, the buffer should be pre-allocated to store
95  *	message. If request-ACK protocol is used, we can reuse the same
97  * @done: command message transmit completion event
98  * @async_done: pointer to delayed response message received event completion
105  *	   response message, the xfer could be finally put on the TX path, and
178  * @num_remaining: Number of remaining items in the multi-part message.
182  * @rx_len: Size in bytes of the currenly processed message; it can be used by
200  *		     SCMI command request pointed by @message. @desc_index is
204  *		  iterator state from the actual message response.
206  *		      each chunk of the multi-part message.
209 	void (*prepare_message)(void *message, unsigned int desc_index,
239  *			parse multi-message responses: when run the iterator