From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Peter Hutterer <peter.hutterer@redhat.com>,
Benjamin Tissoires <btissoir@redhat.com>,
linux-input@vger.kernel.org
Subject: [PATCH 0/2] input: Add INPUT_PROP_POINTING_STICK property
Date: Tue, 2 Sep 2014 14:43:22 +0200 [thread overview]
Message-ID: <1409661804-10489-1-git-send-email-hdegoede@redhat.com> (raw)
Hi,
It is useful for userspace to know that they're not dealing with a regular
mouse but rather with a pointing stick (e.g. a trackpoint) so that userspace
can e.g. automatically enable middle button scrollwheel emulation.
It is impossible to tell the difference from the evdev info without resorting
to putting a list of device / driver names in userspace, this is undesirable.
These patches add a property which allows userspace to see if a device is a
pointing stick, and set it on all the pointing stick drivers.
Note these patch apply on top of the current dtor/input.git for-linus
branch. Specifically they depend upon a2418fc4a13 (Input: elantech - add
support for trackpoint found on some v3 models).
Regards,
Hans
next reply other threads:[~2014-09-02 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 12:43 Hans de Goede [this message]
2014-09-02 12:43 ` [PATCH 1/2] input: Add INPUT_PROP_POINTING_STICK property Hans de Goede
2014-09-02 14:34 ` Benjamin Tissoires
2014-09-03 3:18 ` Peter Hutterer
2014-09-02 12:43 ` [PATCH 2/2] input/mouse: Add missing POINTER / DIRECT properties to a bunch of drivers Hans de Goede
2014-09-02 14:38 ` Benjamin Tissoires
2014-09-03 3:21 ` Peter Hutterer
2014-09-02 12:55 ` [PATCH 0/2] input: Add INPUT_PROP_POINTING_STICK property David Herrmann
2014-09-02 14:34 ` Benjamin Tissoires
[not found] ` <5405D6D4.4070406@redhat.com>
2014-09-02 14:50 ` David Herrmann
2014-09-03 3:24 ` Peter Hutterer
2014-09-08 21:45 ` Dmitry Torokhov
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=1409661804-10489-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=btissoir@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@redhat.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).