From: patchwork-bot+bluetooth@kernel.org
To: Gustavo Evgucci <monesss315@gmail.com>
Cc: luiz.dentz@gmail.com, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
pmenzel@molgen.mpg.de
Subject: Re: [PATCH v2] Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922
Date: Fri, 26 Jun 2026 11:16:42 +0000 [thread overview]
Message-ID: <178247260252.3816447.15187750698312349130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260625083230.300651-1-monesss315@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 25 Jun 2026 11:32:30 +0300 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922
https://git.kernel.org/bluetooth/bluetooth-next/c/ddd25808d4c2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-06-26 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 11:49 [PATCH] Bluetooth: btusb: Add IMC Networks MT7922 device 0x13d3:0x3625 monesss315
2026-06-23 12:46 ` bluez.test.bot
2026-06-23 14:48 ` [PATCH] " Paul Menzel
2026-06-25 8:32 ` [PATCH v2] Bluetooth: btusb: Add USB ID 13d3:3625 for MediaTek MT7922 Gustavo Evgucci
2026-06-25 10:16 ` [v2] " bluez.test.bot
2026-06-26 11:16 ` patchwork-bot+bluetooth [this message]
2026-06-26 11:16 ` [PATCH] Bluetooth: btusb: Add IMC Networks MT7922 device 0x13d3:0x3625 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=178247260252.3816447.15187750698312349130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--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 \
--cc=pmenzel@molgen.mpg.de \
/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