linux-kernel - Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support

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]

Date:	Sun, 10 Oct 2010 13:59:32 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Chase Douglas <chase.douglas@...onical.com>,
	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support

On Sun, Oct 10, 2010 at 09:49:45AM +0200, Henrik Rydberg wrote:
> Takashi, Chase,
> 
> talk about Heinz effect. :-)
> 
> Rather than taking any of the patches, I was wondering if we could get a single
> patch including all the later findings and considerations on what devices should
> have the multitouch mode. Also, unless there is a really really good reason for
> it, without kernel parameters. After all, these patches should only add new
> functionality without regressions.

Yes, I think we should limit number of module options (and even more so
Kconfig options). I believe that either MT support is ready for prime-time
and then it should be enabled unconditionally, or it is not ready and
should be kept as patches. his also means that we should not introduce
regressions in ST (even when emulated in MT mode).

> 
> Regarding the clickpad functionality, it is similar to the macbook pads with
> integrated buttons, which has been implemented in userspace.

Right now we map the "click" to BTN_LEFT leaving it to the synaptics X
driver to work our the "click zone" support.

> 
> Regarding the tracking aspect of pointer emulation, Chase is completely right,
> and this is a generic problem for several drivers. Tracking a single point by
> picking the closest contact is a linear problem and could easily be performed in
> interrupt context. I suggest we add it directly to the synaptics driver and then
> revisit the question of adding generic tracking support to the kernel. Dmitry,
> how does that sound to you?

Sounds good to me. Hopefully it could be made it a library[ish] function
that several MT drivers could use to produce ST-compliant events.

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