From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Henrik Rydberg <rydberg@bitmath.se>
Cc: linux-input@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@enac.fr>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: QUANTA touchscreen controller integrated in HP2310ti no longer recognised (regression in 3.5 and later as compared to 3.3)
Date: Wed, 22 Aug 2012 10:00:12 +0100 [thread overview]
Message-ID: <2303254.RzNp9y400f@f17simon> (raw)
In-Reply-To: <20120821190626.GA1260@polaris.bitmath.org>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
On Tuesday 21 August 2012 21:06:26 Henrik Rydberg wrote:
> Hi Simon,
>
> > We're going through our collection of touch screens, making sure that they all
> > work with current kernels, and we've found one that doesn't work with today's
> > Linus master.
> >
> > lsusb describes the screen as:
> > Bus 006 Device 002: ID 0408:3001 Quanta Computer, Inc. Optical Touch Screen
>
> What about 0408:3008, does that one work?
>
I don't have a sample of 0408:3008 to try.
> > Any ideas on the best way to resolve this regression?
>
> What does 'cat /sys/bus/hid/devices/0003:0408:3001.0001/modalias' say?
It's the same whether or not I revert the patch:
# cat /sys/bus/hid/devices/0003:0408:3001.0001/modalias
hid:b0003g0000v00000408p00003001
If I've understood hid-code.c correctly, this means that
hdev->group == HID_GROUP_ANY, implying that neither hid_scan_usage nor
hid_scan_report have run.
>
> The patch below ought to be enough to make it work, although it is
> still unclear why it is needed.
>
I'd like to get to the bottom of why this patch is needed - the patch I
reverted covered 71 touchscreen controllers, and the fact that hdev->group is
set to HID_GROUP_ANY worries me - I'm concerned that there's something
deeper wrong that's causing the USB HID core to not be able to get the report
descriptor reliably.
> Thanks,
> Henrik
>
> ---
>
> diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
> index bd4bc3c..2b775c3 100644
> --- a/drivers/hid/hid-multitouch.c
> +++ b/drivers/hid/hid-multitouch.c
> @@ -963,7 +963,7 @@ static const struct hid_device_id mt_devices[] = {
> MT_USB_DEVICE(USB_VENDOR_ID_QUANTA,
> USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH) },
> { .driver_data = MT_CLS_CONFIDENCE_CONTACT_ID,
> - MT_USB_DEVICE(USB_VENDOR_ID_QUANTA,
> + HID_USB_DEVICE(USB_VENDOR_ID_QUANTA,
> USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3001) },
> { .driver_data = MT_CLS_CONFIDENCE_CONTACT_ID,
> MT_USB_DEVICE(USB_VENDOR_ID_QUANTA,
--
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2012-08-22 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1700293.Y8yBuPUG33@f17simon>
2012-08-21 19:06 ` QUANTA touchscreen controller integrated in HP2310ti no longer recognised (regression in 3.5 and later as compared to 3.3) Henrik Rydberg
2012-08-22 9:00 ` Simon Farnsworth [this message]
2012-08-22 9:40 ` Simon Farnsworth
2012-08-22 17:04 ` Henrik Rydberg
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=2303254.RzNp9y400f@f17simon \
--to=simon.farnsworth@onelan.co.uk \
--cc=benjamin.tissoires@enac.fr \
--cc=benjamin.tissoires@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@bitmath.se \
/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).