From: "Henrik Rydberg" <rydberg@euromail.se>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@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 v2 10/11] HID: introduce Scan Time
Date: Mon, 29 Oct 2012 23:43:31 +0100 [thread overview]
Message-ID: <20121029224331.GA15608@polaris.bitmath.org> (raw)
In-Reply-To: <1351241067-9521-11-git-send-email-benjamin.tissoires@gmail.com>
Hi Benjamin,
> Win 8 digitizer devices provides the actual scan time computed by the
> hardware itself. The value is global to the frame and is not specific
> to the multitouch protocol (though only touch, not pen, should use it
> according to the specification).
>
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
> ---
> Documentation/input/event-codes.txt | 7 +++++++
> drivers/hid/hid-input.c | 4 ++++
> drivers/hid/hid-multitouch.c | 11 +++++++++--
> include/linux/hid.h | 1 +
> include/linux/input.h | 1 +
> 5 files changed, 22 insertions(+), 2 deletions(-)
This is a nice feature, useful in many other contexts. As such, I
think it should be defined in the context of the input subsystem, with
a more specific definition added to the documentation. For instance,
is 100us suitable? When should it start at zero, at BTN_TOUCH? Or
should it perhaps wrap around on unsigned integer instead? Or display
the difference from the last event?
> diff --git a/Documentation/input/event-codes.txt b/Documentation/input/event-codes.txt
> index 53305bd..8f8c908 100644
> --- a/Documentation/input/event-codes.txt
> +++ b/Documentation/input/event-codes.txt
> @@ -174,6 +174,13 @@ A few EV_ABS codes have special meanings:
> the input device may be used freely in three dimensions, consider ABS_Z
> instead.
>
> +* ABS_SCAN_TIME:
> + - Used when the device provides a timestamp for each frame. The unit must be
> + 100us, and may be reset when the device don't send any events for a
> + period of time. The values increment at each frame and thus, it can roll
> + back to 0 when reach logical_max. If the device does not provide this
> + information, the driver must not provide it to the user space.
> +
> * ABS_MT_<name>:
> - Used to describe multitouch input events. Please see
> multi-touch-protocol.txt for details.
> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> index 16cc89a..5fe7bd3 100644
> --- a/drivers/hid/hid-input.c
> +++ b/drivers/hid/hid-input.c
> @@ -675,6 +675,10 @@ static void hidinput_configure_usage(struct hid_input *hidinput, struct hid_fiel
> map_key_clear(BTN_STYLUS2);
> break;
>
> + case 0x56: /* Scan Time */
> + map_abs(ABS_SCAN_TIME);
> + break;
> +
Is it not enough to map it in the case below? Or you mean this is
picked up by hid core?
> default: goto unknown;
> }
> break;
> diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
> index c0ab1c6..21a120b 100644
> --- a/drivers/hid/hid-multitouch.c
> +++ b/drivers/hid/hid-multitouch.c
> @@ -447,12 +447,19 @@ static int mt_input_mapping(struct hid_device *hdev, struct hid_input *hi,
> mt_store_field(usage, td, hi);
> td->last_field_index = field->index;
> return 1;
> + case HID_DG_SCANTIME:
> + hid_map_usage(hi, usage, bit, max,
> + EV_ABS, ABS_SCAN_TIME);
> + set_abs(hi->input, ABS_SCAN_TIME, field, 0);
> + td->last_field_index = field->index;
> + return 1;
> case HID_DG_CONTACTCOUNT:
> td->last_field_index = field->index;
> return 1;
> case HID_DG_CONTACTMAX:
> - /* we don't set td->last_slot_field as contactcount and
> - * contact max are global to the report */
> + /* we don't set td->last_slot_field as scan time,
> + * contactcount and contact max are global to the
> + * report */
> td->last_field_index = field->index;
> return -1;
> case HID_DG_TOUCH:
> diff --git a/include/linux/hid.h b/include/linux/hid.h
> index 6216529..99a6418 100644
> --- a/include/linux/hid.h
> +++ b/include/linux/hid.h
> @@ -279,6 +279,7 @@ struct hid_item {
> #define HID_DG_DEVICEINDEX 0x000d0053
> #define HID_DG_CONTACTCOUNT 0x000d0054
> #define HID_DG_CONTACTMAX 0x000d0055
> +#define HID_DG_SCANTIME 0x000d0056
>
> /*
> * HID report types --- Ouch! HID spec says 1 2 3!
> diff --git a/include/linux/input.h b/include/linux/input.h
> index ba48743..73c3a96 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -796,6 +796,7 @@ struct input_keymap_entry {
> #define ABS_TILT_X 0x1a
> #define ABS_TILT_Y 0x1b
> #define ABS_TOOL_WIDTH 0x1c
> +#define ABS_SCAN_TIME 0x1d
>
> #define ABS_VOLUME 0x20
>
> --
> 1.7.11.7
>
Thanks,
Henrik
next prev parent reply other threads:[~2012-10-29 22:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 8:44 [PATCH v2 00/11] Win 8 support for digitizers Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 01/11] HID: hid-input: export hidinput_calc_abs_res Benjamin Tissoires
2012-10-29 18:57 ` Henrik Rydberg
2012-10-30 10:04 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 02/11] HID: core: fix unit exponent parsing Benjamin Tissoires
2012-10-29 19:05 ` Henrik Rydberg
2012-10-30 10:07 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 03/11] HID: hid-input: add usage_index argument in input_mapping and event Benjamin Tissoires
2012-10-29 19:25 ` Henrik Rydberg
2012-10-30 10:09 ` Benjamin Tissoires
2012-11-06 13:56 ` Benjamin Tissoires
2012-11-06 15:24 ` Jiri Kosina
2012-10-26 8:44 ` [PATCH v2 04/11] HID: hid-multitouch: support arrays for the split of the touches in a report Benjamin Tissoires
2012-10-29 21:49 ` Henrik Rydberg
2012-10-30 10:11 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 05/11] HID: hid-multitouch: get maxcontacts also from logical_max value Benjamin Tissoires
2012-10-29 21:52 ` Henrik Rydberg
2012-10-26 8:44 ` [PATCH v2 06/11] HID: hid-multitouch: support T and C for win8 devices Benjamin Tissoires
2012-10-29 22:00 ` Henrik Rydberg
2012-10-30 10:16 ` Benjamin Tissoires
2012-10-31 18:47 ` Henrik Rydberg
2012-10-26 8:44 ` [PATCH v2 07/11] HID: hid-multitouch: move ALWAYS_VALID quirk check Benjamin Tissoires
2012-10-29 22:16 ` Henrik Rydberg
2012-10-30 10:19 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 08/11] HID: hid-multitouch: fix Win 8 protocol Benjamin Tissoires
2012-10-29 22:19 ` Henrik Rydberg
2012-10-30 10:24 ` Benjamin Tissoires
2012-10-31 18:53 ` Henrik Rydberg
2012-11-02 14:18 ` Benjamin Tissoires
2012-11-04 20:54 ` Henrik Rydberg
2012-11-05 9:51 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 09/11] HID: hid-multitouch: support for hovering devices Benjamin Tissoires
2012-10-29 22:31 ` Henrik Rydberg
2012-10-30 10:43 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 10/11] HID: introduce Scan Time Benjamin Tissoires
2012-10-29 22:43 ` Henrik Rydberg [this message]
2012-10-30 10:54 ` Benjamin Tissoires
2012-10-31 19:16 ` Henrik Rydberg
2012-11-02 14:23 ` Benjamin Tissoires
2012-10-26 8:44 ` [PATCH v2 11/11] HID: hid-multitouch: get rid of usbhid depedency for general path Benjamin Tissoires
2012-10-29 22:57 ` Henrik Rydberg
2012-10-30 11:04 ` Benjamin Tissoires
2012-10-31 19:18 ` Henrik Rydberg
2012-11-05 12:57 ` Henrik Rydberg
2012-11-05 13:28 ` Benjamin Tissoires
2012-11-05 13:32 ` 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=20121029224331.GA15608@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=benjamin.tissoires@gmail.com \
--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
Powered by JetHome