From: Takashi Iwai <tiwai@suse.de>
To: cryolitia@uniontech.com,
Cryolitia PukNgae via B4 Relay
<devnull+cryolitia.uniontech.com@kernel.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Mingcong Bai <jeffbai@aosc.io>,
Kexy Biscuit <kexybiscuit@aosc.io>,
Wang Yuli <wangyuli@deepin.org>,
Guan Wentao <guanwentao@uniontech.com>,
Nie Cheng <niecheng1@uniontech.com>,
Zhan Jun <zhanjun@uniontech.com>,
Celeste Liu <CoelacanthusHex@gmail.com>,
Guoli An <anguoli@uniontech.com>
Subject: Re: [PATCH] ALSA: usb-audio: move mixer_quirks' min_mute into common quirk
Date: Wed, 27 Aug 2025 07:56:25 +0200 [thread overview]
Message-ID: <874itti9yu.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250827-sound-quirk-min-mute-v1-1-4717aa8a4f6a@uniontech.com>
On Wed, 27 Aug 2025 05:29:02 +0200,
Cryolitia PukNgae via B4 Relay wrote:
>
> From: Cryolitia PukNgae <cryolitia@uniontech.com>
>
> We have found more and more devices that have the same problem, that
> the mixer's minimum value is muted. Accroding to pipewire's MR[1]
> and Arch Linux wiki[2], this should be a very common problem in USB
> audio devices. Move the quirk into common quirk,as a preparation of
> more devices' quirk's patch coming on the road[3].
>
> 1. https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2514
> 2. https://wiki.archlinux.org/index.php?title=PipeWire&oldid=804138#No_sound_from_USB_DAC_until_30%_volume
> 3. On the road, in the physical sense. We have been buying ton of
> these devices for testing the problem.
>
> Tested-by: Guoli An <anguoli@uniontech.com>
> Signed-off-by: Cryolitia PukNgae <cryolitia@uniontech.com>
> ---
> I also would like to know if the quirk worth a kernel param.
If the workaround becomes common for various devices, it makes sense.
Applied now to for-linus branch.
thanks,
Takashi
prev parent reply other threads:[~2025-08-27 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 3:29 Cryolitia PukNgae via B4 Relay
2025-08-27 5:56 ` 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=874itti9yu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=CoelacanthusHex@gmail.com \
--cc=anguoli@uniontech.com \
--cc=cryolitia@uniontech.com \
--cc=devnull+cryolitia.uniontech.com@kernel.org \
--cc=guanwentao@uniontech.com \
--cc=jeffbai@aosc.io \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wangyuli@deepin.org \
--cc=zhanjun@uniontech.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
all inboxes | Powered by JetHome®