Public bug reported:

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 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.

** Affects: hwe-next
     Importance: Critical
     Assignee: Shrirang Bagul (shrirang-bagul)
         Status: Confirmed

** Affects: linux (Ubuntu)
     Importance: Critical
         Status: Confirmed


** Tags: originate-from-1672249 plano

** Changed in: linux (Ubuntu)
       Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1672249 plano

** Summary changed:

- 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

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
     Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

** Description changed:

- Resume from suspend-to-ram and suspend-to-disk should restore data 
send/receive over Exar usb-serial ports.
- This bug is to track the integration of the driver released by the vendor to 
fix this issue.
+ 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 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
+         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.

** Summary changed:

- 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

-- 
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:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

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 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

Reply via email to