From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Henrik Rydberg" Subject: Re: [PATCH v3 13/13] HID: hid-multitouch: forwards ABS_SCAN_TIME Date: Tue, 13 Nov 2012 19:43:57 +0100 Message-ID: <20121113184357.GA3635@polaris.bitmath.org> References: <1352306256-12180-1-git-send-email-benjamin.tissoires@gmail.com> <1352306256-12180-14-git-send-email-benjamin.tissoires@gmail.com> <50A25990.6040302@gmail.com> <20121113172711.GA856@polaris.bitmath.org> <20121113182825.GA3627@polaris.bitmath.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from smtprelay-h31.telenor.se ([213.150.131.4]:38094 "EHLO smtprelay-h31.telenor.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755413Ab2KMShl (ORCPT ); Tue, 13 Nov 2012 13:37:41 -0500 Content-Disposition: inline In-Reply-To: <20121113182825.GA3627@polaris.bitmath.org> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Benjamin Tissoires Cc: Dmitry Torokhov , Jiri Kosina , Stephane Chatty , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org > To conclude, we obviously have devices with a rather short wrap-around > time. However, since the normal inter-frame time is in the millisecond > range, it should not be overly restrictive to change the definition of > the minimum wraparound time from hours to seconds. Sorry, Benjamin, you are right about the counter. To be useful, we do need to know the number of bits of the counter, so that differences can be computed properly. In other words, either ABS_SCAN_TIME is be the better choice, or we need to make sure that the counter wraps on the full 32 bit boundary. Henrik