From: Christopher Heiny <cheiny@synaptics.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Christopher Heiny <cheiny@synaptics.com>,
Allie Xiong <axiong@synaptics.com>, Vivian Ly <vly@synaptics.com>,
Daniel Rosenberg <daniel.rosenberg@synaptics.com>,
Alexandra Chin <alexandra.chin@tw.synaptics.com>,
Joerie de Gram <j.de.gram@gmail.com>,
Wolfram Sang <w.sang@pengutronix.de>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Linus Walleij <linus.walleij@stericsson.com>
Subject: [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver
Date: Fri, 18 Jan 2013 17:12:40 -0800 [thread overview]
Message-ID: <1358557965-29065-1-git-send-email-cheiny@synaptics.com> (raw)
This patchset implements changes based on the synaptics-rmi4 branch of
Dmitry's input tree. The base for the patchset is Dmitry's commit
0af25383d395fb5ece54b79d12d06138bf8b9836 from 2012-11-28. It supersedes
our previous patch submission from 2012-12-18.
Overall this patchset implements the following changes with respect to
the Dmitry's 2012-11-28 commit:
* updates to Dmitry's RMI4_CORE structure from his 2012-11-28 patches.
This tries to maintain the same approach as Dmitry's implementation, but
we had to move away from using the bus probe() routine, since it wasn't
possible for that routine to readily determine if it had a struct driver() for
an RMI4 sensor or an RMI4 device. Otherwise, we've stuck close to Dmitry's
work, which has tidied things up nicely.
* We've renamed the structures rmi_function_handler to rmi_function_driver and
rmi_device to rmi_function_dev, mainly because they actually were being treated
as drivers and devices for individual RMI4 functions, and the previous
terminology was somewhat confusing.
* Changed a bunch of bools to u32 to support standard debugfs macros. Moved
almost all the debugfs and sysfs handling out of these files into their own
modules, simplifying the core functionality of the driver. Once the core is
stable, we can look into adding modules to support the debug/control
features.
* Many other bools were changed to u8, per Dmitry's request.
* Trivial - file copyright header is updated to be more in line with the rest
of the files under ./input.
We've broken this patch into 6 parts, as follows:
01 - public header file
02 - core sensor and bus implementation
03 - I2C physical layer driver
04.05 - drivers for individual RMI functions
Hopefully this is the last time we'll have wide-ranging structural changes in
the driver code, and future patchsets can be much smaller and confined to
one or two areas of interest.
Comments and other feedback on this driver are welcomed.
Christopher Heiny and the Synaptics RMI4 driver team
Signed-off-by: Christopher Heiny <cheiny@synaptics.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>
Cc: Linus Walleij <linus.walleij@stericsson.com>
Cc: Joeri de Gram <j.de.gram@gmail.com>
---
next reply other threads:[~2013-01-19 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 1:12 Christopher Heiny [this message]
2013-01-19 1:12 ` [PATCH 01/05] input: RMI4 public header file Christopher Heiny
2013-01-19 1:12 ` [PATCH 02/05] input: RMI4 core files Christopher Heiny
2013-01-19 1:12 ` [PATCH 03/05] input: RMI4 I2C physical layer Christopher Heiny
2013-01-19 1:12 ` [PATCH 04/05] input: RMI4 F01 device control Christopher Heiny
2013-01-31 8:08 ` Dmitry Torokhov
2013-01-31 21:14 ` Christopher Heiny
2013-02-07 23:19 ` Christopher Heiny
2013-01-19 1:12 ` [PATCH 05/05] input: RMI4 F11 2D input Christopher Heiny
2014-02-04 7:56 ` [PATCH 00/05] input: RMI4 Synaptics RMI4 Touchscreen Driver Linus Walleij
2014-02-04 20:20 ` Christopher Heiny
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=1358557965-29065-1-git-send-email-cheiny@synaptics.com \
--to=cheiny@synaptics.com \
--cc=alexandra.chin@tw.synaptics.com \
--cc=axiong@synaptics.com \
--cc=daniel.rosenberg@synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=j.de.gram@gmail.com \
--cc=khali@linux-fr.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=vly@synaptics.com \
--cc=w.sang@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox