From: Pierre Ossman <drzeus@drzeus.cx>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
matthew@wil.cx,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org, linux-acpi@vger.kernel.org,
Adam Belay <ambx1@neo.rr.com>,
Matthieu Castet <castet.matthieu@free.fr>,
Li Shaohua <shaohua.li@intel.com>, Len Brown <lenb@kernel.org>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: PNP: do not stop/start devices in suspend/resume path
Date: Thu, 13 Dec 2007 09:26:21 +0100 [thread overview]
Message-ID: <20071213092621.7cf6ee87@poseidon.drzeus.cx> (raw)
In-Reply-To: <200712061625.57660.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On Thu, 6 Dec 2007 16:25:57 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> PNP: do not stop/start devices in suspend/resume path
>
> Do not disable PNP devices in the suspend path. We still call
> the driver's suspend method, which should prevent further use of
> the device, and the protocol suspend method, which may put the
> device in a low-power state.
>
> I'm told that Windows puts devices in a low-power state (Linux
> does this in the protocol suspend method), but does not use _DIS
> in the suspend path. Other relevant references:
>
> - In the ACPI 3.0b spec, I can't find any mention of _DIS in
> connection with sleep. And Device Object Notifications,
> Section 5.6.3, Table 5-43, says we should get a bus check
> after awakening if hardware was removed while we slept.
>
> - This: http://msdn2.microsoft.com/en-us/library/ms810079.aspx
> makes a similar point about how the OS re-enumerates devices
> as a result of a power state change (3rd last paragraph of
> text).
>
> - This: http://msdn2.microsoft.com/en-us/library/aa489874.aspx
> suggests that Windows only stops a device to rebalance hardware
> resources.
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
>
Tested-by: Pierre Ossman <drzeus@drzeus.cx>
No noticeable issues with suspend or hibernate using this patch.
Rgds
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-13 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 21:41 WARNING: at kernel/resource.c:189 __release_resource Jiri Slaby
2007-11-27 6:05 ` Andrew Morton
2007-11-27 12:38 ` Matthew Wilcox
2007-11-29 23:40 ` Bjorn Helgaas
2007-11-30 0:42 ` Andrew Morton
2007-11-30 21:08 ` Bjorn Helgaas
2007-11-30 22:49 ` Jiri Slaby
2007-11-30 22:58 ` Bjorn Helgaas
2007-12-01 8:12 ` Jiri Slaby
2007-12-01 12:00 ` Jiri Slaby
2007-12-05 18:24 ` RFC: PNP: do not stop/start devices in suspend/resume path Bjorn Helgaas
2007-12-05 18:50 ` Matthew Wilcox
2007-12-06 1:07 ` Rafael J. Wysocki
2007-12-06 23:25 ` Bjorn Helgaas
2007-12-12 8:16 ` Andrew Morton
2007-12-12 16:29 ` Bjorn Helgaas
2007-12-13 8:26 ` Pierre Ossman [this message]
2007-12-07 7:13 ` RFC: " Shaohua Li
2007-12-10 23:26 ` Bjorn Helgaas
2007-12-24 1:43 ` do not stop/start devices in suspend/resume path: the SCSI case Stephane Ascoet
2007-12-24 3:21 ` Bjorn Helgaas
2007-12-01 21:01 ` WARNING: at kernel/resource.c:189 __release_resource Pierre Ossman
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=20071213092621.7cf6ee87@poseidon.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=akpm@linux-foundation.org \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=jirislaby@gmail.com \
--cc=kristen.c.accardi@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=matthew@wil.cx \
--cc=rjw@sisk.pl \
--cc=shaohua.li@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;
as well as URLs for NNTP newsgroup(s).