From: Johan Hovold <johan@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
lgirdwood@gmail.com, ckeepax@opensource.cirrus.com,
kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: codecs: wcd938x: fix dB range for HPHL and HPHR
Date: Fri, 7 Jul 2023 15:40:15 +0200 [thread overview]
Message-ID: <ZKgVv-G6y16rPdcN@hovoldconsulting.com> (raw)
In-Reply-To: <efaf5960-bcc5-6d52-5552-e1505a13b635@linaro.org>
On Fri, Jul 07, 2023 at 01:54:31PM +0100, Srinivas Kandagatla wrote:
> On 07/07/2023 08:35, Johan Hovold wrote:
> > On Wed, Jul 05, 2023 at 01:57:23PM +0100, Srinivas Kandagatla wrote:
> >> static const SNDRV_CTL_TLVD_DECLARE_DB_MINMAX(ear_pa_gain, 600, -1800);
> >> -static const SNDRV_CTL_TLVD_DECLARE_DB_MINMAX(line_gain, 600, -3000);
> >> +static const DECLARE_TLV_DB_SCALE(line_gain, -3000, 150, -3000);
> >
> > This looks wrong, and indeed that forth argument appears to be a mute
> > flag. I guess that one should have been 0 (false) here?
>
> yes, this should be true instead of a mute dB value.
Ok, so mute is supported. Then that argument can just be changed to "1"
as a cleanup to follow the current convention.
> > Headphone output also appears to be way too loud by default with this
> > patch (alone) applied. Perhaps it's just the default mixer settings need
> > to be updated to match?
> >
> > It looks like you're inverting the scale above. Perhaps that's intended,
>
> yes, the highest value corresponds to lowest dB which is why its inverted.
Got it, thanks.
> > but some more details in the commit message as to what was wrong and
> > what you intended to do would have been good.
>
> HPHR/HPHL Volume control is broken on this codec.
> current UCM uses digital volume control for x13s which needs to be moved
> to Analog volume control.
> I have this change https://termbin.com/mpp9 in UCM which I plan to send
> out once I test and fix other paths as well.
With those UCM changes the headphone volume appears to be restored even
if pavucontrol now sets the "base" marker at 80% rather than 20% volume
on the X13s (which is much too loud here).
Audio quality seem fine and I'm not hearing any distortion at 20%
volume as some people were complaining about (even if I haven't really
used the headphones myself before).
Sounds like you had a similar fix for the speaker distortion coming soon
too, looking forward to that one.
Johan
prev parent reply other threads:[~2023-07-07 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 12:57 [PATCH] ASoC: codecs: wcd938x: fix dB range for HPHL and HPHR Srinivas Kandagatla
2023-07-06 15:03 ` Mark Brown
2023-07-07 7:35 ` Johan Hovold
2023-07-07 12:37 ` Mark Brown
2023-07-07 12:54 ` Srinivas Kandagatla
2023-07-07 13:20 ` Takashi Iwai
2023-07-07 13:22 ` Mark Brown
2023-07-07 13:30 ` Takashi Iwai
2023-07-07 13:35 ` Mark Brown
2023-07-07 13:47 ` Takashi Iwai
2023-07-07 15:06 ` Mark Brown
2023-07-10 8:19 ` Takashi Iwai
2023-07-07 13:40 ` Johan Hovold [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=ZKgVv-G6y16rPdcN@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox