linux-kernel - Re: Proposal for synaptics driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hhbgryxbl.wl%tiwai@suse.de>
Date:	Tue, 12 Oct 2010 22:23:42 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Chase Douglas <chase.douglas@...onical.com>
Cc:	Chris Bagwell <chris@...bagwell.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Henrik Rydberg <rydberg@...math.org>,
	Peter Hutterer <peter.hutterer@...-t.net>,
	linux-input <linux-input@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Proposal for synaptics driver

At Tue, 12 Oct 2010 16:11:36 -0400,
Chase Douglas wrote:
> 
> On Tue, 2010-10-12 at 13:41 -0500, Chris Bagwell wrote:
> > On Tue, Oct 12, 2010 at 11:23 AM, Chase Douglas
> > <chase.douglas@...onical.com> wrote:
> > > Hi all,
> > >
> > > There's been many patches and discussions on the synaptics MT work, so I
> > > wanted to gather thoughts into one thread to push things forward.
> > >
> > > First, I want to note something that I think has been overlooked. We've
> > > been talking about "ClickPad" devices quite a bit. One can find the
> > > product page for these devices at:
> > >
> > > http://www.synaptics.com/solutions/products/clickpad
> > >
> > > As a brief overview, ClickPads are an MT surface where the entire
> > > surface clicks. The click may be uniform over the touchpad, or it may be
> > > hinged on one of the edges. It appears that Takashi has figured out the
> > > appropriate bits in the extended capabilities flags to recognized a
> > > ClickPad. I can't confirm this, but it sounds like the device emits a
> > > middle mouse button click when the touchpad is depressed.
> > >
> > > Here's the confusing part: Synaptics has a different series of touchpads
> > > where only certain regions of the touchpad click. This is the case on my
> > > Dell Mini 1012. Unfortunately, I can't find any documentation for these
> > > touchpads on Synaptics' website. As another brief overview, my touchpad
> > > has two buttons integrated into the bottom ~20% of the touchpad. The
> > > left half of the button area clicks separately from the right half, and
> > > the device emits left and right buttons as appropriate. The rest of the
> > > touchpad is stationary and does not click. If no one has a better name
> > > for these touchpads, I'll refer to them as "integrated buttons"
> > > touchpads. Also unfortunately, I don't know which cap bits inform us of
> > > an integrated buttons touchpad, though I have suspicions it's bit
> > > 0x200000 of the 0c extended caps mask.
> > 
> > Ahh, that clears some things up to me.  Based on Takashi's
> > xf86-input-synaptic patches, it seems the click area is still in this
> > ~20% range even for clickpads.
> 
> Hmm, based on the synaptics product page I figured the click area of a
> ClickPad would be the entire surface. Takashi, do you have any input
> here? Maybe the ClickPad devices people have been using is of the hinged
> type, where it's easier to click on the bottom of the pad instead of the
> top?

(Just a few points as I was explicitly asked :)

There are actually two types of Clickpad devices.  The "ClickZone" one
has a hinge on the top, thus you can't click at the top, more easily at
the bottom position.  More importantly, button areas are drawn on the
touchpad, thus it's supposed to push these areas.


> > It sounds like the main difference
> > between clickpad's and "integrated button" touchpads is clickpads have
> > a way of reporting X/Y events in that click area *without* declaring
> > button press.
> 
> On my touchpad, the "embedded buttons" (what I'm calling "integrated
> buttons" now due to the name clash with the bcm5974 semantics) are touch
> sensitive, so the device still reports X/Y events no matter whether the
> button is depressed or not..

Right, it is the merit of clickpad after all: you'll have a larger area
for touching.  Thus, sensing in the button area is somewhat a required
feature.  So does my patch [PATCH 07/18] Allow touching in clickpad
button area.


(It's late here, and I'll follow up more tomorrow...)


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/