From: Rafi Rubin <rafi@seas.upenn.edu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, micki@n-trig.com,
dmitry.torokhov@gmail.com, chatty@enac.fr
Subject: Re: [PATCH 1/2] Emit TOUCH with DOUBLETAP for single touch
Date: Tue, 13 Apr 2010 16:01:26 -0400 [thread overview]
Message-ID: <4BC4CD96.3050806@seas.upenn.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.1004131526300.8345@pobox.suse.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jiri Kosina wrote:
> On Fri, 9 Apr 2010, Rafi Rubin wrote:
>
>> Signed-off-by: Rafi Rubin <rafi@seas.upenn.edu>
>> ---
>>
>> I squelched TipSwitch in a recent patch which resulted in the loss
>> of Touch events for single touch firmwares. This patch just puts Touch back
>> in for single touch, and bundles it with DoubleTap (like the multitouch code).
>> The two events are used to convey the same message to different drivers.
>
> Thanks Rafi. This should probably still be .34 material, right?
Yes, this fix became more necessary with the previous Touch patch, which
squelched the tipswitch event on behalf of the multi touch firmwares. So it
would be nice to keep them relatively close together.
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkvEzZYACgkQwuRiAT9o60/PaACgmzf/cLF+vyms9JZcR9zZab04
mNsAoPXBPJjFmXdnhITd6NEMf9qjdyR5
=stpn
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-04-13 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 21:58 [PATCH 1/2] Emit TOUCH with DOUBLETAP for single touch Rafi Rubin
2010-04-09 21:58 ` [PATCH 2/2] Use TIPSWITCH for TOUCH Rafi Rubin
2010-04-13 13:31 ` Jiri Kosina
2010-04-13 20:04 ` Rafi Rubin
2010-04-14 5:04 ` [PATCH] Use TipSwitch for Touch Rafi Rubin
2010-04-14 6:32 ` Dmitry Torokhov
2010-04-14 7:51 ` Rafi Rubin
2010-04-14 8:07 ` Stéphane Chatty
2010-04-14 8:15 ` Mohamed Ikbel Boulabiar
2010-04-13 13:27 ` [PATCH 1/2] Emit TOUCH with DOUBLETAP for single touch Jiri Kosina
2010-04-13 20:01 ` Rafi Rubin [this message]
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=4BC4CD96.3050806@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=micki@n-trig.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 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.