linux-kernel - Re: [PATCH 0/4] ASoC/SoundWire: clean up link DMA during stop for IPC4

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: <172928703885.212383.18274357800270627734.b4-ty@kernel.org>
Date: Fri, 18 Oct 2024 22:30:38 +0100
From: Mark Brown <broonie@...nel.org>
To: tiwai@...e.de, vkoul@...nel.org, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>
Cc: vinod.koul@...aro.org, linux-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org, pierre-louis.bossart@...ux.dev, 
 bard.liao@...el.com, ranjani.sridharan@...ux.intel.com
Subject: Re: [PATCH 0/4] ASoC/SoundWire: clean up link DMA during stop for
 IPC4

On Wed, 16 Oct 2024 11:29:06 +0800, Bard Liao wrote:
> Clean up the link DMA for playback during stop for IPC4 is required to
> reset the DMA read/write pointers when the stream is prepared and
> restarted after a call to snd_pcm_drain()/snd_pcm_drop().
> 
> The change is mainly on ASoC. We may go via ASoC tree with Vinod's
> Acked-by tag
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: SOF: ipc4-topology: Do not set ALH node_id for aggregated DAIs
      commit: 9822b4c90d77e3c6555fb21c459c4a61c6a8619f
[2/4] ASoC: SOF: Intel: hda: Handle prepare without close for non-HDA DAI's
      commit: 6e38a7e098d32d128b00b42a536151de9ea1340b
[3/4] soundwire: intel_ace2x: Send PDI stream number during prepare
      commit: c78f1e15e46ac82607eed593b22992fd08644d96
[4/4] ASoC: SOF: Intel: hda: Always clean up link DMA during stop
      commit: ab5593793e9088abcddce30ba8e376e31b7285fd

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