From: Johannes Stezenbach <js@linuxtv.org>
To: dtor_core@ameritech.net
Cc: Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
mchehab@infradead.org, linux-dvb-maintainer@linuxtv.org,
Oliver Endriss <o.endriss@gmx.de>
Subject: Re: [PATCH 29/56] DVB (2390) Adds a time-delay to IR remote button presses for av7110 ir input,
Date: Fri, 9 Dec 2005 18:24:59 +0100 [thread overview]
Message-ID: <20051209172459.GA11025@linuxtv.org> (raw)
In-Reply-To: <d120d5000512090722yb975ccah1eef0cde73ca7e88@mail.gmail.com>
On Fri, Dec 09, 2005, Dmitry Torokhov wrote:
> On 12/9/05, Mauro Carvalho Chehab <mchehab@brturbo.com.br> wrote:
> > static void input_repeat_key(unsigned long data)
> > {
> > - /* dummy routine to disable autorepeat in the input driver */
> > + /* called by the input driver after rep[REP_DELAY] ms */
> > + delay_timer_finished = 1;
> > }
>
> I always wondered why many IR drivers re-implement autorepeat code
> instead of using autorepeat in the inptu core. Is it because of forced
> (by timer) keyup events?
Remote controls don't generate key-up events (think what would
happen if you press a button and then someone walks in between
while you release the key). Instead they generate key-down
and repeated key-still-down events. The repeat rate generated
by remote controls varies roughly between 100...300 msecs and
even depends on battery level for many remotes.
If you use a timer to simulate key-up after you received no
key-still-down for some time, and use input core autorepeat,
then you get this annoying effect that input core generates
key repeats after you released the key on the remote control.
Johannes
next prev parent reply other threads:[~2005-12-09 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 14:16 [PATCH 29/56] DVB (2390) Adds a time-delay to IR remote button presses for av7110 ir input, Mauro Carvalho Chehab
2005-12-09 15:22 ` Dmitry Torokhov
2005-12-09 17:24 ` Johannes Stezenbach [this message]
2005-12-09 19:24 ` Andrew Morton
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=20051209172459.GA11025@linuxtv.org \
--to=js@linuxtv.org \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=mchehab@infradead.org \
--cc=o.endriss@gmx.de \
/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.