mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: noble228@gmail.com
To: tiwai@suse.com
Cc: perex@perex.cz, hulianqin@vivo.com, lina+kernel@asahilina.net,
	cyan.vtb@gmail.com, dan.carpenter@linaro.org, bsevens@google.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	"noble.yang" <noble.yang@comtrue-inc.com>
Subject: [PATCH] ALSA: usb-audio: Add DSD support for Comtrue USB Audio device
Date: Thu, 31 Jul 2025 19:06:14 +0800	[thread overview]
Message-ID: <20250731110614.4070-1-noble228@gmail.com> (raw)

From: "noble.yang" <noble.yang@comtrue-inc.com>

The vendor Comtrue Inc. (0x2fc6) produces USB audio chipsets like
the CT7601 which are capable of Native DSD playback.

This patch adds QUIRK_FLAG_DSD_RAW for Comtrue (VID 0x2fc6), which enables
native DSD playback (DSD_U32_LE) on their USB Audio device. This has been
verified under Ubuntu 25.04 with JRiver.


Signed-off-by: noble.yang <noble.yang@comtrue-inc.com>
---
 sound/usb/quirks.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
index bd24f3a78ea9..cbb66125f839 100644
--- a/sound/usb/quirks.c
+++ b/sound/usb/quirks.c
@@ -2408,6 +2408,8 @@ static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
 		   QUIRK_FLAG_DSD_RAW),
 	VENDOR_FLG(0x2d87, /* Cayin device */
 		   QUIRK_FLAG_DSD_RAW),
+ 	VENDOR_FLG(0x2fc6, /* Comture-inc devices */
+		   QUIRK_FLAG_DSD_RAW),	   
 	VENDOR_FLG(0x3336, /* HEM devices */
 		   QUIRK_FLAG_DSD_RAW),
 	VENDOR_FLG(0x3353, /* Khadas devices */
-- 
2.48.1


             reply	other threads:[~2025-07-31 11:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 11:06 noble228 [this message]
2025-07-31 15:01 ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2025-07-31  8:15 noble228
2025-07-31  9:15 ` Takashi Iwai
2025-07-31  4:51 noble.yang
2025-07-31  5:39 ` Takashi Iwai
2025-07-31  5:50   ` noble.yang
2025-07-31  5:51     ` Takashi Iwai

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=20250731110614.4070-1-noble228@gmail.com \
    --to=noble228@gmail.com \
    --cc=bsevens@google.com \
    --cc=cyan.vtb@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=hulianqin@vivo.com \
    --cc=lina+kernel@asahilina.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=noble.yang@comtrue-inc.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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®