From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext Harrod, John" <john.harrod@philips.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Triggering a DAPM widget event
Date: Thu, 27 Jan 2011 09:09:39 +0200 [thread overview]
Message-ID: <4D411A33.3080205@nokia.com> (raw)
In-Reply-To: <39D4D143FC30524CAB784A72ADFECEEE34A0E8F455@NLCLUEXM02.connect1.local>
On 01/26/11 22:38, ext Harrod, John wrote:
>> What is your actual problem here?
>
> I have a speaker widget (snd_soc_dapm_spk) whose event handler only receives a
> SND_SOC_DAPM_PRE_PMD event when the pcm is closed.
Events on widgets are (among others):
SND_SOC_DAPM_PRE_PMU: will be sent before the widget power up
SND_SOC_DAPM_POST_PMU: will be sent after the widget power up
SND_SOC_DAPM_PRE_PMD: will be sent before the widget power down
SND_SOC_DAPM_POST_PMD: will be sent after the widget power down
The *_PMU events are triggered whenever the widget is going to be
powered up:
stream start, within prepare time;
complete bypass, or loopback path
The *_PMD events are triggered whenever the widget is going to be
powered down:
bypass, or loopback path is disabled
After the stream has been stopped/closed.
In case of playback the power down is delayed (5 sec by default)
In case of capture the power down is instant.
If you stop, and restart the playback stream within 5 sec, events will
not be triggered on the widgets, since they are still powered.
--
Péter
next prev parent reply other threads:[~2011-01-27 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 16:53 Triggering a DAPM widget event Harrod, John
2011-01-26 16:53 ` Mark Brown
2011-01-26 18:08 ` Harrod, John
2011-01-26 18:27 ` Mark Brown
2011-01-26 20:38 ` Harrod, John
2011-01-26 20:43 ` Mark Brown
2011-01-27 7:09 ` Peter Ujfalusi [this message]
2011-01-27 9:56 ` Mark Brown
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=4D411A33.3080205@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=john.harrod@philips.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 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).