From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Brian Austin <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> Babu" <ramesh.babu@intel.com>,
Georgi Vlaev <joe@nucleusys.com>,
"jeeja.kp Kp" <jeeja.kp@intel.com>, "<lrg@ti.com>" <lrg@ti.com>
Subject: Re: [PATCH v5] ASoC:Add support for cs42l73 codec
Date: Fri, 21 Oct 2011 17:00:56 +0100 [thread overview]
Message-ID: <20111021160055.GH4080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1110210822450.13824@heelrod.ad.cirrus.com>
On Fri, Oct 21, 2011 at 08:23:44AM -0500, Brian Austin wrote:
> I get it now! This is going to add a lot of code as there are a lot of
> mixer controls. Using volume controls as DAPM I can create all
> routes in the codec.
I did also mean to say that if you do have the really coarse power
control it might be worth looking at using supply widgets to control
the actual registers and no power management (SND_SOC_NOPM) for the
widgets used for routing.
prev parent reply other threads:[~2011-10-21 16:00 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
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 [this message]
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=20111021160055.GH4080@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@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).