From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: Simon Wood <simon@mungewell.org>,
linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Tim Bird <tim.bird@am.sony.com>,
Roderick Colenbrander <roderick.colenbrander@sony.com>
Subject: Re: [PATCH 5/5] HID: sony: Handle multiple touch events input record
Date: Mon, 31 Oct 2016 09:21:49 +0100 [thread overview]
Message-ID: <20161031082149.GA10661@mail.corp.redhat.com> (raw)
In-Reply-To: <CANndSK=2vZKS3nmzt88j4ugR1YxijwRH_OvEGjWtLzzyyKd9JA@mail.gmail.com>
Hi Roderick,
[sorry for the late reply, I was on PTO until today]
On Oct 18 2016 or thereabouts, Roderick Colenbrander wrote:
> >
> > > Correct, the DS4 sends a touch history. The last element is the
> > > latest. An input report can contain multiple touch samples, because
> > > the device internally samples at a rate which is higher than at which
> > > it generates HID reports. On USB you can easily see multiple touch
> > > events and it is even easier on Bluetooth (especially if it is set to
> > > a low frequency). The extra history is important for gestures.
> >
> > OK, so if it's important, you need to actually send it by adding
> > input_mt_sync_frame() and input_sync() calls. Otherwise, the values will
> > just get mangled by the kernel in evdev and everything happens as if you
> > just sent the last pair in the history.
> >
> > The first 4 patches are IMO mergeable, but this one will need a little
> > bit more polish to actually forward the events.
> >
> > Cheers,
> > Benjamin
> >
> > >
> > > Thanks,
> > > Roderick
>
> Hi Ben,
>
> A kind of follow-up to this patch feedback which made it into the
> final patch. The recommendation was to use input_mt_sync_frame, which
> was a good recommendation. There is one oversight, which I'm not sure
> how we need to handle. Basically input_mt_sync_frame triggers pointer
> emulation, which is a problem for the Dualshock 4 since it already
> provides an ABS_X / ABS_Y, so the pointer emulation affects the analog
> stick values.
Ouch, sorry, I did not realize this :(
>
> The hid-sony driver registers the touchpad through input_mt_init_slots
> with the flags parameter '0', which was intended not to request such
> emulation I think. I'm not too familiar with the other input code, but
> should input_mt_sync_frame gate pointer emulation based on
> INPUT_MT_POINTER / INPUT_MT_DIRECT flags or something like that?
I'd say so, though I need to check the other thread first.
Cheers,
Benjamin
>
> Thanks,
> Roderick
prev parent reply other threads:[~2016-10-31 8:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 2:58 [PATCH 0/5] HID: sony: game controller updates Roderick Colenbrander
2016-10-05 2:58 ` [PATCH 1/5] HID: sony: Fix race condition in sony_probe Roderick Colenbrander
2016-10-05 2:58 ` [PATCH 2/5] HID: sony: Adjust HID report size name definitions Roderick Colenbrander
2016-10-05 2:58 ` [PATCH 3/5] HID: sony: Perform CRC check on bluetooth input packets Roderick Colenbrander
2016-10-05 8:24 ` Benjamin Tissoires
2016-10-05 2:58 ` [PATCH 4/5] HID: sony: Send ds4 output reports on output end-point Roderick Colenbrander
2016-10-05 8:31 ` Benjamin Tissoires
2016-10-05 16:54 ` Frank Praznik
2016-10-05 17:35 ` Simon Wood
2016-10-05 20:35 ` Frank Praznik
2016-10-07 15:56 ` Benjamin Tissoires
2016-10-05 18:53 ` Roderick Colenbrander
2016-10-05 2:58 ` [PATCH 5/5] HID: sony: Handle multiple touch events input record Roderick Colenbrander
2016-10-05 8:35 ` Benjamin Tissoires
2016-10-05 15:29 ` Simon Wood
2016-10-05 17:25 ` Roderick Colenbrander
2016-10-07 16:02 ` Benjamin Tissoires
2016-10-18 23:27 ` Roderick Colenbrander
2016-10-31 8:21 ` Benjamin Tissoires [this message]
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=20161031082149.GA10661@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--cc=roderick@gaikai.com \
--cc=simon@mungewell.org \
--cc=tim.bird@am.sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.