From: Takashi Iwai <tiwai@suse.de>
To: "Geoffrey D. Bennett" <g@b4.vu>
Cc: Takashi Iwai <tiwai@suse.de>, linux-sound@vger.kernel.org
Subject: Re: ALSA: usb-audio: SKIP_IFACE_SETUP regression on Focusrite Scarlett 2i2 (1235:8006)
Date: Mon, 16 Mar 2026 09:51:19 +0100 [thread overview]
Message-ID: <87bjgo9myg.wl-tiwai@suse.de> (raw)
In-Reply-To: <abcGli7C40kr72mB@m.b4.vu>
On Sun, 15 Mar 2026 20:20:54 +0100,
Geoffrey D. Bennett wrote:
>
> Hi Takashi,
>
> A user reported distorted/silent audio on 6.19.7 with a Focusrite 1st
> Generation Scarlett 2i2 (1235:8006), caused by 38c322068a26 ("ALSA:
> usb-audio: Add QUIRK_FLAG_SKIP_IFACE_SETUP").
>
> The Feedback Format (from /proc stream0) changes from 16.16 to 17.15
> when SKIP_IFACE_SETUP is enabled. The user confirmed that removing
> SKIP_IFACE_SETUP fixes the issue.
>
> This device doesn't have the internal mixer, Air, or Safe modes that
> the quirk was designed to protect, so it doesn't benefit from the
> skip.
>
> I'm not sure if there's a better fix than explicitly listing all the
> devices that I tested?
>
> E.g. replace:
>
> VENDOR_FLG(0x1235, /* Focusrite Novation */
> QUIRK_FLAG_SKIP_CLOCK_SELECTOR |
> QUIRK_FLAG_SKIP_IFACE_SETUP),
>
> with ~23 of these:
>
> DEVICE_FLG(0x1235, 0x8203, /* Focusrite Scarlett 2nd Gen 6i6 */
> QUIRK_FLAG_SKIP_CLOCK_SELECTOR |
> QUIRK_FLAG_SKIP_IFACE_SETUP),
>
> What do you think?
>
> Report: https://github.com/geoffreybennett/linux-fcp/issues/54
We can put DEVICE_FLG() entries for the known Focusrite devices that
shouldn't to set QUIRK_FLAG_SKIP_IFACE_SETUP before the VENDOR_FLG()
entry that keeps *_SKIP_IFACE_SETUP flag?
thanks,
Takashi
prev parent reply other threads:[~2026-03-16 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 19:20 ALSA: usb-audio: SKIP_IFACE_SETUP regression on Focusrite Scarlett 2i2 (1235:8006) Geoffrey D. Bennett
2026-03-16 8:51 ` 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=87bjgo9myg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=g@b4.vu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox