From: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
zhanjun@uniontech.com, niecheng1@uniontech.com,
kernel@uniontech.com, 胡连勤 <hulianqin@vivo.com>,
Kagura <me@mail.kagurach.uk>,
stable@vger.kernel.org,
"Cryolitia PukNgae" <cryolitia.pukngae@linux.dev>
Subject: [PATCH] ALSA: usb-audio: apply quirk for MOONDROP JU Jiu
Date: Thu, 02 Apr 2026 13:36:57 +0800 [thread overview]
Message-ID: <20260402-syy-v1-1-068d3bc30ddc@linux.dev> (raw)
It(ID 31b2:0111 JU Jiu) reports a MIN value -12800 for volume control, but
will mute when setting it less than -10880.
Thanks to my girlfriend Kagura for reporting this issue.
Cc: Kagura <me@mail.kagurach.uk>
Cc: stable@vger.kernel.org
Signed-off-by: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
---
Btw, is it a good idea for turn the volume_control_quirks from
switch-case to a table and sort it accroding to USB VID&PID?
---
sound/usb/mixer.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c
index 69026cf54979..a25e8145af67 100644
--- a/sound/usb/mixer.c
+++ b/sound/usb/mixer.c
@@ -1204,6 +1204,13 @@ static void volume_control_quirks(struct usb_mixer_elem_info *cval,
cval->min = -11264; /* Mute under it */
}
break;
+ case USB_ID(0x31b2, 0x0111): /* MOONDROP JU Jiu */
+ if (!strcmp(kctl->id.name, "PCM Playback Volume")) {
+ usb_audio_info(chip,
+ "set volume quirk for MOONDROP JU Jiu\n");
+ cval->min = -10880; /* Mute under it */
+ }
+ break;
}
}
---
base-commit: 872c7433582a3570dd0c827967ba291450096bf0
change-id: 20260402-syy-f04074ca6782
Best regards,
--
Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
next reply other threads:[~2026-04-02 5:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 5:36 Cryolitia PukNgae [this message]
2026-04-02 10:48 ` [PATCH] ALSA: usb-audio: apply quirk for MOONDROP JU Jiu Takashi Iwai
2026-04-02 13:00 ` Takashi Iwai
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=20260402-syy-v1-1-068d3bc30ddc@linux.dev \
--to=cryolitia.pukngae@linux.dev \
--cc=hulianqin@vivo.com \
--cc=kernel@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=me@mail.kagurach.uk \
--cc=niecheng1@uniontech.com \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--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