[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <164570533555.1194769.3668536221336070255.b4-ty@kernel.org>
Date: Thu, 24 Feb 2022 12:22:15 +0000
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: Takashi Iwai <tiwai@...e.com>, Alexander.Deucher@....com,
krisman@...labora.com,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Jaroslav Kysela <perex@...ex.cz>, Sunil-kumar.Dommati@....com,
Liam Girdwood <lgirdwood@...il.com>,
open list <linux-kernel@...r.kernel.org>, wtli@...oton.com
Subject: Re: (subset) [PATCH 1/9] ASoC: amd: vg: fix for pm resume callback sequence
On Wed, 23 Feb 2022 12:49:30 +0530, Vijendar Mukunda wrote:
> The previous condition is used to cross check only the active
> stream status for I2S HS instance playback and capture use cases.
>
> Modified logic to invoke sequence for two i2s controller instances.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-linus
Thanks!
[1/9] ASoC: amd: vg: fix for pm resume callback sequence
(no commit info)
[2/9] ASoC: amd: vangogh: refactor i2s master mode clock sequence code
commit: 5ca4cf2c83dac27768f1d7d3e2404f5a17830ca5
[3/9] ASoC: nau8821: enable no_capture_mute flag
commit: aa9753a4677d0a2c53e7e46ca173c985a3f7b83e
[4/9] ASoC: amd: vg: update platform clock control sequence
commit: 9a617f0e109cfba2017d76f807ebb3a00c47bdca
[5/9] ASoC: amd: vg: apply sample bits pcm constraint
commit: 0c38cc1dd17e766eada0aa44be4c1a47bcbb7bc3
[6/9] ASoC: amd: vg: update acp init and deinit sequence
commit: a9230ccc0c6f5fca0b94f57729dc61e0a6098a0a
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
Powered by blists - more mailing lists