From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
sb@m-labs.hk, Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] HID: i2c-hid: Read wMaxInputLength of input report instead of bufsize
Date: Mon, 23 Feb 2015 15:52:44 +0200 [thread overview]
Message-ID: <1424699565-138045-3-git-send-email-mika.westerberg@linux.intel.com> (raw)
In-Reply-To: <1424699565-138045-1-git-send-email-mika.westerberg@linux.intel.com>
Wacom digitizer (WCOM0008) on Lenovo Thinkpad 10 seems to allow reading of
subsequent reports (or part of them) if we read more than wMaxInputLength
of data at the time. This data is not always aligned so that the next
report would start right after another.
For example we might get following sequence:
i2c_hid i2c-WCOM0008:00: input: 0a 00 02 21 20 17 ad 22 11 03
i2c_hid i2c-WCOM0008:00: input: ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03 0a 00 02 21 20 17
ad 22 11 03
i2c_hid i2c-WCOM0008:00: input: 02 21 20 17 ad 22 11 03 0a 00
02 21 20 17 ad 22 11 03 0a 00
02 21 20 17 ad 22 11 03 0a 00
02 21 20 17 ad 22 11 03 0a 00
02 21 20 17 ad 22 11 03 0a 00
02 21 20 17 ad 22 11 03 0a 00
02 21 20 17
i2c_hid i2c-WCOM0008:00: i2c_hid_get_input: incomplete report (76/8450)
The bufsize is 76 and wMaxInputLength is 10. In above example the first
read gets right amount of data. The second and third reads get full bufsize
(76 bytes) but the report is missing a start already. This causes the
driver to reject the report because we got less than was expected by the
report length (0x2102 = 8450).
If we read only wMaxInputLength at the time this does not happen at all and
the digitizer works fine.
Based on this change the driver to read wMaxInputLength bytes instead of
bufsize if the value looks sane.
Reported-by: Sébastien Bourdeauducq <sb@m-labs.hk>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
---
drivers/hid/i2c-hid/i2c-hid.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
index 8f1dfc5c5d9c..404ccde49acd 100644
--- a/drivers/hid/i2c-hid/i2c-hid.c
+++ b/drivers/hid/i2c-hid/i2c-hid.c
@@ -369,9 +369,17 @@ static int i2c_hid_hwreset(struct i2c_client *client)
static void i2c_hid_get_input(struct i2c_hid *ihid)
{
+ unsigned max_input_length = le16_to_cpu(ihid->hdesc.wMaxInputLength);
int ret, ret_size;
int size = ihid->bufsize;
+ /*
+ * Take the input length from HID descriptor if it is available and
+ * looks reasonable.
+ */
+ if (max_input_length > 0)
+ size = min_t(unsigned, ihid->bufsize, max_input_length);
+
ret = i2c_master_recv(ihid->client, ihid->inbuf, size);
if (ret != size) {
if (ret < 0)
--
2.1.4
next prev parent reply other threads:[~2015-02-23 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:52 [PATCH 0/3] HID: Support for Lenovo Thinkpad 10 digitizer Mika Westerberg
2015-02-23 13:52 ` [PATCH 1/3] HID: wacom: Add support for I2C connected devices Mika Westerberg
2015-02-23 15:22 ` Benjamin Tissoires
2015-02-24 10:31 ` Jiri Kosina
2015-02-23 13:52 ` Mika Westerberg [this message]
2015-02-23 15:26 ` [PATCH 2/3] HID: i2c-hid: Read wMaxInputLength of input report instead of bufsize Benjamin Tissoires
2015-02-24 7:05 ` Mika Westerberg
2015-02-23 13:52 ` [PATCH 3/3] HID: i2c-hid: Add support for ACPI GPIO interrupts Mika Westerberg
2015-02-23 15:35 ` Benjamin Tissoires
2015-02-24 7:42 ` Mika Westerberg
2015-02-24 20:02 ` Jiri Kosina
2015-02-24 21:27 ` Antonio Ospite
2015-02-25 8:02 ` Mika Westerberg
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=1424699565-138045-3-git-send-email-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sb@m-labs.hk \
/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).