https://bugzilla.kernel.org/show_bug.cgi?id=215576 --- Comment #6 from wavexx@xxxxxxxxxx --- Commit b2af264ad3af437238c9500aa830ebcafb180e05 doesn't revert cleanly anymore. Looking at the code however, it's obvious that just setting BT_CODEC_MSBC can't work, since hci_enhanced_setup_sync_conn itself only handles TRANSPARENT (which looks like it's already mSBC underneath) and CVSD. However I tried to brutally disable enhanced synchronous connection support, which is what the commit adds, by doing: > diff -rud linux-5.16.11.Orig/include/net/bluetooth/hci_core.h > linux-5.16.11/include/net/bluetooth/hci_core.h > --- linux-5.16.11.Orig/include/net/bluetooth/hci_core.h 2022-02-23 > 12:06:08.000000000 +0100 > +++ linux-5.16.11/include/net/bluetooth/hci_core.h 2022-02-26 > 16:00:44.896727458 +0100 > @@ -1465,7 +1465,8 @@ > #define use_ll_privacy(dev) ((dev)->le_features[0] & HCI_LE_LL_PRIVACY) > > /* Use enhanced synchronous connection if command is supported */ > -#define enhanced_sco_capable(dev) ((dev)->commands[29] & 0x08) > +#define enhanced_sco_capable(dev) (false) > > /* Use ext scanning if set ext scan param and ext scan enable is supported > */ > #define use_ext_scan(dev) (((dev)->commands[37] & 0x20) && \ and this "unbreaks" mSBC even on a current kernel. I'm not familiar with BT at all, but again doesn't seem to be a controller-specific issue at all. -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
