From: Brad Rubin <brubin@codeaurora.org>
To: alsa-devel@alsa-project.org
Cc: plai@codeaurora.org
Subject: Sending headset insertion events to user space on bootup
Date: Fri, 22 Jul 2011 11:58:42 -0700 [thread overview]
Message-ID: <4E29C862.8010208@codeaurora.org> (raw)
Hi all,
I’m having an issue passing events when a headset is inserted upon
bootup. I’m sending a headset insertion event to user space through
snd_soc_jack_report, but user space is not yet ready to receive events
and therefore misses the event. Since the kernel driver doesn’t resend
this event, then there’s no way for user space to see it. User space is
still booting up when the event is sent.
Does anyone know of a solution so user space can receive headset
insertion events on bootup?
Is is possible to either allow the kernel to postpone sending events
until user space is ready or to store events in some sort of cache so
that user space can access them? Would it be possible to use ALSA to
store the headset status in a device node?
Thanks,
Brad
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2011-07-22 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 18:58 Brad Rubin [this message]
2011-07-23 7:45 ` Sending headset insertion events to user space on bootup 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=4E29C862.8010208@codeaurora.org \
--to=brubin@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=plai@codeaurora.org \
/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.