Re: Howto debug failure to use remote wakup?

Am Mittwoch, 7. Februar 2007 18:45 schrieb Alan Stern:
> On Wed, 7 Feb 2007, Oliver Neukum wrote:

> > If the device is not bound to a driver, that is ignored.
> 
> Not so.  The attribute is checked for every device that gets suspended.  
> Of course, the device itself may choose not to report wakeup events.  If 
> it isn't configured, for instance, it won't report anything.

Sorry I got distracted by this code:

/* Caller has locked udev's pm_mutex */
static int usb_suspend_device(struct usb_device *udev, pm_message_t msg)
{
	struct usb_device_driver	*udriver;
	int				status = 0;

	if (udev->state == USB_STATE_NOTATTACHED ||
			udev->state == USB_STATE_SUSPENDED)
		goto done;

	/* For devices that don't have a driver, we do a standard suspend. */
	if (udev->dev.driver == NULL) {
		udev->do_remote_wakeup = 0;
		status = usb_port_suspend(udev);
		goto done;
	}

	Regards
		Oliver

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel