mbox series

[0/3] ASoC: SOF: topology/intel improvements

Message ID 20240624121519.91703-1-pierre-louis.bossart@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: topology/intel improvements | expand

Message

Pierre-Louis Bossart June 24, 2024, 12:15 p.m. UTC
Two updates for corner cases seen with new topologies, and one
correction for the number of periods reported by Chrome stress tests.

Peter Ujfalusi (3):
  ASoC: SOF: ipc4-topology: Use single token list for the copiers
  ASoC: SOF: ipc4-topology: Use correct queue_id for requesting input
    pin format
  ASoC: SOF: Intel: hda-pcm: Limit the maximum number of periods by
    MAX_BDL_ENTRIES

 sound/soc/sof/intel/hda-pcm.c |  6 ++++
 sound/soc/sof/ipc4-topology.c | 57 ++++++++++++++++-------------------
 2 files changed, 32 insertions(+), 31 deletions(-)

Comments

Mark Brown June 25, 2024, 11:33 a.m. UTC | #1
On Mon, 24 Jun 2024 14:15:16 +0200, Pierre-Louis Bossart wrote:
> Two updates for corner cases seen with new topologies, and one
> correction for the number of periods reported by Chrome stress tests.
> 
> Peter Ujfalusi (3):
>   ASoC: SOF: ipc4-topology: Use single token list for the copiers
>   ASoC: SOF: ipc4-topology: Use correct queue_id for requesting input
>     pin format
>   ASoC: SOF: Intel: hda-pcm: Limit the maximum number of periods by
>     MAX_BDL_ENTRIES
> 
> [...]

Applied to

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

Thanks!

[2/3] ASoC: SOF: ipc4-topology: Use correct queue_id for requesting input pin format
      commit: fe836c78ef1ff16da32912c22348091a0d67bda1

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