linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] input: input: stop autorepeat timer on key release
Date: Mon, 12 Jan 2009 21:02:36 -0800	[thread overview]
Message-ID: <20090113050236.GA10900@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <1231750263.4809.3.camel@johannes>

On Mon, Jan 12, 2009 at 09:51:03AM +0100, Johannes Berg wrote:
> On Sun, 2009-01-11 at 23:36 -0800, Dmitry Torokhov wrote:
> > Hi Johannes,
> > 
> > On Tue, Jan 06, 2009 at 12:26:24PM +0100, Johannes Berg wrote:
> > > Whenever you press and then release a key, the CPU wakes up
> > > three times:
> > >  * press
> > >  * release
> > >  * autorepeat timer exactly 250ms after press
> > > 
> > > The autorepeat timer has nothing to do, obviously, since you already
> > > have released the key, so stop it on key release.
> > > 
> > 
> > This introduces a slight change in behaviour (the key that is released
> > may not be one that is being autorepeated) but I think it still makes
> > sense to do it.
> 
> Hmm, good point, I thought it didn't, but it does when you press a, b
> wait, release a then b doesn't continue autorepeating. Seems like a
> corner case though, so I agree. We could fix that by checking which key
> is being autorepeated though, I'd think, see below (untested as of now)
> 

I actually think the original change was better - sometimes when shift or
alt or ctrl key gets stuck it takes time to figure out what happened. If
we stop autorepeat upon release of any key it will recover much quicker.

-- 
Dmitry

  reply	other threads:[~2009-01-13  5:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 11:26 [PATCH] input: input: stop autorepeat timer on key release Johannes Berg
2009-01-12  7:36 ` Dmitry Torokhov
2009-01-12  8:51   ` Johannes Berg
2009-01-13  5:02     ` Dmitry Torokhov [this message]
2009-01-13  8:56       ` Johannes Berg

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=20090113050236.GA10900@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=arjan@infradead.org \
    --cc=johannes@sipsolutions.net \
    --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).