From: Todd Poynor <tpoynor@mvista.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.7-rc1-mm1: revert leave-runtime-suspended-devices-off-at-system-resume.patch
Date: Thu, 27 May 2004 16:34:32 -0700 [thread overview]
Message-ID: <20040527233432.GE7176@slurryseal.ddns.mvista.com> (raw)
In-Reply-To: <1085658551.1998.7.camel@teapot.felipe-alfaro.com>
On Thu, May 27, 2004 at 01:49:12PM +0200, Felipe Alfaro Solana wrote:
>
> 2.6.7-rc-mm1 includes
> "leave-runtime-suspended-devices-off-at-system-resume" which causes
> mayor problems when used on my ACPI laptop. After resuming from S3
> (STR), both the CardBus and UHCI-HCD bridges won't come up from
> suspension, rendering them completely unusable: neither my CardBus NIC,
> nor my USB mouse are recognized or functional.
Aargh, USB drivers appear to be the only drivers to modify that field, I
didn't catch that, sorry. The following patch against 2.6.6 adds a new
field for "previous state", so that drivers that modify their own
dev->power.power_state during the suspend callback will be resumed. Can
send a patch to fix 2.6.7-rc1-mm1 if desired.
--- linux-2.6.6-orig/drivers/base/power/suspend.c 2004-05-10 11:22:58.000000000 -0700
+++ linux-2.6.6-prevstate/drivers/base/power/suspend.c 2004-05-27 13:58:01.931014888 -0700
@@ -39,7 +39,9 @@
{
int error = 0;
- if (dev->bus && dev->bus->suspend)
+ dev->power.prev_state = dev->power.power_state;
+
+ if (dev->bus && dev->bus->suspend && ! dev->power.power_state)
error = dev->bus->suspend(dev,state);
if (!error) {
--- linux-2.6.6-orig/drivers/base/power/resume.c 2004-05-10 11:22:58.000000000 -0700
+++ linux-2.6.6-prevstate/drivers/base/power/resume.c 2004-05-27 14:35:03.373304328 -0700
@@ -35,7 +35,10 @@
struct list_head * entry = dpm_off.next;
struct device * dev = to_device(entry);
list_del_init(entry);
- resume_device(dev);
+
+ if (! dev->power.prev_state)
+ resume_device(dev);
+
list_add_tail(entry,&dpm_active);
}
}
--- linux-2.6.6-orig/include/linux/pm.h 2004-05-10 11:23:56.000000000 -0700
+++ linux-2.6.6-prevstate/include/linux/pm.h 2004-05-27 14:35:37.143170528 -0700
@@ -231,6 +231,7 @@
struct dev_pm_info {
#ifdef CONFIG_PM
u32 power_state;
+ u32 prev_state;
u8 * saved_state;
atomic_t pm_users;
struct device * pm_parent;
--
Todd
next prev parent reply other threads:[~2004-05-27 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 11:49 Felipe Alfaro Solana
2004-05-27 23:34 ` Todd Poynor [this message]
2004-05-28 11:03 ` Felipe Alfaro Solana
2004-05-28 18:54 ` Todd Poynor
2004-05-28 20:20 ` Greg KH
2004-05-28 21:17 ` Felipe Alfaro Solana
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=20040527233432.GE7176@slurryseal.ddns.mvista.com \
--to=tpoynor@mvista.com \
--cc=akpm@osdl.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®