All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220922] New: btusb: Add USB ID 0x13d3:0x3625 for MediaTek MT7922
Date: Mon, 29 Dec 2025 23:25:59 +0000	[thread overview]
Message-ID: <bug-220922-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=220922

            Bug ID: 220922
           Summary: btusb: Add USB ID 0x13d3:0x3625 for MediaTek MT7922
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: lucenz@proton.me
        Regression: No

USB ID 0x13d3:0x3625 (IMC Networks / Mercusys MA80XE AX3000) for MediaTek
MT7922 Bluetooth is missing from drivers/bluetooth/btusb.c.


  Without it, Bluetooth fails to initialize:

      Bluetooth: hci0: Opcode 0x0c03 failed: -110


  lsusb output:

      Bus 001 Device 002: ID 13d3:3625 IMC Networks Wireless_Device


  Fix: Add to "MediaTek MT7922 Bluetooth devices" section in btusb.c:

      { USB_DEVICE(0x13d3, 0x3625), .driver_info = BTUSB_MEDIATEK |
                                   BTUSB_WIDEBAND_SPEECH },

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2025-12-29 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 23:25 bugzilla-daemon [this message]
2025-12-29 23:33 ` [Bug 220922] btusb: Add USB ID 0x13d3:0x3625 for MediaTek MT7922 bugzilla-daemon
2025-12-31 18:32 ` bugzilla-daemon
2025-12-31 20:47 ` bugzilla-daemon
2026-01-12 19:55 ` bugzilla-daemon
2026-05-15  9:42 ` bugzilla-daemon

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=bug-220922-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.