Regressions List Tracking
 help / color / mirror / Atom feed
From: Zijun Hu <quic_zijuhu@quicinc.com>
To: <luiz.dentz@gmail.com>, <luiz.von.dentz@intel.com>,
	<marcel@holtmann.org>
Cc: <quic_zijuhu@quicinc.com>, <linux-bluetooth@vger.kernel.org>,
	<bartosz.golaszewski@linaro.org>,
	<krzysztof.kozlowski@linaro.org>, <wt@penguintechs.org>,
	<regressions@lists.linux.dev>, <kernel@quicinc.com>,
	<gregkh@linuxfoundation.org>, <stable@vge.kernel.org>
Subject: [PATCH v7 0/2] Fix two BT regression issues for QCA6390
Date: Wed, 24 Apr 2024 12:26:45 +0800	[thread overview]
Message-ID: <1713932807-19619-1-git-send-email-quic_zijuhu@quicinc.com> (raw)

This patch series are to fix below 2 BT regression issues for QCA6390
1) BT can't be enabled any more after below steps:
cold boot -> enable BT -> disable BT -> BT enable failure
if property enable-gpios is not configured within DT|ACPI for QCA6390.

2) BT can't be enabled after below steps:
cold boot -> enable BT -> disable BT -> warm reboot -> BT enable failure
if property enable-gpios is not configured within DT|ACPI for QCA6390.

Fix solution has been verified by the reported device Dell XPS 13 9310
laptop over below bluetooth-next tree commit as the last bugzilla comment
commit 6abf9dd26bb1 ("Bluetooth: qca: Fix triggering coredump
implementation").

These two issues were initially reported at below link:
https://lore.kernel.org/linux-bluetooth/ea20bb9b-6b60-47fc-ae42-5eed918ad7b4@quicinc.com/T/#m73d6a71d2f454bb03588c66f3ef7912274d37c6f
then reported to bugzilla as shown by below link:
https://bugzilla.kernel.org/show_bug.cgi?id=218726
the previous discussion link is listed below
https://lore.kernel.org/linux-bluetooth/1713449192-25926-2-git-send-email-quic_zijuhu@quicinc.com/

Zijun Hu (2):
  Bluetooth: qca: Fix BT enable failure for QCA6390
  Bluetooth: qca: Fix BT enable failure for QCA6390 after disable then
    warm reboot

 drivers/bluetooth/hci_qca.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

-- 
2.7.4


             reply	other threads:[~2024-04-24  4:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  4:26 Zijun Hu [this message]
2024-04-24  4:26 ` [PATCH v7 1/2] Bluetooth: qca: Fix BT enable failure for QCA6390 Zijun Hu
2024-04-24  4:30   ` Krzysztof Kozlowski
2024-04-24  5:02     ` quic_zijuhu
2024-04-24  5:05       ` quic_zijuhu
2024-04-24  5:37       ` Wren Turkal
2024-04-24  5:46         ` quic_zijuhu
2024-04-24  5:49           ` Wren Turkal
2024-04-24  6:01             ` quic_zijuhu
2024-04-24  9:39               ` quic_zijuhu
2024-04-24  9:48                 ` Krzysztof Kozlowski
2024-04-24  9:54                   ` quic_zijuhu
2024-04-24 10:34                 ` Bartosz Golaszewski
2024-04-24 11:35                   ` quic_zijuhu
2024-04-24  4:26 ` [PATCH v7 2/2] Bluetooth: qca: Fix BT enable failure for QCA6390 after disable then warm reboot Zijun Hu
2024-04-24  4:34   ` Greg KH
2024-04-26 20:42     ` Wren Turkal

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=1713932807-19619-1-git-send-email-quic_zijuhu@quicinc.com \
    --to=quic_zijuhu@quicinc.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@quicinc.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vge.kernel.org \
    --cc=wt@penguintechs.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 read-only IMAP folder(s) and NNTP newsgroup(s).