public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Colin King <colin.king@canonical.com>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/1] acpi: clear PCIEXP_WAKE_STS on resume
Date: Tue, 28 Sep 2010 08:31:21 -0700	[thread overview]
Message-ID: <20100928083121.f76e8991.rdunlap@xenotime.net> (raw)
In-Reply-To: <1285671624-7826-2-git-send-email-colin.king@canonical.com>

On Tue, 28 Sep 2010 12:00:24 +0100 Colin King wrote:

> From: Colin Ian King <colin.king@canonical.com>
> 
> Section 4.7.3.1.1 (PM1 Status Registers) of version 4.0 of
> the ACPI spec concerning PCIEXP_WAKE_STS points out in
> in the final note field in table 4-11 that if this bit is
> set to 1 and the system is put into a sleeping state then
> the system will not automatically wake.
> 
> This bit gets set by hardware to indicate that the system
> woke up due to a PCI Express wakeup event, so clear it during
> acpi_hw_clear_acpi_status() calls to enable subsequent
> resumes to work.
> 
> BugLink: http://bugs.launchpad.net/bugs/613381
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/acpi/acpica/aclocal.h |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/acpi/acpica/aclocal.h b/drivers/acpi/acpica/aclocal.h
> index 147a7e6..f26db38 100644
> --- a/drivers/acpi/acpica/aclocal.h
> +++ b/drivers/acpi/acpica/aclocal.h
> @@ -853,6 +853,7 @@ struct acpi_bit_register_info {
>  	ACPI_BITMASK_POWER_BUTTON_STATUS   | \
>  	ACPI_BITMASK_SLEEP_BUTTON_STATUS   | \
>  	ACPI_BITMASK_RT_CLOCK_STATUS       | \
> +        ACPI_BITMASK_PCIEXP_WAKE_DISABLE   | \

(1) Above should be indented with tabs, not spaces.

(2) It should not take 2 emails to send a patch with one line changed.
Patch 0/N is unnecessary and not desirable on short patch series (N = 1 is short).

>  	ACPI_BITMASK_WAKE_STATUS)
>  
>  #define ACPI_BITMASK_TIMER_ENABLE               0x0001
> -- 


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-28 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 11:00 [RESEND][PATCH 0/1] acpi: clear PCIEXP_WAKE_STS on resume Colin King
2010-09-28 11:00 ` [PATCH 1/1] " Colin King
2010-09-28 15:31   ` Randy Dunlap [this message]
2010-09-28 15:46     ` Colin Ian King
2010-09-28 15:51       ` Randy Dunlap
2010-09-28 19:42       ` Len Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-08-04 10:06 [PATCH 0/1] " Colin King
2010-08-04 10:06 ` [PATCH 1/1] " Colin King

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=20100928083121.f76e8991.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=colin.king@canonical.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