aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/misc/iwmc3200top
diff options
context:
space:
mode:
authorSarah Sharp <sarah.a.sharp@linux.intel.com>2010-12-29 22:03:07 -0800
committerSarah Sharp <sarah.a.sharp@linux.intel.com>2011-03-13 18:07:07 -0700
commitdb7c7c0aeef51dba12d877875b8deb78d9886647 (patch)
tree09567f469abcb49861ab347ffae0685b26836db6 /drivers/misc/iwmc3200top
parentfbf9865c6d96f4a131092d2018056e86113e5cea (diff)
downloadkernel_samsung_smdk4412-db7c7c0aeef51dba12d877875b8deb78d9886647.zip
kernel_samsung_smdk4412-db7c7c0aeef51dba12d877875b8deb78d9886647.tar.gz
kernel_samsung_smdk4412-db7c7c0aeef51dba12d877875b8deb78d9886647.tar.bz2
usb: Always return 0 or -EBUSY to the runtime PM core.
The PM core reacts badly when the return code from usb_runtime_suspend() is not 0, -EAGAIN, or -EBUSY. The PM core regards this as a fatal error, and refuses to run anymore PM helper functions. In particular, usbfs_open() and other usbfs functions will fail because the PM core will return an error code when usb_autoresume_device() is called. This causes libusb and/or lsusb to either hang or segfault. If a USB device cannot suspend for some reason (e.g. a hub doesn't report it has remote wakeup capabilities), we still want lsusb and other userspace programs to work. So return -EBUSY, which will fill people's log files with failed tries, but will ensure userspace still works. Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Diffstat (limited to 'drivers/misc/iwmc3200top')
0 files changed, 0 insertions, 0 deletions