From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Andrey Danin <danindrey@mail.ru>, Leon Romanovsky <leon@leon.nu>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Tegra: Add support of tegra boards based on ALC5632 codec
Date: Wed, 23 Nov 2011 22:46:22 +0000 [thread overview]
Message-ID: <20111123224621.GA456@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF174F08C84C@HQMAIL01.nvidia.com>
On Wed, Nov 23, 2011 at 02:30:12PM -0800, Stephen Warren wrote:
> Mark Brown wrote at Wednesday, November 23, 2011 2:59 PM:
> > > That said, while these values are constant right now, I think they won't
> > > always be; I think we'll need to switch between DSP mode for mono and
> > > I2S mode for stereo here; at least I /think/ that's what I remember our
> > > downstream drivers doing...
> > That would be a surprising restriction for your hardware to have. From
> > the CODEC point of view it really doesn't care at all, all the interface
> > formats are interchangable.
> I believe Tegra20 HW "hard-codes" the channel count to 2 in I2S mode,
> And hence always pulls 2 channels from the FIFO for each frame. So, I2S
> can't do mono. This appears to be fixed in Tegra30. Tegra can be
> surprising:-)
If it's got that restriction why not run it in PCM mode all the time?
next prev parent reply other threads:[~2011-11-23 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 20:08 [PATCH] ASoC: Tegra: Add support of tegra boards based on ALC5632 codec Leon Romanovsky
[not found] ` <1321906088-29964-1-git-send-email-leon-2ukJVAZIZ/Y@public.gmane.org>
2011-11-22 13:30 ` [alsa-devel] [PATCH] ASoC: Tegra: Add support of tegra boards basedon " Marc Dietrich
2011-11-23 8:04 ` Leon Romanovsky
[not found] ` <CALq1K=Ka0JYut22FwovAyAcZSbqcQssjUPrk6rUU0Fq2iOZG_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-23 17:37 ` [alsa-devel] " Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF174F08C6FF-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-27 8:37 ` Leon Romanovsky
2011-11-23 15:38 ` [PATCH] ASoC: Tegra: Add support of tegra boards based on " Mark Brown
2011-11-23 21:50 ` Stephen Warren
2011-11-23 21:58 ` Mark Brown
2011-11-23 22:30 ` Stephen Warren
2011-11-23 22:46 ` Mark Brown [this message]
2011-11-23 23:31 ` Stephen Warren
2011-11-27 8:48 ` Leon Romanovsky
2011-11-28 16:52 ` Stephen Warren
2011-11-29 5:35 ` Leon Romanovsky
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=20111123224621.GA456@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=danindrey@mail.ru \
--cc=leon@leon.nu \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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.