From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Stelian Pop <stelian@popies.net>
Cc: Jean Delvare <khali@linux-fr.org>, Andrew Morton <akpm@osdl.org>,
Dmitry Torokhov <dtor_core@ameritech.net>,
Michael Hanselmann <linux-kernel@hansmi.ch>,
"Aristeu S. Rozanski F." <aris@cathedrallabs.org>,
Johannes Berg <johannes@sipsolutions.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>, Robert Love <rml@novell.com>,
Rene Nussbaumer <linux-kernel@killerfox.forkbomb.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Apple Motion Sensor driver
Date: Tue, 14 Nov 2006 01:09:53 -0200 [thread overview]
Message-ID: <20061114030953.GA5810@khazad-dum.debian.net> (raw)
In-Reply-To: <1163450519.23807.11.camel@localhost.localdomain>
On Mon, 13 Nov 2006, Stelian Pop wrote:
> I do believe that the proper place for ams is the hardware monitoring
> section (even if the missing HD parking APIs makes it not very useful
> right now).
>
> The fact that the accelerometer offers a (low res) joystick emulation is
> only a nice hack and I'm not even sure somebody (except Johannes) will
> find an use for it.
Sort of. Some accelerometers actually act more as input devices than as
monitoring devices. E.g. HDAPS has no intelligence whatsoever about what is
happening (it doesn't to any sort of threshold detection, unlike Apple's
motion sensing stuff), but it can give you reasonable resolution at a
maximum sample rate of 500Hz (I don't recommend getting it to go that fast,
though) for two axis, with configurable running-averaging. Looks a lot more
like a joystick to me than a hardware monitoring sensor.
It's just a matter of PoV, and one can easily make a case for accelerometers
to live in either hwmon or input. As long as they're all in one place :-)
--
"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
prev parent reply other threads:[~2006-11-14 3:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 21:36 Stelian Pop
2006-11-11 21:41 ` Michael Hanselmann
2006-11-11 22:00 ` Stelian Pop
2006-11-12 8:37 ` Michael Hanselmann
2006-11-12 21:38 ` Stelian Pop
2006-11-13 18:11 ` Jean Delvare
2006-11-13 18:18 ` Dmitry Torokhov
2006-11-13 15:04 ` Dmitry Torokhov
2006-11-13 15:29 ` Stelian Pop
2006-11-13 15:53 ` Dmitry Torokhov
2006-11-13 16:14 ` Stelian Pop
2006-11-13 16:20 ` Johannes Berg
2006-11-13 18:14 ` Jean Delvare
2006-11-13 18:18 ` Johannes Berg
2006-11-13 18:24 ` Michael Hanselmann
2006-11-13 20:55 ` Stelian Pop
2006-11-13 18:20 ` Dmitry Torokhov
2006-11-13 18:55 ` Robert Love
2006-11-13 20:52 ` Stelian Pop
2006-11-13 21:23 ` Johannes Berg
2006-11-13 21:39 ` Stelian Pop
2006-11-13 18:06 ` Jean Delvare
2006-11-13 18:23 ` Henrique de Moraes Holschuh
2006-11-13 20:41 ` Stelian Pop
2006-11-14 3:09 ` Henrique de Moraes Holschuh [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=20061114030953.GA5810@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=akpm@osdl.org \
--cc=aris@cathedrallabs.org \
--cc=benh@kernel.crashing.org \
--cc=dtor_core@ameritech.net \
--cc=johannes@sipsolutions.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@hansmi.ch \
--cc=linux-kernel@killerfox.forkbomb.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rml@novell.com \
--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®