public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li, Yan I" <yan.i.li@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>,
	"Ding, Jian-feng" <jian-feng.ding@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"meego-kernel@lists.meego.com" <meego-kernel@lists.meego.com>,
	Christopher Heiny <christopherheiny@gmail.com>
Subject: Re: [PATCH] Input: Lenovo S10-3t's touchpad support
Date: Tue, 30 Nov 2010 10:18:40 +0800	[thread overview]
Message-ID: <20101130021833.GA8369@thyme.bj.intel.com> (raw)
In-Reply-To: <20101127075528.GA28667@core.coreip.homeip.net>

On Sat, Nov 27, 2010 at 03:55:28PM +0800, Dmitry Torokhov wrote:
> > So far we've found that the S10-3ts are shipped with two slightly
> > different models of touchpads, of which the 0x0c cap is either
> > 0x5a0400 or 0x4a0500. They are not Clickpad and return BTN_LEFT and
> > BTN_RIGHT normally.
> 
> Hmm, this is weird. According to my data:
> 
> >> Treat it as a two-bit field.
> >>   0x00 == not a clickpad
> >>   0x01 == 1 button clickpad
> >>   0x02 == 2 button clickpad
> >>   0x03 == reserved

Wait, you said there are "2 button clickpad"? If so the current way
the kernel handles clickpad is totally wrong:

    if (SYN_CAP_CLICKPAD(priv->ext_cap_0c)) {
        /* Clickpads report only left button */
        __clear_bit(BTN_RIGHT, dev->keybit);
        __clear_bit(BTN_MIDDLE, dev->keybit);
    }

It could only handle those "1 button clickpad", which emits solely
BTN_MIDDLE (and the kernel sends it out as BTN_LEFT instead). It can't
handle "2 button clickpad" correctly.

So I think the touchpad installed on the S10-3t is a "2 button
clickpad" and it emits BTN_LEFT and BTN_RIGHT as usual.

Also IIRC the current X synaptics driver detects clickpad by checking
whether it has one button only, obviously this could not work with 2
button clickpad either.

-- 
Best regards,
Li, Yan

MeeGo Team, Opensource Technology Center, SSG, Intel
Office tel.: +86-10-82171695 (inet: 8-758-1695)
OpenPGP key: 5C6C31EF
IRC: yanli on network irc.freenode.net

  reply	other threads:[~2010-11-30  2:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27  3:56 [PATCH] Input: Lenovo S10-3t's touchpad support Yan Li
2010-11-27  7:55 ` Dmitry Torokhov
2010-11-30  2:18   ` Li, Yan I [this message]
2010-11-30  7:12     ` Takashi Iwai
2010-11-30  8:09       ` Li, Yan I
2010-11-30  7:44 ` [PATCH v2] Input: Bug 18122 - Support Lenovo S10-3t's 2-button ClickPad Yan Li
2010-11-30  7:50   ` Dmitry Torokhov
2010-11-30  8:08     ` Li, Yan I
2010-11-30 15:48       ` Tobyn Bertram
2010-12-01  4:11         ` Li, Yan I
2010-12-01  6:04           ` Takashi Iwai
     [not found]             ` <BAY130-W15C8BF6B2994FAE083FAF5DE260@phx.gbl>
2010-12-01  7:18               ` Li, Yan I
2010-12-01  7:23                 ` Dmitry Torokhov
2010-12-01  7:46           ` Dmitry Torokhov
2010-12-01  8:01             ` Li, Yan I

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=20101130021833.GA8369@thyme.bj.intel.com \
    --to=yan.i.li@intel.com \
    --cc=christopherheiny@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jian-feng.ding@intel.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meego-kernel@lists.meego.com \
    --cc=tiwai@suse.de \
    /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