From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: linux-input@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Andrew Duggan <aduggan@synaptics.com>
Subject: Re: [PATCH] Input: synaptics - reset the ABS_X/Y fuzz after initializing MT axes
Date: Tue, 16 Jan 2018 15:41:26 -0800 [thread overview]
Message-ID: <20180116234126.4qxrvfyacy2grw37@dtor-ws> (raw)
In-Reply-To: <20180116053459.GA14660@jelly>
On Tue, Jan 16, 2018 at 03:34:59PM +1000, Peter Hutterer wrote:
> input_mt_init_slots() resets the ABS_X/Y fuzz to 0 and expects the driver to
> call input_mt_report_pointer_emulation(). That is based on the MT position
> bits which are already defuzzed - hence a fuzz of 0.
>
> In the case of synaptics semi-mt devices, we report the ABS_X/Y axes manually.
> This results in the MT position being defuzzed but the single-touch emulation
> missing that defuzzing.
>
> Work around this by re-initializing the ABS_X/Y axes after the MT axis to
> get the same fuzz value back.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=104533
>
> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Applied, thank you.
> ---
> Semi-mt devices are Dodos, so I'd rather go for the easy fix here than a
> big rewrite of that code.
>
> drivers/input/mouse/synaptics.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> index ee5466a374bf..0e04275e0d74 100644
> --- a/drivers/input/mouse/synaptics.c
> +++ b/drivers/input/mouse/synaptics.c
> @@ -1280,6 +1280,14 @@ static void set_input_params(struct psmouse *psmouse,
> INPUT_MT_POINTER |
> (cr48_profile_sensor ?
> INPUT_MT_TRACK : INPUT_MT_SEMI_MT));
> +
> + /* For semi-mt devices we send ABS_X/Y ourselves instead of
> + * input_mt_report_pointer_emulation. But
> + * input_mt_init_slots() resets the fuzz to 0, leading to a
> + * filtered ABS_MT_POSITION_X but an unfiltered ABS_X
> + * position. Let's re-initialize ABS_X/Y here. */
> + if (!cr48_profile_sensor)
> + set_abs_position_params(dev, &priv->info, ABS_X, ABS_Y);
> }
>
> if (SYN_CAP_PALMDETECT(info->capabilities))
> --
> 2.14.3
>
--
Dmitry
prev parent reply other threads:[~2018-01-16 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 5:34 [PATCH] Input: synaptics - reset the ABS_X/Y fuzz after initializing MT axes Peter Hutterer
2018-01-16 23:41 ` Dmitry Torokhov [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=20180116234126.4qxrvfyacy2grw37@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
/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).