Dmitry,
I didn't see the MSC_TIMESTAMP before. I should have been more up to
date. I've looked at MSC_TIMESTAMP change and the first impression was
that it is something we can live with. After discussing details with
my colleagues here we came to a conclusion that:
a) we do need absolute time.
b)
Apologies, forgot to make sure it was plain text.
On Tue, Jul 16, 2013 at 4:16 PM, Michael Wright wrote:
> Hi Dmitry,
>
>
> On Fri, Jul 12, 2013 at 11:44 PM, Dmitry Torokhov
> wrote:
>> We already have MSC_TIMESTAMP (which is in usec), do you really need
>> nsec resolution?
>
> We don't actually
Hi Sasha,
On Wed, Jul 10, 2013 at 01:38:00PM -0700, Alexander Levitskiy wrote:
> From: Sasha Levitskiy
>
> Input: Propagate hardware event timestamp to evdev.
>
> Convey hardware generated timestamp associated with the current event packet.
> The use of these event codes by hardware drivers is
From: Sasha Levitskiy
Input: Propagate hardware event timestamp to evdev.
Convey hardware generated timestamp associated with the current event packet.
The use of these event codes by hardware drivers is optional.
Used to reduce jitter and improve velocity tracking in ABS_MT and other timing
sen
4 matches
Mail list logo
