linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: haarp <main.haarp@googlemail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] psmouse: Expose drift duration for IBM trackpoints
Date: Wed, 17 Dec 2014 15:31:58 -0800	[thread overview]
Message-ID: <20141217233158.GB21713@dtor-ws> (raw)
In-Reply-To: <5491B8DB.6070102@gmail.com>

On Wed, Dec 17, 2014 at 06:09:47PM +0100, haarp wrote:
> Hello,
> 
> IBM Trackpoints have a feature to compensate for drift by
> recalibrating themselves periodically. If for 0.5 seconds
> there is no change in position, it uses this as the new zero.
> 
> This happens often when the trackpoint is in fact being used.
> This is frustrating.
> 
> Raising the time solves the problem.
> IBM's Trackpoint Engineering Specifications offer a
> configuration register for this (rstdft1). It just needs to
> be exposed by the driver, as others already are.
> 
> Cheers!
> -Mike
> 
> 
> IBM Trackpoints have a feature to compensate for drift by recalibrating
> themselves periodically. By default, if for 0.5 seconds there is no change in
> position, it's used as the new zero. This duration is too low. Often, the
> calibration happens when the trackpoint is in fact being used.
> 
> IBM's Trackpoint Engineering Specifications show a configuration register that
> allows changing this duration, rstdft1.
> 
> Expose it via sysfs among the other settings.
> 
> Signed-off-by: Mike Murdoch <main.haarp@gmail.com>

Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2014-12-17 23:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 17:09 [PATCH] psmouse: Expose drift duration for IBM trackpoints haarp
2014-12-17 23:31 ` Dmitry Torokhov [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=20141217233158.GB21713@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=main.haarp@googlemail.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 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).