From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Jason Gerecke <killertofu@gmail.com>,
Dennis Kempin <denniskempin@google.com>,
Andrew de los Reyes <adlr@google.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] HID: multitouch: touchscreens also use confidence reports
Date: Thu, 10 Aug 2017 17:45:00 -0700 [thread overview]
Message-ID: <20170811004500.13740-2-dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20170811004500.13740-1-dmitry.torokhov@gmail.com>
According to [1] the confidence is used not only by touchpad devices,
but also by touchscreens.
[1] https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchscreen-required-hid-top-level-collections
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
drivers/hid/hid-multitouch.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
index c28defe50a10..1cb00de4bfd1 100644
--- a/drivers/hid/hid-multitouch.c
+++ b/drivers/hid/hid-multitouch.c
@@ -545,7 +545,8 @@ static int mt_touch_input_mapping(struct hid_device *hdev, struct hid_input *hi,
case HID_DG_CONFIDENCE:
if ((cls->name == MT_CLS_WIN_8 ||
cls->name == MT_CLS_WIN_8_DUAL) &&
- field->application == HID_DG_TOUCHPAD) {
+ (field->application == HID_DG_TOUCHPAD ||
+ field->application == HID_DG_TOUCHSCREEN)) {
cls->quirks |= MT_QUIRK_CONFIDENCE;
input_set_abs_params(hi->input,
ABS_MT_TOOL_TYPE,
--
2.14.0.434.g98096fd7a8-goog
next prev parent reply other threads:[~2017-08-11 0:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 0:44 [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches Dmitry Torokhov
2017-08-11 0:45 ` Dmitry Torokhov [this message]
2017-08-11 6:14 ` Henrik Rydberg
2017-08-11 6:54 ` Dmitry Torokhov
2017-08-11 8:29 ` Henrik Rydberg
2017-08-18 3:08 ` Peter Hutterer
2018-05-30 23:12 ` Peter Hutterer
2018-06-01 9:31 ` Benjamin Tissoires
2018-06-01 14:16 ` Benjamin Tissoires
2018-06-01 18:43 ` Dmitry Torokhov
2018-06-01 19:03 ` Henrik Rydberg
2018-06-04 12:57 ` Benjamin Tissoires
2018-06-04 17:27 ` Dmitry Torokhov
2018-06-04 17:55 ` Henrik Rydberg
2018-06-04 18:26 ` Dmitry Torokhov
2018-06-04 20:59 ` Benjamin Tissoires
2018-06-04 21:32 ` Dmitry Torokhov
2018-06-04 22:14 ` Benjamin Tissoires
2018-06-04 23:06 ` Peter Hutterer
2018-06-04 23:28 ` Dmitry Torokhov
2018-06-04 23:51 ` Peter Hutterer
2018-06-04 23:54 ` Dmitry Torokhov
2018-06-04 13:18 ` Benjamin Tissoires
2018-06-04 17:33 ` Dmitry Torokhov
2018-06-04 20:42 ` Benjamin Tissoires
2018-06-04 21:19 ` Dmitry Torokhov
2018-06-04 22:03 ` Benjamin Tissoires
2018-06-04 22:55 ` Peter Hutterer
2018-06-05 13:50 ` Benjamin Tissoires
2018-06-05 17:05 ` 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=20170811004500.13740-2-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=adlr@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=denniskempin@google.com \
--cc=jikos@kernel.org \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@bitmath.org \
/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).