mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-sound@vger.kernel.org, linux-amlogic@lists.infradead.org,
	 Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: s.nawrocki@samsung.com, lgirdwood@gmail.com,
	 linux-kernel@vger.kernel.org, jbrunet@baylibre.com,
	 ckeepax@opensource.cirrus.com
Subject: Re: [PATCH v3 0/2] ASoC: prepare streams on codec-to-codec links
Date: Wed, 15 Jan 2025 19:38:32 +0000	[thread overview]
Message-ID: <173696991294.258685.10820885833141683786.b4-ty@kernel.org> (raw)
In-Reply-To: <20250114215617.336105-1-martin.blumenstingl@googlemail.com>

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


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2025-01-15 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 21:56 Martin Blumenstingl
2025-01-14 21:56 ` [PATCH v3 1/2] ASoC: soc-dai: add snd_soc_dai_prepare() and use it internally Martin Blumenstingl
2025-01-15  2:08   ` Kuninori Morimoto
2025-01-14 21:56 ` [PATCH v3 2/2] ASoC: dapm: add support for preparing streams Martin Blumenstingl
2025-01-15 19:38 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=173696991294.258685.10820885833141683786.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=jbrunet@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=s.nawrocki@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®