public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Phil Willoughby <willerz@gmail.com>
Cc: linux-sound@vger.kernel.org, Yue Wang <yuleopen@gmail.com>
Subject: Re: [PATCH 1/1] NeuralDSP Quad Cortex isn't a DSD Device
Date: Fri, 27 Mar 2026 20:10:37 -0300	[thread overview]
Message-ID: <accObDQDuDTab7my@geday> (raw)
In-Reply-To: <20260327213318.5338-2-willerz@gmail.com>

Hi Phil,

On Fri, Mar 27, 2026 at 09:21:01PM +0000, Phil Willoughby wrote:
> Signed-off-by: Phil Willoughby <willerz@gmail.com>
> Cc: Yue Wang <yuleopen@gmail.com>
> ---
>  sound/usb/quirks.c | 2 ++
>  1 file changed, 2 insertions(+)
>

Please provide an appropriate commit message and remember to Cc: the
relevant maintainers.

Thanks,
Geraldo Nascimento

> diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
> index 4955cbe3b60a..67e812bd9113 100644
> --- a/sound/usb/quirks.c
> +++ b/sound/usb/quirks.c
> @@ -2361,6 +2361,8 @@ static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
>  		   QUIRK_FLAG_PLAYBACK_FIRST | QUIRK_FLAG_GENERIC_IMPLICIT_FB),
>  	DEVICE_FLG(0x13e5, 0x0001, /* Serato Phono */
>  		   QUIRK_FLAG_IGNORE_CTL_ERROR),
> +	DEVICE_FLG(0x152a, 0x880a, /* NeuralDSP Quad Cortex */
> +		   0), /* Doesn't have the vendor quirk which would otherwise apply */
>  	DEVICE_FLG(0x154e, 0x1002, /* Denon DCD-1500RE */
>  		   QUIRK_FLAG_ITF_USB_DSD_DAC | QUIRK_FLAG_CTL_MSG_DELAY),
>  	DEVICE_FLG(0x154e, 0x1003, /* Denon DA-300USB */
> -- 
> 2.53.0
> 
> 

      reply	other threads:[~2026-03-27 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 21:21 [PATCH 0/1] Mark NeuralDSP Quad Cortex as not supporting DSD playback Phil Willoughby
2026-03-27 21:21 ` [PATCH 1/1] NeuralDSP Quad Cortex isn't a DSD Device Phil Willoughby
2026-03-27 23:10   ` Geraldo Nascimento [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=accObDQDuDTab7my@geday \
    --to=geraldogabriel@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=willerz@gmail.com \
    --cc=yuleopen@gmail.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