linux-kernel - Re: [PATCH v1] ASoC: amd: acp: update tdm channels for specific DAI

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: <176533310879.649124.15118877289373769932.b4-ty@kernel.org>
Date: Wed, 10 Dec 2025 11:18:28 +0900
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org, 
 Raghavendra Prasad Mallela <raghavendraprasad.mallela@....com>
Cc: Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com, 
 Sunil-kumar.Dommati@....com, 
 Hemalatha Pinnamreddy <hemalatha.pinnamreddy2@....com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Venkata Prasad Potturu <venkataprasad.potturu@....com>, 
 Daniel Baluta <daniel.baluta@....com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 "open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." <linux-sound@...r.kernel.org>, 
 open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] ASoC: amd: acp: update tdm channels for specific
 DAI

On Wed, 03 Dec 2025 17:31:34 +0530, Raghavendra Prasad Mallela wrote:
> TDM channel updates were applied to all DAIs, causing configurations
> to overwrite for unrelated streams. The logic is modified to update
> channels only for targeted DAI. This prevents corruption of other DAI
> settings and resolves audio issues observed during system suspend and
> resume cycles.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: update tdm channels for specific DAI
      commit: f34836a8ddf9216ff919927cddb705022bf30aab

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