linux-kernel - Re: [PATCH v2 2/2] ASoC: fsl: imx-wm8962: Grant hw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Dec 2013 18:51:36 +0800
From:	Nicolin Chen <Guangyu.Chen@...escale.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Nicolin Chen <b42378@...escale.com>, <lgirdwood@...il.com>,
	<alsa-devel@...a-project.org>, <tiwai@...e.de>, <perex@...ex.cz>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] ASoC: fsl: imx-wm8962: Grant hw_params/free()
 permission to control FLL

On Tue, Dec 10, 2013 at 10:47:45AM +0000, Mark Brown wrote:
> On Tue, Dec 10, 2013 at 06:25:24PM +0800, Nicolin Chen wrote:
> 
> > Hmm...Sorry for asking a stupid question that how to test bypass path with
> > WM8962? I've tried some amixer commands to enable the bypass-path switches.
> > But we still need to power the Codec up like using arecord or aplay to call
> > wm8962_resume() and DAPM-related, right?
> 
> 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?

Thank you,
Nicolin Chen


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/