From: "Henrik Rydberg" <rydberg@bitmath.org>
To: Benjamin Tissoires <benjamin.tissoires@enac.fr>
Cc: Stephane Chatty <chatty@enac.fr>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid-multitouch: changes from the review process
Date: Tue, 11 Jan 2011 14:11:54 +0100 [thread overview]
Message-ID: <20110111131154.GC1961@polaris.bitmath.org> (raw)
In-Reply-To: <1294743194-2310-1-git-send-email-benjamin.tissoires@enac.fr>
Hi Benjamin,
seems we are cloing in now, although there is still an outstanding
issue with the setting of curvalid, as replied in your previous
mail. Some comments on this patch, too.
> struct mt_class mt_classes[] = {
> - { 0, 0, 0, 10 }, /* MT_CLS_DEFAULT */
> - { MT_QUIRK_SLOT_IS_CONTACTID, 0, 0, 2 }, /* MT_CLS_DUAL1 */
> - { MT_QUIRK_SLOT_IS_CONTACTNUMBER, 0, 0, 10 }, /* MT_CLS_DUAL2 */
> - { MT_QUIRK_CYPRESS | MT_QUIRK_NOT_SEEN_MEANS_UP, 0, 0, 10 }, /* MT_CLS_CYPRESS */
> + { .name = MT_CLS_DEFAULT,
> + .quirks = 0,
Please do not zero-initialize.
> + .sn_move = 0,
> + .sn_pressure = 0,
> + .maxcontacts = 10 },
> + { .name = MT_CLS_DUAL1,
> + .quirks = MT_QUIRK_SLOT_IS_CONTACTID,
> + .sn_move = 0,
> + .sn_pressure = 0,
> + .maxcontacts = 2 },
> + { .name = MT_CLS_DUAL2,
> + .quirks = MT_QUIRK_SLOT_IS_CONTACTNUMBER,
> + .sn_move = 0,
> + .sn_pressure = 0,
> + .maxcontacts = 2 },
> + { .name = MT_CLS_CYPRESS,
> + .quirks = MT_QUIRK_CYPRESS,
> + .sn_move = 0,
> + .sn_pressure = 0,
> + .maxcontacts = 10 },
> +
> + { }
> };
So no device is marked as NOT_SEEN_MEANS_UP, although allegedly some devices should...
> @@ -282,11 +297,10 @@ static void mt_emit_event(struct mt_device *td, struct input_dev *input)
>
> for (i = 0; i < td->mtclass->maxcontacts; ++i) {
> struct mt_slot *s = &(td->slots[i]);
> - if ((td->mtclass->quirks & MT_QUIRK_NOT_SEEN_MEANS_UP) &&
> - !s->seen_in_this_frame) {
> + if (!s->seen_in_this_frame) {
> /*
> - * this slot does not contain useful data,
> - * notify its closure
> + * FixMe: use MT_QUIRK_NOT_SEEN_MEANS_UP here.
> + * This requires to change the curvalid logic.
> */
> s->touch_state = false;
> }
If we were to push this broken behavior, simply to avoid changing the
currently tested code, we would only push the problem of testing onto
the next cycle, with a larger risk of introducing regressions. I
really think we need to sort this out now.
> @@ -392,9 +407,16 @@ static void mt_set_input_mode(struct hid_device *hdev)
>
> static int mt_probe(struct hid_device *hdev, const struct hid_device_id *id)
> {
> - int ret;
> + int ret, i;
> struct mt_device *td;
> - struct mt_class *mtclass = mt_classes + id->driver_data;
> + struct mt_class *mtclass = mt_classes; /* MT_CLS_DEFAULT */
> +
> + for (i = 0; mt_classes[i].name ; i++) {
> + if (id->driver_data == mt_classes[i].name) {
> + mtclass = &(mt_classes[i]);
> + break;
> + }
> + }
Nice.
Thanks,
Henrik
next prev parent reply other threads:[~2011-01-11 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 10:53 [PATCH] hid-multitouch: changes from the review process Benjamin Tissoires
2011-01-11 13:11 ` Henrik Rydberg [this message]
2011-01-11 14:00 ` Benjamin Tissoires
2011-01-11 15:07 ` Benjamin Tissoires
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=20110111131154.GC1961@polaris.bitmath.org \
--to=rydberg@bitmath.org \
--cc=benjamin.tissoires@enac.fr \
--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).