All of lore.kernel.org
 help / color / mirror / Atom feed
From: vojtech@suse.cz (Vojtech Pavlik)
To: Robert Hancock <hancockr@shaw.ca>
Cc: Henrique de Moraes Holschuh <hmh@debian.org>,
	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: [lm-sensors] Generic interface for accelerometers (AMS, HDAPS,
Date: Thu, 06 Jul 2006 06:19:30 +0000	[thread overview]
Message-ID: <20060706061930.GA6033@suse.cz> (raw)
In-Reply-To: <44AC5261.9050708@shaw.ca>

On Wed, Jul 05, 2006 at 05:59:29PM -0600, Robert Hancock wrote:
> Henrique de Moraes Holschuh wrote:
> >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.
> 
> 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.)

-- 
Vojtech Pavlik
Director SuSE Labs


WARNING: multiple messages have this Message-ID (diff)
From: Vojtech Pavlik <vojtech@suse.cz>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Henrique de Moraes Holschuh <hmh@debian.org>,
	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 08:19:30 +0200	[thread overview]
Message-ID: <20060706061930.GA6033@suse.cz> (raw)
In-Reply-To: <44AC5261.9050708@shaw.ca>

On Wed, Jul 05, 2006 at 05:59:29PM -0600, Robert Hancock wrote:
> Henrique de Moraes Holschuh wrote:
> >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.
> 
> 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.)

-- 
Vojtech Pavlik
Director SuSE Labs

  reply	other threads:[~2006-07-06  6:19 UTC|newest]

Thread overview: 18+ 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   ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, Robert Hancock
2006-07-05 23:59     ` Generic interface for accelerometers (AMS, HDAPS, ...) Robert Hancock
2006-07-06  6:19     ` Vojtech Pavlik [this message]
2006-07-06  6:19       ` Vojtech Pavlik
2006-07-07  2:46       ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, Henrique de Moraes Holschuh
2006-07-07  2:46         ` Generic interface for accelerometers (AMS, HDAPS, ...) Henrique de Moraes Holschuh
2006-07-07  5:28         ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, Robert Hancock
2006-07-07  5:28           ` Generic interface for accelerometers (AMS, HDAPS, ...) Robert Hancock
2006-07-07  9:31         ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, Vojtech Pavlik
2006-07-07  9:31           ` Generic interface for accelerometers (AMS, HDAPS, ...) Vojtech Pavlik
     [not found] <fa.+TBrYxvBPaXCptm9JXDjMT6wk58@ifi.uio.no>
     [not found] ` <fa.KtXXXVDoa0Coj62aBgf3NuqbZMo@ifi.uio.no>
2006-07-07  1:40   ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, Robert Hancock
2006-07-03 12:48 [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, ...) Henrique de Moraes Holschuh
2006-07-04  7:59 ` [lm-sensors] Generic interface for accelerometers (AMS, HDAPS, 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
2006-07-05  7:59       ` 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=20060706061930.GA6033@suse.cz \
    --to=vojtech@suse.cz \
    --cc=hancockr@shaw.ca \
    --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@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.