From: "Geoffrey D. Bennett" <g@b4.vu>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Hao Qin <hao.qin@mediatek.com>
Cc: linux-bluetooth@vger.kernel.org,
Sean Wang <sean.wang@mediatek.com>,
Chris Lu <chris.lu@mediatek.com>,
linux-sound@vger.kernel.org, Benedikt Ziemons <ben@rs485.network>
Subject: [PATCH 0/2] Fix for MediaTek reset affecting Focusrite audio interfaces
Date: Sun, 9 Mar 2025 06:02:11 +1030 [thread overview]
Message-ID: <Z8ybO7DfeP3Ag9wz@m.b4.vu> (raw)
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
next reply other threads:[~2025-03-08 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 19:32 Geoffrey D. Bennett [this message]
2025-03-10 21:24 ` [PATCH 0/2] Fix for MediaTek reset affecting Focusrite audio interfaces Geraldo Nascimento
2025-03-12 1:53 ` Luiz Augusto von Dentz
2025-03-13 1:43 ` Benedikt Ziemons
2025-03-13 7:13 ` Geoffrey D. Bennett
2025-03-13 12:07 ` Benedikt Ziemons
2025-03-13 8:08 ` Paul Menzel
2025-03-13 9:05 ` Chris Lu (陸稚泓)
2025-03-13 10:06 ` gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z8ybO7DfeP3Ag9wz@m.b4.vu \
--to=g@b4.vu \
--cc=ben@rs485.network \
--cc=chris.lu@mediatek.com \
--cc=hao.qin@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox