New: QCA Bluetooth [0cf3:e007] failed to initialize if Bluez's "[Policy] AutoEnable=true" was set

https://bugzilla.kernel.org/show_bug.cgi?id=139041

Bug ID: 139041
Summary: QCA Bluetooth [0cf3:e007] failed to initialize if
Bluez's "[Policy] AutoEnable=true" was set
Product: Drivers
Version: 2.5
Kernel Version: 4.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Currently, Ubuntu uses a udev rule, "50-bluetooth-hci-auto-poweron.rules", which uses "hciconfig hci* up" to power the device on at boot.

But that udev rule will make BT failed to pair some BLE devices [1][2].

By following Bluez's release note [3], we should use "AutoEnable=true" instead of hciconfig, and this change at least works on Intel 7260 & Intel 7265.

But it's not the case on QCA Rome [0cf3:e007], which failed to power on when Bluez tried to start adapter.

This can be solved by using hdev->setup instead of data->setup_on_usb, but looks like there are some concerns which I am not fully understand [4][5].

[1] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570
[2] https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
[3] http://www.bluez.org/release-of-bluez-5-35/
[4] https://marc.info/?l=linux-bluetooth&m=142290091920257&w=2
[5] https://marc.info/?l=linux-bluetooth&m=142316166001267&w=4

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=139041

--- Comment #1 from Kai-Heng Feng <[email protected]> --- Created attachment 224901
--> https://bugzilla.kernel.org/attachment.cgi?id=224901&action=edit
usb-devices

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=139041

--- Comment #2 from Kai-Heng Feng <[email protected]> --- Created attachment 224911
--> https://bugzilla.kernel.org/attachment.cgi?id=224911&action=edit
dmesg

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=139041

--- Comment #3 from Kai-Heng Feng <[email protected]> --- Created attachment 224921
--> https://bugzilla.kernel.org/attachment.cgi?id=224921&action=edit
journalctl -b

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=139041

--- Comment #4 from Kai-Heng Feng ([email protected]) --- Fixed by this commit:
commit c7e163fe282f34efdf77fb09b333529de97a6a10

Author: Ethan Hsieh <[email protected]>
Date:   Fri Oct 7 12:06:42 2016 +0800

    Bluetooth: btusb: Fix atheros firmware download error

    Move usb_autopm_get_interface() ahead of setup_on_usb() to prevent
    device from sending usb control message in usb suspend mode.

    The error message is as below:

    [   83.944103] btusb 1-2:1.1: usb_suspend_interface: status 0
    [   83.944107] btusb 1-2:1.0: usb_suspend_interface: status 0
    [   83.960132] usb 1-2: usb auto-suspend, wakeup 0
    [   83.976156] usb 1-2: usb_suspend_device: status 0
    [   83.976162] usb 1-2: usb_suspend_both: status 0
    [  298.689106] Bluetooth: hci0
    [  298.689399] Bluetooth: hci0: Failed to access otp area (-113)

    Signed-off-by: Ethan Hsieh <[email protected]>
    Signed-off-by: Marcel Holtmann <[email protected]>

You are receiving this mail because:
You are the assignee for the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=139041

Kai-Heng Feng ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

You are receiving this mail because:
You are the assignee for the bug.