From: Che-Liang Chiou <clchiou@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org,
Che-Liang Chiou <clchiou@chromium.org>
Subject: [PATCH 0/5] Input: serio_raw - add monitor/replay debugging interface
Date: Wed, 8 Feb 2012 11:24:52 +0800 [thread overview]
Message-ID: <1328671497-20880-1-git-send-email-clchiou@chromium.org> (raw)
In-Reply-To: <1328084386-31110-1-git-send-email-clchiou@chromium.org>
The serio_raw driver is designed to provide "raw access" to mice, keyboards
etc; thus, a driver accessing serio_raw may live entirely in userland.
However, serio_raw lacks testability. It is practically impossible to do
regression tests on changes to a serio_raw -based userland driver. On the other
hand, the kernel's input subsystem has good testability support. With the help
of tools like utouch-evemu, we may capture and replay input events for evdev
drivers in regression tests.
This patchset contains extensions to the serio_raw driver which add debugfs
entries for monitoring and replaying byte sequence between a userland driver
and device. These byte sequences can be used in regression tests of the
userland driver. This patchset closes the gap between serio_raw and the input
subsystem regarding testability.
This patchset is successfully applied on kernel version 3.3-rc2.
Che-Liang Chiou (5):
Input: serio_raw - return proper result when serio_raw_read fails
Input: serio_raw - extract queue interface
Input: serio_raw - factor out common pattern of write
Input: serio_raw - add debugfs interface
Input: serio_raw - implement debugfs interface
drivers/input/serio/serio_raw.c | 394 +++++++++++++++++++++++++++++++++------
1 files changed, 337 insertions(+), 57 deletions(-)
--
1.7.7.3
next prev parent reply other threads:[~2012-02-08 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 8:19 [PATCH] Input: serio_raw - return proper result when serio_raw_read fails Che-Liang Chiou
2012-02-08 3:24 ` Che-Liang Chiou [this message]
2012-02-14 3:18 ` [PATCH 0/5] Input: serio_raw - add monitor/replay debugging interface Daniel Kurtz
2012-04-21 6:21 ` Dmitry Torokhov
2012-05-28 9:41 ` Che-liang Chiou
2012-02-08 3:24 ` [PATCH 1/5] Input: serio_raw - return proper result when serio_raw_read fails Che-Liang Chiou
2012-02-08 3:24 ` [PATCH 2/5] Input: serio_raw - extract queue interface Che-Liang Chiou
2012-02-08 3:24 ` [PATCH 3/5] Input: serio_raw - factor out common pattern of write Che-Liang Chiou
2012-02-08 3:24 ` [PATCH 4/5] Input: serio_raw - add debugfs interface Che-Liang Chiou
2012-02-08 3:24 ` [PATCH 5/5] Input: serio_raw - implement " Che-Liang Chiou
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=1328671497-20880-1-git-send-email-clchiou@chromium.org \
--to=clchiou@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).