Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-2134-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218472] mt7921e bluetooth not working
Date: Sat, 24 Feb 2024 11:52:53 +0000
Message-ID: <bug-218472-62941-ESvdQ6xnoa@https.bugzilla.kernel.org/>
In-Reply-To: <bug-218472-62941@https.bugzilla.kernel.org/>
References: <bug-218472-62941@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0

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

jeremy (jeremy53561@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeremy53561@gmail.com

--- Comment #6 from jeremy (jeremy53561@gmail.com) ---
You should post results from terminal for
sudo cat /sys/kernel/debug/usb/devices| awk '/3585/' RS=3D

The bluetooth devs usually want that info.  I am guessing that you will nee=
d a
kernel patch similar to
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi=
t/commit/drivers/bluetooth/btusb.c?id=3Df0ad26ee822b197f2421462df9c358a5687=
fddfd
but it would be at about line 610 of btusb.c and be

        { USB_DEVICE(0x13d3, 0x3585), .driver_info =3D BTUSB_MEDIATEK |
                                                     BTUSB_WIDEBAND_SPEECH |
                                                     BTUSB_VALID_LE_STATES =
},

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

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