Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: bardliao@realtek.com
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	swarren@nvidia.com, lgirdwood@gmail.com, broonie@kernel.org,
	flove@realtek.com
Subject: Re: [PATCH] ASoC: add RT5640 CODEC driver
Date: Tue, 04 Jun 2013 15:51:34 -0600	[thread overview]
Message-ID: <51AE6166.1020809@wwwdotorg.org> (raw)
In-Reply-To: <1369983899-13580-1-git-send-email-bardliao@realtek.com>

On 05/31/2013 01:04 AM, bardliao@realtek.com wrote:
> From: Bard Liao <bardliao@realtek.com>
> 
> * Use regmap_range_cfg to replace index read/write function.
> * Remove I2S3 related code since there is no I2S3 in ALC5640.
> * Remove Voice DSP related code since there is no Voice DSP in ALC5640.
> * Remove MICBIAS2 since there is no MICBIAS2 in ALC5640.
> * Change DMIC1/2 CLK to DMIC1/2 Power since it is for enable/disable DMIC1/2
> * Modify some texts for consistent coding style.
> * Merge sto adc l/r mux since it shares the same control bits.
> * Other minor changes.

> +static const struct snd_soc_dapm_widget rt5640_dapm_widgets[] = {

> +	/* Input Lines */
> +	SND_SOC_DAPM_INPUT("DMIC1"),
> +	SND_SOC_DAPM_INPUT("DMIC2"),

Can you explain that more? In the spec for this part, I don't see any
DMIC1/2 input pins. Instead, I think they're alternative uses for the
IN1P/N pins, right?

> +	SND_SOC_DAPM_MIXER("HPO MIX L", SND_SOC_NOPM, 0, 0,
> +		rt5640_hpo_mix, ARRAY_SIZE(rt5640_hpo_mix)),
> +	SND_SOC_DAPM_MIXER("HPO MIX R", SND_SOC_NOPM, 0, 0,
> +		rt5640_hpo_mix, ARRAY_SIZE(rt5640_hpo_mix)),

In the version of the driver I posted, I had replaced this with a single
"HPO MIX" DAPM_MIXER, because there is a single bit in HW that controls
both the L and R channels. I think you should incorporate that same change.

That relies on commit 85762e7 "ASoC: dapm: Implement mixer control sharing".

In an earlier review, IIRC, Mark had asked you to implement platform
data to configure whether the microphones were single-ended or not. I
don't see that in this patch.

Finally, I really would prefer if you could implement the support for
the LDO1_EN GPIO via platform data. Getting that right requires a bit of
knowledge of how set_bias_level() is supposed to work on this CODEC, and
I think Realtek have the best information to get that right. I'll
certainly send a patch to implement this all by device tree after that.

Anyway, I'll go test this patch and see if it works for me on my HW.

  parent reply	other threads:[~2013-06-04 21:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1369983899-13580-1-git-send-email-bardliao@realtek.com>
2013-06-03 15:35 ` [PATCH] ASoC: add RT5640 CODEC driver Mark Brown
2013-06-04  6:39   ` Bard Liao
2013-06-04  9:53     ` Mark Brown
     [not found] ` <1121E117AD4ECE49880A389A396215BB8A8969924B@rtitmbs7.realtek.com.tw>
2013-06-03 15:48   ` Stephen Warren
2013-06-04  6:23     ` Bard Liao
2013-06-04 21:51 ` Stephen Warren [this message]
2013-06-04 22:05   ` Stephen Warren
2013-06-05 10:02   ` Bard Liao
     [not found] <1370927416-12216-1-git-send-email-bardliao@realtek.com>
2013-06-11  9:12 ` Mark Brown
2013-06-11 17:36   ` Stephen Warren
2013-06-12  7:47   ` Bard Liao
2013-06-11 17:41 ` Stephen Warren
2013-06-12  7:56   ` Bard Liao
2013-06-12 15:31   ` Mark Brown
2013-06-11 20:43 ` Stephen Warren
2013-06-12 16:42 ` Mark Brown
     [not found] <1366121437-19396-1-git-send-email-bardliao@realtek.com>
     [not found] ` <20130416143807.GJ26958@opensource.wolfsonmicro.com>
2013-04-22  7:03   ` Bard
2013-04-22 14:06     ` Mark Brown
     [not found] <1364340938-17175-1-git-send-email-swarren@wwwdotorg.org>
2013-03-27  1:15 ` Mark Brown
2013-03-27 22:50   ` Stephen Warren
2013-03-27 23:07     ` Mark Brown
     [not found]       ` <1121E117AD4ECE49880A389A396215BB8718BB370D@rtitmbs7.realtek.com.tw>
     [not found]         ` <516DD0D4.5070409@wwwdotorg.org>
2013-04-17 14:01           ` Mark Brown
2013-04-17 15:18             ` Stephen Warren
2013-04-17 15:28               ` Mark Brown
2013-04-17 16:25                 ` Stephen Warren
2013-04-17 18:52                   ` Mark Brown
2013-04-17 18:56                     ` Stephen Warren
2013-04-17 19:13                       ` Mark Brown

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=51AE6166.1020809@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=swarren@nvidia.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