linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andrew Duggan <aduggan@synaptics.com>,
	Seth Forshee <seth.forshee@canonical.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: Fri, 9 Oct 2015 09:39:02 -0400	[thread overview]
Message-ID: <20151009133902.GA4579@mail.corp.redhat.com> (raw)
In-Reply-To: <20151009085308.GT1506@lahna.fi.intel.com>

On Oct 09 2015 or thereabouts, Mika Westerberg wrote:
> On Thu, Oct 08, 2015 at 06:10:23PM -0700, Andrew Duggan wrote:
> > No, this touchpad doesn't have HID_QUIRK_NO_INIT_REPORTS set and
> > usbhid/hid-core.c is calling usbhid_init_reports() which is retrieving
> > feature 8. But, I did some additional testing and I wasn't able to reproduce
> > this issue on other systems. The failure occurs on a Dell XPS 13 9343, but
> > the exact same touchpad and the exact same kernel (I booted both systems off
> > an external HD to ensure that the kernel and OS are identical) I didn't see
> > a problem. I also tried a different USB PTP touchpad which didn't have an
> > issue. Also, I tried returning in mt_get_feature() instead of reading the
> > report when the report id is 8. When I did that everything worked.
> > 
> > So as of right now, it looks like a single non production USB PTP touchpad
> > fails on one particular system. But, all other tests have been successful.
> > 
> > Let me know if you have any other suggestions for me to test. But, it seems
> > like this failure might be fairly isolated.
> 
> Thanks a lot for testing all this.
> 
> If the failure is limited to a single non-production touchpad then, I
> suppose we should be fine. As long as there are no such systems out
> there in the wild.
> 
> One additional thing we could check in mt_get_feature() is if the device
> is connected via I2C and only in that case fetch the feature in
> question.
> 
> Jiri, Benjamin, what do you think?

I think we are fine with the current patch. The windows driver does
retrieve the important features during the initialization so with this
patch we are closer than ever than what it does.

If (and only if) we ever encounter a problem later on, we can always
make this patch only for i2c devices, but I would still try to match the
Windows driver as much as possible.

So my reviewed-by still applies.

Cheers,
Benjamin

  reply	other threads:[~2015-10-09 13:39 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
2015-10-09  1:10                 ` Andrew Duggan
2015-10-09  8:53                   ` Mika Westerberg
2015-10-09 13:39                     ` Benjamin Tissoires [this message]
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=20151009133902.GA4579@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=aduggan@synaptics.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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).