From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Tissoires Subject: Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP Date: Mon, 2 Oct 2017 15:01:52 +0200 Message-ID: <20171002130152.GI1063@mail.corp.redhat.com> References: <20170822011011.39112-1-drinkcat@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55770 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751104AbdJBNB5 (ORCPT ); Mon, 2 Oct 2017 09:01:57 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Jiri Kosina Cc: Nicolas Boichat , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, dtor@chromium.org On Oct 02 2017 or thereabouts, Jiri Kosina wrote: > On Tue, 22 Aug 2017, Nicolas Boichat wrote: > > > Computes and forwards the device timestamp according to the > > specification. > > > > Many devices use a 16-bit timestamp field, with a resolution > > of 100us, therefore rolling around very frequently (every > > 6.5 seconds). To make sure there is no ambiguity, the > > timestamp reported to the input stack reset to 0 whenever > > the time between 2 received events is greater than > > MAX_TIMESTAMP_INTERVAL (1 second). > > > > Signed-off-by: Nicolas Boichat > > > --- > > > > Inspired from Benjamin Tissoires's patch here: > > https://patchwork.kernel.org/patch/1742181/, and changing the > > logic to resynchronize the timestamps to use received time > > instead of a potentially more fragile difference between > > the 2 deltas. > > Benjamin, any objections on merging this one for 4.15? I like it. > No objections from my side. Acked-by: Benjamin Tissoires Cheers, Benjamin > Thanks, > > -- > Jiri Kosina > SUSE Labs >