Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>:
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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
