From: Vojtech Pavlik <vojtech@suse.cz>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Marko Macek <Marko.Macek@gmx.net>,
thoffman@arnor.net, vanackere@lif.univ-mrs.fr,
linux-kernel@vger.kernel.org
Subject: Re: USB input ati_remote autorepeat problem
Date: Wed, 28 Jun 2006 08:52:04 +0200 [thread overview]
Message-ID: <20060628065204.GC5546@suse.cz> (raw)
In-Reply-To: <29495f1d0606271446y79ffef0aiffe445ee9e3909cd@mail.gmail.com>
On Tue, Jun 27, 2006 at 02:46:39PM -0700, Nish Aravamudan wrote:
> On 6/27/06, Marko Macek <Marko.Macek@gmx.net> wrote:
> >Hello!
> >
> >I have problems with autorepeat in ati_remote (drivers/usb/input) driver
> >in "recent" kernels: all keys start repeating immediately without some
> >delay.
> >
> >This makes some things, like changing the channel prev/next or toggling
> >fullscreen, etc... impossible/hard.
> >
> >The problem seems to be related to FILTER_TIME and HZ=250 (which I
> >forgot to change).
> >
> >FILTER_TIME is defined to HZ / 20, and since 250 is not divisible by 20,
> >the time will be too short to ignore enough events.
> >
> >Defining FILTER_TIME to HZ / 20 + 1 seems to fix things, but I'm not
> >sure if there are any bad side effects.
>
> Can you try just defining it to msecs_to_jiffies(50)? That should
> handle the various HZ cases just fine.
Indeed, that would be thr right solution. Even better would be to
#define FILTER_TIME 50 /* 50 msec */
and later use
msecs_to_jiffies(FILTER_TIME)
in the code.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2006-06-28 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:51 USB input ati_remote autorepeat problem Marko Macek
2006-06-27 20:09 ` John Daiker
2006-06-27 21:46 ` Nish Aravamudan
2006-06-28 6:52 ` Vojtech Pavlik [this message]
2006-07-02 18:37 ` Marko Macek
2006-07-02 19:18 ` Vojtech Pavlik
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=20060628065204.GC5546@suse.cz \
--to=vojtech@suse.cz \
--cc=Marko.Macek@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=thoffman@arnor.net \
--cc=vanackere@lif.univ-mrs.fr \
/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.