From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
Alexey Starikovskiy <aystarik@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH, RFC] HP WMI hotkey driver, RFKill query?
Date: Wed, 16 Jan 2008 01:49:47 +0000 [thread overview]
Message-ID: <20080116014947.GA7101@srcf.ucam.org> (raw)
In-Reply-To: <200801160138.36347.carlos@strangeworlds.co.uk>
On Wed, Jan 16, 2008 at 01:38:35AM +0000, Carlos Corbacho wrote:
> The question is, would exporting the GUID virtual device and using that as the
> parent make more sense? So, in the case of hp-wmi, it only uses the GUID
> 95F24279-4D7B-4334-9387-ACCDC67EF61C, so should we use the virtual device
> associated with that GUID as the parent, or just have WMI itself as the
> parent device? I'm really not sure which would be the better way to go.
It's possible for a driver to bind itself to multiple GUIDs, and I guess
it's /potentially/ possible for a machine to have multiple event GUIDs.
I'm not sure whether those should be created as separate input devices,
or whether it would make sense for a driver to bind them into a single
input driver. If the latter, wmi probably ought to be the parent?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-01-16 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071218235137.12838.75397.stgit@localhost>
2007-12-26 22:48 ` [PATCH, RFC] HP WMI hotkey driver Matthew Garrett
2008-01-03 16:58 ` Dmitry Torokhov
2008-01-14 17:41 ` [PATCH, RFC] HP WMI hotkey driver, RFKill query? Matthew Garrett
2008-01-14 18:27 ` Carlos Corbacho
2008-01-14 22:25 ` Carlos Corbacho
2008-01-15 20:54 ` Dmitry Torokhov
2008-01-16 1:38 ` Carlos Corbacho
2008-01-16 1:49 ` Matthew Garrett [this message]
2008-02-07 3:54 ` Len Brown
2008-02-08 15:26 ` Carlos Corbacho
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=20080116014947.GA7101@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=aystarik@gmail.com \
--cc=carlos@strangeworlds.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.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 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).