public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>,
	Henrique de Moraes Holschuh <hmh@debian.org>,
	Stelian Pop <stelian@popies.net>,
	Michael Hanselmann <linux-kernel@hansmi.ch>,
	hdaps-devel@lists.sourceforge.net, lm-sensors@lm-sensors.org
Subject: Re: [Hdaps-devel] Generic interface for accelerometers (AMS, HDAPS, ...)
Date: Wed, 05 Jul 2006 10:00:15 +0200	[thread overview]
Message-ID: <1152086415.4995.0.camel@localhost> (raw)
In-Reply-To: <41840b750607040326y7bfe92dy21c6845ab034ce30@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

[I hope I managed to not break the thread]

> 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.

Note that with AMS we're better off -- it has two interrupts telling us
when something is wrong.

Hence, most of the discussion about loads of input values only applies
to hdaps, the actual head-park functionality can be implemented with AMS
without ever reading any sensor values.

Hence we also need much less complexity in userland -- once an interrupt
comes in we trigger the hd park...

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2006-07-05  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 12:48 Generic interface for accelerometers (AMS, HDAPS, ...) Henrique de Moraes Holschuh
2006-07-04  7:59 ` Pavel Machek
2006-07-04 10:26   ` [Hdaps-devel] " Shem Multinymous
2006-07-04 10:57     ` Pavel Machek
2006-07-04 15:02     ` Thomas Tuttle
2006-07-05  3:13     ` Dmitry Torokhov
2006-07-05  8:00     ` Johannes Berg [this message]
2006-07-05 14:06       ` Henrique de Moraes Holschuh
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

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=1152086415.4995.0.camel@localhost \
    --to=johannes@sipsolutions.net \
    --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