linux-kernel - Re: [PATCH v3 0/2] ASoC: prepare streams on codec-to-codec links

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: <173696991294.258685.10820885833141683786.b4-ty@kernel.org>
Date: Wed, 15 Jan 2025 19:38:32 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, linux-amlogic@...ts.infradead.org, 
 Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: s.nawrocki@...sung.com, lgirdwood@...il.com, 
 linux-kernel@...r.kernel.org, jbrunet@...libre.com, 
 ckeepax@...nsource.cirrus.com
Subject: Re: [PATCH v3 0/2] ASoC: prepare streams on codec-to-codec links

On Tue, 14 Jan 2025 22:56:15 +0100, Martin Blumenstingl wrote:
> the DRM subsystem has recently gained a HDMI audio codec framework [0].
> This is already queued for Linux 6.14.
> 
> I want to implement a HDMI controller driver for the Amlogic
> Meson8/8b/8m2 SoCs using the DRM HDMI audio codec framework. Internally
> the DRM HDMI audio codec framework relies on hdmi-codec's .prepare
> callback to be called. This unfortunately is not happening on Amlogic
> Meson8/8b/8m2 platforms [1].
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: soc-dai: add snd_soc_dai_prepare() and use it internally
      commit: d4e91adfc261de1454538ee6437e6014a2d1fca1
[2/2] ASoC: dapm: add support for preparing streams
      commit: e436d43551764bd6ca22a1ab1e80e98939b8aec7

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