From: Takashi Iwai <tiwai@suse.de>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: Brian van den Berg <faxuser@proton.me>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ALSA: usb-audio: Add quirk for Logitech PRO X 2 LIGHTSPEED
Date: Mon, 03 Aug 2026 09:38:33 +0200 [thread overview]
Message-ID: <87tspbac1y.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGwozwGXLu8qWQw8MwMFQ=jiWfRJX6Xs0=4mMOwH2cPJHnjigA@mail.gmail.com>
On Fri, 31 Jul 2026 17:01:50 +0200,
Antheas Kapenekakis wrote:
>
> On Fri, 31 Jul 2026 at 05:13, Brian van den Berg <faxuser@proton.me> wrote:
> >
> > The UAC mixer of Logitech PRO X 2 LIGHTSPEED works fine except that its
> > volume GET_CUR method returns sticky values.
> >
> > Since commit 86aa1ea1f15c
> > ("ALSA: usb-audio: Do not expose sticky mixers"), the sticky check
> > considers the mixer to be sticky and unnecessarily disables the mixer.
> >
> > Add QUIRK_FLAG_MIXER_GET_CUR_BROKEN for Logitech PRO X 2 LIGHTSPEED
> > (046d:0af7) to address this.
> >
> > Compiled and tested on 7.2-rc5
>
> There is a first time for everything. Happy to have helped with your
> first submission. The description still seems a bit vague to me as I
> do not have the mixer. Maybe there is a better way to phrase it. But I
> will leave this up to Takashi and Jaroslav. Hopefully next time you
> get most things right on the V1 ;)
>
> Reviewed-by: Antheas Kapenekakis <lkml@antheas.dev>
>
> > Signed-off-by: Brian van den Berg <faxuser@proton.me>
FYI, somehow this mail thread didn't reach to my inbox directly, so I
took another fix from Rong already now -- which is the very same fix.
Takashi
prev parent reply other threads:[~2026-08-03 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 3:13 [PATCH v4] ALSA: usb-audio: Add quirk for Logitech PRO X 2 LIGHTSPEED Brian van den Berg
2026-07-31 15:01 ` Antheas Kapenekakis
2026-08-03 7:38 ` 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=87tspbac1y.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=faxuser@proton.me \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkml@antheas.dev \
--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