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: Mon, 20 Sep 2010 21:48:50 +0200 [thread overview]
Message-ID: <4C97BAA2.6000309@euromail.se> (raw)
In-Reply-To: <FF722ED6-6568-47D0-82D1-99B9E9D5AEAF@enac.fr>
On 09/20/2010 09:43 PM, Stéphane Chatty wrote:
>
> Le 28 août 10 à 16:29, Henrik Rydberg a écrit :
>
>> The Microtouch controller is capable of doing finger tracking on
>> up to 60 fingers. To reduce bandwidth and cpu usage, convert the
>> driver to use the MT slots protocol.
>
> As I understand it, this patch actually has three roles:
> 1. improving the evdev parameters of the device
> 2. cleaning the protocol to get rid of useless MISC/SCANCODE messages
> 3. convert the protocol to MT slots
>
>
>> +#define SN_MOVE 2048
>> +#define SN_WIDTH 128
>>
>
> In the long run, it might be useful to comment these signal/noise constants
>
>
>
>> hid_map_usage(hi, usage, bit, max, EV_KEY, BTN_TOUCH);
>> + input_set_capability(hi->input, EV_KEY, BTN_TOUCH);
>
>> {
>> + /* tell hid-input to skip setup of these event types */
>> if (usage->type == EV_KEY || usage->type == EV_ABS)
>> - clear_bit(usage->code, *bit);
>> -
>> - return 0;
>> + set_bit(usage->type, hi->input->evbit);
>> + return -1;
>> }
>>
>
> I understand this as a trick to get rid of MISC/SCANCODEs that are added for
> every EV_KEY message, consequence of a rule in hid-input.c. Wouldn't it be
> simpler to improve the rule than to work around it?
The main reason is to be able to set the fuzz parameters, which are otherwise
overwritten by hid-input setup.
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
next prev parent reply other threads:[~2010-09-20 19:49 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 [this message]
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
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=4C97BAA2.6000309@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).