mbox series

[0/2] ASoC: SOF: ipc4: Take priority into cosideration when sorting pipelines

Message ID 20231006084454.19170-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: ipc4: Take priority into cosideration when sorting pipelines | expand

Message

Peter Ujfalusi Oct. 6, 2023, 8:44 a.m. UTC
Hi,

Add pipeline priority support for IPC4: Add support for parsing pipeline
priorities from the topology. This will be used to break the tie between
pipelines to set the trigger order when multiple pipelines are triggered
simultaneously.

Regards,
Peter
---
Rander Wang (2):
  ASoC: SOF: IPC4: get pipeline priority from topology
  ASoC: SOF: IPC4: sort pipeline based on priority

 sound/soc/sof/ipc4-pcm.c      | 55 +++++++++++++++++++++++++++++------
 sound/soc/sof/ipc4-topology.c |  5 ++--
 2 files changed, 48 insertions(+), 12 deletions(-)

Comments

Mark Brown Oct. 6, 2023, 5:45 p.m. UTC | #1
On Fri, 06 Oct 2023 11:44:52 +0300, Peter Ujfalusi wrote:
> Add pipeline priority support for IPC4: Add support for parsing pipeline
> priorities from the topology. This will be used to break the tie between
> pipelines to set the trigger order when multiple pipelines are triggered
> simultaneously.
> 
> Regards,
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: IPC4: get pipeline priority from topology
      commit: ae67b6371d0432e3fe25993189e89f814ec1e4d0
[2/2] ASoC: SOF: IPC4: sort pipeline based on priority
      commit: 4df7d6a61f2c0e0920f4f4caa02e41797974a487

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