From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Ping Cheng <pingc@wacom.com>,
Chris Bagwell <chris@cnpbagwell.com>
Subject: Re: [RFC][PATCH] input: Introduce device information ioctl
Date: Tue, 7 Dec 2010 08:48:12 -0800 [thread overview]
Message-ID: <20101207164811.GA25344@core.coreip.homeip.net> (raw)
In-Reply-To: <20101207162222.GA32237@kroah.com>
On Tue, Dec 07, 2010 at 08:22:22AM -0800, Greg KH wrote:
> On Tue, Dec 07, 2010 at 08:25:26AM +0100, Henrik Rydberg wrote:
> > /**
> > + * struct input_devinfo - device information via EVIOCGDEVINFO ioctl
> > + * @types: bitmask of types (DEVTYPE_*) matching this device
> > + * @capabilities: bitmask of capabilities (DEVCAPS_*) of this device
> > + *
> > + * This struct provides information about the device needed for
> > + * automatic setup in userspace, such as if the device is direct
> > + * (touchscreen) or indirect (touchpad), and if there are other
> > + * special considerations, such as the touchpad also being a button.
> > + */
> > +struct input_devinfo {
> > + __u32 types;
> > + __u32 capabilities;
> > +};
>
> Why use an ioctl for this at all? It's just 2 simple values that don't
> need to be atomically read at the same time. What's wrong with 2 more
> sysfs files?
>
Because if you already dealing with a file descriptor ioctl is much more
convenient. Sysfs can be nice (and that is why we'll add it as well) but
it is not a recipe for the world peace.
--
Dmitry
next prev parent reply other threads:[~2010-12-07 16:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 7:25 [RFC][PATCH] input: Introduce device information ioctl Henrik Rydberg
2010-12-07 9:16 ` Dmitry Torokhov
2010-12-07 10:48 ` Kay Sievers
2010-12-07 10:56 ` Dmitry Torokhov
2010-12-07 11:19 ` Kay Sievers
2010-12-07 12:44 ` Arnd Bergmann
2010-12-07 12:52 ` Kay Sievers
2010-12-07 12:55 ` Arnd Bergmann
2010-12-07 12:40 ` Arnd Bergmann
2010-12-07 12:49 ` Kay Sievers
2010-12-07 16:51 ` Dmitry Torokhov
2010-12-07 19:57 ` Henrik Rydberg
2010-12-08 6:02 ` Dmitry Torokhov
2010-12-08 19:04 ` Henrik Rydberg
2010-12-09 9:25 ` Dmitry Torokhov
2010-12-07 16:22 ` Greg KH
2010-12-07 16:48 ` Dmitry Torokhov [this message]
2010-12-07 18:48 ` Ping Cheng
2010-12-07 19:35 ` Dmitry Torokhov
2010-12-07 19:18 ` Chris Bagwell
2010-12-07 19:37 ` Dmitry Torokhov
2010-12-08 20:26 ` Valdis.Kletnieks
2010-12-08 20:37 ` Henrik Rydberg
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=20101207164811.GA25344@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chris@cnpbagwell.com \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pingc@wacom.com \
--cc=rydberg@euromail.se \
/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).