From: Shengyu Qu <wiagn@4d2.org>
To: perex@perex.cz, tiwai@suse.com, hulianqin@vivo.com, i@rong.moe,
g@b4.vu, jon@soh.re, hhkieu@gmail.com, panxucc@gmail.com
Cc: wiagn233@outlook.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, Shengyu Qu <wiagn@4d2.org>
Subject: [PATCH v1] ALSA: usb-audio: Add native DSD support for NiceHCK Octave
Date: Fri, 13 Nov 2026 01:31:31 +0800 [thread overview]
Message-ID: <20261112173131.86655-1-wiagn@4d2.org> (raw)
NiceHCK Octave is an OEM of TTGK TT39039F01-PROMAX[1] and supports DSD64/
DSD128/DSD256/DSD512[2].
It advertises the UAC2 RAW_DATA format on altsetting 4 of its playback
interface, but without the DSD_RAW quirk flag the driver exposes it only as
a SPECIAL format that cannot be used.
Add QUIRK_FLAG_DSD_RAW for the device (USB ID 3302:39c3), so the altsetting
is exposed as DSD_U32_BE, enabling native DSD playback.
[1] https://www.audiosciencereview.com/forum/index.php?threads/nicehck-octave-dongle-dac.65535/post-2390027
[2] https://szttgk.com/product/HIFIAUDIOMODULE/846.html
Signed-off-by: Shengyu Qu <wiagn@4d2.org>
---
sound/usb/quirks.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index 4ec1f2a0b359a..d59eef24363ec 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -2829,6 +2829,8 @@ static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
QUIRK_FLAG_DSD_RAW),
DEVICE_FLG(0x3302, 0x17c2, /* TTGK Technology USB-C Audio */
QUIRK_FLAG_FORCE_IFACE_RESET | QUIRK_FLAG_IFACE_DELAY),
+ DEVICE_FLG(0x3302, 0x39c3, /* NiceHCK Octave */
+ QUIRK_FLAG_DSD_RAW),
DEVICE_FLG(0x339b, 0x3a07, /* Synaptics HONOR USB-C HEADSET */
QUIRK_FLAG_MIXER_PLAYBACK_MIN_MUTE),
DEVICE_FLG(0x3443, 0x930d, /* NexiGo N930W 60fps Webcam */
--
2.56.0
reply other threads:[~2026-11-12 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261112173131.86655-1-wiagn@4d2.org \
--to=wiagn@4d2.org \
--cc=g@b4.vu \
--cc=hhkieu@gmail.com \
--cc=hulianqin@vivo.com \
--cc=i@rong.moe \
--cc=jon@soh.re \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=panxucc@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wiagn233@outlook.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®