From 4f789286e4ab7f6fecc2ccb895d79362a9b2382a Mon Sep 17 00:00:00 2001 From: Alexandros Frantzis Date: Mon, 18 Dec 2017 14:55:00 +0200 Subject: unstable: Add input-timestamps protocol MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit timestamp with millisecond resolution. In some cases, notably latency measurements, this resolution is too coarse to be useful. This protocol provides additional high-resolution timestamps events, which are emitted before the corresponding input event. Each timestamp event contains a high-resolution, and ideally higher-accuracy, version of the 'time' argument of the first subsequent supported input event. Clients that care about high-resolution timestamps just need to keep track of the last timestamp event they receive and associate it with the next supported input event that arrives. Signed-off-by: Alexandros Frantzis Reviewed-by: Pekka Paalanen Acked-by: Jonas Ådahl Reviewed-by: Daniel Stone --- unstable/input-timestamps/README | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 unstable/input-timestamps/README (limited to 'unstable/input-timestamps/README') diff --git a/unstable/input-timestamps/README b/unstable/input-timestamps/README new file mode 100644 index 0000000..3e82890 --- /dev/null +++ b/unstable/input-timestamps/README @@ -0,0 +1,4 @@ +High-resolution timestamps for input events. + +Maintainers: +Alexandros Frantzis -- cgit v1.2.3