ACK: [linux-oem] [PATCH 0/1] QCA Rome bluetooth connection cannot be established after S3

Hui Wang hui.wang at canonical.com
Thu Nov 23 06:29:02 UTC 2017


On 2017年11月23日 12:24, Kai-Heng Feng wrote:
> BugLink: https://bugs.launchpad.net/bugs/1734020
>
> [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.
>
> This patch is only needed for linux-oem to match schedule, I've already
> ask linux-stable folks to include this patch, so stable kernels will
> get this patch from stable kernel SRU.

Acked-by: Hui Wang<hui.wang at canonical.com>

>
> Leif Liddy (1):
>    Bluetooth: btusb: fix QCA Rome suspend/resume
>
>   drivers/bluetooth/btusb.c | 6 ++++++
>   1 file changed, 6 insertions(+)
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20171123/13d2fd93/attachment.html>


More information about the kernel-team mailing list