From: Takashi Iwai <tiwai@suse.de>
To: Grant Diffey <gdiffey@gmail.com>
Cc: linux-sound@vger.kernel.org,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] More quirks for M-Audio Fast Track Ultra.
Date: Sun, 19 Jul 2026 11:00:54 +0200 [thread overview]
Message-ID: <877bmrs69l.wl-tiwai@suse.de> (raw)
In-Reply-To: <CACckToXHuiq4RYeoBfpbui_wNCYSgjRmOiDFZH1EW_1VQLr3cQ@mail.gmail.com>
On Fri, 17 Jul 2026 16:50:24 +0200,
Grant Diffey wrote:
>
> Hi all
>
> 86aa1ea1f15ce broke the fast track ultra... patch adds a quirk for 'broken
> GET_CUR' which is absolutely required to be able to configure this
> interface.
Which controls are affected?
> I've also applied the IMPLICIT FEEDBACK quirk as I believe this card should
> be treated as implicit feedback like the C600
>
> This should probably be applied for the Fast track ultra 8R as well but I
> don't have one to test.
Could you resubmit in a proper format?
Please post & submit to linux-sound@vger.kernel.org instead of here,
and always put maintainers to Cc, at the next time.
thanks,
Takashi
>
>
> Regards
> Grant
> diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
> index 41149561aa06..ab5d008a2748 100644
> --- a/sound/usb/quirks.c
> +++ b/sound/usb/quirks.c
> @@ -2320,6 +2320,8 @@ static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
> QUIRK_FLAG_GENERIC_IMPLICIT_FB),
> DEVICE_FLG(0x0763, 0x2031, /* M-Audio Fast Track C600 */
> QUIRK_FLAG_GENERIC_IMPLICIT_FB),
> + DEVICE_FLG(0x0763, 0x2080, /* M-Audio Fast Track Ultra */
> + QUIRK_FLAG_MIXER_GET_CUR_BROKEN | QUIRK_FLAG_GENERIC_IMPLICIT_FB),
> DEVICE_FLG(0x07fd, 0x000b, /* MOTU M Series 2nd hardware revision */
> QUIRK_FLAG_CTL_MSG_DELAY_1M),
> DEVICE_FLG(0x08bb, 0x2702, /* LineX FM Transmitter */
prev parent reply other threads:[~2026-07-19 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 14:50 [PATCH] More quirks for M-Audio Fast Track Ultra Grant Diffey
2026-07-19 9:00 ` Takashi Iwai [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=877bmrs69l.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=gdiffey@gmail.com \
--cc=linux-sound@vger.kernel.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.