From: Bill Gatliff <bgat@billgatliff.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Synchronizing evdev readers and drivers?
Date: Fri, 3 Dec 2010 07:03:12 -0600 [thread overview]
Message-ID: <AANLkTimFoyFksd1orc9Bf8y5y7xQf14i_hhDoRyR3vnE@mail.gmail.com> (raw)
In-Reply-To: <20101203124240.GH3182@sirena.org.uk>
On Fri, Dec 3, 2010 at 6:42 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
>
> The sysfs interface offered by polldev is *mostly* doing the same thing
True, except that there is still no synchronization of the polling
events between the driver and application. For example, if the
polling interval is once per second then the sample ultimately
delivered to applications could be almost one second old--- even if
the application reads from the evdev interface once a second as well.
The callback can be used to reduce the delay between sample generation
and event delivery. It can also increase system load, but reduces
phase error in situations where that is desirable. I don't expect
that many drivers will use the callback, but for the ones that do it
will be very useful.
> A callback on read seems like it's a bit limited as it's more work for
> the application (handling the latency introduced by waking up from your
> delay and doing the read is faff) and requires polling in the hardware
> too.
Right. But if the hardware works that way anyway, then the
alternatives seem to boil down to either unsynchronized polling, or
samples-on-demand. Some applications e.g. mine, really want the
latter.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2010-12-03 13:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 17:26 Synchronizing evdev readers and drivers? Bill Gatliff
2010-12-02 21:22 ` Dmitry Torokhov
2010-12-02 21:34 ` Bill Gatliff
2010-12-03 12:42 ` Mark Brown
2010-12-03 13:03 ` Bill Gatliff [this message]
2010-12-03 13:53 ` Mark Brown
2010-12-03 17:36 ` Bill Gatliff
2010-12-03 18:52 ` Mark Brown
2010-12-03 19:41 ` Bill Gatliff
2010-12-03 22:27 ` Mark Brown
2010-12-03 23:05 ` Dmitry Torokhov
2010-12-03 19:50 ` Dmitry Torokhov
2010-12-03 20:17 ` Bill Gatliff
2010-12-03 21:24 ` Dmitry Torokhov
2010-12-03 19:32 ` Dmitry Torokhov
2010-12-03 19:50 ` Bill Gatliff
2010-12-03 20:56 ` Dmitry Torokhov
2010-12-04 17:52 ` Jonathan Cameron
2010-12-04 18:15 ` Bill Gatliff
2010-12-04 17:46 ` Jonathan Cameron
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=AANLkTimFoyFksd1orc9Bf8y5y7xQf14i_hhDoRyR3vnE@mail.gmail.com \
--to=bgat@billgatliff.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@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).