linux-kernel - Re: [PATCH 1/2] ASoC: soc-pcm: add a flag to reverse the stop sequence

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 16 Jul 2021 16:05:32 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vijendar Mukunda <vijendar.mukunda@....com>,
        alsa-devel@...a-project.org
Cc:     Mark Brown <broonie@...nel.org>, Alexander.Deucher@....com,
        Peter Ujfalusi <peter.ujfalusi@...com>, amistry@...gle.com,
        Jaroslav Kysela <perex@...ex.cz>, nartemiev@...gle.com,
        Takashi Iwai <tiwai@...e.com>,
        open list <linux-kernel@...r.kernel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Vijendar Mukunda <Vijendar.Mukunda@....com>,
        Sunil-kumar.Dommati@....com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Basavaraj.Hiregoudar@....com
Subject: Re: [PATCH 1/2] ASoC: soc-pcm: add a flag to reverse the stop sequence

On Fri, 16 Jul 2021 18:00:12 +0530, Vijendar Mukunda wrote:
> On stream stop, currently CPU DAI stop sequence invoked first
> followed by DMA. For Few platforms, it is required to stop the
> DMA first before stopping CPU DAI.
> 
> Introduced new flag in dai_link structure for reordering stop sequence.
> Based on flag check, ASoC core will re-order the stop sequence.

Applied to

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

Thanks!

[1/2] ASoC: soc-pcm: add a flag to reverse the stop sequence
      commit: 59dd33f82dc0975c55d3d46801e7ca45532d7673
[2/2] ASoC: amd: reverse stop sequence for stoneyridge platform
      commit: 7883490cba002121a5870e786a1dc0acce5e1caf

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