linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rydberg@euromail.se
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
	linux-input <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] HID: multitouch: do not init reports for multitouch devices
Date: Fri, 19 Jul 2013 23:04:30 +0200	[thread overview]
Message-ID: <20130719210430.GA31481@polaris.bitmath.org> (raw)
In-Reply-To: <CAN+gG=G6jw0BkJejZ=Rb+Vzzey1=JdqiiYmMonwjt9G1R779Tg@mail.gmail.com>

Hi Benjamin,

> >> Some multitouch screens do not like to be polled for input reports.
> >> However, the Win8 spec says that all touches should be sent during
> >> each report, making the initialization of reports unnecessary.
> >> The Win7 spec is less precise, but we can safely assume that when
> >> the module is loaded (at boot), no one is touching the screen.
> >>
> >> Add the quirk HID_QUIRK_NO_INIT_REPORTS so that we do not have to
> >> introduce a quirk for each problematic device.
> >
> > I assume you have tested thoroughly for regressions? How about odd
> > eGalax devices, for instance? Changes affecting existing hardware
> > makes me nervous. Is it so bad to add this quirk on a per-device
> > basis? Or perhaps turned on by default for win8 devices only?
> 
> Aargh, I forgot the eGalax... (I don't have it anymore on my desk). I
> was pretty confident because Win [7-8] is not doing any quirks for the
> multitouch devices, and I had in mind that it did not asked for the
> reports at startup (at least, I am sure about it for HID/I2C). I'm not
> sure win 8 devices is a sufficient denominator, because this init
> sequence is not mentioned anywhere in the Win 8 spec. It's true that
> we are going to see fewer Win 7 devices, but I would say it's the
> exact same problem for win 7 and 8. Moreover, asking this for Win 8
> devices only will forces us to detect it in core before hid-multitouch
> is loaded because the init reports is called before the parsing.

We already branch on report specifics in hid_add_device(). Adding win8
detection there is more or less what it was built for.

> If I capture the Win 7 & Win 8 initialization events and I observe
> that they do not retrieve the reports, will it be sufficient as a
> guarantee to include this patch even if it is not widely tested under
> Linux?

We already have the usbhid quirks to handle odd cases, and we can add
all sorts of generic detection during device add, so there really is
no reason to risk regressions at all, is there?

Cheers,
Henrik

  reply	other threads:[~2013-07-19 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  9:08 [PATCH] HID: multitouch: do not init reports for multitouch devices Benjamin Tissoires
2013-07-18 19:24 ` rydberg
2013-07-19  8:47   ` Benjamin Tissoires
2013-07-19 21:04     ` rydberg [this message]
2013-07-24 15:01       ` Benjamin Tissoires

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=20130719210430.GA31481@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=benjamin.tissoires@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=chatty@enac.fr \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).