** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: hwe-next
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690362
Title:
Exar usb-serial doesn't restore baud rate after resume from S3/S4
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
Resume from suspend-to-ram and suspend-to-disk should restore data
send/receive over Exar usb-serial ports. The XR21V1412 ports were using the
hardware power-on default of 9600bps
after resume from S3/S4. This patch re-initializes the baud rate and fixes
the re-connection issues after resume from S3/S4.
This bug is to track the integration of the driver released by the
vendor to fix this issue.
Changelog:
Version 1B, 11/6/2015
Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396
in xr_usb_serial_common.c).
Version 1A, 1/9/2015
This driver will work with any USB UART function in these Exar devices:
XR21V1410/1412/1414
XR21B1411
XR21B1420/1422/1424
XR22801/802/804
Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]
This bug is used for tracking purposes, please do not triage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1690362/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
