ACK / APPLIED[D/Unstable]: [SRU] [B/C/D/Unstable] [PATCH 0/2] Fix non-working QCA Rome Bluetooth after S3

[Seth Forshee]

On Tue, Jan 22, 2019 at 04:07:25PM +0800, Kai-Heng Feng wrote:
> BugLink: https://bugs.launchpad.net/bugs/1812812
> 
> [Impact]
> Sometimes QCA Rome Bluetooth USB host doesn't work after S3:
> [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
> [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
> 
> This is due to USB core enables LPM two times after S3.
> 
> [Fix]
> Only enable LPM once.
> 
> [Test]
> The Bluetooth USB works all the time after applying the fix.
> 
> [Regression Potential]
> Low. Enabling a hardware feature twice in a row isn't right, I'd be
> surprise if any hardware relies on this driver behavior.

Cherry picks from linux-next, seems reasonable and has positive testing.

Acked-by: Seth Forshee <seth.forshee at canonical.com>

Applied to disco/master-next and unstable/master, thanks!