mbox series

[0/3] ASoC: SOF: ipc4: Add core_id support from topology

Message ID 20230307123556.31328-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: ipc4: Add core_id support from topology | expand

Message

Peter Ujfalusi March 7, 2023, 12:35 p.m. UTC
Hi,

The following series will add support for handling the core_id token which is
needed for supporting multiple cores with complex topologies.

Regards,
Peter
---
Peter Ujfalusi (2):
  ASoC: SOF: ipc4: Add macro to set the core_id in create_pipe message
  ASoC: SOF: ipc4-topology: Add support for core_id for pipelines

Rander Wang (1):
  ASoC: SOF: ipc4-topology: add core token in each module extended token
    list

 include/sound/sof/ipc4/header.h |  4 ++++
 sound/soc/sof/ipc4-topology.c   | 13 ++++++++++---
 sound/soc/sof/ipc4-topology.h   |  2 ++
 3 files changed, 16 insertions(+), 3 deletions(-)

Comments

Mark Brown March 8, 2023, 1:52 p.m. UTC | #1
On Tue, 07 Mar 2023 14:35:53 +0200, Peter Ujfalusi wrote:
> The following series will add support for handling the core_id token which is
> needed for supporting multiple cores with complex topologies.
> 
> Regards,
> Peter
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: SOF: ipc4: Add macro to set the core_id in create_pipe message
      commit: 11f45690b3f6c6a2b5c57dbb036df3f838f7c016
[2/3] ASoC: SOF: ipc4-topology: Add support for core_id for pipelines
      commit: 05ade472278a1a2fccc465ace205d6cfa9b521d5
[3/3] ASoC: SOF: ipc4-topology: add core token in each module extended token list
      commit: 755ddc3acd50ca70e46b032c5c4a078e7b1b7d46

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