ASoC: sun4i-spdif: Add 24bit support

[PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support

Posted by codekipper@gmail.com 1 year, 2 months ago

From: Marcus Cooper <codekipper@gmail.com>

Hi All,
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

George Lander (1):
  ASoC: sun4i-spdif: Add clock multiplier settings

Marcus Cooper (2):
  ASoC: sun4i-spdif: Always set the valid data to be the MSB
  ASoC: sun4i-spdif: Add working 24bit audio support

 sound/soc/sunxi/sun4i-spdif.c | 24 ++++++++++++++++++------
 1 file changed, 18 insertions(+), 6 deletions(-)

-- 
2.47.0

Re: [PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support

Posted by Mark Brown 1 year, 1 month ago

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