Skip to content

Fix for MediaTek reset affecting Focusrite audio interfaces

Geoffrey D. Bennett linux-bluetooth linux-sound regressions 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 9 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2Revert "Bluetooth: btusb: mediatek: reset the controller before downloading the fw"drivers/bluetooth/btmtk.c+0 -101 reply
2/2Bluetooth: btmtk: Remove resetting mt7922 before downloading the fwdrivers/bluetooth/btmtk.c+1 -10 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by.

PatchBenedikt Ziemons
1/2Bisected-by T-b
2/2Bisected-by T-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] Fix for MediaTek reset affecting Focusrite audio interfaces

This series (choose 1 of the 2 patches) addresses an issue where the MT7922 Bluetooth controller reset added in commit ccfc8948d7e4 ("Bluetooth: btusb: mediatek: reset the controller before downloading the fw") is causing Focusrite USB audio devices to fail to initialise when connected during boot on kernels 6.11 and newer.

Reported by three users here:
https://github.com/geoffreybennett/linux-fcp/issues/24

Two users confirmed they have an MT7922.

I'm providing two possible solutions as I note there was a similar change made in commit a7208610761a ("Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw"), so I'm not sure if the reset should be reverted for the MT7925 as well as the MT7922.

Option 1: Revert the problematic reset behaviour entirely (MT7922 + MT7925)

Option 2: Remove the reset only for the MT7922

Geoffrey D. Bennett (2):

[PATCH 1/2] Revert "Bluetooth: btusb: mediatek: reset the controller
before downloading the fw"

[PATCH 2/2] Bluetooth: btmtk: Remove resetting mt7922 before
downloading the fw

--
2.45.0