All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: ASoC: SND_SOC_DAPM_LINE behavior
Date: Tue, 29 Sep 2009 15:36:39 +0300	[thread overview]
Message-ID: <200909291536.39792.peter.ujfalusi@nokia.com> (raw)

Hello,

as I'm writing a new codec driver I have noticed the following (using 2.6.31 
kernel).

The codec itself is really simple, it is only capable of playback and it can 
bypass audio from line-in to the output.
The DAPM routing is something like this in the codec driver:

|DAC|------------->|              |              
                   |Playback Mixer|->|OUTPUT|
|INPUT|->|Bypass|->|              |
         |SWITCH|

Now if in the machine driver I create the following DAPM widget:
SND_SOC_DAPM_LINE("Line In", NULL),

and than connect this DAPM_LINE to the codec's INPUT (LINE-IN):
{"LINE-IN", NULL, "Line In"},

Than the codec bias level would be always in ON state, regardless of the state 
of the Bypass Switch (it is off by default).
I can use the snd_soc_dapm_disable_pin(codec, "Line In") in the machine driver 
to disable the pin, which moves the codec to STANDBY state.

Now, if I change the SND_SOC_DAPM_LINE to
SND_SOC_DAPM_MIC("Line In", NULL),
in the machine driver, than the codec bias would be STANDBY as long as the 
Bypass switches are off, if they changed to on, than the codec bias goes to ON, 
as expected.

Is this expected behavior?

-- 
Péter

             reply	other threads:[~2009-09-29 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 12:36 Peter Ujfalusi [this message]
2009-09-29 12:44 ` ASoC: SND_SOC_DAPM_LINE behavior Mark Brown
2009-09-29 12:59   ` Peter Ujfalusi

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=200909291536.39792.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.