linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benson Leung <bleung@chromium.org>
To: Scott <scott.liu@emc.com.tw>
Cc: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"Charles Mooney" <charliemooney@google.com>,
	"Jeff.Chuang" <Jeff.chuang@emc.com.tw>,
	梁博翔 <paul.liang@emc.com.tw>, "Duson Lin" <dusonlin@emc.com.tw>
Subject: Re: Elan TS driver patch
Date: Mon, 13 Oct 2014 11:47:21 -0700	[thread overview]
Message-ID: <CANLzEktRicHTvAbDWe6E73EUdknJQT8TmTeHtmK=kUz46HPFtA@mail.gmail.com> (raw)
In-Reply-To: <24A1508F-93CB-4139-BF22-4BD7A118E005@emc.com.tw>

Hi Scott,

On Sun, Oct 12, 2014 at 8:22 AM, Scott <scott.liu@emc.com.tw> wrote:
>         I would call this driver name as “Elan Large-Size Touchscreen”.
>         We (Elan) have two types of TS series internally, Large-size( > 10” ~ 20") and small-size ( <= 10”)
>         and this driver patch is for large size. thanks.

While this may be an accurate description of the touchscreen family,
Dmitry is looking for a part number that can identify the class of
devices. For example, Duson identified the touchpad part as "eKTH3000"

Is there a similar part number for the large size touchscreen?

-- 
Benson Leung
Software Engineer, Chrom* OS
bleung@chromium.org
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-10-13 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 11:27 Elan TS driver patch ELAN 劉嘉駿
2014-10-07 16:03 ` Dmitry Torokhov
2014-10-08  1:06   ` ELAN 劉嘉駿
2014-10-10 22:11     ` 'Dmitry Torokhov'
2014-10-12 15:22       ` Scott
2014-10-13 18:47         ` Benson Leung [this message]
2014-10-14  2:30           ` ELAN 劉嘉駿
2014-10-14  6:16             ` '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='CANLzEktRicHTvAbDWe6E73EUdknJQT8TmTeHtmK=kUz46HPFtA@mail.gmail.com' \
    --to=bleung@chromium.org \
    --cc=Jeff.chuang@emc.com.tw \
    --cc=charliemooney@google.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dusonlin@emc.com.tw \
    --cc=linux-input@vger.kernel.org \
    --cc=paul.liang@emc.com.tw \
    --cc=scott.liu@emc.com.tw \
    /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).