summaryrefslogtreecommitdiffstats
path: root/drivers/serial/8250_boca.c
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2009-06-04 22:30:48 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2009-06-15 21:44:47 -0700
commit23a54e567534d4895056df558e2564114513524a (patch)
treed2a7967bc412becb9b7dce6b48f6d468a57e10e3 /drivers/serial/8250_boca.c
parent453f77558810ffa669ed5a510a7173ec49def396 (diff)
downloadop-kernel-dev-23a54e567534d4895056df558e2564114513524a.zip
op-kernel-dev-23a54e567534d4895056df558e2564114513524a.tar.gz
USB: Avoid PM error messages during resume if a device was disconnected
Currently if a laptop is suspended e.g. while docked and then resumed after undocking it, the following errors get generated because the USB hub in the docking station and the devices connected to it are no longer available: pm_op(): usb_dev_resume+0x0/0x10 returns -19 PM: Device 1-2 failed to resume: error -19 pm_op(): usb_dev_resume+0x0/0x10 returns -19 PM: Device 1-2.2 failed to resume: error -19 pm_op(): usb_dev_resume+0x0/0x10 returns -19 PM: Device 1-2.3 failed to resume: error -19 As the removal of USB devices while a system is suspended is a relatively common use case and in most cases not an error, just return success on -ENODEV. The user gets informed anyway as the USB subsystem generates regular disconnect messages for the devices shortly afterwards: usb 1-2: USB disconnect, address 3 usb 1-2.2: USB disconnect, address 4 usblp0: removed usb 1-2.3: USB disconnect, address 5 Signed-off-by: Frans Pop <elendil@planet.nl> Acked-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/serial/8250_boca.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud