From: codekipper@gmail.com
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
Cc: lgirdwood@gmail.com, broonie@kernel.org, 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,
Marcus Cooper <codekipper@gmail.com>
Subject: [PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support
Date: Mon, 11 Nov 2024 17:55:28 +0100 [thread overview]
Message-ID: <20241111165600.57219-1-codekipper@gmail.com> (raw)
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
next reply other threads:[~2024-11-11 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 16:55 codekipper [this message]
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 ` [PATCH 0/3] ASoC: sun4i-spdif: Add 24bit support Mark Brown
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=20241111165600.57219-1-codekipper@gmail.com \
--to=codekipper@gmail.com \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.