From: Henrique de Moraes Holschuh <hmh@debian.org>
To: lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org,
hdaps-devel@lists.sourceforge.net,
Stelian Pop <stelian@popies.net>,
Michael Hanselmann <linux-kernel@hansmi.ch>
Subject: Generic interface for accelerometers (AMS, HDAPS, ...)
Date: Mon, 3 Jul 2006 09:48:23 -0300 [thread overview]
Message-ID: <20060703124823.GA18821@khazad-dum.debian.net> (raw)
We have now (or we are about to have, anyway) two drivers that export
accelerometer data: IBM's HDAPS, and Apple's AMS. More accelerometer
drivers could be coming in the future.
Both drivers export one common set of data (accelerometer output), and some
extra information that is not related to acellerometers. Both have at least
two functionality goals in common: to export accelerometer data to
userspace, and also to allow somehow for HD head parking when the
accelerometer detects a potentially incoming impact.
Userspace utilities that interface to accelerometers like hdapsd and
smackpad could benefit from a common interface, so that they work with
HDAPS, AMS, and any other future accelerometer drivers.
If any kernel-space functionality needed by HDAPS and AMS is also shared, we
would have benefits there too. Some examples I can think of are: generic HD
queue-freeze and HD head parking, and a generic acellerometer-driven
joystick event interface. This would also enable generic userspace
notifiers that the HD heads have been parked, etc.
I am posting this message as a head's up for the two projects (HDAPS, AMS)
to make sure that they are actively aware of each other. I do so in hope
that we can work in a joint, generic interface and port both drivers to this
new interface in the near future, and also that we can make as much
functionality shared between the two drivers as possible.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next reply other threads:[~2006-07-03 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 12:48 Henrique de Moraes Holschuh [this message]
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-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
[not found] <fa.GOQkHC8inXir2wbg4bZayOWXzAY@ifi.uio.no>
[not found] ` <fa.qLWuLxQd7Mhcnixy/TLVs/nPwig@ifi.uio.no>
2006-07-05 23:59 ` Robert Hancock
2006-07-06 6:19 ` Vojtech Pavlik
2006-07-07 2:46 ` Henrique de Moraes Holschuh
2006-07-07 5:28 ` Robert Hancock
2006-07-07 9:31 ` Vojtech Pavlik
[not found] <fa.+TBrYxvBPaXCptm9JXDjMT6wk58@ifi.uio.no>
[not found] ` <fa.KtXXXVDoa0Coj62aBgf3NuqbZMo@ifi.uio.no>
2006-07-07 1:40 ` Robert Hancock
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=20060703124823.GA18821@khazad-dum.debian.net \
--to=hmh@debian.org \
--cc=hdaps-devel@lists.sourceforge.net \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--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
all inboxes | Powered by JetHome®