From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randolph Chung <rchung42@gmail.com>
Cc: alsa-devel@alsa-project.org,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Eric Bénard" <eric@eukrea.com>
Subject: Re: Problem with MX27 ASoC audio
Date: Wed, 18 Aug 2010 10:02:23 +0100 [thread overview]
Message-ID: <20100818090223.GD26804@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinm96norAT4YQhTqg+eP80gwoeZf13V2QQa0_QV@mail.gmail.com>
On Wed, Aug 18, 2010 at 04:58:12PM +0800, Randolph Chung wrote:
> The codec (at least the variant of tlv320aic3x that I am using) can
> have two pins in the hardware, but it's up to the board whether it's
> hooked up that way. The codec driver as currently implemented assumes
> the rates are symmetric, but it need not be.
In that case the driver should be setting the symmetric_rates flag
anyway since it does have this constraint - if it implements support for
asymmetric rates then the flag can be removed then.
> I see that there is a symmetric_rates flag for the dai_link too.
This is still a good idea if your board has a single LRCLK anyway in
case someone does do asymmetric rates.
next prev parent reply other threads:[~2010-08-18 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 10:15 Problem with MX27 ASoC audio Randolph Chung
2010-08-12 12:56 ` Sascha Hauer
2010-08-12 14:59 ` Randolph Chung
2010-08-12 15:01 ` Mark Brown
2010-08-16 9:27 ` Randolph Chung
2010-08-16 9:36 ` Eric Bénard
2010-08-18 3:44 ` Randolph Chung
2010-08-18 7:53 ` Randolph Chung
2010-08-18 8:41 ` Mark Brown
2010-08-18 8:58 ` Randolph Chung
2010-08-18 9:02 ` Mark Brown [this message]
2013-07-11 12:24 ` Dhiv
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=20100818090223.GD26804@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=eric@eukrea.com \
--cc=rchung42@gmail.com \
--cc=s.hauer@pengutronix.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