From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Timur Tabi <timur@freescale.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 4/4] ASoC: Flag the i.MX SSI driver as using symmetric rates
Date: Mon, 11 Jan 2010 11:51:01 +0000 [thread overview]
Message-ID: <20100111115101.GA8471@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <eedb5541001110339s6c7af715g2c95c65ab1028898@mail.gmail.com>
On Mon, Jan 11, 2010 at 12:39:13PM +0100, javier Martin wrote:
> However,
> I think it would be a good idea to add an optional flag to activate
> symmetric rate.
> Understanding it as TX and RX SSI sections sharing the same CLKs.
> This is necessary for some codecs like wm8974 to work because they can only
> provide
> one BCLK and FCLK for both directions.
That's not what the patch does - it only sets the symmetric_rates flag,
which can also be flagged from the machine driver, which adds some
constraints for applications so you can't configure asymmetric rates.
It doesn't affect the hardware configuration at all.
next prev parent reply other threads:[~2010-01-11 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 16:19 [PATCH 1/4] ASoC: Add a new imx-ssi sound driver Mark Brown
2010-01-08 16:19 ` [PATCH 2/4] ASoC: Fix i.MX audio build for i.MX3x Mark Brown
2010-01-08 16:19 ` [PATCH 3/4] ASoC: Convert new i.MX SSI driver to use static DAI array Mark Brown
2010-01-08 16:19 ` [PATCH 4/4] ASoC: Flag the i.MX SSI driver as using symmetric rates Mark Brown
2010-01-11 11:20 ` Sascha Hauer
2010-01-11 11:36 ` Mark Brown
2010-01-11 11:39 ` javier Martin
2010-01-11 11:51 ` Mark Brown [this message]
2010-01-11 15:51 ` Timur Tabi
2010-01-11 16:25 ` Mark Brown
2010-01-11 17:38 ` Sascha Hauer
2010-01-11 12:14 ` Sascha Hauer
2010-01-11 12:30 ` Mark Brown
2010-01-11 7:33 ` [PATCH 1/4] ASoC: Add a new imx-ssi sound driver javier Martin
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=20100111115101.GA8471@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=javier.martin@vista-silicon.com \
--cc=lrg@slimlogic.co.uk \
--cc=s.hauer@pengutronix.de \
--cc=timur@freescale.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.