* [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware
@ 2026-09-04 5:30 Ivan Hu
2026-09-04 16:56 ` patchwork-bot+bluetooth
0 siblings, 1 reply; 2+ messages in thread
From: Ivan Hu @ 2026-09-04 5:30 UTC (permalink / raw)
To: marcel, luiz.dentz, peter.tsao
Cc: matthias.bgg, angelogioacchino.delregno, linux-bluetooth,
linux-kernel, linux-arm-kernel, linux-mediatek
btmtk_fw_get_filename() constructs the firmware name at runtime, so for
the MT7920 variant (dev_id 0x7961 with fw_flavor set) it requests
"mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin" without ever declaring it via
MODULE_FIRMWARE(). Tools that select firmware from module metadata (e.g.
"modinfo -F firmware") therefore omit this blob, so request_firmware()
fails and Bluetooth does not initialise on MT7920, even though the file
is present in linux-firmware.
Declare it with MODULE_FIRMWARE(), as the mt76 driver already does for
the corresponding MT7920 wifi firmware.
Fixes: 1cb63d80fff6 ("Bluetooth: btusb: Add support Mediatek MT7920")
Signed-off-by: Ivan Hu <ivan.hu@canonical.com>
---
drivers/bluetooth/btmtk.c | 1 +
drivers/bluetooth/btmtk.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c
index ea0c320f9827..911aba5c134e 100644
--- a/drivers/bluetooth/btmtk.c
+++ b/drivers/bluetooth/btmtk.c
@@ -1581,5 +1581,6 @@ MODULE_FIRMWARE(FIRMWARE_MT7663);
MODULE_FIRMWARE(FIRMWARE_MT7668);
MODULE_FIRMWARE(FIRMWARE_MT7922);
MODULE_FIRMWARE(FIRMWARE_MT7961);
+MODULE_FIRMWARE(FIRMWARE_MT7920);
MODULE_FIRMWARE(FIRMWARE_MT7925);
MODULE_FIRMWARE(FIRMWARE_MT7927);
diff --git a/drivers/bluetooth/btmtk.h b/drivers/bluetooth/btmtk.h
index c83c24897c95..bc26148ec544 100644
--- a/drivers/bluetooth/btmtk.h
+++ b/drivers/bluetooth/btmtk.h
@@ -7,6 +7,7 @@
#define FIRMWARE_MT7922 "mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin"
#define FIRMWARE_MT7902 "mediatek/BT_RAM_CODE_MT7902_1_1_hdr.bin"
#define FIRMWARE_MT7961 "mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin"
+#define FIRMWARE_MT7920 "mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin"
#define FIRMWARE_MT7925 "mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin"
#define FIRMWARE_MT7927 "mediatek/mt7927/BT_RAM_CODE_MT6639_2_1_hdr.bin"
--
2.53.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware
2026-09-04 5:30 [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware Ivan Hu
@ 2026-09-04 16:56 ` patchwork-bot+bluetooth
0 siblings, 0 replies; 2+ messages in thread
From: patchwork-bot+bluetooth @ 2026-09-04 16:56 UTC (permalink / raw)
To: Ivan Hu
Cc: marcel, luiz.dentz, peter.tsao, matthias.bgg,
angelogioacchino.delregno, linux-bluetooth, linux-kernel,
linux-arm-kernel, linux-mediatek
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 4 Sep 2026 13:30:07 +0800 you wrote:
> btmtk_fw_get_filename() constructs the firmware name at runtime, so for
> the MT7920 variant (dev_id 0x7961 with fw_flavor set) it requests
> "mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin" without ever declaring it via
> MODULE_FIRMWARE(). Tools that select firmware from module metadata (e.g.
> "modinfo -F firmware") therefore omit this blob, so request_firmware()
> fails and Bluetooth does not initialise on MT7920, even though the file
> is present in linux-firmware.
>
> [...]
Here is the summary with links:
- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware
https://git.kernel.org/bluetooth/bluetooth-next/c/860043e48274
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-04 16:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-04 5:30 [PATCH] Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware Ivan Hu
2026-09-04 16:56 ` patchwork-bot+bluetooth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox