From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
Suspend-devel list <suspend-devel@lists.sourceforge.net>
Cc: "Li, Shaohua" <shaohua.li@intel.com>,
"Zhao, Yakui" <yakui.zhao@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"andi@firstfloor.org" <andi@firstfloor.org>
Subject: ACPI suspend: test 64-bit waking vector (was Re: [PATCH] ACPI suspend: Always use the 32-bit waking vector)
Date: Mon, 15 Sep 2008 13:18:36 +0200 [thread overview]
Message-ID: <20080915111836.GA17913@elf.ucw.cz> (raw)
In-Reply-To: <200809061313.02088.rjw@sisk.pl>
Hi!
ACPI specificiation tells us that x_firmware_waking_vector is
preffered, and maybe it works better than firmware_waking_vector on
some machines.
Unfortunately, it does not seem to work on thinkpad x60... but I am
not sure if I'm not doing something wrong.
Testing/ideas would be welcome.
Pavel
diff --git a/arch/x86/kernel/acpi/sleep.c b/arch/x86/kernel/acpi/sleep.c
index 426e5d9..8ce0899 100644
--- a/arch/x86/kernel/acpi/sleep.c
+++ b/arch/x86/kernel/acpi/sleep.c
@@ -164,3 +164,24 @@ #endif
}
__setup("acpi_sleep=", acpi_sleep_setup);
+
+void acpi_pmode_wakeup(void)
+{
+ asm volatile ("\
+ cli; \
+ inb $97, %al; \
+ outb %al, $0x80; \
+ movb $3, %al; \
+ outb %al, $97; \
+ outb %al, $0x80; \
+ movb $-74, %al; \
+ outb %al, $67; \
+ outb %al, $0x80; \
+ movb $-119, %al; \
+ outb %al, $66; \
+ outb %al, $0x80; \
+ movb $15, %al; \
+ outb %al, $66; \
+ 1: jmp 1b; ");
+}
+
diff --git a/drivers/acpi/hardware/hwsleep.c b/drivers/acpi/hardware/hwsleep.c
index dba3cfb..33f157a 100644
--- a/drivers/acpi/hardware/hwsleep.c
+++ b/drivers/acpi/hardware/hwsleep.c
@@ -44,6 +44,7 @@
#include <acpi/acpi.h>
#include <acpi/actables.h>
+#include <asm/io.h>
#define _COMPONENT ACPI_HARDWARE
ACPI_MODULE_NAME("hwsleep")
@@ -60,6 +61,9 @@ ACPI_MODULE_NAME("hwsleep")
* DESCRIPTION: Access function for the firmware_waking_vector field in FACS
*
******************************************************************************/
+
+extern void acpi_pmode_wakeup(void);
+
acpi_status
acpi_set_firmware_waking_vector(acpi_physical_address physical_address)
{
@@ -80,6 +84,12 @@ acpi_set_firmware_waking_vector(acpi_phy
/* Set the vector */
+ if (facs->length < 32)
+ panic("only acpi1 supported?!");
+
+ facs->firmware_waking_vector = 0;
+ facs->xfirmware_waking_vector = virt_to_phys(acpi_pmode_wakeup);
+#if 0
if ((facs->length < 32) || (!(facs->xfirmware_waking_vector))) {
/*
* ACPI 1.0 FACS or short table or optional X_ field is zero
@@ -91,6 +101,7 @@ acpi_set_firmware_waking_vector(acpi_phy
*/
facs->xfirmware_waking_vector = physical_address;
}
+#endif
return_ACPI_STATUS(AE_OK);
}
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-09-15 12:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 5:51 [PATCH]: ACPI : Set 32bit and 64bit waking vector in FCAS table Zhao Yakui
2008-09-04 8:10 ` Rafael J. Wysocki
2008-09-04 9:18 ` Zhang Rui
2008-09-04 9:37 ` Rafael J. Wysocki
2008-09-04 12:07 ` Matthew Garrett
2008-09-05 1:17 ` Zhao Yakui
2008-09-05 1:21 ` Li, Shaohua
2008-09-05 10:48 ` Rafael J. Wysocki
2008-09-06 11:13 ` [PATCH] ACPI suspend: Always use the 32-bit waking vector Rafael J. Wysocki
2008-09-14 11:46 ` Pavel Machek
2008-09-14 23:56 ` Rafael J. Wysocki
2008-09-15 9:50 ` Pavel Machek
2008-09-17 5:46 ` Rafael J. Wysocki
2008-09-17 7:29 ` Pavel Machek
2008-09-15 11:18 ` Pavel Machek [this message]
2008-09-17 5:45 ` ACPI suspend: test 64-bit waking vector (was Re: [PATCH] ACPI suspend: Always use the 32-bit waking vector) Rafael J. Wysocki
2008-09-17 7:28 ` Pavel Machek
2008-09-17 16:58 ` Rafael J. Wysocki
2008-09-24 7:17 ` [PATCH] ACPI suspend: Always use the 32-bit waking vector Len Brown
2008-09-04 9:27 ` [PATCH]: ACPI : Set 32bit and 64bit waking vector in FCAS table Zhao Yakui
2008-09-04 9:48 ` 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=20080915111836.GA17913@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.com \
--cc=shaohua.li@intel.com \
--cc=suspend-devel@lists.sourceforge.net \
--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