From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Lin Ming <ming.m.lin@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Moore, Robert" <robert.moore@intel.com>,
Linux PM <linux-pm@lists.linux-foundation.org>
Subject: [PATCH 0/3] ACPI / ACPICA: Avoid executing _PRW twice for all devices
Date: Mon, 5 Jul 2010 00:56:22 +0200 [thread overview]
Message-ID: <201007050056.22705.rjw@sisk.pl> (raw)
Hi,
Following our recent IRC discussion I thought I'd bite the bullet and prepare
a patch to remove the execution of _PRW from ACPICA and there it goes.
The series is on top of the patch I sent a couple of days ago:
https://patchwork.kernel.org/patch/110076/
[1/3] - Drops the code to walk the namespace in search of _PRW and adds
acpi_gpe_can_wake() so that the host OS can disable wakeup GPEs
previously enabled unconditionally by the ACPICA initialization code.
This basically reproduces the current behavior except that the GPEs
are temporarily enabled before acpi_bus_extract_wakeup_device_power_package()
runs for all devices with _PRW referring to them.
[2/3] - Simplifies code in acpi_ev_initialize_gpe_block(), which only is a
cosmetic thing, but worth doing IMO.
[3/3] - Changes acpi_gpe_wakeup() to return error code for the GPEs whose
ACPI_GPE_CAN_WAKE flags are not set.
Please apply.
Rafael
next reply other threads:[~2010-07-04 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 22:56 Rafael J. Wysocki [this message]
2010-07-04 22:59 ` [PATCH 1/3] ACPI / ACPICA: Do not execute _PRW methods during initialization Rafael J. Wysocki
2010-07-04 23:00 ` [PATCH 2/3] ACPI / ACPICA: Simplify acpi_ev_initialize_gpe_block() Rafael J. Wysocki
2010-07-04 23:01 ` [PATCH 3/3] ACPI / ACPICA: Fail acpi_gpe_wakeup() if ACPI_GPE_CAN_WAKE is unset Rafael J. Wysocki
2010-07-06 22:20 ` [PATCH 0/3] ACPI / ACPICA: Avoid executing _PRW twice for all devices Len Brown
2010-07-06 23:59 ` Rafael J. Wysocki
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=201007050056.22705.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ming.m.lin@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=robert.moore@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