[v4,0/4] Bluetooth: qca: fix device-address endianness

Message

Johan Hovold March 20, 2024, 7:55 a.m. UTC

The Qualcomm Bluetooth driver is configuring the device address in
reverse order for none-ROME devices, which breaks user space tools like
btmgmt and the 'local-bd-address' devicetree property.

As these Qualcomm controllers lack persistent storage for the device
address, boot firmware can use the 'local-bd-address' devicetree
property to provide a valid address. The property should specify the
address in little endian order but instead some boot firmware has been
reversing the address to match the buggy Qualcomm driver.

This specifically affects some Chromebook devices for which we now need
to maintain compatibility with the current boot firmware. As ChromeOS
updates the kernel and devicetree in lockstep, this can be done by
adding a new 'qcom,local-bd-address-broken' property that can be used to
determine if the firmware passes the address in the wrong byte order.
[1][2]

Note that this series depends on the following revert:

	https://lore.kernel.org/lkml/[e-mail]/

Also note that the devicetree patch (patch 2/4) is expected to be merged
through the Qualcomm SoC tree once the other three patches have been
picked up by the Bluetooth maintainers.

An alternative would be if Bjorn could ack the DT patch so that
everything can go in through the Bluetooth tree.

Johan


[1] https://lore.kernel.org/lkml/[e-mail]/
[2] https://lore.kernel.org/lkml/CAD=FV=[e-mail]/


Changes in v4
 - add the missing type for the new vendor property to the binding
 - move the Trogdor DT patch after the binding patch and combine the
   endianness fix and Chromium workaround to avoid having any point in
   the series where the address is reversed on those platforms as
   requested by Doug

Changes in v3
 - add a 'qcom,local-bd-address-broken' property instead of deprecating
   the current WCN3991 binding
 - mark the bluetooth address on SC7180 Trogdor Chromebooks as broken

Changes in v2
 - add quirk to handle deprecated devicetree compatibles that expect
   broken address properties
 - deprecate 'qcom,wcn3991-bt' and mark it as broken


Johan Hovold (4):
  dt-bindings: bluetooth: add 'qcom,local-bd-address-broken'
  arm64: dts: qcom: sc7180-trogdor: mark bluetooth address as broken
  Bluetooth: add quirk for broken address properties
  Bluetooth: qca: fix device-address endianness

 .../bindings/net/bluetooth/qualcomm-bluetooth.yaml     |  4 ++++
 arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi           |  2 ++
 drivers/bluetooth/btqca.c                              |  8 ++++++--
 drivers/bluetooth/hci_qca.c                            | 10 ++++++++++
 include/net/bluetooth/hci.h                            |  9 +++++++++
 net/bluetooth/hci_sync.c                               |  5 ++++-
 6 files changed, 35 insertions(+), 3 deletions(-)

Comments

[e-mail] March 26, 2024, 3:30 p.m. UTC | #1

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <[e-mail]>:

On Wed, 20 Mar 2024 08:55:50 +0100 you wrote:
> The Qualcomm Bluetooth driver is configuring the device address in
> reverse order for none-ROME devices, which breaks user space tools like
> btmgmt and the 'local-bd-address' devicetree property.
> 
> As these Qualcomm controllers lack persistent storage for the device
> address, boot firmware can use the 'local-bd-address' devicetree
> property to provide a valid address. The property should specify the
> address in little endian order but instead some boot firmware has been
> reversing the address to match the buggy Qualcomm driver.
> 
> [...]

Here is the summary with links:
  - [v4,1/4] dt-bindings: bluetooth: add 'qcom,local-bd-address-broken'
    https://git.kernel.org/bluetooth/bluetooth-next/c/ea56aab91231
  - [v4,2/4] arm64: dts: qcom: sc7180-trogdor: mark bluetooth address as broken
    https://git.kernel.org/bluetooth/bluetooth-next/c/c4406d97b78c
  - [v4,3/4] Bluetooth: add quirk for broken address properties
    https://git.kernel.org/bluetooth/bluetooth-next/c/ddaa064664fe
  - [v4,4/4] Bluetooth: qca: fix device-address endianness
    https://git.kernel.org/bluetooth/bluetooth-next/c/ff2ed85c0122

You are awesome, thank you!