From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org, ben@trinity.fluff.org,
Jassi <jassi.brar@samsung.com>
Subject: Re: [PATCH] S3C64XX I2S: Added machine driver for WM8580
Date: Thu, 17 Sep 2009 14:11:02 +0100 [thread overview]
Message-ID: <20090917131102.GA16720@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1b68c6790909170526s4bf9e0e0m726dfe771ca71015@mail.gmail.com>
On Thu, Sep 17, 2009 at 09:26:28PM +0900, jassi brar wrote:
> > > + /* Currently, WM8580 driver doesn't support PLL-out rates
> > > + * other than those mentioned in Table-52 Page-58 of WM8580A
> That very manual. And i don't say the WM8580 doesn't support, I said
> the WM8580 driver doesn't support: which can be verified looking at the
> CODEC driver.
Your comment says that only the output frequencies in table 52 are
supported. Could you please provide more specific references to where
this is done in the driver? I think you're confusing the fact that the
example table lists most of the common audio frequencies with what the
driver supports here.
> Theoretically all output clocks are possible but usually the PLL coefficients
> have limits on their value and thus final output. WM8580 driver too seems
> to enforce that.
> Though, you wud know better of WM8580.
So what you're actually saying is that 256fs doesn't give us the option
of an an in-range Fvco for the FLL at those frequencies (which is the
check I think you're talking about here)? That's a limitation of the
chip.
Certainly, the comment is not accurate - the contents of table 52 aren't
relevant here, the driver is calculating what it can do dynamically so
the restrictions are a combination of the limits on Fvco and the pre and
post scaling dividers available.
next prev parent reply other threads:[~2009-09-17 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 4:54 [PATCH] S3C64XX I2S: Added machine driver for WM8580 jassi brar
2009-09-17 11:02 ` Mark Brown
2009-09-17 11:35 ` jassi brar
2009-09-17 12:03 ` Mark Brown
2009-09-17 12:26 ` jassi brar
2009-09-17 13:11 ` Mark Brown [this message]
2009-09-17 13:36 ` jassi brar
2009-09-17 14:12 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 10:02 Jassi
2009-09-16 20:00 ` Mark Brown
2009-09-17 0:02 ` jassi brar
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=20090917131102.GA16720@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben@trinity.fluff.org \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.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.