[PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Javier Tia]

Add USB device IDs for the Bluetooth interface of the MediaTek MT7927
(Filogic 380) combo WiFi 7 + BT 5.4 module. The BT side uses hardware
variant 0x6639 and connects via USB.

Known devices:
- 0489:e13a - ASUS ROG Crosshair X870E Hero (Foxconn/Hon Hai)
- 0489:e0fa - Lenovo Legion Pro 7 16ARX9 (Foxconn/Hon Hai)
- 0489:e10f - Gigabyte Z790 AORUS MASTER X (Foxconn/Hon Hai)
- 0489:e116 - TP-Link Archer TBE550E PCIe (Foxconn/Hon Hai)
- 13d3:3588 - ASUS X870E-E / ProArt X870E-Creator (IMC/Azurewave)

Link: https://bugzilla.kernel.org/show_bug.cgi?id=221096
Link: https://github.com/openwrt/mt76/issues/927
Assisted-by: Claude Code <noreply@anthropic.com> [claude-opus-4-6]
Signed-off-by: Javier Tia <floss@jetm.me>
---
 drivers/bluetooth/btusb.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index a5e44887a5b5..d5e990cf8ccd 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -751,6 +751,16 @@ static const struct usb_device_id quirks_table[] = {
 						     BTUSB_WIDEBAND_SPEECH },
 	{ USB_DEVICE(0x0489, 0xe139), .driver_info = BTUSB_MEDIATEK |
 						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x0489, 0xe13a), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x0489, 0xe0fa), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x0489, 0xe10f), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x0489, 0xe116), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
+	{ USB_DEVICE(0x13d3, 0x3588), .driver_info = BTUSB_MEDIATEK |
+						     BTUSB_WIDEBAND_SPEECH },
 	{ USB_DEVICE(0x0489, 0xe14e), .driver_info = BTUSB_MEDIATEK |
 						     BTUSB_WIDEBAND_SPEECH },
 	{ USB_DEVICE(0x0489, 0xe14f), .driver_info = BTUSB_MEDIATEK |
-- 
2.53.0

Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Luiz Augusto von Dentz]

Hi Javier,

On Thu, Mar 5, 2026 at 11:33 AM Javier Tia <floss@jetm.me> wrote:
>
> Add USB device IDs for the Bluetooth interface of the MediaTek MT7927
> (Filogic 380) combo WiFi 7 + BT 5.4 module. The BT side uses hardware
> variant 0x6639 and connects via USB.
>
> Known devices:
> - 0489:e13a - ASUS ROG Crosshair X870E Hero (Foxconn/Hon Hai)
> - 0489:e0fa - Lenovo Legion Pro 7 16ARX9 (Foxconn/Hon Hai)
> - 0489:e10f - Gigabyte Z790 AORUS MASTER X (Foxconn/Hon Hai)
> - 0489:e116 - TP-Link Archer TBE550E PCIe (Foxconn/Hon Hai)
> - 13d3:3588 - ASUS X870E-E / ProArt X870E-Creator (IMC/Azurewave)

Is the lsusb information for these devices present in the links? We
normally require that to confirm these ID's are real/valid.

> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221096
> Link: https://github.com/openwrt/mt76/issues/927
> Assisted-by: Claude Code <noreply@anthropic.com> [claude-opus-4-6]

Ok, this is especially valid if AI assisted, otherwise we would
probably need to ensure the agent has access to every board to list
its IDs, etc.

Regarding the use of AI, there doesn't seem to be a global policy.
However, for Bluetooth Im not inclined to accept any patches that
hasn't been properly reviewed by the author, so if this was fully
automated and not verified by a human and I definitely don't want my
feedback to just be used as prompt to AI agents, I would do it myself
and not waste my time writing a response.

> Signed-off-by: Javier Tia <floss@jetm.me>
> ---
>  drivers/bluetooth/btusb.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index a5e44887a5b5..d5e990cf8ccd 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -751,6 +751,16 @@ static const struct usb_device_id quirks_table[] = {
>                                                      BTUSB_WIDEBAND_SPEECH },
>         { USB_DEVICE(0x0489, 0xe139), .driver_info = BTUSB_MEDIATEK |
>                                                      BTUSB_WIDEBAND_SPEECH },
> +       { USB_DEVICE(0x0489, 0xe13a), .driver_info = BTUSB_MEDIATEK |
> +                                                    BTUSB_WIDEBAND_SPEECH },
> +       { USB_DEVICE(0x0489, 0xe0fa), .driver_info = BTUSB_MEDIATEK |
> +                                                    BTUSB_WIDEBAND_SPEECH },
> +       { USB_DEVICE(0x0489, 0xe10f), .driver_info = BTUSB_MEDIATEK |
> +                                                    BTUSB_WIDEBAND_SPEECH },
> +       { USB_DEVICE(0x0489, 0xe116), .driver_info = BTUSB_MEDIATEK |
> +                                                    BTUSB_WIDEBAND_SPEECH },
> +       { USB_DEVICE(0x13d3, 0x3588), .driver_info = BTUSB_MEDIATEK |
> +                                                    BTUSB_WIDEBAND_SPEECH },
>         { USB_DEVICE(0x0489, 0xe14e), .driver_info = BTUSB_MEDIATEK |
>                                                      BTUSB_WIDEBAND_SPEECH },
>         { USB_DEVICE(0x0489, 0xe14f), .driver_info = BTUSB_MEDIATEK |
> --
> 2.53.0
>


-- 
Luiz Augusto von Dentz

Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Javier Tia]

Hi Luiz,

On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Is the lsusb information for these devices present in the links? We
> normally require that to confirm these ID's are real/valid.

Yes. Here is lsusb -v from my ASUS ROG Crosshair X870E Hero
(0489:e13a):

  Bus 001 Device 005: ID 0489:e13a Foxconn / Hon Hai Wireless_Device
  Device Descriptor:
    idVendor           0x0489 Foxconn / Hon Hai
    idProduct          0xe13a Wireless_Device
    iManufacturer           5 MediaTek Inc.
    iProduct                6 Wireless_Device
    Interface Association:
      bFunctionClass        224 Wireless
      bFunctionSubClass       1 Radio Frequency
      bFunctionProtocol       1 Bluetooth

The other four USB IDs have been confirmed by users on their hardware
with lsusb output in the tracking issue and bugzilla:

  0489:e0fa - Lenovo Legion Pro 7 (kerberos272)
  0489:e10f - Gigabyte Z790 AORUS MASTER X (Thex-Thex)
  0489:e116 - TP-Link Archer TBE550E (marcin-fm)
  13d3:3588 - ASUS ProArt X870E-Creator (samutoljamo)

Each is documented in the GitHub tracking issue [1] and the upstream
bugzilla [2] with lsusb and dmesg output.

> Ok, this is especially valid if AI assisted, otherwise we would
> probably need to ensure the agent has access to every board to list
> its IDs, etc.
>
> Regarding the use of AI, there doesn't seem to be a global policy.
> However, for Bluetooth Im not inclined to accept any patches that
> hasn't been properly reviewed by the author

Understood. To be clear: I wrote and reviewed these patches myself.
Claude Code was used as a coding assistant (editor-level help, similar
to copilot), not as an autonomous agent. The Assisted-by trailer
follows the kernel coding-assistants policy from Documentation/
process/coding-assistants.rst.

I tested the patches on my own hardware (ASUS ROG Crosshair X870E
Hero, BT 0489:e13a, Arch Linux kernel 6.19.6). The USB IDs come from
real hardware reports by real users, not generated by AI. The patches
have been running as a DKMS out-of-tree module [1] since January 2026
across Arch, Ubuntu, Fedora, NixOS, and openSUSE.

Your feedback is being read and responded to by me personally.

[1] https://github.com/jetm/mediatek-mt7927-dkms
[2] https://bugzilla.kernel.org/show_bug.cgi?id=221096

Javier

Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Luiz Augusto von Dentz]

Hi Javier,

On Thu, Mar 5, 2026 at 12:28 PM Javier Tia <floss@jetm.me> wrote:
>
> Hi Luiz,
>
> On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> > Is the lsusb information for these devices present in the links? We
> > normally require that to confirm these ID's are real/valid.
>
> Yes. Here is lsusb -v from my ASUS ROG Crosshair X870E Hero
> (0489:e13a):
>
>   Bus 001 Device 005: ID 0489:e13a Foxconn / Hon Hai Wireless_Device
>   Device Descriptor:
>     idVendor           0x0489 Foxconn / Hon Hai
>     idProduct          0xe13a Wireless_Device
>     iManufacturer           5 MediaTek Inc.
>     iProduct                6 Wireless_Device
>     Interface Association:
>       bFunctionClass        224 Wireless
>       bFunctionSubClass       1 Radio Frequency
>       bFunctionProtocol       1 Bluetooth
>
> The other four USB IDs have been confirmed by users on their hardware
> with lsusb output in the tracking issue and bugzilla:
>
>   0489:e0fa - Lenovo Legion Pro 7 (kerberos272)
>   0489:e10f - Gigabyte Z790 AORUS MASTER X (Thex-Thex)
>   0489:e116 - TP-Link Archer TBE550E (marcin-fm)
>   13d3:3588 - ASUS ProArt X870E-Creator (samutoljamo)

Let's gather their emails and list them as Tested-by, or perhaps we it
should really be multiple changes to make easier to trace back how it
was tested.

> Each is documented in the GitHub tracking issue [1] and the upstream
> bugzilla [2] with lsusb and dmesg output.
>
> > Ok, this is especially valid if AI assisted, otherwise we would
> > probably need to ensure the agent has access to every board to list
> > its IDs, etc.
> >
> > Regarding the use of AI, there doesn't seem to be a global policy.
> > However, for Bluetooth Im not inclined to accept any patches that
> > hasn't been properly reviewed by the author
>
> Understood. To be clear: I wrote and reviewed these patches myself.
> Claude Code was used as a coding assistant (editor-level help, similar
> to copilot), not as an autonomous agent. The Assisted-by trailer
> follows the kernel coding-assistants policy from Documentation/
> process/coding-assistants.rst.
>
> I tested the patches on my own hardware (ASUS ROG Crosshair X870E
> Hero, BT 0489:e13a, Arch Linux kernel 6.19.6). The USB IDs come from
> real hardware reports by real users, not generated by AI. The patches
> have been running as a DKMS out-of-tree module [1] since January 2026
> across Arch, Ubuntu, Fedora, NixOS, and openSUSE.

Ok, so Id probably require 'Tested-by' to be a human, and in this
case, I want the lsusb and dmesg | grep bluetooth either directly in
the commit message or as a Link so it can be verified.

> Your feedback is being read and responded to by me personally.
>
> [1] https://github.com/jetm/mediatek-mt7927-dkms
> [2] https://bugzilla.kernel.org/show_bug.cgi?id=221096
>
> Javier



-- 
Luiz Augusto von Dentz

Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Javier Tia]

Hi Luiz,

On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Let's gather their emails and list them as Tested-by, or perhaps we
> it should really be multiple changes to make easier to trace back
> how it was tested.

Good idea. I'll split patch 2/2 into per-device commits so each USB
ID has a clear Tested-by trail. The split will be:

  - 0489:e0fa (Lenovo Legion Pro 7)
  - 0489:e10f (Gigabyte Z790/X870E boards)
  - 0489:e116 (TP-Link Archer TBE550E)
  - 0489:e13a (ASUS X870E boards)
  - 13d3:3588 (ASUS ProArt X870E-Creator)

> Ok, so Id probably require 'Tested-by' to be a human, and in this
> case, I want the lsusb and dmesg | grep bluetooth either directly
> in the commit message or as a Link so it can be verified.

Understood. Each commit will include lsusb + dmesg snippets in the
body and a Link: tag pointing to the full hardware report.

I'm collecting the Tested-by consents now. Will send v2 once I have
them all.

Javier

Re: [PATCH 2/2] Bluetooth: btusb: Add USB device IDs for MediaTek MT7927 (MT6639)

[Javier Tia]

Hi Luiz,

On Thu, Mar 5, 2026 Luiz Augusto von Dentz wrote:
> Let's gather their emails and list them as Tested-by, or perhaps
> we it should really be multiple changes to make easier to trace
> back how it was tested.

Done. v2 splits the USB IDs into per-device commits (6 commits),
each with its own Tested-by trailer from the hardware owner.

> Ok, so Id probably require 'Tested-by' to be a human, and in this
> case, I want the lsusb and dmesg | grep bluetooth either directly
> in the commit message or as a Link so it can be verified.

Each USB ID commit in v2 includes the full USB descriptor output
from /sys/kernel/debug/usb/devices. All Tested-by trailers are
from humans who tested on their own hardware.

Tested-by coverage: 5 of 6 USB IDs have trailers. The one
exception is 0489:e110 (MSI X870E Ace Max) where the user
confirmed it works but has not provided a formal trailer yet.

v2 is sent with all requested changes.

Best,
Javier