public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: garlic.tseng@mediatek.com (Garlic Tseng)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH v5 6/9] ASoC: mediatek: add mt2701 platform driver implementation.
Date: Mon, 4 Jul 2016 10:28:52 +0800	[thread overview]
Message-ID: <1467599332.11819.11.camel@mtksdaap41> (raw)
In-Reply-To: <1467293981.17087.18.camel@mtksdaap41>

On Thu, 2016-06-30 at 21:39 +0800, Garlic Tseng wrote:
> On Wed, 2016-06-29 at 20:13 +0100, Mark Brown wrote:
> > On Fri, Jun 17, 2016 at 03:43:57PM +0800, Garlic Tseng wrote:
> > 
> > > +static int mt2701_afe_i2s_set_clkdiv(struct snd_soc_dai *dai, int div_id,
> > > +				     int div)
> > > +{
> > 
> > Why are we adding a set_clkdiv() operation?  I would expect the driver
> > to be able to figure things out automatically.
> > 
> > > +	case DIV_ID_MCLK_TO_BCK:
> > > +		afe_priv->i2s_path[i2s_num].div_mclk_to_bck = div;
> > > +		break;
> > > +	case DIV_ID_BCK_TO_LRCK:
> > > +		afe_priv->i2s_path[i2s_num].div_bck_to_lrck = div;
> > > +		break;
> > 
> > Especially in the case where we're configuring LRCLK, that's trivial
> > when we know the sample rate which we have to know anyway.
> 
> Oh... actually I want to say 'div_mclk_over_bck' and 'div_bck_over_lrck'
> I'll fix the naming if we decide to reserve the set_clkdiv() operation.
> (omit some comment)

Hi Mark, I recognize that we can set mclk by set_sysclk, fix bck to 64fs
and let lrck be the same as sample rate so yes we don't need set_clkdiv.

Thanks for comment, I'll fix that in the next patch.

Garlic

  reply	other threads:[~2016-07-04  2:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  7:43 [alsa-devel] [PATCH v5 0/9] ASoC: Mediatek: Add support for MT2701 SOC Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 1/9] ASoC: mediatek: Refine mt8173 driver and change config option Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 2/9] ASoC: mediatek: implement mediatek common structure Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 3/9] ASoC: mediatek: let mt8173 use " Garlic Tseng
2016-06-29 19:16   ` Applied "ASoC: mediatek: let mt8173 use mediatek common structure" to the asoc tree Mark Brown
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 4/9] ASoC: mediatek: add documents for mt2701 Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 5/9] ASoC: mediatek: add structure define and clock control for 2701 Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 6/9] ASoC: mediatek: add mt2701 platform driver implementation Garlic Tseng
2016-06-29 19:13   ` Mark Brown
2016-06-30 13:39     ` Garlic Tseng
2016-07-04  2:28       ` Garlic Tseng [this message]
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 7/9] ASoC: bt-sco: extend rate and add a general compatible string Garlic Tseng
2016-06-29 19:15   ` Mark Brown
2016-06-30 12:55     ` Garlic Tseng
2016-07-01  2:49       ` Garlic Tseng
2016-07-01 16:11         ` Mark Brown
2016-07-02  9:05           ` Chen-Yu Tsai
2016-07-04  1:59             ` Garlic Tseng
2016-06-17  7:43 ` [alsa-devel] [PATCH v5 8/9] ASoC: mediatek: add BT implementation Garlic Tseng
2016-06-17  7:44 ` [alsa-devel] [PATCH v5 9/9] ASoC: mediatek: Add mt2701-cs42448 driver and config option Garlic Tseng

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=1467599332.11819.11.camel@mtksdaap41 \
    --to=garlic.tseng@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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