alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <Guangyu.Chen@freescale.com>
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 10:47:45 +0000	[thread overview]
Message-ID: <20131210104745.GC29268@sirena.org.uk> (raw)
In-Reply-To: <20131210102523.GB12042@MrMyself>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-10 10:47 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 [this message]
2013-12-10 10:51           ` Nicolin Chen
2013-12-10 11:15             ` Mark Brown
2013-12-10 11:08               ` Nicolin Chen

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=20131210104745.GC29268@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Guangyu.Chen@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=b42378@freescale.com \
    --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).