From: Nigel Cunningham <ncunningham@cyclades.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Linux PM <linux-pm@osdl.org>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Complain if driver reenables interrupts during drivers_[suspend|resume] & re-disable
Date: Thu, 9 Feb 2006 09:58:57 +1000 [thread overview]
Message-ID: <200602090959.02015.ncunningham@cyclades.com> (raw)
In-Reply-To: <200602080040.41495.dtor_core@ameritech.net>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Hi Dmitry et al.
On Wednesday 08 February 2006 15:40, Dmitry Torokhov wrote:
> On Tuesday 07 February 2006 04:06, Nigel Cunningham wrote:
> > Hi all.
> >
> > This patch is designed to help with diagnosing and fixing the cause of
> > problems in suspending/resuming, due to drivers wrongly re-enabling
> > interrupts in their .suspend or .resume methods.
> >
> > I nearly forgot about it in sending patches in suspend2 that might help
> > where swsusp fails.
> >
>
> Only sysdevs are guaranteed to be suspebded/resumed with interrupts off,
> other devices are suspended with interrupts on (at least on first pass
> over device list).
Ok. I guess I missed that outcome of that discussion. Sorry for the
bogusness :(. Is the sysdev bit useful at all?
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-09 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 9:06 [PATCH] Complain if driver reenables interrupts during drivers_[suspend|resume] & re-disable Nigel Cunningham
2006-02-07 23:59 ` Russell King
2006-02-08 3:47 ` Benjamin Herrenschmidt
2006-02-08 5:40 ` Dmitry Torokhov
2006-02-08 6:46 ` Rafael J. Wysocki
2006-02-08 23:58 ` Nigel Cunningham [this message]
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=200602090959.02015.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.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