public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: yakui_zhao <yakui.zhao@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "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: Wed, 13 May 2009 11:13:04 +0800	[thread overview]
Message-ID: <1242184384.3773.241.camel@localhost.localdomain> (raw)
In-Reply-To: <200905120857.40058.bjorn.helgaas@hp.com>

On Tue, 2009-05-12 at 22:57 +0800, Bjorn Helgaas wrote:
> On Monday 11 May 2009 11:27:40 pm yakui_zhao wrote:
> > From: Zhao Yakui <yakui.zhao@intel.com>
> > 
> > Skip the power state check in course of power transition by changing the
> > default value of acpi_power_nocheck to 1. If so, it is unnecessary to add the
> > boot option of "acpi.power_nocheck=1" or add it into DMI power check table to
> > skip the power state check.
> > 
> > Of course the power state check still can be enabled by adding the boot option
> > of "acpi.power_nocheck=0".
> 
> What is the value of keeping the "acpi.power_nocheck" option at all?
> 
> If we can get along without it, it'd be nice to just remove the
> whole thing.
Yes. If we delete the course of the power state check in power
transition, it will be unnecessary to add the boot option.

In fact this object is defined in ACPI spec. And we had better follow
that. IMO Linux ACPI does the right thing.
The boot option of "acpi.power_nocheck" is only to make Linux be
compatible with windows.

At the same time if we want to make the power state check more strict,
we will have to re-add the source-code. 

So IMO it will be better that the power state check in power transition
is controlled by one module parameter.

Best regards.
    Yakui.

> 
> Bjorn
> 
> > Index: linux-2.6/drivers/acpi/power.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/acpi/power.c	2009-04-16 16:10:24.000000000 +0800
> > +++ linux-2.6/drivers/acpi/power.c	2009-05-12 13:12:27.000000000 +0800
> > @@ -54,7 +54,7 @@
> >  #define ACPI_POWER_RESOURCE_STATE_ON	0x01
> >  #define ACPI_POWER_RESOURCE_STATE_UNKNOWN 0xFF
> >  
> > -int acpi_power_nocheck;
> > +int acpi_power_nocheck = 1;
> >  module_param_named(power_nocheck, acpi_power_nocheck, bool, 000);
> >  
> >  static int acpi_power_add(struct acpi_device *device);
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> 
> 


  reply	other threads:[~2009-05-13  3:10 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 [this message]
2009-05-13 13:08     ` Matthew Garrett
2009-05-14  1:47       ` yakui_zhao
2009-05-14 10:56         ` Matthew Garrett
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=1242184384.3773.241.camel@localhost.localdomain \
    --to=yakui.zhao@intel.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    /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