From: Takashi Iwai <tiwai@suse.de>
To: Asai Neko <sugar@sne.moe>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] ALSA: usb-audio: skip the broken mute control on AVerMedia GC553Pro
Date: Mon, 14 Sep 2026 17:53:12 +0200 [thread overview]
Message-ID: <87ecevommv.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260914-avermedia-gc553pro-alsa-v1-1-4c694e8b0cd5@sne.moe>
On Mon, 14 Sep 2026 12:58:29 +0200,
Asai Neko wrote:
>
> Skip the nonfunctional master mute control on the AVerMedia Live Gamer
> ULTRA S GC553Pro (07ca:1553).
>
> USB tracing shows that GET_CUR returns zero bytes instead of the required
> one-byte value, both through usbfs and during ALSA initialization.
> SET_CUR succeeds, but switching capture off does not mute HDMI audio.
>
> Before the change, the driver exposed a misleading PCM Capture Switch
> and logged: 3:2: failed to get current value for ch 0 (-22)
>
> With the patch applied, the switch and warning are absent. A ten-second
> sound recording through PipeWire confirmed that stereo 48 kHz, 16-bit
> capture still works.
>
> Tested on NixOS with the patched 7.3.0-rc3 kernel. The USB audio driver
> object builds with Clang and W=1; sparse and strict checkpatch pass.
>
> Signed-off-by: Asai Neko <sugar@sne.moe>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-09-14 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 10:58 [PATCH] ALSA: usb-audio: skip the broken mute control on AVerMedia GC553Pro Asai Neko
2026-09-14 15:53 ` 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=87ecevommv.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=perex@perex.cz \
--cc=sugar@sne.moe \
--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 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.