ASoC: SOF: Add rx_data pointer to snd_sof_ipc_msg struct

The rx_data pointer can be used by IPC implementations to pass the received
message (or part of the message, like the header) from platform code to
generic, high level IPC code.

IPC4 is going to be the first user of this as its implementation on Intel
platforms detaches the header and payload and the rx cannot be handled in
a similar way as it is implemented for ipc3.

If the rx_data is dynamically allocated, it is up to the platform code to
free it up.
After the message reception handling (rx_msg ops) returned, the pointer via
the msg->rx_data should be considered as invalid.

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
Reviewed-by: Rander Wang <rander.wang@intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Link: https://lore.kernel.org/r/20220505094818.10346-2-peter.ujfalusi@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
This commit is contained in:
Peter Ujfalusi 2022-05-05 12:48:16 +03:00 committed by Mark Brown
parent 6ff98a694c
commit 84c2dca3c3
No known key found for this signature in database
GPG Key ID: 24D68B725D5487D0

View File

@ -350,6 +350,9 @@ struct snd_sof_ipc_msg {
size_t reply_size; size_t reply_size;
int reply_error; int reply_error;
/* notification, firmware initiated messages */
void *rx_data;
wait_queue_head_t waitq; wait_queue_head_t waitq;
bool ipc_complete; bool ipc_complete;
}; };