From: Chase Douglas <chasedouglas@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
Benjamin Tissoires <benjamin.tissoires@enac.fr>,
Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] HID: multitouch: add support of Atmel multitouch panels
Date: Fri, 23 Dec 2011 10:54:02 -0800 [thread overview]
Message-ID: <4EF4CE4A.1020907@gmail.com> (raw)
In-Reply-To: <1324651260-4067-2-git-send-email-benjamin.tissoires@gmail.com>
On 12/23/2011 06:40 AM, Benjamin Tissoires wrote:
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
> ---
> drivers/hid/Kconfig | 1 +
> drivers/hid/hid-ids.h | 3 +++
> drivers/hid/hid-multitouch.c | 5 +++++
> 3 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
> index 5d6eb4e..e95b07c 100644
> --- a/drivers/hid/Kconfig
> +++ b/drivers/hid/Kconfig
> @@ -335,6 +335,7 @@ config HID_MULTITOUCH
> Say Y here if you have one of the following devices:
> - 3M PCT touch screens
> - ActionStar dual touch panels
> + - Atmel panels
> - Cando dual touch panels
> - Chunghwa panels
> - CVTouch panels
I'm guessing this is different than the Atmel maXTouch chips. If so, can
you figure out a model name so people aren't confused on which driver to
use?
-- Chase
next prev parent reply other threads:[~2011-12-23 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 14:40 [PATCH 0/2] 3M and Atmel for hid-multitouch Benjamin Tissoires
2011-12-23 14:40 ` [PATCH 1/2] HID: multitouch: add support of Atmel multitouch panels Benjamin Tissoires
2011-12-23 18:54 ` Chase Douglas [this message]
2011-12-29 18:26 ` Benjamin Tissoires
2012-01-03 13:09 ` Nick Dyer
2011-12-23 14:41 ` [PATCH 2/2] HID: multitouch: add support for 3M 32" Benjamin Tissoires
2011-12-29 10:16 ` [PATCH 0/2] 3M and Atmel for hid-multitouch Henrik Rydberg
2012-01-02 10:12 ` Jiri Kosina
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=4EF4CE4A.1020907@gmail.com \
--to=chasedouglas@gmail.com \
--cc=benjamin.tissoires@enac.fr \
--cc=benjamin.tissoires@gmail.com \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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
Powered by JetHome