Realtek submitted a new revision for linux-next. It drops the BTUSB_VALID_LE_STATES flag in comparison to the previous revision.
In v6.11-rc5, https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aae6b81260fd9a7224f7eb4fc440d625852245bb (“Bluetooth: HCI: Invert LE State quirk to be opt-out rather then opt- in”), it changed the behaviour from “if has BTUSB_VALID_LE_STATES flag then set the HCI_QUIRK_VALID_LE_STATES flag” to “if has no BTUSB_VALID_LE_STATES flag then set the HCI_QUIRK_BROKEN_LE_STATES flag”. Later in v6.12 merge window, https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fec656d08aa59ad3ea1bba148a4f7e5618fd4d3 (“Bluetooth: btusb: Invert LE State flag to set invalid rather then valid”), it drops that BTUSB_VALID_LE_STATES and becomes “if has the BTUSB_INVALID_LE_STATES flag, then set the HCI_QUIRK_BROKEN_LE_STATES flag“. No btusb device has the flag set at the moment. This fix is not marked for linux-stable. So, any way, MT7920/MT7925 doesn't want HCI_QUIRK_BROKEN_LE_STATES to be set. Then when backported to 6.11 kernels, it should continue to carry the BTUSB_VALID_LE_STATES flag, and that flag should be dropped when migrates to v6.12. The net effect is that the patch content will be identical to the one currently being proposed for oem-6.11, unstable and linux/oracular, but the commit messages need updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078878 Title: Missing Bluetooth device IDs for new Mediatek MT7920/MT7925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078878/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
