From: Ping Cheng <pinglinux@gmail.com>
To: jkosina@suse.cz
Cc: linux-input@vger.kernel.org, Ping Cheng <pingc@wacom.com>
Subject: [PATCH 0/2] Cleanup and fix touch_down implementation
Date: Fri, 20 Feb 2015 14:25:19 -0800 [thread overview]
Message-ID: <1424471119-4628-1-git-send-email-pingc@wacom.com> (raw)
Hi Jiri,
This set is based on your for-3.20/upstream-fixes branch.
If pen comes in proximity while touch is down, we force touch up
before sending pen events. This idea has been implemented for
Tablet PCs. But other tablets that support both pen and touch are
not fully considered.
Ping Cheng (2):
HID: wacom: do not send pen events before touch is up/forced out
HID: wacom: rely on actual touch down count to decide touch_down
drivers/hid/wacom_wac.c | 81 ++++++++++++++++++++++++++++++-------------------
1 file changed, 49 insertions(+), 32 deletions(-)
--
1.9.1
next reply other threads:[~2015-02-20 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 22:25 Ping Cheng [this message]
2015-02-27 7:38 ` [PATCH 0/2] Cleanup and fix touch_down implementation Jiri Kosina
2015-02-27 17:41 ` Ping Cheng
2015-02-27 20:18 ` Jiri Kosina
2015-02-27 20:32 ` Ping Cheng
2015-03-02 23:28 ` Jiri Kosina
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=1424471119-4628-1-git-send-email-pingc@wacom.com \
--to=pinglinux@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@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).