From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [RFC][PATCH -mm 3/3] PM: Disable _request_firmware before hibernation/suspend Date: Mon, 28 May 2007 17:12:42 +0100 Message-ID: <20070528161242.GA1063@srcf.ucam.org> References: <20070527220158.GB22687@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Alan Stern Cc: LKML , Pavel Machek , pm list List-Id: linux-pm@vger.kernel.org On Mon, May 28, 2007 at 12:09:30PM -0400, Alan Stern wrote: > I can't speak for the second example, but there's a good reason the > first example works this way. It's not a matter of races; the problem > is that the kernel thread's job is to selectively suspend and resume > devices. We don't want it doing this while a system sleep is in > progress; it would (and in fact has, before the thread was made > freezable) cause the sleep transition to abort. How does this work on PPC or APM systems? -- Matthew Garrett | mjg59@srcf.ucam.org