From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Neukum Subject: Re: Re: [PATCH] Remove process freezer from suspend to RAM pathway Date: Wed, 4 Jul 2007 12:53:32 +0200 Message-ID: <200707041253.33154.oliver@neukum.org> References: <20070703042916.GA17240@srcf.ucam.org> <200707041208.40735.oliver@neukum.org> <18059.31346.806801.871454@cargo.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18059.31346.806801.871454@cargo.ozlabs.ibm.com> Content-Disposition: inline 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: Paul Mackerras Cc: Matthew Garrett , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org List-Id: linux-pm@vger.kernel.org Am Mittwoch, 4. Juli 2007 schrieb Paul Mackerras: > Oliver Neukum writes: > > > You cannot simply restart the URB without thinking. > > The device after resumption may or may not be in the stage > > you left it. It needs to be rechecked and some settings must be > > renewed. You cannot simple throw an URB from an arbitrary > > stage of the protocol at it. > > Suspension of devices can only happen at some points > > in the protocol. > > Yeah, and? > > I said "the higher-level driver needs to do the sensible thing". They can't. Device specific protocols are known to the drivers only. The fact remains, remove the freezer and you need to go through all drivers. Oliver