linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Peter Hutterer <peter.hutterer@who-t.net>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input - synaptics: use dmax in input_mt_assign_slots
Date: Tue, 3 Feb 2015 15:40:59 -0800	[thread overview]
Message-ID: <20150203234059.GA23942@dtor-ws> (raw)
In-Reply-To: <1422904558-30055-1-git-send-email-benjamin.tissoires@redhat.com>

On Mon, Feb 02, 2015 at 02:15:58PM -0500, Benjamin Tissoires wrote:
> When tapping a clickpad with two fingers, there is a chance that the
> sensor sees first only one finger, and at the next scan only the
> second one.
> In this case, the sensors says that there has been only one finger
> on the clickpad, which moved really fast between two scans.
> 
> We can try to counter this by adding a limit to what an actual finger
> can move between 2 scans.
> A distance of 1cm between two scans for one finger seems reasonable.
> 
> However, this is not really accurate because the resolution in X and in Y
> differs. But heh, that's how the in-kernel tracking works right now, and
> its job is quite good, even with this approximation.
> 
> This parameter solves most of the jumps observed, not all of them however.
> But this is a hardware defect, and we might not be able to get something
> better without much heavier computations.
> 
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=76722
> 
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>

Applied, thank you.

> ---
>  drivers/input/mouse/synaptics.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> index a3692e3..bee0387 100644
> --- a/drivers/input/mouse/synaptics.c
> +++ b/drivers/input/mouse/synaptics.c
> @@ -67,6 +67,9 @@
>  #define X_MAX_POSITIVE 8176
>  #define Y_MAX_POSITIVE 8176
>  
> +/* maximum ABS_MT_POSITION displacement (in mm) */
> +#define DMAX 10
> +
>  /*****************************************************************************
>   *	Stuff we need even when we do not want native Synaptics support
>   ****************************************************************************/
> @@ -809,7 +812,7 @@ static void synaptics_report_mt_data(struct psmouse *psmouse,
>  		pos[i].y = synaptics_invert_y(hw[i]->y);
>  	}
>  
> -	input_mt_assign_slots(dev, slot, pos, nsemi, 0);
> +	input_mt_assign_slots(dev, slot, pos, nsemi, DMAX * priv->x_res);
>  
>  	for (i = 0; i < nsemi; i++) {
>  		input_mt_slot(dev, slot[i]);
> -- 
> 2.1.0
> 

-- 
Dmitry

      reply	other threads:[~2015-02-03 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 19:15 [PATCH] Input - synaptics: use dmax in input_mt_assign_slots Benjamin Tissoires
2015-02-03 23:40 ` 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=20150203234059.GA23942@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rydberg@bitmath.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).