alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Kuninori Morimoto <morimoto.kuninori@renesas.com>,
	alsa-devel@alsa-project.org, linux-sh@vger.kernel.org,
	Magnus Damm <damm@opensource.se>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/4 v4] ASoC: add a WM8978 codec driver
Date: Wed, 3 Feb 2010 10:34:07 +0000	[thread overview]
Message-ID: <20100203103406.GC8300@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1002012047200.4617@axis700.grange>

On Mon, Feb 01, 2010 at 09:01:41PM +0100, Guennadi Liakhovetski wrote:
> On Mon, 1 Feb 2010, Mark Brown wrote:

> > I don't follow your logic there at all, I'm afraid.  Both options have a
> > table of possible values for the divider (and hence the PLL output
> > frequencies they can use) which they need to additionally constrain
> > based on the PLL operating conditions.

> In principle, yes, both dividers have a table of possible values. But, 
> possible OPCLK dividers are 1, 2, 3, and 4, which makes it possible to 
> just calculate the needed divisor by dividing the target through the 
> source. Whereas possible MCLK divisors are 1, 3/2, 2, 3, 4, 6, 8, 12, so, 
> you cannot compute the index, therefore I just iterate over the table and 
> try each. Of course, the sequence is ascending, so, you could bisection, 
> but I found that to be an overkill for this case;)

You're missing the point here.  It's not the working out the divisor
bit that I'm noticing, it's all the stuff around it imposing the
constraints for the input frequency and the PLL itself.  What's there at
the minute seems to split the OPCLK and non-OPCLK cases too early and
has these very large comments explaining what it's trying to do - a more
step by step approach might be clearer.

      reply	other threads:[~2010-02-03 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 17:56 [PATCH 1/4 v4] ASoC: add a WM8978 codec driver Guennadi Liakhovetski
2010-01-27 20:17 ` Mark Brown
2010-01-28  8:24   ` Guennadi Liakhovetski
2010-01-28 19:01     ` Dan Williams
2010-01-29 13:57   ` Guennadi Liakhovetski
2010-02-01 14:31     ` Mark Brown
2010-02-01 20:01       ` Guennadi Liakhovetski
2010-02-03 10:34         ` Mark Brown [this message]

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=20100203103406.GC8300@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=damm@opensource.se \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-sh@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=morimoto.kuninori@renesas.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).