| Message ID | 20220505094818.10346-1-peter.ujfalusi@linux.intel.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | ASoC: SOF: IPC4: Introduce message handling functionality | expand |
On Thu, 5 May 2022 12:48:15 +0300, Peter Ujfalusi wrote: > The series adds the basic IPC4 message handling code, implementing the ipc > callbacks. > Due to the difference between IPC3 and IPC4 messaging we need to introduce new > message container for IPC4, but the SOF internal callbacks and structures can be > kept as they were and leaving it for the IPC specific code to handle the > differences. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] ASoC: SOF: Add rx_data pointer to snd_sof_ipc_msg struct commit: 84c2dca3c3d4b8e011a2536fc7aaf2a2bdc77972 [2/3] ASoC: SOF: Add initial header file for ipc4 commit: ed85a6e6fe7c01faff4504af9d5569e8ba417999 [3/3] ASoC: SOF: ipc4: Add support for mandatory message handling functionality commit: ceb89acc4dc8f071f63f8d64442c7a5d768e4c9d All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
Hi, The series adds the basic IPC4 message handling code, implementing the ipc callbacks. Due to the difference between IPC3 and IPC4 messaging we need to introduce new message container for IPC4, but the SOF internal callbacks and structures can be kept as they were and leaving it for the IPC specific code to handle the differences. The series provides the foundation for both lowe level (sound/soc/sof/intel) and high level IPC4 implementation (topologies, firmware loading, control handling, etc). Regards, Peter --- Peter Ujfalusi (3): ASoC: SOF: Add rx_data pointer to snd_sof_ipc_msg struct ASoC: SOF: Add initial header file for ipc4 ASoC: SOF: ipc4: Add support for mandatory message handling functionality include/sound/sof/ipc4/header.h | 460 ++++++++++++++++++++++++ sound/soc/sof/Makefile | 3 +- sound/soc/sof/ipc4.c | 604 ++++++++++++++++++++++++++++++++ sound/soc/sof/sof-priv.h | 4 + 4 files changed, 1070 insertions(+), 1 deletion(-) create mode 100644 include/sound/sof/ipc4/header.h create mode 100644 sound/soc/sof/ipc4.c