From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
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: Fri, 04 Feb 2022 10:50:32 +0100 [thread overview]
Message-ID: <801a26e88df1512391e436cc3520ac0fdf1ed386.camel@puri.sm> (raw)
In-Reply-To: <7b3306d7a80f605973c932a0a4679bcac067ae8a.camel@puri.sm>
Am Freitag, dem 04.02.2022 um 10:43 +0100 schrieb Martin Kepplinger:
> Am Donnerstag, dem 03.02.2022 um 11:05 +0000 schrieb Charles Keepax:
> > 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.
>
> yes my bad :) If I may, just let me describe my situation again and
> see
> whether anything else comes to your mind.
>
> It's weird but I when I set "Capture Volume" to 60 instead of 29, I
> didn't hear a difference.
>
> So far I don't hear a difference when setting "INPGAR IN1R Switch"
> on.
>
> Does "Value" in this ucm description make any sense to you?
>
> EnableSequence [
> cset "name='Digital Capture Volume' 127,127"
> cset "name='Capture Volume' 63,63"
> cset "name='MIXINR IN3R Switch' on"
> cset "name='MIXINR IN3R Volume' 7"
> cset "name='INPGAR IN1R Switch' on"
> cset "name='Input Mode' Analog"
> ]
>
> DisableSequence [
> cset "name='INPGAR IN1R Switch' off"
> cset "name='MIXINR IN3R Switch' off"
> cset "name='MIXINR IN3R Volume' 0"
> cset "name='Input Mode' Digital"
> ]
>
> Value {
> CapturePriority "100"
> CaptureChannels "2"
> CaptureSwitch "name='MIXINR IN3R Volume'"
sorry, of course this is a typo I've fixed: CaptureVolume
>
> CaptureSwitch "name='MIXINR IN3R Switch'"
> CapturePCM "hw:${CardId},0"
> JackControl "Headphones Jack"
I know this is a workaround until I have mic detection.
>
> }
>
>
> Let me just append the correct amixer contents where I hear my usual
> "quiet and bad signal" recording:
>
>
next prev parent reply other threads:[~2022-02-07 14:47 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
2022-02-04 9:43 ` Martin Kepplinger
2022-02-04 9:50 ` Martin Kepplinger [this message]
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=801a26e88df1512391e436cc3520ac0fdf1ed386.camel@puri.sm \
--to=martin.kepplinger@puri.sm \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=daniel.baluta@nxp.com \
--cc=geert@glider.be \
--cc=kernel@puri.sm \
--cc=lgirdwood@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).