From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216580] Jabra Elite 75t (ear buds):Unable to connect and use (`hci0: Opcode 0x 401 failed: -16`)
Date: Thu, 13 Oct 2022 21:04:01 +0000 [thread overview]
Message-ID: <bug-216580-62941-7qZVrHoZim@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216580-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216580
--- Comment #4 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
Perhaps something like the following makes more sense since what the command
was meant for is to synchronize the RFKILL of state of the host with the
controller:
diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
index a657e9a3e96a..f8be70f7924e 100644
--- a/drivers/bluetooth/btintel.c
+++ b/drivers/bluetooth/btintel.c
@@ -2597,7 +2597,7 @@ static int btintel_shutdown_combined(struct hci_dev
*hdev)
* goes off. As a workaround, sends HCI_Intel_SW_RFKILL to put the
* device in the RFKILL ON state which turns off the BT LED
immediately.
*/
- if (btintel_test_flag(hdev, INTEL_BROKEN_SHUTDOWN_LED)) {
+ if (hci_dev_test_flag(hdev, HCI_RFKILLED)) {
skb = __hci_cmd_sync(hdev, 0xfc3f, 0, NULL, HCI_INIT_TIMEOUT);
if (IS_ERR(skb)) {
ret = PTR_ERR(skb);
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-10-13 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:36 [Bug 216580] New: Jabra Elite 75t (ear buds):Unable to connect and use (`hci0: Opcode 0x 401 failed: -16`) bugzilla-daemon
2022-10-13 15:39 ` [Bug 216580] " bugzilla-daemon
2022-10-13 15:40 ` bugzilla-daemon
2022-10-13 19:44 ` bugzilla-daemon
2022-10-13 21:04 ` bugzilla-daemon [this message]
2022-10-13 21:52 ` [Bug,216580] " bluez.test.bot
2022-10-21 13:58 ` [Bug 216580] " bugzilla-daemon
2022-10-21 19:40 ` 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-216580-62941-7qZVrHoZim@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox