From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Async suspend-resume patch w/ completions (was: Re: Async suspend-resume patch w/ rwsems) Date: Sun, 20 Dec 2009 20:51:01 +0100 Message-ID: <200912202051.01328.rjw@sisk.pl> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:37581 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755899AbZLTTuY (ORCPT ); Sun, 20 Dec 2009 14:50:24 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alan Stern Cc: Linus Torvalds , Dmitry Torokhov , Zhang Rui , LKML , ACPI Devel Maling List , pm list On Sunday 20 December 2009, Alan Stern wrote: > On Sun, 20 Dec 2009, Rafael J. Wysocki wrote: > > > BTW, what's the right place to call device_enable_async_suspend() for USB > > devices? > > For USB devices, it's in drivers/usb/core/hub.c:usb_new_device() > anywhere before the call to usb_device_add(). > > For USB interfaces, it's in > drivers/usb/core/message.c:usb_set_configuration() before the call to > device_add(). > > For USB endpoints, it's in > drivers/usb/core/endpoint.c:usb_create_ep_devs() before the call to > device_register(). Thanks! > However you won't need to do it for interfaces and endpoints if you > automatically treat as async any device without suspend/resume > callbacks. I don't do that right now and I need these settings just for testing at the moment. Rafael