public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: yakui_zhao <yakui.zhao@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH]: ACPI: Skip the power state check in power transition
Date: Thu, 14 May 2009 11:56:27 +0100	[thread overview]
Message-ID: <20090514105626.GA17294@srcf.ucam.org> (raw)
In-Reply-To: <1242265659.3773.428.camel@localhost.localdomain>

On Thu, May 14, 2009 at 09:47:39AM +0800, yakui_zhao wrote:
> On Wed, 2009-05-13 at 21:08 +0800, Matthew Garrett wrote:
> > The default behaviour should be to be compatible with Windows, 
> > regardless of what the spec says. There's an argument for providing a 
> > strict interpretation of the spec for testing purposes, but I don't
> > see 
> > any reason for it to be split up into dozens of individual kernel 
> > parameters
> The ACPI 1.0 spec is followed by windows XP. And the power state is not
> checked in power transition under windows XP.
> But we don't know whether it is still skipped on the new version
> windows.(For example: Windows 7).
>
> If the module param is removed, we must delete the source code related
> with power state check. And if the power state is checked in power
> transition on windows 7, what we should do? It is not reasonable to add
> them again.

If Windows 7 changes the behaviour then the correct approach is to key 
this behaviour on whether the system firmware requests the Windows 7 OSI 
string. The code can be #if 0ed out until then, or placed under an 
acpi.strict kernel option that turns on all standards-compliant but 
windows-incompatible code.

> Maybe it is better to determine whether the power state check is skipped
> in power transition.

We have a stated policy that Linux will default to being Windows 
compatible. You've demonstrated that in this case Linux isn't Windows 
compatible, which means that it's a bug. The correct behaviour for Linux 
here is to ignore the _STA value (or, indeed, not to call _STA at all in 
this path).

-- 

Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-05-14 10:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  5:27 [PATCH]: ACPI: Skip the power state check in power transition yakui_zhao
2009-05-12 14:57 ` Bjorn Helgaas
2009-05-13  3:13   ` yakui_zhao
2009-05-13 13:08     ` Matthew Garrett
2009-05-14  1:47       ` yakui_zhao
2009-05-14 10:56         ` Matthew Garrett [this message]
2009-05-14 18:49           ` Bjorn Helgaas
2009-05-18  2:08             ` yakui_zhao
2009-05-18  7:13               ` Matthew Garrett
2009-05-21 23:28               ` Bjorn Helgaas
2009-05-28  1:43 ` Len Brown

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=20090514105626.GA17294@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@intel.com \
    /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