linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: "Stéphane Chatty" <chatty@enac.fr>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] hid: 3m: Convert to MT slots
Date: Tue, 21 Sep 2010 19:37:31 +0200	[thread overview]
Message-ID: <4C98ED5B.7020408@euromail.se> (raw)
In-Reply-To: <EBFF8B5B-5361-45B3-88B8-8254E3953578@enac.fr>

On 09/20/2010 10:23 PM, Stéphane Chatty wrote:

> 
> Le 20 sept. 10 à 22:04, Henrik Rydberg a écrit :
>>>
>>> What about this:
>>> +            value = clamp_val(value, 0, MAX_SLOTS - 1);
>>>              if (md->valid) {
>>>                  md->curid = value;
>>>                  md->f[value].touch = md->touch;
>>>
>>> If you had tracking IDs 59, 60 and 61 in the same frame, this would not work
>>> properly would it?
>>
>>
>> That is the slot id being set. The microtouch controller is also using slots
>> internally.
>>
> 
> Oh, right. Once again back to your definition of tracking ID that is not so
> intuitive to me :-) In the end we might end up dealing with three IDs: the
> device's tracking ID, the slot ID, and the Linux tracking ID. Here, the first
> and the second are the same but will they always be? I remember when Stantum
> used to provide us with 16 bit "device tracking IDs"...
> 
> Anyway, I have no more problem with this constant. Just with the vocabulary :-)


In the HID protocol, it is called ContactID... So, Stéphane, are we close to
acking this patch now? :-)

Cheers,
Henrik
--
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:[~2010-09-21 17:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 14:29 [PATCH 1/3] hid: 3m: Adjust to sequential MT HID protocol Henrik Rydberg
2010-08-28 14:29 ` [PATCH 2/3] hid: 3m: Convert to MT slots Henrik Rydberg
2010-09-20 19:43   ` Stéphane Chatty
2010-09-20 19:48     ` Henrik Rydberg
2010-09-20 19:53       ` Stéphane Chatty
2010-09-20 19:46   ` Stéphane Chatty
2010-09-20 19:51     ` Henrik Rydberg
2010-09-20 20:01       ` Stéphane Chatty
2010-09-20 20:04         ` Henrik Rydberg
2010-09-20 20:23           ` Stéphane Chatty
2010-09-21 17:37             ` Henrik Rydberg [this message]
2010-09-21 19:21               ` Stéphane Chatty
2010-09-21 19:34                 ` Henrik Rydberg
2010-09-21 21:24                 ` Jiri Kosina
2010-08-28 14:29 ` [PATCH 3/3] hid: 3m: Correct touchscreen emulation Henrik Rydberg
2010-08-28 15:56   ` Stéphane Chatty
2010-08-28 16:08     ` Henrik Rydberg
2010-08-28 17:07       ` Stéphane Chatty
2010-08-30 13:36         ` Jiri Kosina
2010-09-21 17:00   ` Stéphane Chatty
2010-09-21 17:05     ` Jiri Kosina
2010-09-21 19:20       ` Stéphane Chatty
2010-09-21 21:23         ` Jiri Kosina
2010-09-20 18:21 ` [PATCH 1/3] hid: 3m: Adjust to sequential MT HID protocol Stéphane Chatty
2010-09-21 14: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=4C98ED5B.7020408@euromail.se \
    --to=rydberg@euromail.se \
    --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 \
    /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).