mbox series

[0/2] ASoC: SOF: Intel/ipc4: Do not reset BE DAI pipeline during stop/suspend

Message ID 20230515112022.30297-1-peter.ujfalusi@linux.intel.com (mailing list archive)
Headers show
Series ASoC: SOF: Intel/ipc4: Do not reset BE DAI pipeline during stop/suspend | expand

Message

Peter Ujfalusi May 15, 2023, 11:20 a.m. UTC 
Hi,

Do not reset pipelines during the stop/suspend triggers in the BE DAI
ops as the BE DAI pipeline needs to be left in the PAUSED state. It should
only be reset during hw_free. This simplification is already done for
the FE pipelines and the DAI trigger only toggles the states between
PAUSED and RUNNING.

Regards
Peter
---
Ranjani Sridharan (2):
  ASoC: SOF: Intel: hda-dai-ops: Split the get_hext_stream() op for IPC4
  ASoC: SOF: ipc4-pcm: reset all pipelines during FE DAI hw_free

 sound/soc/sof/intel/hda-dai-ops.c | 69 +++++++++++++++++++++++--------
 sound/soc/sof/ipc4-pcm.c          |  4 +-
 sound/soc/sof/ipc4-topology.c     |  1 -
 3 files changed, 53 insertions(+), 21 deletions(-)

Comments

Mark Brown May 15, 2023, 3:22 p.m. UTC | #1 
On Mon, 15 May 2023 14:20:20 +0300, Peter Ujfalusi wrote:
> Do not reset pipelines during the stop/suspend triggers in the BE DAI
> ops as the BE DAI pipeline needs to be left in the PAUSED state. It should
> only be reset during hw_free. This simplification is already done for
> the FE pipelines and the DAI trigger only toggles the states between
> PAUSED and RUNNING.
> 
> Regards
> Peter
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: SOF: Intel: hda-dai-ops: Split the get_hext_stream() op for IPC4
      commit: 81a5d699217d1ae2853d6b022fc110aa95a2ff52
[2/2] ASoC: SOF: ipc4-pcm: reset all pipelines during FE DAI hw_free
      commit: 225f37b578a9f6462afd46c976e31977f765c38b

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