From: "Henrik Rydberg" <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
Chase Douglas <chasedouglas@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: evdev - use monotonic clock for event timestamps
Date: Fri, 7 Oct 2011 13:05:42 +0200 [thread overview]
Message-ID: <20111007110542.GA5333@polaris.bitmath.org> (raw)
In-Reply-To: <20111007063617.GA6167@core.coreip.homeip.net>
> > if the values don't change. The timestamp axis
> > would always change, hence it would always be sent, even if no other
> > axes change. Of course, we can mitigate this with special-case
> > handling of the ABS_TIMESTAMP in the evdev layer.
> >
>
> I'd prefer if we go this route then:
>
> 1. Have input core emit this event. Then we could decide if we should
> suppress it when suppressing entire packet.
If we go this route, we could also make use of the time stamps of the
hardware, when existent.
> 2. Make it MSC_ event.
> 3. Turn it on and off via ioctl since not all users are interested in
> this facility.
Perhaps it is time for the per-file-descriptor event filters.
> OTOH if we do ioctl why don't we simply allow usres select monotnic vs
> wall time in event structure.
>
> Still, why does your clock fluctuate so much that it matters?
Yes, some actual experimental timing data would be most interesting.
Thanks,
Henrik
prev parent reply other threads:[~2011-10-07 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 6:43 [PATCH] Input: evdev - use monotonic clock for event timestamps Daniel Kurtz
2011-10-03 9:06 ` Henrik Rydberg
2011-10-05 7:55 ` Daniel Kurtz
2011-10-05 9:23 ` Henrik Rydberg
2011-10-05 14:35 ` Chase Douglas
2011-10-06 3:42 ` Dmitry Torokhov
2011-10-06 6:25 ` Daniel Kurtz
2011-10-07 6:36 ` Dmitry Torokhov
2011-10-07 11:05 ` Henrik Rydberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111007110542.GA5333@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=chasedouglas@gmail.com \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).