mbox series

[0/1,SRU,Unstable,Oracular] Support Qualcomm WCN7851 Dual Bluetooth Adapter 0489:E0F3

Message ID 20240927045601.1816638-1-vicamo.yang@canonical.com
Headers show
Series Support Qualcomm WCN7851 Dual Bluetooth Adapter 0489:E0F3 | expand

Message

You-Sheng Yang Sept. 27, 2024, 4:56 a.m. UTC
BugLink: https://bugs.launchpad.net/bugs/2081796

[Impact]

A new Qualcomm WCN7851 variant is not currently supported.

[Fix]

Proposed fix:
https://lore.kernel.org/linux-bluetooth/20240920-btusb_add_id-v1-1-8c488ccf83ae@quicinc.com/T/#u

[Test Case]

dmesg output at boot:
```
Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
Bluetooth: hci0: QCA: patch rome 0x190200 build 0x5656, firmware rome 0x190200 build 0x43fb
Bluetooth: hci0: using NVM file: qca/nvm_usb_00190200.bin
Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
```
```
$ btmgmt info
Index list with 1 item
hci0:   Primary controller
        addr AA:BB:CC:DD:EE:FF version 12 manufacturer 29 class 0x6c0104
        supported settings: powered connectable fast-connectable discoverable
        bondable link-security ssp br/edr le advertising secure-conn debug-keys
        privacy configuration static-addr phy-configuration wide-band-speech
        cis-central cis-peripheral
        current settings: powered ssp br/edr le secure-conn cis-central
        cis-peripheral
        name localhost
        short name
hci0:   Configuration options
        supported options: public-address
        missing options:
```

[Where problems could occur]

The dmesg has:
```
Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
```
That's HCI_CONN_FLAG_REMOTE_WAKEUP, which is set when the device supports waking
up. So somehow the driver code conflicts with the flags returned from the device
firmware, meaning there might be still something wrong even we have the right
driver being loaded. It's unrelated to this patch and is still being sorting out
separately.

[Other Info]

Nominate for linux/oracular, linux-oem-6.11/noble, linux-unstable only.

Zijun Hu (1):
  UBUNTU: SAUCE: Bluetooth: btusb: Add one more ID 0x0489:0xe0f3 for
    Qualcomm WCN785x

 drivers/bluetooth/btusb.c | 3 +++
 1 file changed, 3 insertions(+)

Comments

Timo Aaltonen Oct. 2, 2024, 8:18 a.m. UTC | #1
You-Sheng Yang kirjoitti 27.9.2024 klo 7.56:
> BugLink: https://bugs.launchpad.net/bugs/2081796
> 
> [Impact]
> 
> A new Qualcomm WCN7851 variant is not currently supported.
> 
> [Fix]
> 
> Proposed fix:
> https://lore.kernel.org/linux-bluetooth/20240920-btusb_add_id-v1-1-8c488ccf83ae@quicinc.com/T/#u
> 
> [Test Case]
> 
> dmesg output at boot:
> ```
> Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
> Bluetooth: hci0: QCA: patch rome 0x190200 build 0x5656, firmware rome 0x190200 build 0x43fb
> Bluetooth: hci0: using NVM file: qca/nvm_usb_00190200.bin
> Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
> ```
> ```
> $ btmgmt info
> Index list with 1 item
> hci0:   Primary controller
>          addr AA:BB:CC:DD:EE:FF version 12 manufacturer 29 class 0x6c0104
>          supported settings: powered connectable fast-connectable discoverable
>          bondable link-security ssp br/edr le advertising secure-conn debug-keys
>          privacy configuration static-addr phy-configuration wide-band-speech
>          cis-central cis-peripheral
>          current settings: powered ssp br/edr le secure-conn cis-central
>          cis-peripheral
>          name localhost
>          short name
> hci0:   Configuration options
>          supported options: public-address
>          missing options:
> ```
> 
> [Where problems could occur]
> 
> The dmesg has:
> ```
> Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
> Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
> ```
> That's HCI_CONN_FLAG_REMOTE_WAKEUP, which is set when the device supports waking
> up. So somehow the driver code conflicts with the flags returned from the device
> firmware, meaning there might be still something wrong even we have the right
> driver being loaded. It's unrelated to this patch and is still being sorting out
> separately.
> 
> [Other Info]
> 
> Nominate for linux/oracular, linux-oem-6.11/noble, linux-unstable only.
> 
> Zijun Hu (1):
>    UBUNTU: SAUCE: Bluetooth: btusb: Add one more ID 0x0489:0xe0f3 for
>      Qualcomm WCN785x
> 
>   drivers/bluetooth/btusb.c | 3 +++
>   1 file changed, 3 insertions(+)
> 

applied to oracular, thanks
Timo Aaltonen Oct. 23, 2024, 7:34 a.m. UTC | #2
You-Sheng Yang kirjoitti 27.9.2024 klo 7.56:
> BugLink: https://bugs.launchpad.net/bugs/2081796
> 
> [Impact]
> 
> A new Qualcomm WCN7851 variant is not currently supported.
> 
> [Fix]
> 
> Proposed fix:
> https://lore.kernel.org/linux-bluetooth/20240920-btusb_add_id-v1-1-8c488ccf83ae@quicinc.com/T/#u
> 
> [Test Case]
> 
> dmesg output at boot:
> ```
> Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00190200.bin
> Bluetooth: hci0: QCA: patch rome 0x190200 build 0x5656, firmware rome 0x190200 build 0x43fb
> Bluetooth: hci0: using NVM file: qca/nvm_usb_00190200.bin
> Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
> ```
> ```
> $ btmgmt info
> Index list with 1 item
> hci0:   Primary controller
>          addr AA:BB:CC:DD:EE:FF version 12 manufacturer 29 class 0x6c0104
>          supported settings: powered connectable fast-connectable discoverable
>          bondable link-security ssp br/edr le advertising secure-conn debug-keys
>          privacy configuration static-addr phy-configuration wide-band-speech
>          cis-central cis-peripheral
>          current settings: powered ssp br/edr le secure-conn cis-central
>          cis-peripheral
>          name localhost
>          short name
> hci0:   Configuration options
>          supported options: public-address
>          missing options:
> ```
> 
> [Where problems could occur]
> 
> The dmesg has:
> ```
> Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
> Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
> ```
> That's HCI_CONN_FLAG_REMOTE_WAKEUP, which is set when the device supports waking
> up. So somehow the driver code conflicts with the flags returned from the device
> firmware, meaning there might be still something wrong even we have the right
> driver being loaded. It's unrelated to this patch and is still being sorting out
> separately.
> 
> [Other Info]
> 
> Nominate for linux/oracular, linux-oem-6.11/noble, linux-unstable only.
> 
> Zijun Hu (1):
>    UBUNTU: SAUCE: Bluetooth: btusb: Add one more ID 0x0489:0xe0f3 for
>      Qualcomm WCN785x
> 
>   drivers/bluetooth/btusb.c | 3 +++
>   1 file changed, 3 insertions(+)
> 

applied to unstable, had to be amended due to 0fec656d08aa59ad3