From: "Pali Rohár" <pali.rohar@gmail.com>
To: Paul Donohue <linux-kernel@PaulSD.com>
Cc: linux-input@vger.kernel.org, Ben Gamari <ben@smart-cactus.org>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v4 2/3] Input: ALPS - Clean up TrackStick handling for SS5 hardware
Date: Wed, 9 Nov 2016 13:14:43 +0100 [thread overview]
Message-ID: <20161109121443.GC19557@pali> (raw)
In-Reply-To: <20161108151621.GO2927@TopQuark.net>
On Tuesday 08 November 2016 10:16:21 Paul Donohue wrote:
> For consistency and clarity, the input_report_*() functions should
> be called by alps_process_packet_ss4_v2() instead of by
> alps_decode_ss4_v2().
>
> Signed-off-by: Paul Donohue <linux-kernel@PaulSD.com>
>
> diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
> index b93fe83..12376d2 100644
> --- a/drivers/input/mouse/alps.c
> +++ b/drivers/input/mouse/alps.c
> @@ -1267,18 +1267,11 @@ static int alps_decode_ss4_v2(struct alps_fields *f,
> break;
>
> case SS4_PACKET_ID_STICK:
> - if (!(priv->flags & ALPS_DUALPOINT)) {
> - psmouse_warn(psmouse,
> - "Rejected trackstick packet from non DualPoint device");
> - } else {
> - int x = (s8)(((p[0] & 1) << 7) | (p[1] & 0x7f));
> - int y = (s8)(((p[3] & 1) << 7) | (p[2] & 0x7f));
> - int pressure = (s8)(p[4] & 0x7f);
> -
> - input_report_rel(priv->dev2, REL_X, x);
> - input_report_rel(priv->dev2, REL_Y, -y);
> - input_report_abs(priv->dev2, ABS_PRESSURE, pressure);
> - }
> + f->st.x = (s8)(((p[0] & 1) << 7) | (p[1] & 0x7f));
> + f->st.y = -(s8)(((p[3] & 1) << 7) | (p[2] & 0x7f));
> + f->pressure = (s8)(p[4] & 0x7f);
This is not correct. Those fields values are used for single touch
events from touchpad -- not from trackstick.
Btw, you have access to packet also in process functions, so you can
extract x, y and pressure in process function too.
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2016-11-09 12:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 21:01 [PATCH] Input: ALPS - Fix TrackStick support for SS5 hardware Paul Donohue
2016-11-01 9:35 ` Pali Rohár
2016-11-05 16:30 ` Paul Donohue
2016-11-05 16:44 ` [PATCH v2] " Paul Donohue
2016-11-06 19:59 ` Pali Rohár
2016-11-08 14:24 ` Paul Donohue
2016-11-06 19:57 ` [PATCH] " Pali Rohár
2016-11-08 14:54 ` [PATCH v3 1/3] " Paul Donohue
2016-11-08 14:59 ` [PATCH v3 2/3] " Paul Donohue
2016-11-08 15:06 ` Paul Donohue
2016-11-08 15:14 ` [PATCH v4 1/3] " Paul Donohue
2016-11-08 15:16 ` [PATCH v4 2/3] Input: ALPS - Clean up TrackStick handling " Paul Donohue
2016-11-08 15:17 ` [PATCH v4 3/3] Input: ALPS - Clean up code " Paul Donohue
2016-11-08 15:46 ` Paul Donohue
2016-11-08 15:49 ` Paul Donohue
2016-11-09 12:14 ` Pali Rohár [this message]
2016-11-10 14:27 ` [PATCH v4 2/3] Input: ALPS - Clean up TrackStick handling " Paul Donohue
2016-11-10 15:19 ` Pali Rohár
2016-11-10 16:44 ` [PATCH v5 0/3] Input: ALPS - Bug fix and cleanup " Paul Donohue
2016-11-10 16:44 ` [PATCH v5 1/3] Input: ALPS - Fix TrackStick support " Paul Donohue
2016-11-10 16:44 ` [PATCH v5 2/3] Input: ALPS - Clean up TrackStick handling " Paul Donohue
2016-11-10 16:44 ` [PATCH v5 3/3] Input: ALPS - Clean up code " Paul Donohue
2016-11-11 13:59 ` [PATCH v5 0/3] Input: ALPS - Bug fix and cleanup " Pali Rohár
2016-11-12 0:56 ` Dmitry Torokhov
2016-11-12 1:03 ` Pali Rohár
2016-11-12 1:06 ` Dmitry Torokhov
2016-11-12 12:29 ` Pali Rohár
2016-11-13 6:43 ` Dmitry Torokhov
2016-11-13 10:31 ` Pali Rohár
2016-11-13 15:28 ` Paul Donohue
2016-11-24 14:25 ` [PATCH v6 " Paul Donohue
2016-11-24 14:25 ` [PATCH v6 1/3] Input: ALPS - Fix TrackStick support " Paul Donohue
2016-11-24 14:25 ` [PATCH v6 2/3] Input: ALPS - Clean up TrackStick handling " Paul Donohue
2016-11-24 14:25 ` [PATCH v6 3/3] Input: ALPS - Clean up code " Paul Donohue
2016-11-09 12:12 ` [PATCH v4 1/3] Input: ALPS - Fix TrackStick support " Pali Rohár
2016-11-10 14:17 ` Paul Donohue
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=20161109121443.GC19557@pali \
--to=pali.rohar@gmail.com \
--cc=ben@smart-cactus.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@PaulSD.com \
--cc=mhocko@suse.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).