Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-05 Thread Jiri Kosina
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

Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-05 Thread Jiri Kosina
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

Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-02 Thread Benjamin Tissoires
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

Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-02 Thread Benjamin Tissoires
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

Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-02 Thread Jiri Kosina
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

Re: [PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-10-02 Thread Jiri Kosina
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

[PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-08-21 Thread Nicolas Boichat
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

[PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

2017-08-21 Thread Nicolas Boichat
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