[SRU] [A/B] [PATCH 0/2] Fix bluetooth (Atheros) won't connect after resume

Khaled Elmously khalid.elmously at canonical.com
Fri Feb 2 06:31:05 UTC 2018


On 2018-02-01 13:06:52 , Kai-Heng Feng wrote:
> BugLink: https://bugs.launchpad.net/bugs/1744712
> 
> [Impact]
> Bluetooth (Atheros) won't connect after resume.
> 
> [Test Case]
> Suspend/resume XPS 9360. BT controller is not functional now.
> With the fix, user confirms the issue is fixed.
> 
> [Fix]
> Reset resume the BT device.
> There was some back and forth about the approach. The original one from
> Leif Liddy causes regression on some machines. The one from Hans de
> Geode should work correctly.
> Patches previouly sent for Artful/Linux OEM is not needed.
> 
> [Regression Potential]
> Low. Limited to Atheros BT. No regression report so far since Hans'
> patch got merged upstream.
> 
> Hans de Goede (1):
>   Bluetooth: btusb: Restore QCA Rome suspend/resume fix with a
>     "rewritten" version
> 
> Kai-Heng Feng (1):
>   Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"
> 
>  drivers/bluetooth/btusb.c | 20 ++++++--------------
>  1 file changed, 6 insertions(+), 14 deletions(-)
> 
> -- 
> 2.15.1
> 
> 
> -- 
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team

Kai-Heng, I'm not sure I understand what you mean when you tag patch 1/2 for [Bionic] and tag patch 2/2 for [Artful][Bionic].

My understanding is that patch 1 is needed only for Bionic and patch 2 is needed for both - but I hadn't seen that syntax before so I didn't want to make assumptions.  Can you confirm?  Thanks.




More information about the kernel-team mailing list