From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: linux-input@vger.kernel.org, Henrik Rydberg <rydberg@bitmath.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Tim Bird <tim.bird@am.sony.com>,
Roderick Colenbrander <roderick.colenbrander@sony.com>
Subject: Re: [PATCH] Input: mt: only perform pointer emulation on drivers desiring this functionality
Date: Thu, 27 Oct 2016 16:19:42 -0700 [thread overview]
Message-ID: <20161027231942.GB12312@dtor-ws> (raw)
In-Reply-To: <1477603873-9143-1-git-send-email-roderick@gaikai.com>
On Thu, Oct 27, 2016 at 02:31:13PM -0700, Roderick Colenbrander wrote:
> From: Roderick Colenbrander <roderick.colenbrander@sony.com>
>
> The input-mt driver pointer emulation from 'input_mt_sync_frame' regardless
> of the flags passed in to 'input_mt_init_slots' by device drivers.
Right, because needing single-touch (pointer) emulation is not property
of device or driver but rather consumer. If we get to the point where
everything is ready to accept multi-touch (are we there yet) then we can
stop doing pointer emulation altogether.
>
> Pointer emulation is undesired on drivers, which didn't request this
> capability like the hid-sony driver for the Dualshock 4. This gamepad already
> reports ABS_X / ABS_Y for gamepad stick purposes. Pointer emulation would
> inject touchpad values into these sticks, which is undesired.
The driver should not be re-purposing events like that.
ABS_MT_POSITION_X and ABS_X should match.
Why doesn't driver follow Documentation/input/gamepad.txt?
>
> This patch checks the flags INPUT_MT_POINTER / INPUT_MT_DIRECT from within
> input_mt_sync_frame to only allow pointer emulation when the feature was
> requested by the driver as the flags were set in input_mt_init_slots.
> ---
> drivers/input/input-mt.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/input-mt.c b/drivers/input/input-mt.c
> index a1bbec9..30c8128 100644
> --- a/drivers/input/input-mt.c
> +++ b/drivers/input/input-mt.c
> @@ -305,7 +305,8 @@ void input_mt_sync_frame(struct input_dev *dev)
> if ((mt->flags & INPUT_MT_POINTER) && !(mt->flags & INPUT_MT_SEMI_MT))
> use_count = true;
>
> - input_mt_report_pointer_emulation(dev, use_count);
> + if (mt->flags & (INPUT_MT_POINTER | INPUT_MT_DIRECT))
> + input_mt_report_pointer_emulation(dev, use_count);
>
> mt->frame++;
> }
> --
> 2.7.4
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-10-27 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 21:31 [PATCH] Input: mt: only perform pointer emulation on drivers desiring this functionality Roderick Colenbrander
2016-10-27 21:36 ` Bird, Timothy
2016-10-27 22:46 ` Henrik Rydberg
2016-10-27 23:27 ` Roderick Colenbrander
2016-10-27 23:19 ` Dmitry Torokhov [this message]
2016-10-27 23:46 ` Roderick Colenbrander
2016-10-27 23:54 ` Dmitry Torokhov
2016-10-28 0:10 ` Roderick Colenbrander
-- strict thread matches above, loose matches on Subject: below --
2016-10-30 15:04 Frank Praznik
2016-10-30 18:45 ` Colenbrander, Roelof
2016-11-03 10:43 ` 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=20161027231942.GB12312@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=roderick.colenbrander@sony.com \
--cc=roderick@gaikai.com \
--cc=rydberg@bitmath.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 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).