linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 21 Jul 2015 09:12:18 +0200	[thread overview]
Message-ID: <20150721071218.GA27290@pali> (raw)
In-Reply-To: <CANuv8Qx0QyYg0SCYqx=auVd9__UjHBj0DEuF-xcA4Ar4Ha=aVw@mail.gmail.com>

On Monday 20 July 2015 23:00:27 Douglas Christman wrote:
> On Mon, Jul 20, 2015 at 3:25 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > Hi! Please recompile psmouse.ko with dev_dbg() debug information and
> > send new dmesg output. We need to know type of ALPS device. Thanks!
> 
> I recompiled with CONFIG_DYNAMIC_DEBUG and echoed 'module psmouse' to
> /sys/kernel/debug/dynamic_debug/control as described in
> Documentation/dynamic-debug-howto.txt, but I don't see any additional
> output in dmesg after reloading the module.  I haven't done this
> before, so I'm probably overlooking something...
> 
> In the meantime, hopefully this output from hwinfo can be of use:
> 
> 52: PS/2 00.0: 10500 PS/2 Mouse
>   [Created at input.249]
>   Unique ID: AH6Q.5+smWHVjPI3
>   Hardware Class: mouse
>   Model: "AlpsPS/2 ALPS DualPoint Stick"
>   Vendor: 0x0002
>   Device: 0x0008 "AlpsPS/2 ALPS DualPoint Stick"
>   Compatible to: int 0x0210 0x0003
>   Device File: /dev/input/mice (/dev/input/mouse0)
>   Device Files: /dev/input/mice, /dev/input/mouse0,
> /dev/input/event11,
> /dev/input/by-path/platform-i8042-serio-1-event-mouse,
> /dev/input/by-path/platform-i8042-serio-1-mouse
>   Device Number: char 13:63 (char 13:32)
>   Driver Info #0:
>     Buttons: 3
>     Wheels: 0
>     XFree86 Protocol: explorerps/2
>     GPM Protocol: exps2
>   Config Status: cfg=new, avail=yes, need=no, active=unknown
> 
> 53: PS/2 00.0: 10500 PS/2 Mouse
>   [Created at input.249]
>   Unique ID: AH6Q.5+smWHVjPI3
>   Hardware Class: mouse
>   Model: "AlpsPS/2 ALPS DualPoint TouchPad"
>   Vendor: 0x0002
>   Device: 0x0008 "AlpsPS/2 ALPS DualPoint TouchPad"
>   Compatible to: int 0x0210 0x0003
>   Device File: /dev/input/mice (/dev/input/mouse1)
>   Device Files: /dev/input/mice, /dev/input/mouse1,
> /dev/input/event12,
> /dev/input/by-path/platform-i8042-serio-1-event-mouse,
> /dev/input/by-path/platform-i8042-serio-1-mouse
>   Device Number: char 13:63 (char 13:33)
>   Driver Info #0:
>     Buttons: 3
>     Wheels: 0
>     XFree86 Protocol: explorerps/2
>     GPM Protocol: exps2
>   Config Status: cfg=new, avail=yes, need=no, active=unknown

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.

-- 
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

  reply	other threads:[~2015-07-21  7:12 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 [this message]
2015-07-21 23:51         ` Douglas Christman
2015-07-22  7:21           ` Pali Rohár
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=20150721071218.GA27290@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).