From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 3/3] ASoC: Add support for AIF channel muxing on WM8903
Date: Fri, 11 Feb 2011 11:26:09 +0000 [thread overview]
Message-ID: <20110211112608.GH7180@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310F6050C@HQMAIL01.nvidia.com>
On Thu, Feb 10, 2011 at 02:59:17PM -0800, Stephen Warren wrote:
> However, if I flip the Right Capture Mux to setting Left (while not capturing),
> then this breaks case (3) above; the initial portion of the recording is fine,
> but when I remove and plug the mic back in, something isn't turned on, and so
> nothing is recorded after that.
That's just bizzare; I can't off the top of my head think of any reason
for it and I'm out of the office today so can't test.
Does the left channel data stay OK (assuming you're mapping the data
through on both channels)?
next prev parent reply other threads:[~2011-02-11 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 22:59 [PATCH 3/3] ASoC: Add support for AIF channel muxing on WM8903 Stephen Warren
2011-02-11 5:40 ` Stephen Warren
2011-02-11 11:36 ` Mark Brown
2011-02-11 11:26 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-09 13:47 [PATCH 1/3] ASoC: Remove redundant -codec from WM8903 driver name Mark Brown
2011-02-09 13:47 ` [PATCH 3/3] ASoC: Add support for AIF channel muxing on WM8903 Mark Brown
2011-02-09 16:33 ` Stephen Warren
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=20110211112608.GH7180@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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.