From: "Henrik Rydberg" <rydberg@euromail.se>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] HID: input: don't register unmapped input devices
Date: Tue, 19 Mar 2013 22:25:11 +0100 [thread overview]
Message-ID: <20130319212511.GA7821@polaris.bitmath.org> (raw)
In-Reply-To: <1361984127-912-2-git-send-email-benjamin.tissoires@redhat.com>
Hi Benjamin,
> There is no need to register an input device containing no events.
> This allows drivers using the quirk MULTI_INPUT to register one input
> per report effectively used.
>
> For backward compatibility, we need to add a quirk to request
> this behavior.
>
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> ---
> drivers/hid/hid-input.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/hid.h | 1 +
> 2 files changed, 78 insertions(+)
>
> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> index 21b196c..7aaf7d3 100644
> --- a/drivers/hid/hid-input.c
> +++ b/drivers/hid/hid-input.c
> @@ -1198,6 +1198,67 @@ static struct hid_input *hidinput_allocate(struct hid_device *hid)
> return hidinput;
> }
>
> +static bool hidinput_has_been_populated(struct hid_input *hidinput)
> +{
> + int i;
> + bool r = 0;
> +
> + for (i = 0; i < BITS_TO_LONGS(EV_CNT); i++)
> + r = r || hidinput->input->evbit[i];
I believe there is a bit count method that will do this for you (weight).
> +
> + for (i = 0; i < BITS_TO_LONGS(KEY_CNT); i++)
> + r = r || hidinput->input->keybit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(REL_CNT); i++)
> + r = r || hidinput->input->relbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(ABS_CNT); i++)
> + r = r || hidinput->input->absbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(MSC_CNT); i++)
> + r = r || hidinput->input->mscbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(LED_CNT); i++)
> + r = r || hidinput->input->ledbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(SND_CNT); i++)
> + r = r || hidinput->input->sndbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(FF_CNT); i++)
> + r = r || hidinput->input->ffbit[i];
> +
> + for (i = 0; i < BITS_TO_LONGS(SW_CNT); i++)
> + r = r || hidinput->input->swbit[i];
> +
> + return !!r;
> +}
> +
> +static void hidinput_cleanup_hidinput(struct hid_device *hid,
> + struct hid_input *hidinput)
> +{
> + struct hid_report *report;
> + int i, k;
> +
> + list_del(&hidinput->list);
> + input_free_device(hidinput->input);
> +
> + for (k = HID_INPUT_REPORT; k <= HID_OUTPUT_REPORT; k++) {
> + if (k == HID_OUTPUT_REPORT &&
> + hid->quirks & HID_QUIRK_SKIP_OUTPUT_REPORTS)
> + continue;
> +
> + list_for_each_entry(report, &hid->report_enum[k].report_list,
> + list) {
> +
> + for (i = 0; i < report->maxfield; i++)
> + if (report->field[i]->hidinput == hidinput)
> + report->field[i]->hidinput = NULL;
Why test before clearing?
> + }
> + }
> +
> + kfree(hidinput);
> +}
> +
> /*
> * Register the input device; print a message.
> * Configure the input layer interface
> @@ -1249,6 +1310,10 @@ int hidinput_connect(struct hid_device *hid, unsigned int force)
> hidinput_configure_usage(hidinput, report->field[i],
> report->field[i]->usage + j);
>
> + if ((hid->quirks & HID_QUIRK_NO_EMPTY_INPUT) &&
> + !hidinput_has_been_populated(hidinput))
> + continue;
> +
Is there possibly a subset of input properties that may be populated
but still not duplicated? Or the other way around?
> if (hid->quirks & HID_QUIRK_MULTI_INPUT) {
> /* This will leave hidinput NULL, so that it
> * allocates another one if we have more inputs on
> @@ -1265,6 +1330,18 @@ int hidinput_connect(struct hid_device *hid, unsigned int force)
> }
> }
>
> + if (hidinput && (hid->quirks & HID_QUIRK_NO_EMPTY_INPUT) &&
> + !hidinput_has_been_populated(hidinput)) {
> + /* no need to register an input device not populated */
> + hidinput_cleanup_hidinput(hid, hidinput);
> + hidinput = NULL;
> + }
> +
> + if (list_empty(&hid->inputs)) {
> + hid_err(hid, "No inputs registered, leaving\n");
> + goto out_unwind;
> + }
> +
> if (hidinput) {
> if (drv->input_configured)
> drv->input_configured(hid, hidinput);
> diff --git a/include/linux/hid.h b/include/linux/hid.h
> index 7071eb3..15b98a6 100644
> --- a/include/linux/hid.h
> +++ b/include/linux/hid.h
> @@ -282,6 +282,7 @@ struct hid_item {
> #define HID_QUIRK_BADPAD 0x00000020
> #define HID_QUIRK_MULTI_INPUT 0x00000040
> #define HID_QUIRK_HIDINPUT_FORCE 0x00000080
> +#define HID_QUIRK_NO_EMPTY_INPUT 0x00000100
> #define HID_QUIRK_SKIP_OUTPUT_REPORTS 0x00010000
> #define HID_QUIRK_FULLSPEED_INTERVAL 0x10000000
> #define HID_QUIRK_NO_INIT_REPORTS 0x20000000
> --
> 1.8.1.2
>
next prev parent reply other threads:[~2013-03-19 21:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 16:55 [PATCH 0/7] HID: multitouch: support of hybrid finger/pen devices Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 1/7] HID: input: don't register unmapped input devices Benjamin Tissoires
2013-03-19 21:25 ` Henrik Rydberg [this message]
2013-03-20 9:30 ` Benjamin Tissoires
2013-03-22 14:48 ` Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 2/7] HID: multitouch: breaks out touch handling in specific functions Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 3/7] HID: multitouch: do not map usage from non used reports Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 4/7] HID: multitouch: add handling for pen in dual-sensors device Benjamin Tissoires
2013-03-19 21:32 ` Henrik Rydberg
2013-03-20 13:42 ` Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 5/7] HID: multitouch: manually send sync event for pen input report Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 6/7] HID: multitouch: append " Pen" to the name of the stylus input Benjamin Tissoires
2013-03-19 21:38 ` Henrik Rydberg
2013-03-20 14:42 ` Benjamin Tissoires
2013-02-27 16:55 ` [PATCH 7/7] HID: multitouch: force BTN_STYLUS for pen devices Benjamin Tissoires
2013-03-18 22:14 ` [PATCH 0/7] HID: multitouch: support of hybrid finger/pen devices Jiri Kosina
2013-03-19 21:40 ` Henrik Rydberg
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=20130319212511.GA7821@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=benjamin.tissoires@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=chatty@enac.fr \
--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).