From: Sean Young <sean@mess.org>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-input@vger.kernel.org, linux-media@vger.kernel.org
Subject: [PATCH 0/3] Improve CEC autorepeat handling
Date: Fri, 24 Nov 2017 11:43:58 +0000 [thread overview]
Message-ID: <cover.1511523174.git.sean@mess.org> (raw)
Due to the slowness of the CEC bus, autorepeat handling rather special
on CEC. If the repeated user control pressed message is received, a
keydown repeat should be sent immediately.
By handling this in the input layer, we can remove some ugly code from
cec, which also sends a keyup event after the first keydown, to prevent
autorepeat.
Sean Young (3):
input: remove redundant check for EV_REP
input: handle case whether first repeated key triggers repeat
media: cec: move cec autorepeat handling to rc-core
Documentation/input/input.rst | 4 +++-
drivers/input/input.c | 21 ++++++++++++----
drivers/media/cec/cec-adap.c | 56 ++++---------------------------------------
drivers/media/cec/cec-core.c | 12 ----------
drivers/media/rc/rc-main.c | 10 +++++++-
include/media/cec.h | 5 ----
6 files changed, 33 insertions(+), 75 deletions(-)
--
2.14.3
next reply other threads:[~2017-11-24 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 11:43 Sean Young [this message]
2017-11-24 11:43 ` [PATCH 1/3] input: remove redundant check for EV_REP Sean Young
2017-11-24 11:44 ` [PATCH 2/3] input: handle case whether first repeated key triggers repeat Sean Young
2017-11-24 11:44 ` [PATCH 3/3] media: cec: move cec autorepeat handling to rc-core Sean Young
2017-11-25 23:47 ` [PATCH 0/3] Improve CEC autorepeat handling Dmitry Torokhov
2017-11-27 9:13 ` Hans Verkuil
2017-11-27 9:47 ` Sean Young
2017-11-27 10:01 ` Hans Verkuil
2017-11-27 10:11 ` Dmitry Torokhov
2017-11-27 15:43 ` Hans Verkuil
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=cover.1511523174.git.sean@mess.org \
--to=sean@mess.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).