linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Masaki Ota" <masaki.ota@jp.alps.com>
Cc: linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Regression since commit 92bac83
Date: Sun, 18 Oct 2015 18:59:55 -0500	[thread overview]
Message-ID: <5624327B.7080906@lwfinger.net> (raw)

Hi,

I recently upgraded the kernel in a Dell Latitude D600 and found that the 
touchpad clicks failed. The problem was bisected to commit 
92bac83dd79e60e65c475222e41a992a70434beb ("Input: alps - non interleaved V2 
dualpoint has separate stick button bits"). The laptop has a combination 
touchpad and control stick. For this device, the following values are found:

priv->protoversion is 0x200 (ALPS_PROTO_V2)
priv->flags is 0x6 (ALPS_DUALPOINT | ALPS_PASS)

As a result, the new code added in this patch is executed, and left, right, and 
middle are updated. Once this code is introduced, a left click causes some event 
as it will wake a sleeping screen, but not select any windows or do anything useful.

Please advise on what information would be needed to help debug this problem.

Thanks,

Larry

             reply	other threads:[~2015-10-18 23:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 23:59 Larry Finger [this message]
2015-10-19  8:08 ` Regression since commit 92bac83 Hans de Goede
2015-10-19 15:55   ` Larry Finger
2015-10-19 16:51     ` Dmitry Torokhov
2015-10-19 17:21       ` Hans de Goede
2015-10-20  7:22       ` Pali Rohár
2015-10-20 11:39     ` Hans de Goede
2015-10-20 17:33       ` Larry Finger
2015-10-21  8:19       ` Pali Rohár
2015-10-21  8:30         ` Hans de Goede
2015-10-21  8:37           ` Pali Rohár

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=5624327B.7080906@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masaki.ota@jp.alps.com \
    --cc=pali.rohar@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).