From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Maxwell Anselm <silverhammermba@gmail.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Hans de Goede <hdegoede@redhat.com>,
grafi@grafi.jp, Oliver Neukum <oneukum@suse.de>
Subject: Re: [PATCH v3 2/5] input: synaptics - change default width value of cr48 sensors
Date: Mon, 23 Mar 2015 22:17:02 +0100 [thread overview]
Message-ID: <1962533.LEt6rqGP9j@xps13> (raw)
In-Reply-To: <CAN+gG=H7KUsuCgdNDpra8pqS3xcxrXBDHr0FG+tVgqFHWDJV5Q@mail.gmail.com>
On Monday 23 March 2015 16:48:15 Benjamin Tissoires wrote:
> On Sun, Mar 22, 2015 at 10:43 AM, Gabriele Mazzotta
> <gabriele.mzt@gmail.com> wrote:
> > The minimum value these sensors can report is 4, so this should be the
> > value used when W is not reporting the width.
> >
> > Signed-off-by: Gabriele Mazzotta <gabriele.mzt@gmail.com>
> > ---
> > drivers/input/mouse/synaptics.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> > index 133e488..a7a0e73 100644
> > --- a/drivers/input/mouse/synaptics.c
> > +++ b/drivers/input/mouse/synaptics.c
> > @@ -1018,7 +1018,7 @@ static void synaptics_process_packet(struct psmouse *psmouse)
> >
> > if (hw.z > 0 && hw.x > 1) {
> > num_fingers = 1;
> > - finger_width = 5;
> > + finger_width = 4;
>
> I am not sure about this change. It looks benign, but I don't get how
> changing the local variable finger_width can change anything in the
> CR48 processing.
I fail to remember why I did this exactly. I think the reason why I did this
was that before e9e8520f229b ("Input: synaptics - use in-kernel tracking for
reporting mt data") cr48 sensors used ABS_TOOL_WIDTH for all the fingers. If
you had two fingers on the touchpad it was possible for the kernel to emit
fake width variations in case you lifted one (5->4) and brought it back
on the touchpad (4->5). I'm actually not sure of this as I have an Image
Sensor, but even if it's correct, it should no longer be a problem since
multiple slots are used and so 5 would only be used for the second slot.
> Except for this one (which could be dropped IMO), the *rest* of the series is:
> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>
> Thanks for pushing this Gabriele.
>
> Cheers,
> Benjamin
>
> > if (SYN_CAP_EXTENDED(priv->capabilities)) {
> > switch (hw.w) {
> > case 0 ... 1:
> > --
> > 2.1.4
> >
next prev parent reply other threads:[~2015-03-23 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 14:43 [PATCH v3 0/5] input: synaptics - report correct width and pressure values Gabriele Mazzotta
2015-03-22 14:43 ` [PATCH v3 1/5] input: synaptics - fix width values calculation on image sensors Gabriele Mazzotta
2015-03-22 14:43 ` [PATCH v3 2/5] input: synaptics - change default width value of cr48 sensors Gabriele Mazzotta
2015-03-23 20:48 ` Benjamin Tissoires
2015-03-23 21:17 ` Gabriele Mazzotta [this message]
2015-03-22 14:43 ` [PATCH v3 3/5] input: synaptics - setup devices depending on their capabilities Gabriele Mazzotta
2015-03-22 14:43 ` [PATCH v3 4/5] input: synaptics - make image sensors and cr48 sensors report widths Gabriele Mazzotta
2015-06-12 0:40 ` Dmitry Torokhov
2015-06-12 18:39 ` Gabriele Mazzotta
2015-03-22 14:43 ` [PATCH v3 5/5] input: MT - add ABS_TOOL_WIDTH to the legacy pointer emulation Gabriele Mazzotta
2015-06-12 0:38 ` Dmitry Torokhov
2015-04-27 20:01 ` [PATCH v3 0/5] input: synaptics - report correct width and pressure values Gabriele Mazzotta
2015-06-09 10:26 ` Gabriele Mazzotta
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=1962533.LEt6rqGP9j@xps13 \
--to=gabriele.mzt@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=grafi@grafi.jp \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@bitmath.org \
--cc=silverhammermba@gmail.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).