All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bard Liao <bardliao@realtek.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: Cherry Trail + RT5645 devices analog microphone not working.
Date: Tue, 2 Jan 2018 02:41:19 +0000	[thread overview]
Message-ID: <ABFD875FF5FB574BA706497D987D48D7027513B3@RTITMBSV02.realtek.com.tw> (raw)
In-Reply-To: <f98183ba-0811-4688-24c6-a50790709282@redhat.com>

> -----Original Message-----
> From: Hans de Goede [mailto:hdegoede@redhat.com]
> Sent: Monday, January 01, 2018 8:32 PM
> To: Bard Liao
> Cc: Pierre-Louis Bossart; alsa-devel@alsa-project.org
> Subject: Re: Cherry Trail + RT5645 devices analog microphone not working.
> 
> Hi,
> 
> On 29-12-17 03:10, Bard Liao wrote:
> >> Some questions for you:
> >>
> >> 1) I think enabling micbias2 may be a problem on devices with a DMIC,
> >> could this be a problem?  Currently the codec driver itself contains
> >> quirks for dmic pin-mapping, maybe we should leave micbias2 disabled
> >> if dmic pin-mapping is specified through a quirk?
> >
> > No, micbias2 and DMIC are independent and micbias2 will not be enabled
> > if we don't add it in the audio route. So I don't think we need to disable it
> > if dmic pin-mapping is specified.
> 
> Right, but currently we use the "Int Mic" switch in both the DMIC and analog
> mic paths, and the changes to the machine driver enable micbias2 when Int
> Mic
> gets turned on. After my changes the machine driver has:
> 
> 	{"IN2P", NULL, "Int Mic"},
> 	{"IN2N", NULL, "Int Mic"},
>   	{"DMIC L1", NULL, "Int Mic"},
>   	{"DMIC R1", NULL, "Int Mic"},
> ...
> 	{"Int Mic", NULL, "micbias2"},
> 
> Since the analog mic is currently not working anyways, maybe we should
> use Int Mic2 for the analog mic, so make the above:

Do you mean the analog mic doesn't work with above change?
Could you dump registers for me?

> 
> 	{"IN2P", NULL, "Int Mic2"},
> 	{"IN2N", NULL, "Int Mic2"},
>   	{"DMIC L1", NULL, "Int Mic"},
>   	{"DMIC R1", NULL, "Int Mic"},
> ...
> 	{"Int Mic2", NULL, "micbias2"},
> 
> And then use
> 
> 	cset "name='Int Mic Switch2' on"

It will be cset "name='Int Mic2 Switch' on"
And you will also need to add "Int Mic2" in cht_mc_controls[].

> 
> In the ucm file in the analog mic enable sequence?
> 
> This way the already working dmic support stays unchanged and the
> analog mic support I'm adding does not enable micbias2 when using
> dmic inputs.

If you are using dmic inputs, you will need to set below switches on
"Sto1 ADC MIXL ADC2 Switch"
"Sto1 ADC MIXR ADC2 Switch"
And below switches are for analog mics
"Sto1 ADC MIXL ADC1 Switch"
"Sto1 ADC MIXR ADC1 Switch"
So you can select dmic or amic by rt5645's mixer.
But, anyway it's a good idea to add a new widget for analog mic.
However, it is better to have a more specific name for it.
Something like "Int A Mic" and "Int D Mic".

> 
> ?
> 
> Regards,
> 
> Hans
> 
> ------Please consider the environment before printing this e-mail.

  reply	other threads:[~2018-01-02  2:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-24 10:42 Cherry Trail + RT5645 devices analog microphone not working Hans de Goede
2017-12-25  2:15 ` Bard Liao
2017-12-25 12:02   ` Hans de Goede
2017-12-26  5:29     ` Bard Liao
2017-12-27 19:12       ` Hans de Goede
2017-12-28  3:05         ` Bard Liao
2017-12-29  0:22           ` Hans de Goede
2017-12-29  2:10             ` Bard Liao
2018-01-01 12:31               ` Hans de Goede
2018-01-02  2:41                 ` Bard Liao [this message]
2018-01-02 19:23                   ` Hans de Goede

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=ABFD875FF5FB574BA706497D987D48D7027513B3@RTITMBSV02.realtek.com.tw \
    --to=bardliao@realtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=hdegoede@redhat.com \
    --cc=pierre-louis.bossart@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.