mbox series

[0/4] ASoC: codecs: Realtek/SoundWire: fix remove/suspend issues

Message ID 20210204201739.25206-1-pierre-louis.bossart@linux.intel.com
Headers show
Series ASoC: codecs: Realtek/SoundWire: fix remove/suspend issues | expand

Message

Pierre-Louis Bossart Feb. 4, 2021, 8:17 p.m. UTC 
These issues and fixes were identified during our module load/unload
and suspend/resume stress tests.

Bard Liao (1):
  ASoC: rt5682: do nothing in rt5682_suspend/resume in sdw mode

Pierre-Louis Bossart (3):
  ASoC: rt700-sdw: use cancel_work_sync() in .remove as well as .suspend
  ASoC: rt711-sdw: use cancel_work_sync() for .remove
  ASoC: rt5682-sdw: cancel_work_sync() in .remove and .suspend

 sound/soc/codecs/rt5682-sdw.c | 4 +++-
 sound/soc/codecs/rt5682.c     | 6 ++++++
 sound/soc/codecs/rt700-sdw.c  | 4 ++--
 sound/soc/codecs/rt711-sdw.c  | 4 ++--
 4 files changed, 13 insertions(+), 5 deletions(-)

Comments

Mark Brown Feb. 5, 2021, 2:56 p.m. UTC | #1 
On Thu, 4 Feb 2021 14:17:35 -0600, Pierre-Louis Bossart wrote:
> These issues and fixes were identified during our module load/unload
> and suspend/resume stress tests.
> 
> Bard Liao (1):
>   ASoC: rt5682: do nothing in rt5682_suspend/resume in sdw mode
> 
> Pierre-Louis Bossart (3):
>   ASoC: rt700-sdw: use cancel_work_sync() in .remove as well as .suspend
>   ASoC: rt711-sdw: use cancel_work_sync() for .remove
>   ASoC: rt5682-sdw: cancel_work_sync() in .remove and .suspend
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: rt700-sdw: use cancel_work_sync() in .remove as well as .suspend
      commit: 737ee8bdf682cedb3c42b713d20ffa5c899591fb
[2/4] ASoC: rt711-sdw: use cancel_work_sync() for .remove
      commit: 121871a75ae4032cf5e506ba5159761805709def
[3/4] ASoC: rt5682-sdw: cancel_work_sync() in .remove and .suspend
      commit: c792c3690b82c8d26c01494a51ebf66d9cae7e72
[4/4] ASoC: rt5682: do nothing in rt5682_suspend/resume in sdw mode
      commit: 30fd8f65af78d0ac0859cf436beed14834b39802

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