[PATCH 0/8] ASoC: SOF: finalize Baytrail/CherryTrail support

[Mark Brown]

On Tue, 26 May 2020 15:36:32 -0500, Pierre-Louis Bossart wrote:
> This long-overdue patchset adds missing system suspend/resume support
> and hardens the IPC to solve module load/unload issues on specific
> devices such as Cyan Chromebook. With this series SOF is finally
> iso-feature with the legacy driver. Thanks to Ranjani and Keyon for
> the basic patches and Enric for testing.
> 
> The last part needed for Baytrail/Cherrytrail is simplification of the
> driver/card names and turn-key UCM support (on-going work with
> Jaroslav).
> 
> [...]

Applied to

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

Thanks!

[1/8] ASoC: SOF: Intel: byt: Add PM callbacks
      commit: ddcccd543f5dbd841fe305452651b0f8c1d74f0f
[2/8] ASoC: SOF: pm: handle resume on legacy Intel platforms
      commit: fc907cc527e6568b7486309188e545161891e1f2
[3/8] ASoC: Intel: bytcr_rt5640/51: remove .ignore_suspend
      commit: 512e76724ffd07c6a5eb7d93c79d160e85465228
[4/8] ASoC: Intel: byt/cht: add .pm_ops
      commit: 68224376bc2a0508f57bff67c8dcd2b5761dc939
[5/8] ASoC: SOF: ipc: ignore DSP replies received when they are not expected
      commit: d7a1ed268993f4bc758fa509b22fc730af1623f9
[6/8] ASoC: SOF: Intel: BYT: add .remove op
      commit: c691f0c6e267da4207392b1082d011323c3f8606
[7/8] ASoC: SOF: Intel: BYT: mask BUSY or DONE interrupts in handler
      commit: 3d3d1fb9ce34bc045b9d140a5f2ec531eff6a0fe
[8/8] ASoC: SOF: Intel: BYT: harden IPC initialization and handling
      commit: 3d2e5c480742b4a22534e72e2647b6c8c98a94a4

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