All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215576] HSP/HFP mSBC profile broken with QCA6174
Date: Sat, 26 Feb 2022 16:21:08 +0000	[thread overview]
Message-ID: <bug-215576-62941-17zsB6vVHG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215576-62941@https.bugzilla.kernel.org/>

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

--- Comment #7 from Mike Jones (mike@mjones.io) ---
Thanks for looking into this, Luiz, and thanks wavexx for your experiments! I
can confirm the same results on my system: the first patch (codec.id =
BT_CODEC_MSBC) doesn't work, but wavexx's workaround to disable enhanced SCO
results in fully-functional mSBC.

I've managed to find a laptop with an Intel AX200, and here mSBC works fine on
an unpatched v5.16.11 kernel. So this issue doesn't seem to affect all
adapters.

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

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

  parent reply	other threads:[~2022-02-26 16:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 18:00 [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 bugzilla-daemon
2022-02-08  6:49 ` Thorsten Leemhuis
2022-03-07 11:24   ` [Bug 215576] New: HSP/HFP mSBC profile broken with QCA6174 #forregzbot Thorsten Leemhuis
2022-04-10  8:56     ` Thorsten Leemhuis
2022-05-30 10:38       ` Thorsten Leemhuis
2022-02-08  6:49 ` [Bug 215576] HSP/HFP mSBC profile broken with QCA6174 bugzilla-daemon
2022-02-09 17:27 ` bugzilla-daemon
2022-02-14 15:09 ` bugzilla-daemon
2022-02-18 14:15 ` bugzilla-daemon
2022-02-18 20:55   ` Luiz Augusto von Dentz
2022-02-18 20:55 ` bugzilla-daemon
2022-02-18 21:44   ` [Bug,215576] " bluez.test.bot
2022-02-26 15:03 ` [Bug 215576] " bugzilla-daemon
2022-02-26 15:31 ` bugzilla-daemon
2022-02-26 16:21 ` bugzilla-daemon [this message]
2022-02-27 17:00 ` bugzilla-daemon
2022-03-09 11:50 ` bugzilla-daemon
2022-03-29 20:21 ` bugzilla-daemon
2022-05-27 10:52 ` bugzilla-daemon
2022-05-27 22:59 ` bugzilla-daemon
2022-05-28  0:15 ` bugzilla-daemon
2022-05-30 11:12 ` bugzilla-daemon
2022-06-18 19:17 ` bugzilla-daemon
2022-06-19 16:46 ` bugzilla-daemon
2022-06-19 17:08 ` bugzilla-daemon
2022-06-19 17:47 ` bugzilla-daemon
2022-07-04 15:55 ` bugzilla-daemon
2022-07-05  9:30 ` 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-215576-62941-17zsB6vVHG@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.