Public bug reported:
SRU justification:
[Impact]
QCA Rome Bluetooth hosts (btusb) failed to search/pair after S3.
[Fix]
The device may loses its power under S3, hence doing a USB reset upon resume
can solve the issue.
[Test Case]
With this patch, bluetooth connection always gets established after S3.
[Regression Potential]
Minimal, only QCA Rome needs this quirk. Also, reset-resume is kinda mandatory
for tons of USB devices.
** Affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => linux-oem (Ubuntu)
--
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/1734020
Title:
QCA Rome bluetooth connection cannot be established after S3
Status in linux-oem package in Ubuntu:
New
Bug description:
SRU justification:
[Impact]
QCA Rome Bluetooth hosts (btusb) failed to search/pair after S3.
[Fix]
The device may loses its power under S3, hence doing a USB reset upon resume
can solve the issue.
[Test Case]
With this patch, bluetooth connection always gets established after S3.
[Regression Potential]
Minimal, only QCA Rome needs this quirk. Also, reset-resume is kinda
mandatory for tons of USB devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1734020/+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
