linux-kernel - Re: [PATCH] ASoC: soc-pcm: Fix hw_params() and DAPM widget 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]

Message-Id: <174463900542.86688.12975575965483573998.b4-ty@kernel.org>
Date: Mon, 14 Apr 2025 14:56:45 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-sound@...r.kernel.org, "Sheetal ." <sheetal@...dia.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
 jonathanh@...dia.com, thierry.reding@...il.com, mkumard@...dia.com, 
 spujar@...dia.com
Subject: Re: [PATCH] ASoC: soc-pcm: Fix hw_params() and DAPM widget
 sequence

On Fri, 04 Apr 2025 10:59:53 +0000, Sheetal . wrote:
> Issue:
>  When multiple audio streams share a common BE DAI, the BE DAI
>  widget can be powered up before its hardware parameters are configured.
>  This incorrect sequence leads to intermittent pcm_write errors.
> 
>  For example, the below Tegra use-case throws an error:
>   aplay(2 streams) -> AMX(mux) -> ADX(demux) -> arecord(2 streams),
>   here, 'AMX TX' and 'ADX RX' are common BE DAIs.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-pcm: Fix hw_params() and DAPM widget sequence
      commit: 9aff2e8df240e84a36f2607f98a0a9924a24e65d

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