From: Wolfram Sang <w.sang@pengutronix.de>
To: linux-input@vger.kernel.org
Cc: dp@opensource.wolfsonmicro.com,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: [RFC 0/3] Updates to the wm97xx-drivers
Date: Sun, 3 Jul 2011 19:09:27 +0200 [thread overview]
Message-ID: <1309712970-5829-1-git-send-email-w.sang@pengutronix.de> (raw)
I noticed a problem that reading battery status was dependent on the pen_down
status. While trying to solve the problem, I came up with the first two cleanup
patches. The third one then fixes the original itch. The series been tested
with Linux 3.0-rc5 on a Jaytech PID7901 having a WM9715. The code for WM9705
and WM9713 has only been compile tested. Testers are very welcome :)
Thanks,
Wolfram
Wolfram Sang (3):
input: touchscreen: wm97xx: remove redundant define
input: touchscreen: wm97xx: refactor channel selection in poll_sample()
input: touchscreen: wm97xx: mark channels which need pen_down
drivers/input/touchscreen/atmel-wm97xx.c | 2 +-
drivers/input/touchscreen/mainstone-wm97xx.c | 6 ++--
drivers/input/touchscreen/wm9705.c | 25 +++++++++++------------
drivers/input/touchscreen/wm9712.c | 27 +++++++++++++------------
drivers/input/touchscreen/wm9713.c | 25 ++++++++++++-----------
drivers/input/touchscreen/zylonite-wm97xx.c | 6 ++--
include/linux/wm97xx.h | 13 ++++-------
7 files changed, 51 insertions(+), 53 deletions(-)
--
1.7.2.5
next reply other threads:[~2011-07-03 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 17:09 Wolfram Sang [this message]
2011-07-03 17:09 ` [RFC 1/3] input: touchscreen: wm97xx: remove redundant define Wolfram Sang
2011-07-03 17:09 ` [RFC 2/3] input: touchscreen: wm97xx: refactor channel selection in poll_sample() Wolfram Sang
2011-07-03 17:09 ` [RFC 3/3] input: touchscreen: wm97xx: mark channels which need pen_down Wolfram Sang
2011-07-03 20:37 ` [RFC 0/3] Updates to the wm97xx-drivers Mark Brown
2011-07-05 2:33 ` Dmitry Torokhov
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=1309712970-5829-1-git-send-email-w.sang@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=linux-input@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).