mbox series

[0/3] ASoC: SOF: remove suport for TRIGGER_RESUME

Message ID 20211216231628.344687-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: SOF: remove suport for TRIGGER_RESUME | expand

Message

Pierre-Louis Bossart Dec. 16, 2021, 11:16 p.m. UTC 
None of the SOF platforms support INFO_RESUME, and rely on the
indirect path used by the ALSA core with the prepare and TRIGGER_START
steps.

Let's remove the left-over dead code.

Ranjani Sridharan (3):
  ASoC: SOF: pcm: remove support for RESUME trigger
  ASoC: SOF: Intel: hda: remove support for RESUME trigger
  ASoC: SOF: Intel: hda: remove support for RESUME in platform trigger

 sound/soc/sof/intel/hda-dai.c    | 10 ----------
 sound/soc/sof/intel/hda-stream.c |  1 -
 sound/soc/sof/pcm.c              | 20 --------------------
 3 files changed, 31 deletions(-)

Comments

Mark Brown Dec. 21, 2021, 2:50 a.m. UTC | #1 
On Thu, 16 Dec 2021 17:16:25 -0600, Pierre-Louis Bossart wrote:
> None of the SOF platforms support INFO_RESUME, and rely on the
> indirect path used by the ALSA core with the prepare and TRIGGER_START
> steps.
> 
> Let's remove the left-over dead code.
> 
> Ranjani Sridharan (3):
>   ASoC: SOF: pcm: remove support for RESUME trigger
>   ASoC: SOF: Intel: hda: remove support for RESUME trigger
>   ASoC: SOF: Intel: hda: remove support for RESUME in platform trigger
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: SOF: pcm: remove support for RESUME trigger
      commit: eed5391f6747ffa7e3972b53aa721bded8feeff7
[2/3] ASoC: SOF: Intel: hda: remove support for RESUME trigger
      commit: 9b465060d144dd8196729cc8d77e328f1328dcbf
[3/3] ASoC: SOF: Intel: hda: remove support for RESUME in platform trigger
      commit: 35218cf61869ca4b11c8c0b49a95f75f379e403a

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