linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: 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, 07 Dec 2010 20:57:14 +0100	[thread overview]
Message-ID: <4CFE919A.1040704@euromail.se> (raw)
In-Reply-To: <20101207091653.GA22416@core.coreip.homeip.net>

On 12/07/2010 10:16 AM, Dmitry Torokhov wrote:

> Hi Henrik,
> 
> On Tue, Dec 07, 2010 at 08:25:26AM +0100, Henrik Rydberg wrote:
>> Today, userspace sets up an input device based on the data it emits.
>> This is not always enough; a tablet and a touchscreen may emit exactly
>> the same data, for instance, but the former should be set up with a
>> pointer whereas the latter does not need to. Recently, a new type of
>> touchpad has emerged where the buttons are under the pad, which changes
>> handling logic without changing the emitted data. This patch introduces
>> a new ioctl, EVIOCGDEVINFO, which allows userspace to extract information
>> about the device resulting in proper setup.
> 
> If we agree that the new ioctl is suitable we'llalso need to wireit up
> through sysfs. Also, can we keep all definitions to INPUT_ namespace?
> 
> Thanks.
> 


Thanks all for the comments, this is what I extract from them:

* Split struct into separate calls, although this still seems debated.

* Use INPUT_ namespace

* Add sysfs version

* Keep bitmask for types. Is the list of types complete?

* Still only one data point for capabilities. Anything else?

Sounds about right?

Thanks,
Henrik

  parent reply	other threads:[~2010-12-07 19:57 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 [this message]
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
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=4CFE919A.1040704@euromail.se \
    --to=rydberg@euromail.se \
    --cc=chris@cnpbagwell.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pingc@wacom.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).