From: Alexandra Chin <alexandra.chin@tw.synaptics.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Linus Walleij <linus.walleij@stericsson.com>,
Naveen Kumar Gaddipati <naveen.gaddipati@stericsson.com>,
Mahesh Srinivasan <msrinivasan@synaptics.com>,
Alex Chang <alex.chang@tw.synaptics.com>,
Scott Lin <scott.lin@tw.synaptics.com>,
Christopher Heiny <Cheiny@synaptics.com>
Subject: RE: [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices
Date: Thu, 4 Oct 2012 05:52:45 +0000 [thread overview]
Message-ID: <CC51EC7B5B7F984AA566DC102237848896F593FA@hkdcw-mail1.synaptics-inc.local> (raw)
In-Reply-To: <20121003180121.GA4198@polaris.bitmath.org>
From: Henrik Rydberg
Sent: Thursday, October 04, 2012 2:01 AM
> It seems this driver is already present in staging. Comments and
> formatting have been improved in the staging version, but that aside,
> the two versions look very similar. Why don't you submit fixes to
> that driver instead?
> On a general note, both versions of the driver use MT-A. Please
> convert to MT-B, using the in-kernel tracking if necessary.
Hi Henrik,
Appreciate your suggestion!
We are going to update a patch of using MT-B, because Synaptics devices are
capable of tracking identifiable contacts (type B).
Thanks for pointing out this.
You are right, there is already a synaptics_i2c_rmi4 driver in staging
state (drivers/staging/ste_rmi4).
Actually synaptics_ds4_i2c driver is developed based on synaptics_i2c_rmi4
driver. The point is that we would want to make a clear definition that
synaptics_ds4_i2c only targets to DS4 family, so that we can keep maintaining
driver focusing on DS4 product line (not all Synaptics touchscreen devices are
DS4 compatible).
We are open to discuss if it is appropriate to retained DS4 driver, and please
let us know if you have any concerns.
Best Regards,
Alexandra Chin
next prev parent reply other threads:[~2012-10-04 5:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 3:30 [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices Alexandra Chin
2012-10-03 18:01 ` Henrik Rydberg
2012-10-04 5:52 ` Alexandra Chin [this message]
2012-10-04 6:51 ` Dmitry Torokhov
2012-10-05 9:44 ` Alexandra Chin
2012-10-31 9:17 ` [PATCH] staging: ste_rmi4: Convert to Type-B support Alexandra Chin
2012-10-31 18:43 ` Henrik Rydberg
2012-11-01 3:14 ` Alexandra Chin
-- strict thread matches above, loose matches on Subject: below --
2012-10-02 7:50 [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices Alexandra Chin
2012-09-16 9:56 Alexandra Chin
2012-09-16 22:33 ` Linus Walleij
2012-09-19 21:57 ` 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=CC51EC7B5B7F984AA566DC102237848896F593FA@hkdcw-mail1.synaptics-inc.local \
--to=alexandra.chin@tw.synaptics.com \
--cc=Cheiny@synaptics.com \
--cc=alex.chang@tw.synaptics.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msrinivasan@synaptics.com \
--cc=naveen.gaddipati@stericsson.com \
--cc=rydberg@euromail.se \
--cc=scott.lin@tw.synaptics.com \
/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).