ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@vger.kernel.org,
	 linux-sunxi@googlegroups.com, linux-sunxi@lists.linux.dev,
	 linux-sound@vger.kernel.org, lander@jagmn.com,
	codekipper@gmail.com
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	 jernej.skrabec@gmail.com, samuel@sholland.org,
	andre.przywara@arm.com,  wens@csie.org,
	u.kleine-koenig@baylibre.com
Subject: Re: [PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support
Date: Tue, 10 Dec 2024 13:36:00 +0000	[thread overview]
Message-ID: <173383776048.46965.5173929465030260982.b4-ty@kernel.org> (raw)
In-Reply-To: <20241111165600.57219-1-codekipper@gmail.com>

On Mon, 11 Nov 2024 17:55:28 +0100, codekipper@gmail.com wrote:
> I've tested this patch series on the Allwinner H3, A64, H6 and H313 SoCs
> up to 192KHz.
> 24bit support is working on my H313 board but 16bit plays a bit slow and
> I suspect that there is an issue with the clock setups. This is even
> present without this patch stack. I would look to address this asap,
> but for now can you please review what's here.
> BR,
> CK
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: sun4i-spdif: Add clock multiplier settings
      commit: 0a2319308de88b9e819c0b43d0fccd857123eb31
[2/3] ASoC: sun4i-spdif: Always set the valid data to be the MSB
      commit: 80ac12ffb3a9e19a2f11eb1975ed31c9a39183c8
[3/3] ASoC: sun4i-spdif: Add working 24bit audio support
      commit: 6e750d3ec7410c8d3aa6a006d37142eb837b3c03

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


      parent reply	other threads:[~2024-12-10 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-11 16:55 [PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support codekipper
2024-11-11 16:55 ` [PATCH 1/3] ASoC: sun4i-spdif: Add clock multiplier settings codekipper
2024-11-11 16:55 ` [PATCH 2/3] ASoC: sun4i-spdif: Always set the valid data to be the MSB codekipper
2024-11-11 16:55 ` [PATCH 3/3] ASoC: sun4i-spdif: Add working 24bit audio support codekipper
2024-12-10 13:36 ` 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=173383776048.46965.5173929465030260982.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=codekipper@gmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=lander@jagmn.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=perex@perex.cz \
    --cc=samuel@sholland.org \
    --cc=tiwai@suse.com \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=wens@csie.org \
    /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