From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolin Chen <b42378@freescale.com>,
lgirdwood@gmail.com, alsa-devel@alsa-project.org, tiwai@suse.de,
perex@perex.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ASoC: fsl: imx-wm8962: Grant hw_params/free() permission to control FLL
Date: Tue, 10 Dec 2013 19:08:44 +0800 [thread overview]
Message-ID: <20131210110842.GD12042@MrMyself> (raw)
In-Reply-To: <20131210111505.GE29268@sirena.org.uk>
On Tue, Dec 10, 2013 at 11:15:05AM +0000, Mark Brown wrote:
> On Tue, Dec 10, 2013 at 06:51:36PM +0800, Nicolin Chen wrote:
> > On Tue, Dec 10, 2013 at 10:47:45AM +0000, Mark Brown wrote:
>
> > > For this sort of question you should follow the DAPM graph... the
> > > headphone and speaker mixers have IN4 and MIXIN as inputs for analogue
> > > bypass and the STL and STR paths provide digital sidetones through the
> > > ADC and DAC.
>
> > So I could test it merely by using 'amixer cset' to enable those switches
> > without doing anything to power WM8962 up as long as my operation follows
> > the DAPM graph so that the DPAM would automatically turn on the regulator
> > for me?
>
> Yes, as soon as you have a complete path from an active input to an
> active output the path should get powered up.
I'll try again tomorrow. Thank you sir.
prev parent reply other threads:[~2013-12-10 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 15:38 [PATCH v2 0/2] Enhance imx-wm8962 machine driver Nicolin Chen
2013-12-06 15:38 ` [PATCH v2 1/2] ASoC: fsl: imx-wm8962: Don't update bias_level in " Nicolin Chen
2013-12-09 17:51 ` Mark Brown
2013-12-06 15:38 ` [PATCH v2 2/2] ASoC: fsl: imx-wm8962: Grant hw_params/free() permission to control FLL Nicolin Chen
2013-12-09 17:56 ` Mark Brown
2013-12-10 5:18 ` Nicolin Chen
2013-12-10 10:25 ` Nicolin Chen
2013-12-10 10:47 ` Mark Brown
2013-12-10 10:51 ` Nicolin Chen
2013-12-10 11:15 ` Mark Brown
2013-12-10 11:08 ` Nicolin Chen [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=20131210110842.GD12042@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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).