Lines Matching refs:message
22 to notify the client module on receiving a message.
45 ## IN-BAND message communication
47 ### Sending a message
49 the message using the channels(for example, the MHUv2 driver sends the message
50 using the message status registers in the sender channel) by calling the
64 | | | | Copy message to
65 | | | | message status
86 ### Receiving a message
88 When a message is received the transport module is signalled by the driver
89 module. The transport module then retrieves the message by calling the
90 `get_message()` function in the driver API. The message is stored in a local
91 read buffer and the length of the message header and payload is verified and
93 from the signal API. The recipient module then retrieves the message header
94 and payload from the transport module and then processes the message.
110 +----+Copy message from | |
111 | |message status registers | |
117 | | | Verify the message |
134 … | | transport_release_channel_lock() or | | Process the message
142 ## OUT-BAND message communication
144 ### Sending a message
146 Out-band messages are transmitted by the transport module by copying the message
160 | | | Copy message to |
182 ### Receiving a message
184 When a message is received the transport module is signalled by the driver
185 module. The transport module then retrieves the message by reading the shared
186 memory. The message is stored in a local read buffer and the length of the
187 message header and the payload is verified and then the recipient module is
189 recipient module then retrieves the message header and payload from the
190 transport module and then processes the message.
205 | | |Copy the message header |
219 … | | | | Process the message
237 fast channels) that needs to called back when a message is received on the fast
238 channel. So, when a message is received on the fast channel, the driver calls
280 * In-band message support enabled in the firmware.
284 * Fast Channels message support enabled in the firmware.
288 In order to send firmware message, a module needs to bind to the
294 in-turn uses the transport module. So, if a module needs to send an scmi message,
301 the module so that it can be notified on receiving a message.