From: Patrick Lai <plai@codeaurora.org>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: Signaling user-space through kcontrol
Date: Tue, 27 Sep 2011 23:47:35 -0700 [thread overview]
Message-ID: <4E82C307.30407@codeaurora.org> (raw)
In-Reply-To: <1317190544.1573.1646.camel@vkoul-udesk3>
On 9/27/2011 11:15 PM, Vinod Koul wrote:
> On Tue, 2011-09-27 at 23:14 -0700, Patrick Lai wrote:
>> Hi Mark,
>>
>> The codec I am working on, beside headset detection, also have other
>> type of events to be propagated to user space. Per our discussion at
>> IPC, there is way to signal user-space through kcontrol. Is it through
>> calling snd_ctl_notify()? What is the ALSA library API to intercept the
>> event? Is there an sample user-space code which gets kcontrol event?
>>
> What events do you have in mind?
>
Main one is detection of short circuiting headphone For this case,
there is no need for extra payload. In case of there is need to pass
back some payload, I presume user-space application can simply call the
get function upon receiving notification.
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-09-28 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 6:14 Signaling user-space through kcontrol Patrick Lai
2011-09-28 6:15 ` Vinod Koul
2011-09-28 6:47 ` Patrick Lai [this message]
2011-09-28 7:03 ` Vinod Koul
2011-09-28 7:26 ` Patrick Lai
2011-09-28 10:48 ` Mark Brown
2011-09-28 16:27 ` Patrick Lai
2011-09-28 17:17 ` Mark Brown
2011-09-28 8:41 ` Clemens Ladisch
2011-09-28 9:33 ` Sebastian H.
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=4E82C307.30407@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=vinod.koul@linux.intel.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).