linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218726] qca6390 bluetooth fails after disabling/re-enabling bluetooth
Date: Wed, 17 Apr 2024 13:57:09 +0000	[thread overview]
Message-ID: <bug-218726-62941-AQDcJVJ0Mq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218726-62941@https.bugzilla.kernel.org/>

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

--- Comment #32 from Zijun Hu (quic_zijuhu@quicinc.com) ---
there are two issues as described below.

1) cold boot -> enable BT -> disable BT -> 2nd Enable BT -> 2nd Disable BT....
BT can't be enabled for 2nd and later enabled operations.

this issue is caused by below commit. i have reverted it and submit a formal
below patch
https://patchwork.kernel.org/project/bluetooth/patch/1713354823-17826-1-git-send-email-quic_zijuhu@quicinc.com/

Fixes: 56d074d26c58 ("Bluetooth: hci_qca: don't use IS_ERR_OR_NULL() with
gpiod_get_optional()")


2) cold boot (power off then power on) -> enable BT -> warm reboot after
disable BT or NOT -> enable is failed to be Enable after warm reboot.

let us explain the 2) issue we are checking as below:
your device does not have H/W reset way since BT reset pin is not configured.
so 
qca_serdev_shutdown() needs to send VSC EDL_RESET_REQ to make controller return
to initial clean state. the only reason for 2) happens is that EDL_RESET_REQ is
not sent successfully during warm reset.
let me check it.

we can get logs for issue 2) by this way.
cold boot -> enable BT -> disable BT -> unload hci_uart.ko -> dmesg kernel log
to see if EDL_RESET_REQ was sent successfully.

-- 
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:[~2024-04-17 13:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15  8:21 [Bug 218726] New: qca6390 bluetooth fails after disabling/re-enabling bluetooth bugzilla-daemon
2024-04-15  8:50 ` [Bug 218726] " bugzilla-daemon
2024-04-15  9:01 ` bugzilla-daemon
2024-04-15  9:27 ` bugzilla-daemon
2024-04-15  9:28 ` bugzilla-daemon
2024-04-15  9:34 ` bugzilla-daemon
2024-04-15 10:14 ` bugzilla-daemon
2024-04-15 10:18 ` bugzilla-daemon
2024-04-15 19:38 ` bugzilla-daemon
2024-04-15 19:59 ` bugzilla-daemon
2024-04-15 20:28 ` bugzilla-daemon
2024-04-16  1:37 ` bugzilla-daemon
2024-04-16  2:01 ` bugzilla-daemon
2024-04-16  2:18 ` bugzilla-daemon
2024-04-16  2:28 ` bugzilla-daemon
2024-04-16  7:52 ` bugzilla-daemon
2024-04-16  7:54 ` bugzilla-daemon
2024-04-16  8:08 ` bugzilla-daemon
2024-04-16  9:24 ` bugzilla-daemon
2024-04-16  9:33 ` bugzilla-daemon
2024-04-16  9:41 ` bugzilla-daemon
2024-04-16 10:11 ` bugzilla-daemon
2024-04-16 10:15 ` bugzilla-daemon
2024-04-16 12:26 ` bugzilla-daemon
2024-04-17  6:33 ` bugzilla-daemon
2024-04-17  8:18 ` bugzilla-daemon
2024-04-17  8:20 ` bugzilla-daemon
2024-04-17  8:22 ` bugzilla-daemon
2024-04-17  8:27 ` bugzilla-daemon
2024-04-17  8:28 ` bugzilla-daemon
2024-04-17  9:18 ` bugzilla-daemon
2024-04-17  9:18 ` bugzilla-daemon
2024-04-17 13:57 ` bugzilla-daemon [this message]
2024-04-17 14:08 ` bugzilla-daemon
2024-04-17 14:45 ` bugzilla-daemon
2024-04-17 15:13 ` bugzilla-daemon
2024-04-17 15:13 ` bugzilla-daemon
2024-04-18  7:22 ` bugzilla-daemon
2024-04-18  7:35 ` bugzilla-daemon
2024-04-18  7:44 ` bugzilla-daemon
2024-04-18  8:14 ` bugzilla-daemon
2024-04-18  8:26 ` bugzilla-daemon
2024-04-18  8:35 ` bugzilla-daemon
2024-04-18  8:46 ` bugzilla-daemon
2024-04-18  8:48 ` bugzilla-daemon
2024-04-18  9:11 ` bugzilla-daemon
2024-04-22  5:30 ` bugzilla-daemon
2024-04-23 23:52 ` 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-218726-62941-AQDcJVJ0Mq@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;
as well as URLs for NNTP newsgroup(s).