group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1734020] Re: QCA Rome bluetooth connection cannot be established after S3

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Timo Aaltonen <tjaalton@xxxxxxxxxx>
Date: Sun, 26 Nov 2017 15:25:13 -0000
Reply-to: Bug 1734020 <1734020@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: linux-oem (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1734020

Title:
  QCA Rome bluetooth connection cannot be established after S3

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Xenial:
  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/hwe-next/+bug/1734020/+subscriptions