public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Daiker <jdaiker@osdl.org>
To: Marko Macek <Marko.Macek@gmx.net>
Cc: vojtech@suse.cz, thoffman@arnor.net, vanackere@lif.univ-mrs.fr,
	linux-kernel@vger.kernel.org
Subject: Re: USB input ati_remote autorepeat problem
Date: Tue, 27 Jun 2006 13:09:12 -0700	[thread overview]
Message-ID: <44A19068.9060904@osdl.org> (raw)
In-Reply-To: <44A18C38.7040504@gmx.net>

I have also experience this problem with the ati_remote driver, but 
didn't know the fix.  If I am correct, the HZ always used to default to 
1000HZ, but not it is configurable in the kernel as 1000HZ, 250HZ, or 
100HZ.  By my calculations, the FILTER_TIME will be at most 20% longer 
than before, but as little as 2% bigger.

        HZ       Old        New        % Difference
       100       5          6          20%
       250       12.5       13.5       8%
      1000       50         51         2%

Those are my calculations based on your previously stated definitions.  
The FILTER_TIME const is only used 1 time in ati_remote.c, so I doubt 
there would be a problem redefining it.  Would a redefinition to 50 be 
more appropriate (so keep the repeat delay the same across all platforms)?

Tonight I will recompile and test the driver with the 2 new definitions 
and report on my findings.

John



Marko Macek 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.
>
>    Mark
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2006-06-27 20:09 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 [this message]
2006-06-27 21:46 ` Nish Aravamudan
2006-06-28  6:52   ` Vojtech Pavlik
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=44A19068.9060904@osdl.org \
    --to=jdaiker@osdl.org \
    --cc=Marko.Macek@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thoffman@arnor.net \
    --cc=vanackere@lif.univ-mrs.fr \
    --cc=vojtech@suse.cz \
    /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