linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	alsa-devel@alsa-project.org, shawn.guo@linaro.org,
	pawel.moll@arm.com, ijc+devicetree@hellion.org.uk, tiwai@suse.de,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	timur@tabi.org, lgirdwood@gmail.com, robh+dt@kernel.org,
	rob@landley.net, galak@codeaurora.org, grant.likely@linaro.org,
	perex@perex.cz, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver
Date: Fri, 10 Jan 2014 10:35:39 +0800	[thread overview]
Message-ID: <20140110023537.GB16467@MrMyself> (raw)
In-Reply-To: <20140110023252.GA16467@MrMyself>

[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

Resent this because of losing attached file.

On Fri, Jan 10, 2014 at 10:32:52AM +0800, Nicolin Chen wrote:
> On Thu, Jan 09, 2014 at 06:44:53PM +0000, Mark Brown wrote:
> > On Thu, Jan 09, 2014 at 06:57:58PM +0800, Nicolin Chen wrote:
> > 
> > > +/**
> > > + * This function configures the ratio between MCLK (HCK) and BCLK (SCK)
> > > + * (For DAI Master Mode only)
> > > + *
> > > + * Note: Machine driver should calculate the ratio to call this function.
> > > + * 	 Only effective after calling set_dai_sysclk() to set HCK direction.
> > > + */
> > > +static int fsl_esai_set_bclk_ratio(struct snd_soc_dai *dai, unsigned int ratio)
> > 
> > Why does the machine driver have to do this by hand, being able to
> > override is fine but having sensible defaults is easier?  Or does it
> > actually do that and the comment just needs updating?
> 
> The divider part of ESAI is pretty complicated due to caring about three
> configure bits - ETO, ETI, HCKD. (I've attached a diagram to this mail.)
> So setting sysclk() alone is not enough to take care all the configurations.
> That's why I designed these two interfaces at the first place. And it should
> be hard to find a default situation.
> 
> But there is one approach to omit this calling for machine driver is to do
> the set_bclk_ratio() at this CPU DAI driver. And this might be a good idea
> because we can then separate the settings between PLAYBACK and CAPTURE, even
> though we might then need to check the Master or Slave state to apply the
> settings accordingly.
> 
> I'll try this idea in v3 if you feel it's plausible.
> 
> > > +	ret = devm_snd_soc_register_component(&pdev->dev, &fsl_esai_component,
> > > +					      &fsl_esai_dai, 1);
> > > +	if (ret) {
> > > +		dev_err(&pdev->dev, "failed to register DAI: %d\n", ret);
> > > +		return ret;
> > > +	}
> > > +
> > > +	ret = imx_pcm_dma_init(pdev);
> > > +	if (ret)
> > > +		dev_err(&pdev->dev, "failed to init imx pcm dma: %d\n", ret);
> > > +
> > > +	/* Reset ESAI unit */
> > > +	regmap_write(esai_priv->regmap, REG_ESAI_ECR, ESAI_ECR_ERST);
> > > +
> > > +	/*
> > > +	 * We need to enable ESAI so as to access some of its registers.
> > > +	 * Otherwise, we would fail to dump regmap from user space.
> > > +	 */
> > > +	regmap_write(esai_priv->regmap, REG_ESAI_ECR, ESAI_ECR_ESAIEN);
> > 
> > I would expect to see the hardware initialisation before we start
> > registering with the core otherwise the core might start trying to run
> > prior to the hardware being initialised.
> 
> Will switch this initial code in v3 as your suggestion.
> 
> Thank you,
> Nicolin Chen

[-- Attachment #2: esai_div.jpg --]
[-- Type: image/jpeg, Size: 61359 bytes --]

  parent reply	other threads:[~2014-01-10  2:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 10:57 [PATCH v2] ASoC: fsl_esai: Add ESAI CPU DAI driver Nicolin Chen
2014-01-09 18:44 ` Mark Brown
     [not found]   ` <20140110023252.GA16467@MrMyself>
2014-01-10  2:35     ` Nicolin Chen [this message]
2014-01-10 12:04       ` Mark Brown
2014-01-10 13:03         ` Nicolin Chen
2014-01-10 13:26           ` Mark Brown
2014-01-10 15:48             ` Nicolin Chen
2014-01-10 16:52               ` Mark Brown
2014-01-10 16:45                 ` Nicolin Chen

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=20140110023537.GB16467@MrMyself \
    --to=guangyu.chen@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=perex@perex.cz \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=timur@tabi.org \
    --cc=tiwai@suse.de \
    /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).