From: Takashi Iwai <tiwai@suse.de>
To: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Cryolitia PukNgae <cryolitia@uniontech.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, zhanjun@uniontech.com,
niecheng1@uniontech.com, anguoli@uniontech.com,
zhaochengyi@uniontech.com, fengyuan@uniontech.com
Subject: Re: [PATCH] ALSA: usb-audio: apply quirk for Huawei Technologies Co., Ltd. CM-Q3
Date: Sat, 11 Oct 2025 12:50:13 +0200 [thread overview]
Message-ID: <87ecr9af16.wl-tiwai@suse.de> (raw)
In-Reply-To: <20251011-sound_quirk-v1-1-d693738108ee@linux.dev>
On Sat, 11 Oct 2025 11:51:18 +0200,
Cryolitia PukNgae wrote:
>
> There're several different actual hardwares sold by Huawei, using the
> same USB ID 12d1:3a07.
>
> The first one we found, having a volume control named "Headset Playback
> Volume", reports a min value -15360, and will mute iff setting it to
> -15360. It can be simply fixed by quirk flag MIXER_PLAYBACK_MIN_MUTE,
> which we have already submitted previously.[1]
>
> The second one we found today, having a volume control named "PCM
> Playback Volume", reports its min -11520 and res 256, and will mute
> when less than -11008. Because of the already existing quirk flag, we
> can just set its min to -11264, and the new minimum value will still
> not be available to userspace, so that userspace's minimum will be the
> correct -11008.
>
> 1. https://lore.kernel.org/all/20250903-sound-v1-3-d4ca777b8512@uniontech.com/
>
> Tested-by: Guoli An <anguoli@uniontech.com>
> Signed-off-by: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
Thanks, applied now.
Takashi
prev parent reply other threads:[~2025-10-11 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 9:51 [PATCH] ALSA: usb-audio: apply quirk for Huawei Technologies Co., Ltd. CM-Q3 Cryolitia PukNgae
2025-10-11 9:52 ` kernel test robot
2025-10-11 10:50 ` 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=87ecr9af16.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=anguoli@uniontech.com \
--cc=cryolitia.pukngae@linux.dev \
--cc=cryolitia@uniontech.com \
--cc=fengyuan@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=zhanjun@uniontech.com \
--cc=zhaochengyi@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