linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andrew Duggan <aduggan@synaptics.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Jiri Kosina <jikos@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] HID: multitouch: Fetch feature reports on demand for Win8 devices
Date: Thu, 8 Oct 2015 12:40:57 +0300	[thread overview]
Message-ID: <20151008094057.GN1506@lahna.fi.intel.com> (raw)
In-Reply-To: <5615C30A.5060503@synaptics.com>

On Wed, Oct 07, 2015 at 06:12:42PM -0700, Andrew Duggan wrote:
> I can confirm that it is working on the Dell XPS 13 and the buttonpad
> property is set correctly. However, I also tried it on an older non
> production precision touchpad and it didn't work. It reports that it fails
> to fetch feature 8 and then doesn't report any input. I'm concerned that
> some of the early PTPs in some Dell and Acer systems might not work with
> this change. I'll test this tomorrow on a few more systems to see if the
> problem is isolated to just this one non production touchpad.

Thanks for testing.

> [ 2969.222125] usb 1-1: New USB device found, idVendor=06cb, idProduct=2393
> [ 2969.222128] usb 1-1: New USB device strings: Mfr=0, Product=2,
> SerialNumber=0
> [ 2969.222130] usb 1-1: Product: Synaptics T Pad V 01.31
> [ 2974.223578] hid-multitouch 0003:06CB:2393.0008: failed to fetch feature 8
> [ 2979.226037] hid-multitouch 0003:06CB:2393.0008: failed to fetch feature 8
> [ 2979.226137] input: Synaptics T Pad V 01.31 UNKNOWN as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:06CB:2393.0008/input/input34
> [ 2979.226431] hid-multitouch 0003:06CB:2393.0008: input,hiddev0,hidraw2:
> USB HID v1.11 Mouse [Synaptics T Pad V 01.31] on usb-0000:00:14.0-1/input0

Without the patch is it successfully retrieving feature 8?

It may be that it has HID_QUIRK_NO_INIT_REPORTS set via quirks in usbhid
which causes the driver to fetch the report in mt_feature_mapping() and
previously it did not do that.

  reply	other threads:[~2015-10-08  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 14:47 [PATCH] HID: multitouch: Fetch feature reports on demand for Win8 devices Mika Westerberg
2015-09-29  9:04 ` Benjamin Tissoires
2015-09-30  8:45   ` Mika Westerberg
2015-10-06 14:07     ` Jiri Kosina
2015-10-07 12:33       ` [PATCH v2] " Mika Westerberg
2015-10-07 13:34         ` Benjamin Tissoires
2015-10-07 15:56           ` Seth Forshee
2015-10-08  1:12             ` Andrew Duggan
2015-10-08  9:40               ` Mika Westerberg [this message]
2015-10-09  1:10                 ` Andrew Duggan
2015-10-09  8:53                   ` Mika Westerberg
2015-10-09 13:39                     ` Benjamin Tissoires
2015-10-11 22:51         ` 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=20151008094057.GN1506@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seth.forshee@canonical.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).