From: Jason Gerecke <killertofu@gmail.com>
To: jkosina@suse.cz
Cc: linux-input@vger.kernel.org, benjamin.tissoires@gmail.com,
pinglinux@gmail.com
Subject: [PATCH 0/3] HID: wacom: Fix generic multitouch device handling
Date: Mon, 24 Nov 2014 15:32:11 -0800 [thread overview]
Message-ID: <1416871934-14133-1-git-send-email-killertofu@gmail.com> (raw)
This set of patches addresses the problems that I had getting Benjamin's
"HID generic handling" patches. Each of the patches addresses a seprate
issue I encountered:
* Patch 1/3: The devices that I'm using have some usages outside of
a logical or physical collection container which prevents the
reports from being sent. I'm not sure if keying on the application
collection is ideal, but it does do the job.
* Patch 2/3: The devices that I'm using put their X and Y usages after
the finger count, which prevents the (compatibility) ABS_X and
ABS_Y axes from being initialized. This patch just guarantees that
they'll be initialized.
* Patch 3/3: Benjamin's original code seemed to only report data about
the last finger in a multitouch report since information about "earlier"
fingers would be overwritten. This patch changes the logic so that
we immediately report field values whenever we can (there are some
cases that we can't -- the tip/range bits appear before the contact
identifier, so we have to store their state for a short time).
next reply other threads:[~2014-11-24 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 23:32 Jason Gerecke [this message]
2014-11-24 23:32 ` [PATCH 1/3] HID: wacom: Consult the application usage when determining field type Jason Gerecke
2014-11-25 15:29 ` Benjamin Tissoires
2014-11-27 13:45 ` Jiri Kosina
2014-11-24 23:32 ` [PATCH 2/3] HID: wacom: Manually declare ABS_{X,Y} for pointer emulation Jason Gerecke
2014-11-25 15:34 ` Benjamin Tissoires
2014-11-24 23:32 ` [PATCH 3/3] HID: wacom: Report input events immediately upon receipt Jason Gerecke
2014-11-25 15:52 ` Benjamin Tissoires
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=1416871934-14133-1-git-send-email-killertofu@gmail.com \
--to=killertofu@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=pinglinux@gmail.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).