On Mon, 13 Mar 2023 13:03:37 +0200, Peter Ujfalusi wrote:
This series will add support for bytes control and topology types. With IPC4 only the binary payload is sent to the firmware via LARGE_CONFIG message (which does similar multi-part message handling as the IPC3 control message did).
The bytes payload itself is not checked by the kernel but user space expected to wrap it in sof_abi_hdr struct in order to get the target information of the binary data.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SOF: ipc3-control: Rename snd_sof_refresh_control() commit: 3eac8de3f51b3567c4ba6139736b59027da56285 [2/7] ASoC: SOF: ipc3-control: Merge functions to handle bytes_ext get variants commit: 76fc628aebdb452e3c620d9ff5c5e9448d316754 [3/7] ASoC: SOF: uapi: header: Convert sof_abi_hdr comments to kernel style commit: 2e4ef6f4798c1d2951dd7bb3ae5f0d41ec3d31e8 [4/7] ASoC: SOF: uapi: header: Update sof_abi_hdr doc for IPC4 use commit: ea4a4e82f625ae451175a2a74779776b006d25a1 [5/7] ASoC: SOF: ipc4-control: set_volume_data only applies to VOLSW family commit: dc47ef4f8f6426cd625eb4057e174541e7c23ccd [6/7] ASoC: SOF: ipc4-topology: Add support for TPLG_CTL_BYTES commit: a382082ff74b036944cbc5b6ad29b65f633acd3a [7/7] ASoC: SOF: ipc4-control: Add support for bytes control get and put commit: a062c8899fede2ab5660a817e9b602d3fa280a99
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