From: Dmitry Torokhov <dtor@insightbb.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Liam Girdwood <liam.girdwood@wolfsonmicro.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
Johannes Berg <johannes@sipsolutions.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: sound connector detection
Date: Sun, 2 Jul 2006 22:48:35 -0400 [thread overview]
Message-ID: <200607022248.36459.dtor@insightbb.com> (raw)
In-Reply-To: <1151832510.5536.32.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Sunday 02 July 2006 05:28, Richard Purdie wrote:
> One thing the input system does well is pass simple switch events to
> userspace though its event devices. Not using the input system for
> switch like events like these is going to result in code duplication.
>
I think that hotplug/uevent like mechanism would be better suited here.
You want to monitor changes in system state and you do not really want
to monitor myriad of devices but just latch onto one data feed and get
all the data from it (unlike input devices where you might want to
separate data coming from different devices). The following "event"
might be a good starting point:
struct system_change_event {
struct timeval time; /* look for 32/64 bit issues */
__u16 type;
__u16 code;
__s32 value;
char object_path[224];
};
Maybe we should start looking into connector or a pure netlink implementation.
--
Dmitry
[-- Attachment #2: Type: text/html, Size: 1217 bytes --]
next prev parent reply other threads:[~2006-07-03 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 12:49 sound connector detection Johannes Berg
2006-07-01 20:09 ` Dmitry Torokhov
2006-07-02 9:28 ` Richard Purdie
2006-07-03 2:48 ` Dmitry Torokhov [this message]
2006-07-03 13:31 ` Johannes Berg
2006-07-03 13:30 ` Johannes Berg
2006-07-04 15:55 ` [Alsa-devel] " Takashi Iwai
2006-07-04 18:51 ` Johannes Berg
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=200607022248.36459.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpurdie@rpsys.net \
/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).