Home
last modified time | relevance | path

Searched hist:"2 bf4086d7a7722b470aa24e1be725cc58619c6fe" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/drivers/usb/core/
H A Ddriver.cdiff 2bf4086d7a7722b470aa24e1be725cc58619c6fe Sat Jul 01 21:12:19 CDT 2006 Alan Stern <stern@rowland.harvard.edu> usbcore: set device and power states properly

This patch (as733) fixes up the places where device states and power
states are set in usbcore. Right now things are duplicated or missing;
this should straighten things out.

The idea is that udev->state is USB_STATE_SUSPENDED exactly when the
device's upstream port has been suspended, whereas
udev->dev.power.power_state.event reflects the result of the last call
to the suspend/resume routines (which might not actually change the
device state, especially if CONFIG_USB_SUSPEND isn't set).


Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
H A Dhub.cdiff 2bf4086d7a7722b470aa24e1be725cc58619c6fe Sat Jul 01 21:12:19 CDT 2006 Alan Stern <stern@rowland.harvard.edu> usbcore: set device and power states properly

This patch (as733) fixes up the places where device states and power
states are set in usbcore. Right now things are duplicated or missing;
this should straighten things out.

The idea is that udev->state is USB_STATE_SUSPENDED exactly when the
device's upstream port has been suspended, whereas
udev->dev.power.power_state.event reflects the result of the last call
to the suspend/resume routines (which might not actually change the
device state, especially if CONFIG_USB_SUSPEND isn't set).


Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>