From: "Henrik Rydberg" <rydberg@euromail.se>
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: [RFC v2 01/10] hid: add feature_mapping callback
Date: Fri, 7 Jan 2011 11:18:39 +0100 [thread overview]
Message-ID: <20110107101839.GA2312@polaris.bitmath.org> (raw)
In-Reply-To: <AANLkTi=xdPJP9okhRL8q-0vL5cVPKniAjve6BQHmB=+p@mail.gmail.com>
> >> struct input_dev *input_dev;
> >> int i, j, k;
> >> - int max_report_type = HID_OUTPUT_REPORT;
> >> + int max_report_type = HID_FEATURE_REPORT;
> >
> > Doing it this way conflicts with the HID_QUIRK_SKIP_OUTPUT_REPORTS quirk.
>
>
> Do you agree on this way? (will send the patch in the next version)
>
> @@ -834,11 +842,10 @@ int hidinput_connect(struct hid_device *hid,
> unsigned int force)
> {
> struct hid_report *report;
> struct hid_input *hidinput = NULL;
> struct input_dev *input_dev;
> int i, j, k;
> - int max_report_type = HID_OUTPUT_REPORT;
>
> INIT_LIST_HEAD(&hid->inputs);
>
> if (!force) {
> for (i = 0; i < hid->maxcollection; i++) {
> @@ -851,14 +858,14 @@ int hidinput_connect(struct hid_device *hid,
> unsigned int force)
>
> if (i == hid->maxcollection)
> return -1;
> }
>
> - if (hid->quirks & HID_QUIRK_SKIP_OUTPUT_REPORTS)
> - max_report_type = HID_INPUT_REPORT;
> + for (k = HID_INPUT_REPORT; k <= HID_FEATURE_REPORT; k++)
> + if (hid->quirks & HID_QUIRK_SKIP_OUTPUT_REPORTS)
> + continue;
>
> - for (k = HID_INPUT_REPORT; k <= max_report_type; k++)
> list_for_each_entry(report, &hid->report_enum[k].report_list, list) {
>
> if (!report->maxfield)
> continue;
Perfect.
Thanks,
Henrik
next prev parent reply other threads:[~2011-01-07 10:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 17:27 [RFC v2 0/10] hid-multitouch: a first step towards multitouch unification Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 01/10] hid: add feature_mapping callback Benjamin Tissoires
2011-01-06 16:22 ` Henrik Rydberg
2011-01-07 9:44 ` Benjamin Tissoires
2011-01-07 10:18 ` Henrik Rydberg [this message]
2011-01-07 11:12 ` Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 02/10] hid: set HID_MAX_FIELD at 128 Benjamin Tissoires
2011-01-06 16:28 ` Henrik Rydberg
2011-01-05 17:27 ` [RFC v2 03/10] hid-multitouch: support for PixCir-based panels Benjamin Tissoires
2011-01-06 17:25 ` Henrik Rydberg
2011-01-07 9:38 ` Benjamin Tissoires
2011-01-07 12:23 ` Henrik Rydberg
2011-01-07 15:12 ` Benjamin Tissoires
2011-01-07 15:57 ` Henrik Rydberg
2011-01-07 17:07 ` Benjamin Tissoires
2011-01-07 17:27 ` Henrik Rydberg
2011-01-07 17:31 ` Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 04/10] hid-multitouch: migrated support for Cando panels Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 05/10] hid-multitouch: Add support for Cando 10.1" panels Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 06/10] hid-multitouch: added support for Cypress TrueTouch panels Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 07/10] hid-multitouch: migrated support for MosArt panels Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 08/10] hid-multitouch: migrated support for Quanta dual-touch panels Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 09/10] hid-mulitouch: added support for the 'Sensing Win7-TwoFinger' Benjamin Tissoires
2011-01-05 17:27 ` [RFC v2 10/10] hid-multitouch: migrated support for Stantum panels Benjamin Tissoires
2011-01-05 17:49 ` [RFC v2 0/10] hid-multitouch: a first step towards multitouch unification Henrik Rydberg
2011-01-06 15:08 ` Benjamin Tissoires
2011-01-06 15:11 ` Jiri Kosina
2011-01-06 16:04 ` Henrik Rydberg
2011-01-06 16:08 ` Benjamin Tissoires
2011-01-06 17:28 ` Henrik Rydberg
2011-01-06 23:26 ` Jiri Kosina
2011-01-07 1:14 ` Dmitry Torokhov
2011-01-07 9:41 ` Jiri Kosina
2011-01-07 9:48 ` Benjamin Tissoires
2011-01-07 10:03 ` 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=20110107101839.GA2312@polaris.bitmath.org \
--to=rydberg@euromail.se \
--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