From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
"<joe@nucleusys.com>" <joe@nucleusys.com>,
"<lrg@ti.com>" <lrg@ti.com>,
"<alsa-devel@alsa-project.org>" <alsa-devel@alsa-project.org>,
"<ramesh.babu@intel.com>" <ramesh.babu@intel.com>
Subject: Re: [PATCH v3] ASoC: Add support for cs42l73 codec
Date: Fri, 7 Oct 2011 15:27:42 +0100 [thread overview]
Message-ID: <20111007142742.GI14518@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <F41D058E-D2A8-4046-B391-1452889ED54C@cirrus.com>
On Fri, Oct 07, 2011 at 02:05:57PM +0000, Austin, Brian wrote:
> The way to enable the output is to enable the output pin. I have no control in SW
> over the DAC's. The pins are power controlled of course. I know it looks strange,
> but without using a machine driver to enable/disable the pins for a certain route,
> this seems to be the best solution.
Right, which is why I'm saying this routing makes no sense. You've got
code which has a mixer mixing input signals down into the DAC but what
you've actually got is a single output from the DAC which can then be
sent to the outputs separately. You should be able to draw a graph of
the audio routes through the CODEC which directly corresponds to the
DAPM graph.
next prev parent reply other threads:[~2011-10-07 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 16:19 [PATCH v3] ASoC: Add support for cs42l73 codec Brian Austin
2011-10-06 18:57 ` Mark Brown
2011-10-06 19:15 ` Austin, Brian
2011-10-07 10:34 ` Mark Brown
2011-10-07 11:07 ` Vinod Koul
2011-10-07 11:42 ` Mark Brown
2011-10-07 14:05 ` Austin, Brian
2011-10-07 14:27 ` Mark Brown [this message]
2011-10-07 14:29 ` Vinod Koul
2011-10-12 15:58 ` Austin, Brian
2011-10-12 21:37 ` Austin, Brian
2011-10-12 21:50 ` Austin, Brian
2011-10-12 21:55 ` Austin, Brian
2011-10-17 19:11 ` Austin, Brian
2011-10-17 20:15 ` Mark Brown
2011-10-07 3:59 ` Vinod Koul
2011-10-07 2:13 ` Tabi Timur-B04825
2011-10-07 10:27 ` Mark Brown
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=20111007142742.GI14518@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Brian.Austin@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=joe@nucleusys.com \
--cc=lrg@ti.com \
--cc=ramesh.babu@intel.com \
--cc=vinod.koul@linux.intel.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.