Exar usb-serial doesn't restore baud rate after resume from S3/S4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
Shrirang Bagul | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Critical
|
Unassigned | ||
linux-oem (Ubuntu) |
Fix Released
|
Undecided
|
Shrirang Bagul | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Shrirang Bagul |
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_
Version 1A, 1/9/2015
This driver will work with any USB UART function in these Exar devices:
XR21B1411
Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3]
This bug is used for tracking purposes, please do not triage.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
tags: | added: originate-from-1672249 plano |
summary: |
- Exar usb-serial doesn't restore baud rates after resume from S3/S4 + Exar usb-serial doesn't restore baudrate after resume from S3/S4 |
Changed in hwe-next: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Shrirang Bagul (shrirang-bagul) |
description: | updated |
summary: |
- Exar usb-serial doesn't restore baudrate after resume from S3/S4 + Exar usb-serial doesn't restore baud rate after resume from S3/S4 |
description: | updated |
Changed in hwe-next: | |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | New → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
Changed in hwe-next: | |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in linux-oem (Ubuntu): | |
assignee: | nobody → Shrirang Bagul (shrirang-bagul) |
status: | New → Confirmed |
Changed in linux-oem (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Bionic): | |
status: | Fix Released → Triaged |
Changed in linux (Ubuntu Bionic): | |
status: | Triaged → Fix Released |
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Released |
tags: | added: cscc |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- xenial' to 'verification- done-xenial' . If the problem still exists, change the tag 'verification- needed- xenial' to 'verification- failed- xenial' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!