Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Sidharth Seela <sidharthseela@gmail.com>
To: perex@perex.cz, tiwai@suse.com, zhujun2@cmss.chinamobile.com,
	kuninori.morimoto.gx@renesas.com
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC]sound:usb:mixer.c: Solving 'Generic AB13X USB Audio' Unlikely volume range.
Date: Mon, 29 Sep 2025 19:07:52 +0530	[thread overview]
Message-ID: <20250929133752.31847-1-sidharthseela@gmail.com> (raw)

Dear Maintainers,
I am using a generic "boat" make earphones, which are too loud across
different systems with eg: iOS, macOS, Debian Linux. And hence I believe
the issue is not with a driver but the headphones.

After connecting this device to laptop I get the following in dmesg logs:
	usb 1-5: New USB device found, idVendor=001f, idProduct=0b21, bcdDevice= 1.00
	usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
	usb 1-5: Product: AB13X USB Audio
	usb 1-5: Manufacturer: Generic
	usb 1-5: SerialNumber: 20210726905926
	usb 1-5: Warning! Unlikely big volume range (=11520), cval->res is probably wrong.
	usb 1-5: [2] FU [PCM Playback Volume] ch = 2, val = -11520/0/1
	usb 1-5: Warning! Unlikely big volume range (=8191), cval->res is probably wrong.
	usb 1-5: [5] FU [Mic Capture Volume] ch = 1, val = 0/8191/1

By using pavucontrol, I am able to get fair sound, after reducing 17dB in
Analog Stereo Output and reducing 6dB in Digital Stereo Output.

I believe this issue could be solved by adding a quirk patch to
sound/usb/mixer.c:1096 (/* volume control quriks */).


BR,
Sidharth Seela

             reply	other threads:[~2025-09-29 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 13:37 Sidharth Seela [this message]
2025-09-29 15:20 ` [RFC]sound:usb:mixer.c: Solving 'Generic AB13X USB Audio' Unlikely volume range Takashi Iwai
2025-09-30 13:46   ` Sidharth Seela

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=20250929133752.31847-1-sidharthseela@gmail.com \
    --to=sidharthseela@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zhujun2@cmss.chinamobile.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