From: Henrique de Moraes Holschuh <hmh@debian.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Pavel Machek <pavel@suse.cz>,
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: Re: Generic interface for accelerometers (AMS, HDAPS, ...)
Date: Wed, 5 Jul 2006 10:58:16 -0300 [thread overview]
Message-ID: <20060705135816.GA8452@khazad-dum.debian.net> (raw)
In-Reply-To: <20060705073455.GA6027@suse.cz>
On Wed, 05 Jul 2006, Vojtech Pavlik wrote:
> > > I don't know about AMS, but talking to HDAPS when
> > > you don't need to does waste enough system resources and power to actually
> > > justify implementing this.
>
> I'd doubt any of the accelerometer implementations would consume much
> power or CPU.
It is not just CPU or power, although IMO striving for perfection on power
management in a laptop is almost always a good thing if it can be done
safely.
HDAPS talks to the embedded controller using IO over the LPC bus, and not to
the accelerometer chip or to a simple A/D i2c chip which is used excusively
for accelerometer access. The EC interface for HDAPS data retrieval is
not friendly to any errors, and hardlocks the machine somehow if any
firmware bugs hit or if we violate any of the rules (that are not written
anywhere) about how to access the EC without geting the SMBIOS unhappy.
So, turning off HDAPS polling while it is not necessary really looks like a
good idea overall.
We are investigating the ACPI global lock as a way to at least get the
SMBIOS to stay away from the EC while we talk to it, but we don't know if
the entire SMBIOS firmware respects that lock.
--
"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 prev parent reply other threads:[~2006-07-05 13:58 UTC|newest]
Thread overview: 20+ 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 ` [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 [this message]
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=20060705135816.GA8452@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=pavel@suse.cz \
--cc=stelian@popies.net \
--cc=vojtech@suse.cz \
/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®