From: Paul Fox <pgf@laptop.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dsaxena@laptop.org, Andres Salomon <dilinger@collabora.co.uk>
Subject: Re: [PATCH] forced recalibration for the OLPC hgpk touchpad
Date: Wed, 17 Jun 2009 16:16:11 -0400 [thread overview]
Message-ID: <31138.1245269771@foxharp.boston.ma.us> (raw)
In-Reply-To: <20090604001740.490f747e@mycelium.queued.net>
hi dmitry --
have you had a chance to think any more about this? i'm open to
suggestions on implementation detail, but i think that a full
reset of the device won't really work, because of the time it
adds to the recalibration.
paul
andres wrote:
> On Wed, 03 Jun 2009 23:58:33 -0400
> Paul Fox <pgf@laptop.org> wrote:
>
> > dmitry wrote:
> > > Hi Paul,
> > >
> > > On Tuesday 02 June 2009 12:47:59 pgf@laptop.org wrote:
> > > > The OLPC XO laptop incorporates a combination touchpad/tablet
> > > > device which unfortunately requires frequent recalibration. The
> > > > driver will force this automatically when various suspicious
> > > > behaviors are observed, and the user can recalibrate manually
> > > > (with a special keyboard sequence). There's currently no way,
> > > > however, for an external program to cause recalibration.
> > > >
> > > > This patch creates a new node in /sys which, when written with
> > > > '1', will force a touchpad recalibration. No other writes (or
> > > > reads) of this node are supported.
> > > >
> > >
> > >
> > > Instead of creating a new sysfs attribute maybe we should make
> > > the touchpad recalibrate upon resume (reconnect)? Userspace can
> > > already request reconnect via sysfs.
> >
> > dmitry -- thanks for the suggestion.
> >
> > i took a look, and tried it. the problem is that doing a full
> > reset of the touchpad takes quite a long time -- 1.1 or 1.2
> > seconds. recalibration deprives the user of their touchpad for
> > long enough as it is -- i don't think we can afford that time.
> > (remember that this is a workaround for bad hardware -- the XO
> > no longer uses this touchpad at least partly due to this very
> > issue, but there are enough in use that we're still trying to
> > improve things.)
> >
>
> I do like the idea of having a sysfs trigger for recalibrations. We've
> never been successful in having the kernel driver handle recalibrations
> seamlessly. Perhaps touchpad hardware screwups would be easier to
> detect in userspace, given a daemon that can keep a history of the last
> N touchpad coordinates?
=---------------------
paul fox, pgf@laptop.org
next prev parent reply other threads:[~2009-06-17 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 19:47 [PATCH] forced recalibration for the OLPC hgpk touchpad pgf
2009-06-03 15:04 ` Dmitry Torokhov
2009-06-04 3:58 ` Paul Fox
2009-06-04 4:17 ` Andres Salomon
2009-06-17 20:16 ` Paul Fox [this message]
2009-07-29 22:08 ` Paul Fox
2009-07-30 5:44 ` Dmitry Torokhov
2009-07-30 14:37 ` Paul Fox
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=31138.1245269771@foxharp.boston.ma.us \
--to=pgf@laptop.org \
--cc=dilinger@collabora.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=dsaxena@laptop.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).