From: Henrique de Moraes Holschuh <hmh@debian.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Robert Hancock <hancockr@shaw.ca>, 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: Thu, 6 Jul 2006 23:46:04 -0300 [thread overview]
Message-ID: <20060707024603.GC22666@khazad-dum.debian.net> (raw)
In-Reply-To: <20060706061930.GA6033@suse.cz>
On Thu, 06 Jul 2006, Vojtech Pavlik wrote:
> > >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.
> >
> > It had better, that is exactly what the ACPI Global Lock is supposed to
> > prevent (concurrent access to non-sharable resources between the OS and
> > SMI code). The ACPI DSDT contains information on whether or not the
> > machine requires the Global Lock in order to access the EC or whether it
> > is safe to access without locking.
>
> Isn't that vaild only if you actully use ACPI to access the EC? (AFAIK
> the HDAPS driver does direct port access.)
It better be valid for any OS-side access to the EC, otherwise the ACPI
global lock would be utterly useless. The system vendor would have done its
own "global-lock-like" functionality without the need for an ACPI global
lock specification.
What is not clear to me is whether an ACPI DSDT method is on the "OS side"
or on the "SMM side" of the ACPI global 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-07 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2006-07-03 12:48 Henrique de Moraes Holschuh
2006-07-04 7:59 ` Pavel Machek
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
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=20060707024603.GC22666@khazad-dum.debian.net \
--to=hmh@debian.org \
--cc=hancockr@shaw.ca \
--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®