From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Martin Kepplinger <martin.kepplinger@puri.sm>
Cc: alsa-devel@alsa-project.org, kernel@puri.sm,
patches@opensource.cirrus.com, tiwai@suse.com,
lgirdwood@gmail.com, broonie@kernel.org, geert@glider.be,
daniel.baluta@nxp.com
Subject: Re: [PATCH] wm8962: add a simple DMIC enable control
Date: Thu, 3 Feb 2022 11:05:18 +0000 [thread overview]
Message-ID: <20220203110518.GF18506@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <62ee89792a3f8921b4aad4d47f4db0bf2adb33f0.camel@puri.sm>
On Thu, Feb 03, 2022 at 10:57:44AM +0100, Martin Kepplinger wrote:
> Am Mittwoch, dem 02.02.2022 um 13:35 +0000 schrieb Charles Keepax:
> > On Wed, Feb 02, 2022 at 12:55:04PM +0100, Martin Kepplinger wrote:
> > > Am Mittwoch, dem 02.02.2022 um 10:46 +0000 schrieb Charles Keepax:
> > > > On Wed, Feb 02, 2022 at 11:17:34AM +0100, Martin Kepplinger
> > > > wrote:
> > > > > Am Mittwoch, dem 02.02.2022 um 09:53 +0000 schrieb Charles
> > > > > Keepax:
> > > > > > On Tue, Feb 01, 2022 at 04:01:13PM +0100, Martin Kepplinger
> > > > > > wrote:
> > > Volume / sensitivity of Analog input is too low, I saw that before.
> > > What would you try to change that?
> > >
> >
> > Hmm... you say you saw this before? I assume the input volume
> > is always low, not just low sometimes? I would probably start by
> > checking the voltage you have on the micbias, make sure that is
> > as expected. Does the signal coming into the IN3R pin look low on
> > a scope or is it just the level after it has been through the ADC
> > on the chip that seems low?
>
> Literally *no* effort went into this yet :) All I see is when I set the
> "headset mic" volume to max in gnome settings, the recorded volume is
> something like "almost usable", so that's off a bit.
>
> I can't easily measure, but different headset mics produce similar
> volume.
>
No problem keep me posted any additional tests/info you guys get
might help out here. Looking through your routing I think you are
sending the mic directly to the speaker, I would definitely test
capturing the signal over the I2S as well to confirm it is
consistently a low volume on both paths.
> :) thank you very much so far. You already really helped. We can even
> make the mic available now (to enable manually by the user) while we
> look into the volume and detection.
>
Happy to help, please feel free to keep the questions/debug info
coming.
> numid=11,iface=MIXER,name='Capture Switch'
> ; type=BOOLEAN,access=rw------,values=2
> : values=off,off
Ermm.... this should be muting the input PGA? I wouldn't expect
any input from the analogue here.
> numid=10,iface=MIXER,name='Capture Volume'
> ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
> : values=29,29
> | dBscale-min=-23.25dB,step=0.75dB,mute=0
This is the PGA volume on the inputs and appears to be set to
-1.5dB. Not sure if that might be part of the problem?
> numid=23,iface=MIXER,name='DAC Monomix Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=on
> numid=9,iface=MIXER,name='Digital Capture Volume'
> ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
> : values=116,116
> | dBscale-min=-72.00dB,step=0.75dB,mute=1
This looks set to +15dB at the moment, so presumably no problem
here.
> numid=84,iface=MIXER,name='INPGAR IN1R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
This is a total random hunch and might just be my unfamilarity
with the chip. But I would definitely try a test with this switch
turned on. From the input circuitry diagrams in the data sheet
kinda looks like it will be needed to connect one side of the
input PGA to the grounded output in your schematic.
> numid=85,iface=MIXER,name='INPGAR IN2R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
> numid=86,iface=MIXER,name='INPGAR IN3R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=on
> numid=87,iface=MIXER,name='INPGAR IN4R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
> numid=2,iface=MIXER,name='Input Mixer Switch'
> ; type=BOOLEAN,access=rw------,values=2
> : values=off,on
> numid=94,iface=MIXER,name='Input Mode'
> ; type=ENUMERATED,access=rw------,values=1,items=2
> ; Item #0 'Analog'
> ; Item #1 'Digital'
> : values=1
Ah... I think you have the wrong path configured here. This
appears to be coming from the digital mics. Just to confirm it is
the analog mics you are having issues with?
> numid=91,iface=MIXER,name='MIXINR IN2R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
> numid=6,iface=MIXER,name='MIXINR IN2R Volume'
> ; type=INTEGER,access=rw---R--,values=1,min=0,max=7,step=0
> : values=7
> | dBscale-min=-15.00dB,step=3.00dB,mute=0
> numid=92,iface=MIXER,name='MIXINR IN3R Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=off
> numid=8,iface=MIXER,name='MIXINR IN3R Volume'
> ; type=INTEGER,access=rw---R--,values=1,min=0,max=7,step=0
> : values=0
> | dBscale-min=-15.00dB,step=3.00dB,mute=0
> numid=93,iface=MIXER,name='MIXINR PGA Switch'
> ; type=BOOLEAN,access=rw------,values=1
> : values=on
> numid=7,iface=MIXER,name='MIXINR PGA Volume'
> ; type=INTEGER,access=rw---R--,values=1,min=0,max=7,step=0
> : values=7
> | dBrange-
> rangemin=0,,rangemax=1
> | dBscale-min=0.00dB,step=6.00dB,mute=0
> rangemin=2,,rangemax=2
> | dBscale-min=13.00dB,step=13.00dB,mute=0
> rangemin=3,,rangemax=4
> | dBscale-min=18.00dB,step=2.00dB,mute=0
> rangemin=5,,rangemax=5
> | dBscale-min=24.00dB,step=0.00dB,mute=0
> rangemin=6,,rangemax=7
> | dBscale-min=27.00dB,step=3.00dB,mute=0
>
Plenty of gain on the PGA.
> numid=65,iface=MIXER,name='Speaker Switch'
> ; type=BOOLEAN,access=rw------,values=2
> : values=on,off
> numid=64,iface=MIXER,name='Speaker Volume'
> ; type=INTEGER,access=rw---R--,values=2,min=0,max=127,step=0
> : values=121,121
> | dBscale-min=-121.00dB,step=1.00dB,mute=1
Thanks,
Charles
next prev parent reply other threads:[~2022-02-03 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220201150113.880330-1-martin.kepplinger@puri.sm>
2022-02-02 9:53 ` [PATCH] wm8962: add a simple DMIC enable control Charles Keepax
[not found] ` <3542af028b622ec1513810b014c35a94b82a94c0.camel@puri.sm>
2022-02-02 10:46 ` Charles Keepax
[not found] ` <99b847d17e8ac399dba10842ec20091df926aa06.camel@puri.sm>
2022-02-02 13:35 ` Charles Keepax
2022-02-03 9:57 ` Martin Kepplinger
2022-02-03 11:05 ` Charles Keepax [this message]
2022-02-04 9:43 ` Martin Kepplinger
2022-02-04 9:50 ` Martin Kepplinger
2022-02-04 17:21 ` Charles Keepax
2022-02-07 10:49 ` Martin Kepplinger
2022-02-07 14:21 ` Charles Keepax
2022-03-01 13:44 ` Charles Keepax
2022-03-01 14:00 ` Martin Kepplinger
2022-03-02 11:48 ` Martin Kepplinger
2022-03-02 13:40 ` Charles Keepax
2022-03-02 14:11 ` Martin Kepplinger
2022-03-03 11:27 ` Charles Keepax
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=20220203110518.GF18506@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=geert@glider.be \
--cc=kernel@puri.sm \
--cc=lgirdwood@gmail.com \
--cc=martin.kepplinger@puri.sm \
--cc=patches@opensource.cirrus.com \
--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