From: Seth Forshee <seth.forshee@canonical.com>
To: George Pantalos <gpantalos@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: ALPS v4 Semi-mt Support
Date: Tue, 17 Apr 2012 10:22:36 -0500 [thread overview]
Message-ID: <20120417152236.GD14091@thinkpad-t410> (raw)
In-Reply-To: <1708752.SgOWjWFNqk@vaio>
On Tue, Apr 17, 2012 at 03:52:34AM +0300, George Pantalos wrote:
> On Monday 16 of April 2012 16:24:07 Seth Forshee wrote:
> > If the latency really is noticible when you stash the ST points, here's
> > what I'd suggest trying instead. Stash away the last set of MT data you
> > saw and repeat it with each of the next two ST coordinates. I suspect
> > that will probably work well enough, and will allow every ST point to
> > still be reported. And it should significantly simplify the code as
> > well.
>
> I tried your suggestion and I have to say that it works great.
> Thank you, Seth.
> I hope my execution is ok.
The implementation looks good to me. If you're confident that the
interpretation of the sync is correct, submit the patch according to the
guidelines in Documentation/SubmittingPatches and I'll be happy to give
my ack.
Seth
next prev parent reply other threads:[~2012-04-17 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 14:02 ALPS v4 Semi-mt Support George Pantalos
2012-04-10 15:21 ` Seth Forshee
2012-04-10 21:59 ` Seth Forshee
2012-04-16 14:24 ` George Pantalos
2012-04-16 21:24 ` Seth Forshee
2012-04-16 22:21 ` George Pantalos
2012-04-17 13:16 ` Seth Forshee
2012-04-17 0:52 ` George Pantalos
2012-04-17 15:22 ` Seth Forshee [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 14:01 George Pantalos
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=20120417152236.GD14091@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=gpantalos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).