aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/usb/mon
diff options
context:
space:
mode:
authorMing Lei <tom.leiming@gmail.com>2009-02-20 21:23:09 +0800
committerGreg Kroah-Hartman <gregkh@suse.de>2009-03-24 16:20:36 -0700
commit1ded7ea47b8829a06068c3bb5e3ebe471076617a (patch)
tree113e3daefadaec5e25c7b4b8a7ce3cff23ba0327 /drivers/usb/mon
parenta227fd7db74fa05d866790a4b29ba049bb5035cc (diff)
downloadkernel_samsung_smdk4412-1ded7ea47b8829a06068c3bb5e3ebe471076617a.zip
kernel_samsung_smdk4412-1ded7ea47b8829a06068c3bb5e3ebe471076617a.tar.gz
kernel_samsung_smdk4412-1ded7ea47b8829a06068c3bb5e3ebe471076617a.tar.bz2
USB: ch341 serial: fix port number changed after resume
This patch fixes the following bug: .plug ch341 usb serial port into a hub port; .ch341 driver bound to the device and /dev/ttyUSB0 comes .open /dev/ttyUSB0 by minicom and we can use the serial successfully .suspend the ch341 usb serial device(such as: echo suspend > power/level) .resume the ch341 usb serial device (such as: echo on > power/level) .new port /dev/ttyUSB1 comes ,and the original /dev/ttyUSB0 still exists, but is no longer usable by minicom The patch adds suspend and resume callback to ch341 usb driver to prevent it from unbinding during suspend. The /dev/ttyUSB0 is not released until being closed, so /dev/ttyUSB1 comes after resume, and the original /dev/ttyUSB0 is no longer usable by minicom. It is really a mess for a minicom user. This patch also adds the reset_resume callback to make it usable after resuming from STR or hibernation, for generally STR or hibernation will make the vbus of root-hub lost. Finally enable the driver's supports_autosuspend, for the device is in working order with it. Signed-off-by: Ming Lei <tom.leiming@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/mon')
0 files changed, 0 insertions, 0 deletions