mbox series

[0/2] ASoC: SOF: ipc4-topology: Configure copier sink format

Message ID 20230209142123.17193-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: ipc4-topology: Configure copier sink format | expand

Message

Peter Ujfalusi Feb. 9, 2023, 2:21 p.m. UTC 
Hi,

In a course of creating complicated topologies where multiple output pins of a
copier is enabled, we have discovered that additional configuration needs to be
sent to the firmware to make the use cases working.

Regards,
Peter
---
Bard Liao (1):
  ASoC: SOF: ipc4-topology: set copier sink format

Ranjani Sridharan (1):
  ASoC: SOF: ipc4-topology: Print queue IDs in error

 sound/soc/sof/ipc4-topology.c | 81 +++++++++++++++++++++++++++++++----
 sound/soc/sof/ipc4-topology.h | 46 ++++++++++++++++++++
 sound/soc/sof/sof-audio.h     |  1 +
 3 files changed, 119 insertions(+), 9 deletions(-)

Comments

Mark Brown Feb. 9, 2023, 6:36 p.m. UTC | #1 
On Thu, 09 Feb 2023 16:21:21 +0200, Peter Ujfalusi wrote:
> In a course of creating complicated topologies where multiple output pins of a
> copier is enabled, we have discovered that additional configuration needs to be
> sent to the firmware to make the use cases working.
> 
> Regards,
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: ipc4-topology: Print queue IDs in error
      commit: b796ff3bf03fd8c838ddd2709ded15865e4af4a4
[2/2] ASoC: SOF: ipc4-topology: set copier sink format
      commit: 11f605633b33cdffd4ffe3b8e1e89590e8f521e7

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