Re: [PATCH 0/6] ASoC: SOF: ipc4-topology: Update the memory data building
Mark Brown <[email protected]> Fri, 31 Jul 2026 15:45:50 +0100
| Newsgroups | org.kernel.vger.linux-sound |
|---|---|
| Message-ID | <178550915043.352272.1291735907793519666.b4-ty@b4> |
On Thu, 30 Jul 2026 13:41:35 +0300, Peter Ujfalusi wrote:
> ASoC: SOF: ipc4-topology: Update the memory data building
>
> Hi,
>
> This series fixes some issues left to the first version
> sof_ipc4_mod_init_ext_dp_memory_data payload building code. The
> payload to specify memory requirements of Data Processing components,
> running as independent processes in SOF firmware.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.3
Thanks!
[1/6] ASoC: SOF: ipc4-topology: Remove dp_ from all module memory attributes
https://git.kernel.org/broonie/sound/c/5a25f27f5118
[2/6] ASoC: SOF: ipc4-topology: Fix SOF_TKN_COMP_STACK_BYTES_REQUIREMENT id
https://git.kernel.org/broonie/sound/c/18d0619ced26
[3/6] ASoC: SOF: ipc4: Add SOF_IPC4_GLB_CREATE_PIPELINE payload macros and structs
https://git.kernel.org/broonie/sound/c/52db046c388d
[4/6] ASoC: SOF: ipc4-topology: Add payload to pipeline create messages
https://git.kernel.org/broonie/sound/c/0244c162d1a5
[5/6] ASoC: SOF: ipc4-topology: Fix sof_ipc4_mod_init_ext_dp_memory_data comments
https://git.kernel.org/broonie/sound/c/e5b0daa6f974
[6/6] ASoC: SOF: ipc4-topology: Refactor sof_ipc4_widget_mod_init_msg_payload()
https://git.kernel.org/broonie/sound/c/221f3b29366e
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