From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
"<alsa-devel@alsa-project.org>" <alsa-devel@alsa-project.org>,
"<ramesh.babu@intel.com>" <ramesh.babu@intel.com>,
"<joe@nucleusys.com>" <joe@nucleusys.com>,
"<heelrod@heelrod.ad.cirrus.com>" <heelrod@heelrod.ad.cirrus.com>,
"jeeja.kp" <jeeja.kp@intel.com>, "<lrg@ti.com>" <lrg@ti.com>
Subject: Re: [PATCH v5] ASoC:Add support for cs42l73 codec
Date: Thu, 20 Oct 2011 15:20:08 +0100 [thread overview]
Message-ID: <20111020142007.GE3524@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <EBA4E46B-C386-4800-829D-73CE475FB965@cirrus.com>
On Thu, Oct 20, 2011 at 02:11:32PM +0000, Austin, Brian wrote:
> With the current mixer settings enabling the AMP to be used for
> output, the power is exactly where it is supposed to be.
Could you explain how this works please? It may be that we're just
missing something about how the chip power is managed here but what
you're describing is definitely not normal.
next prev parent reply other threads:[~2011-10-20 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 15:46 [PATCH v5] ASoC:Add support for cs42l73 codec Brian Austin
2011-10-19 8:42 ` Vinod Koul
2011-10-20 13:54 ` Austin, Brian
2011-10-20 13:58 ` Mark Brown
2011-10-20 13:54 ` Vinod Koul
2011-10-20 14:11 ` Austin, Brian
2011-10-20 14:20 ` Mark Brown [this message]
2011-10-20 16:23 ` Austin, Brian
[not found] ` <4EA06916.6090601@nucleusys.com>
2011-10-20 20:00 ` Mark Brown
2011-10-20 20:26 ` Austin, Brian
2011-10-20 21:28 ` Mark Brown
2011-10-20 21:34 ` Austin, Brian
2011-10-21 13:23 ` Brian Austin
2011-10-21 16:00 ` 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=20111020142007.GE3524@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Brian.Austin@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=heelrod@heelrod.ad.cirrus.com \
--cc=jeeja.kp@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).