mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Shem Multinymous" <multinymous@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Henrique de Moraes Holschuh" <hmh@debian.org>,
	"Stelian Pop" <stelian@popies.net>,
	"Michael Hanselmann" <linux-kernel@hansmi.ch>,
	hdaps-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	lm-sensors@lm-sensors.org
Subject: Re: [Hdaps-devel] Generic interface for accelerometers (AMS, HDAPS, ...)
Date: Tue, 4 Jul 2006 13:26:56 +0300	[thread overview]
Message-ID: <41840b750607040326y7bfe92dy21c6845ab034ce30@mail.gmail.com> (raw)
In-Reply-To: <20060704075950.GA13073@elf.ucw.cz>

On 7/4/06, Pavel Machek <pavel@ucw.cz> wrote:
> Just use input infrastructure and be done with that? You can do
> parking from userspace.

Will moving the hdapsd userspace daemon from sysfs polling to the
input infrastructure cause a noticable latency increase compared to
polling sysfs? This functionality is highly time-critical.

Also, there's a small issue with polling frequency. hdapsd needs a
fairly high frequency (say, 50Hz) to gather statistics and keep
response latency low, whereas the hdaps driver's internal polling
(routing to the input infrastructure) is currently done at only 20Hz.
We'll need to increase the latter, thereby slightly increasing system
load when hdaps isn't running.

In terms of magnitude, an hdaps readout takes ~70usec on average and
(very rarely) up to ~1msec. This is with the tp_smapi [1] patches to
hdaps, which add the checks and retries needed to ensure the readout
is valid.

BTW, can the driver tell when nothing is accessing its input device,
and avoid polling in that case?

  Shem

[1] http://thinkwiki.org/wiki/tp_smapi

  reply	other threads:[~2006-07-04 10:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 12:48 Henrique de Moraes Holschuh
2006-07-04  7:59 ` Pavel Machek
2006-07-04 10:26   ` Shem Multinymous [this message]
2006-07-04 10:57     ` [Hdaps-devel] " Pavel Machek
2006-07-04 15:02     ` Thomas Tuttle
2006-07-05  3:13     ` Dmitry Torokhov
2006-07-04 16:23   ` Henrique de Moraes Holschuh
2006-07-04 23:57     ` Pavel Machek
2006-07-05  7:34       ` Vojtech Pavlik
2006-07-05 13:58         ` Henrique de Moraes Holschuh
2006-07-06  1:12           ` Pavel Machek
2006-07-05  7:59       ` [lm-sensors] " Jean Delvare
2006-07-05  8:00   ` [Hdaps-devel] " Johannes Berg
2006-07-05 14:06     ` Henrique de Moraes Holschuh

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=41840b750607040326y7bfe92dy21c6845ab034ce30@mail.gmail.com \
    --to=multinymous@gmail.com \
    --cc=hdaps-devel@lists.sourceforge.net \
    --cc=hmh@debian.org \
    --cc=linux-kernel@hansmi.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=pavel@ucw.cz \
    --cc=stelian@popies.net \
    /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

Powered by JetHome