From: Oskari Saarenmaa <os@ohmu.fi>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Tai-hwa Liang <avatar@sentelic.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: sentelic - filter on-pad clicks in absolute mode
Date: Mon, 02 Apr 2012 18:37:04 +0300 [thread overview]
Message-ID: <4F79C7A0.6060601@ohmu.fi> (raw)
In-Reply-To: <4F79C029.3040606@canonical.com>
On 02/04/12 18:05, Chase Douglas wrote:
> On 04/02/2012 07:57 AM, Oskari Saarenmaa wrote:
>> On 02/04/12 17:22, Chase Douglas wrote:
>>> On 04/01/2012 11:30 AM, Oskari Saarenmaa wrote:
>>>> On-pad clicks in absolute positioning single-finger mode are reported
>>>> without the PHY_BTN bit set, the on-pad clicks are handled by userspace
>>>> so the kernel shouldn't report them as real clicks.
>>>
>>> What is the definition of an "on-pad" click?
>>
>> In this case it's a tap on the pad without actually clicking it. The
>> Asus UX21 Zenbook has a touchpad that can be tapped or clicked.
>> Single-finger taps on it are reported by the touchpad with FSP_PB0_LBTN
>> flag set and FSP_PB0_PHY_BTN not set.
>
> So if I understand correctly, the device currently emits a "physical"
> left button click event when the clickpad is tapped. Your patch will
> prevent this event from being sent to userspace, since userspace does
> its own tap detection. Is that correct?
Yes. Without this patch there's no way to disable click-on-tap in
userspace.
/ Oskari
next prev parent reply other threads:[~2012-04-02 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 18:30 [PATCH] Input: sentelic - filter on-pad clicks in absolute mode Oskari Saarenmaa
2012-04-02 14:22 ` Chase Douglas
2012-04-02 14:57 ` Oskari Saarenmaa
2012-04-02 15:05 ` Chase Douglas
2012-04-02 15:37 ` Oskari Saarenmaa [this message]
2012-04-02 16:04 ` Dmitry Torokhov
2012-04-02 16:06 ` Tai-hwa Liang
2012-04-02 16:35 ` Chase Douglas
2012-04-03 6:59 ` [PATCHv2] Input: sentelic - filter taps " Oskari Saarenmaa
2012-04-03 16:46 ` 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=4F79C7A0.6060601@ohmu.fi \
--to=os@ohmu.fi \
--cc=avatar@sentelic.com \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.