From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH] Complain if driver reenables interrupts during drivers_[suspend|resume] & re-disable Date: Wed, 8 Feb 2006 07:46:09 +0100 Message-ID: <200602080746.10524.rjw@sisk.pl> References: <200602071906.55281.ncunningham@cyclades.com> <200602080040.41495.dtor_core@ameritech.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============40867046855434008==" Return-path: In-Reply-To: <200602080040.41495.dtor_core@ameritech.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Dmitry Torokhov Cc: Andrew Morton , Linux PM , Nigel Cunningham , linux-kernel@vger.kernel.org List-Id: linux-pm@vger.kernel.org --===============40867046855434008== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 08 February 2006 06: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). Yes, and AFAICT this is how it's supposed to be. [There was an LKML thread last year that finished with this conclusion. I think I can find it for reference, if necessary.] Greetings, Rafael --===============40867046855434008== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============40867046855434008==--