linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bogdan George Stefan <bogdan.george.stefan@gmail.com>
Cc: Bogdan George Stefan <bogdan.g.stefan@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Purdila Octavian <octavian.purdila@intel.com>
Subject: Re: [PATCH v2] Input: Add generic driver for Zeitec touchscreens
Date: Thu, 11 Jun 2015 17:45:18 -0700	[thread overview]
Message-ID: <20150612004518.GE20581@dtor-pixel> (raw)
In-Reply-To: <CAEm+DGVPNqWQOP_Tu4ae=pua6N5nC0Q+TkUCDB8tKzaX43iYNw@mail.gmail.com>

Hi Bogdan,

On Tue, Jun 02, 2015 at 10:43:01AM +0300, Bogdan George Stefan wrote:
> Dimitry,
> 
> I know 0xB2 should provide that information according to the
> datasheet, however here is what Zeitec guys had to say when I asked
> them why it does not work:
> 
> "0xB2 is deprecated.
> It only supports in Zet6221/31 serious but zet9172/zet6273."
> 
> If you like, I can attach my conversation with them.
>

Not really, but I would like to understand how the part selection works.
Are they the same parts or different parts? Let's say you want to build
a system and you want part that reports up to 7 contacts. How do you
communicate this to the supplier? The number of contacts - is it
controller by the config file you load into the controller, or they have
separate parts for different contact count or what?

Thanks.

-- 
Dmitry

  reply	other threads:[~2015-06-12  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 12:22 [PATCH v2] Input: Add generic driver for Zeitec touchscreens Bogdan George Stefan
2015-05-30  0:14 ` Dmitry Torokhov
2015-06-02  7:43   ` Bogdan George Stefan
2015-06-12  0:45     ` Dmitry Torokhov [this message]
2015-06-18  8:39       ` Bogdan George Stefan
2015-07-29 11:55         ` Bogdan George Stefan

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=20150612004518.GE20581@dtor-pixel \
    --to=dmitry.torokhov@gmail.com \
    --cc=bogdan.g.stefan@intel.com \
    --cc=bogdan.george.stefan@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=octavian.purdila@intel.com \
    --cc=rafael.j.wysocki@intel.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).