From: Iiro Valkonen <iiro.valkonen@atmel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: kyungmin.park@samsung.com, jy0922.shim@samsung.com,
linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Add Atmel maXTouch touchscreen driver
Date: Wed, 17 Nov 2010 12:41:40 +0200 [thread overview]
Message-ID: <4CE3B164.9070607@atmel.com> (raw)
In-Reply-To: <20101112201001.GE1299@core.coreip.homeip.net>
On 11/12/2010 10:10 PM, Dmitry Torokhov wrote:
> Hi Iiro,
>
> I believe there is already a driver for this hardware in the tree
> (qt602240.c). Could you tell me what additional features your driver
> implements and why can't they be added to the existing driver.
>
Hi Dmitry,
the current driver is written for one maXTouch chip, mXT224. The driver that I submitted will support all current maXTouch chips, and it is built to be future-proof so it should work with yet to be released chips too, with minor or no changes. This shows in the naming too, part name "qt602240" is deprecated and it shouldn't be used. As the driver should work with all chips in the maXTouch family, a more generic naming convention in the driver name itself and all the code inside the driver would be more appropriate.
Atmel would like to be the maintainer of this driver, and it would be easiest if we could use the code I submitted. Of course we would be happy to implement any improvements like the threaded IRQs.
Best Regards,
--
Iiro Valkonen
Application Engineer / Atmel Corporation
Tel: +358(9)45208250 / Mobile: +358(40)5820012
iiro.valkonen@atmel.com / www.atmel.com
next prev parent reply other threads:[~2010-11-17 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 14:14 [PATCH] input: Add Atmel maXTouch touchscreen driver Iiro Valkonen
2010-11-12 20:10 ` Dmitry Torokhov
2010-11-17 10:41 ` Iiro Valkonen [this message]
2010-11-17 14:04 ` Murphy, Dan
2010-11-17 18:23 ` Dmitry Torokhov
[not found] <4CE2F692.8040403@atmel.com>
2010-11-16 22:05 ` 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=4CE3B164.9070607@atmel.com \
--to=iiro.valkonen@atmel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.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).