From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Gustavo Evgucci <monesss315@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: btusb: Add IMC Networks MT7922 device 0x13d3:0x3625
Date: Tue, 23 Jun 2026 16:48:47 +0200 [thread overview]
Message-ID: <14bafb2e-2d12-4022-a6f9-8fff962b82dd@molgen.mpg.de> (raw)
In-Reply-To: <20260623114937.6385-1-monesss315@gmail.com>
Dear Gustavo,
Thank you for your patch. Just a note to add all listed MAINTAINERS
entries to the receivers (`scripts/get_maintainer.pl
drivers/bluetooth/btusb.c`).
Am 23.06.26 um 13:49 schrieb monesss315:
> From: Gustavo Evgucci <monesss315@gmail.com>
>
> The IMC Networks MT7922 Bluetooth adapter with USB ID 13d3:3625 is not
> recognized as a MediaTek device because it is missing from the btusb
> device ID table. As a result, btmtk firmware loading is never triggered
> and the HCI reset command times out with -ETIMEDOUT.
>
> Add the device with BTUSB_MEDIATEK | BTUSB_WIDEBAND_SPEECH flags,
> consistent with the neighboring 13d3:3627, 13d3:3628 and 13d3:3630
> entries which use the same chip.
>
> Tested on: MediaTek MT7922 (Wi-Fi 6E combo card, IMC Networks BT USB
> interface), kernel 7.0.11-arch1-1.
It’s common to add the output of `/sys/kernel/debug/usb/devices` to the
commit message, cf `git log drivers/bluetooth/btusb.c`.
> Signed-off-by: Gustavo Evgucci <monesss315@gmail.com>
> ---
> drivers/bluetooth/btusb.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -755,6 +755,8 @@ static const struct usb_device_id btusb_table[] = {
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x13d3, 0x3613), .driver_info = BTUSB_MEDIATEK |
> BTUSB_WIDEBAND_SPEECH },
> + { USB_DEVICE(0x13d3, 0x3625), .driver_info = BTUSB_MEDIATEK |
> + BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x13d3, 0x3627), .driver_info = BTUSB_MEDIATEK |
> BTUSB_WIDEBAND_SPEECH },
> { USB_DEVICE(0x13d3, 0x3628), .driver_info = BTUSB_MEDIATEK |
Feel free to add:
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
next parent reply other threads:[~2026-06-23 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260623114937.6385-1-monesss315@gmail.com>
2026-06-23 14:48 ` Paul Menzel [this message]
2026-06-25 8:32 ` [PATCH v2] Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922 Gustavo Evgucci
2026-06-26 11:16 ` patchwork-bot+bluetooth
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=14bafb2e-2d12-4022-a6f9-8fff962b82dd@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=monesss315@gmail.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
all inboxes | Powered by JetHome®