Exar usb-serial doesn't restore baud rate after resume from S3/S4

Bug #1690362 reported by Shrirang Bagul on 2017-05-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
Critical
Shrirang Bagul
linux (Ubuntu)
Critical
Unassigned
Xenial
Undecided
Unassigned

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.

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers