[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0912201434340.27137-100000@netrider.rowland.org>
Date: Sun, 20 Dec 2009 14:38:23 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Zhang Rui <rui.zhang@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: Async suspend-resume patch w/ completions (was: Re: Async
suspend-resume patch w/ rwsems)
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().
However you won't need to do it for interfaces and endpoints if you
automatically treat as async any device without suspend/resume
callbacks.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists