From: "Pali Rohár" <pali.rohar@gmail.com>
To: Douglas Christman <douglaschristman@gmail.com>
Cc: linux-input@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: ALPS DualPoint double click bug
Date: Wed, 22 Jul 2015 09:21:16 +0200 [thread overview]
Message-ID: <20150722072116.GA22138@pali> (raw)
In-Reply-To: <CANuv8QxKap=K=OoCufcM-Yxujmg+3sUOjWX2D9r7qf==EQoTFQ@mail.gmail.com>
On Tuesday 21 July 2015 19:51:48 Douglas Christman wrote:
> On Tue, Jul 21, 2015 at 3:12 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > It is not enough. If do not want to recompile full kernel, but just only
> > psmouse.ko I think that the easiest way is to change this define
> >
> > #define psmouse_dbg
> >
> > in file drivers/input/mouse/psmouse.h to call dev_warn instead dev_dbg.
> > And then just compile psmouse.ko and reload it.
>
> Thanks, that seemed to do the trick. This is what I get from dmesg now:
>
> [ 6.281814] psmouse serio1: cypress_ps2: send extension cmd 0x00, [0 0 0 0]
> [ 6.540028] psmouse serio1: cypress_ps2: Command 0x00 response data
> (0x): 00 00 14
> [ 6.582031] psmouse serio1: alps: E6 report: 00 00 64
> [ 6.617471] psmouse serio1: alps: E7 report: 22 02 14
> [ 6.656974] psmouse serio1: alps: EC report: 10 00 64
> [ 7.104479] psmouse serio1: alps: E6 report: 00 00 64
> [ 7.139714] psmouse serio1: alps: E7 report: 22 02 14
> [ 7.176568] psmouse serio1: alps: EC report: 10 00 64
> [ 7.368849] psmouse serio1: alps: F5 report: 05 01 0a
> [ 7.541367] input: AlpsPS/2 ALPS DualPoint Stick as
> /devices/platform/i8042/serio1/input/input11
> [ 7.571454] input: AlpsPS/2 ALPS DualPoint TouchPad as
> /devices/platform/i8042/serio1/input/input8
Ok, your ALPS touchpad is identified as:
{ { 0x22, 0x02, 0x14 }, 0x00, { ALPS_PROTO_V2, 0xff, 0xff, ALPS_PASS | ALPS_DUALPOINT } }, /* Dell Latitude D600 */
You mentioned that commit 92bac83d introduced your problem:
========================================
commit 92bac83dd79e60e65c475222e41a992a70434beb
Author: Hans de Goede <hdegoede@redhat.com>
Date: Sun Apr 12 15:42:35 2015 -0700
Input: alps - non interleaved V2 dualpoint has separate stick button bits
========================================
Hans, can you look at this problem as it is clearly problem with
protocol V2?
--
Pali Rohár
pali.rohar@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-22 7:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 13:29 ALPS DualPoint double click bug Douglas Christman
2015-07-20 6:54 ` Dmitry Torokhov
2015-07-20 7:25 ` Pali Rohár
2015-07-21 3:00 ` Douglas Christman
2015-07-21 7:12 ` Pali Rohár
2015-07-21 23:51 ` Douglas Christman
2015-07-22 7:21 ` Pali Rohár [this message]
2015-07-22 15:08 ` Benjamin Tissoires
2015-07-22 17:26 ` Stephen Chandler Paul
2015-07-23 9:31 ` Hans de Goede
2015-07-25 14:07 ` Douglas Christman
2015-07-27 16:40 ` Hans de Goede
2015-07-27 23:38 ` Douglas Christman
2015-07-29 20:45 ` [PATCH 0/1] Alps button reporting bugfix cpaul
2015-07-29 20:45 ` [PATCH 1/1] Input - alps: Fix button reporting on the V2 Alps protocol cpaul
2015-07-29 21:01 ` Dmitry Torokhov
2015-07-30 7:52 ` Pali Rohár
2015-07-30 13:51 ` Hans de Goede
2015-07-30 14:11 ` Pali Rohár
2015-07-30 14:18 ` Hans de Goede
2015-07-30 14:28 ` Pali Rohár
2015-07-30 14:32 ` Pali Rohár
2015-07-30 14:38 ` Hans de Goede
2015-07-30 14:45 ` Pali Rohár
2015-07-30 14:17 ` ALPS DualPoint double click bug Hans de Goede
2015-07-30 14:46 ` Pali Rohár
2015-07-30 15:00 ` Hans de Goede
2015-07-30 15:49 ` Pali Rohár
2015-07-31 8:12 ` Hans de Goede
2015-07-31 21:12 ` Douglas Christman
2015-07-31 21:17 ` Pali Rohár
2015-08-01 6:48 ` Hans de Goede
2015-07-21 17:12 ` Dmitry Torokhov
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=20150722072116.GA22138@pali \
--to=pali.rohar@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=douglaschristman@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.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).