All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: "Wang, Kuirong" <kuirongw@quicinc.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: How to trigger a widget?
Date: Tue, 21 Feb 2012 22:06:59 +0100	[thread overview]
Message-ID: <4F440773.4080407@metafoo.de> (raw)
In-Reply-To: <D618B7A80E26984A9E4E1FD204983C1AA8AAF4@nasanexd01d.na.qualcomm.com>

On 02/21/2012 06:09 AM, Wang, Kuirong wrote:
> On 02/20/2012 1:08 AM, Lars-Peter Clausen wrote:
>>
>> Hi,
>>
>> snd_soc_dapm_force_enable_pin is probably what you are looking for.
>>
>> - Lars
> 
> Thanks Lars. I tried the snd_soc_dapm_force_enable_pin, it didn't make different.
> 
> I have kcontrol to enable a function of codec on fly.  With or without the function, it cannot impact the established audio routing.  So I created widget as a supply, as long as the audio path is established, this supply widget is triggered. The supply widget has a callback event function.  The kcontrol control has an event callback function as well which calls the enable/disable pin to trigger the widget callback event, so this particular function can be enabled or disabled.
> 

I'm not quite sure if I understand what you want to do, but a
snd_soc_dapm_force_enable_pin followed by a snd_soc_dapm_sync should enable a
widget regardless of whether it is currently in use or not.

  reply	other threads:[~2012-02-21 21:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  7:13 How to trigger a widget? Wang, Kuirong
2012-02-20  9:07 ` Lars-Peter Clausen
2012-02-21  5:09   ` Wang, Kuirong
2012-02-21 21:06     ` Lars-Peter Clausen [this message]
2012-02-22  7:28     ` Peter Ujfalusi
2012-02-24  4:57       ` Wang, Kuirong

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=4F440773.4080407@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kuirongw@quicinc.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.