From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Minor WM8580 enhancements.
Date: Sun, 6 Sep 2009 12:11:33 +0100 [thread overview]
Message-ID: <20090906111133.GA26748@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1b68c6790909051850y2386addhae71898ada96954@mail.gmail.com>
On Sun, Sep 06, 2009 at 10:50:26AM +0900, jassi brar wrote:
> Not all combinations of BFS and RFS are possible at all LRCLK values
> for CPU_DAI, not for Samsung SoCs those I am aware of.
These things are all sufficiently constrained by other factors - for
example, the MCLK to sample rate ratio is fixed by those two parameters
which are already known. The Samsung CPUs aren't particularly
restrictive here as far as I remember, the fact that they implement
standard I2S helps a lot. If you have datasheet references for any
restrictions you're concerned about please let me know.
> I get your recommendation, but i am already in the middle of
> submitting I2S machine
> driver for 6410-WM8580 mainline and that is one of the tasks i am assigned.
> Ofcourse, after 6410-wm8580 driver is all up and available to our
> users, i can switch to AC97.
All I'm saying is do the CPU drivers first - like I say, the main
obstacle to finishing off refreshing the CODEC driver has been having
the CPU driver to work off. I'd expect to have something quickly given
that. There shouldn't be much overall delay to getting the boards fully
supported.
next prev parent reply other threads:[~2009-09-06 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 0:09 [PATCH] Minor WM8580 enhancements jassi brar
2009-09-06 1:22 ` Mark Brown
2009-09-06 1:50 ` jassi brar
2009-09-06 11:11 ` Mark Brown [this message]
2009-09-06 12:13 ` jassi brar
2009-09-06 13:42 ` Mark Brown
2009-09-07 2:35 ` jassi brar
2009-09-07 11:58 ` Mark Brown
2009-09-07 12:40 ` 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=20090906111133.GA26748@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--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.