From: Takashi Iwai <tiwai@suse.de>
To: Rong Zhang <i@rong.moe>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian van den Berg <faxuser@proton.me>
Subject: Re: [PATCH] ALSA: usb-audio: Add QUIRK_FLAG_MIXER_GET_CUR_BROKEN for Logitech PRO X 2 LIGHTSPEED
Date: Mon, 03 Aug 2026 08:59:29 +0200 [thread overview]
Message-ID: <87bjbjbsfi.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260731-uac-lg-pro-x-2-ls-v1-1-268eaefe66ab@rong.moe>
On Fri, 31 Jul 2026 15:45:05 +0200,
Rong Zhang wrote:
>
> The UAC mixer of the Logitech PRO X 2 LIGHTSPEED has broken mixer
> GET_CUR behavior but otherwise works fine.
>
> Add a quirk table entry matching VID/PID=0x046d/0x0af7 and apply the
> MIXER_GET_CUR_BROKEN quirk flag to make the mixer usable again.
>
> Quirky device sample (after applying the quirk flag):
>
> usb 3-2.1: New USB device found, idVendor=046d, idProduct=0af7, bcdDevice= 1.00
> usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 3-2.1: Product: PRO X 2 LIGHTSPEED
> usb 3-2.1: Manufacturer: Logitech
> usb 3-2.1: SerialNumber: 0000000000000000
> usb 3-2.1: 2:0: broken mixer GET_CUR (-18944/0/256 => -2662)
> usb 3-2.1: 6:0: broken mixer GET_CUR (-18944/0/256 => 0)
>
> Suggested-by: Brian van den Berg <faxuser@proton.me>
> Reported-by: Brian van den Berg <faxuser@proton.me>
> Link: https://lore.kernel.org/all/370007e6-b73b-4bfc-8410-a860781c7ad7@proton.me/
> Signed-off-by: Rong Zhang <i@rong.moe>
Thanks, applied now.
Takashi
prev parent reply other threads:[~2026-08-03 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 13:45 [PATCH] ALSA: usb-audio: Add QUIRK_FLAG_MIXER_GET_CUR_BROKEN for Logitech PRO X 2 LIGHTSPEED Rong Zhang
2026-08-03 6:59 ` 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=87bjbjbsfi.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=faxuser@proton.me \
--cc=i@rong.moe \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--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