From: Wren Turkal <wt@penguintechs.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Zijun Hu <quic_zijuhu@quicinc.com>,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org
Cc: linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH v1] Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot
Date: Fri, 10 May 2024 12:49:34 -0700 [thread overview]
Message-ID: <d9232cf5-b0ca-47f2-841d-45f5880368c8@penguintechs.org> (raw)
In-Reply-To: <5e5e869c-da12-4818-837e-55709f0c4db9@kernel.org>
On 5/3/24 3:16 AM, Krzysztof Kozlowski wrote:
> On 02/05/2024 16:06, Zijun Hu wrote:
>> Commit 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed
>> serdev") will cause below regression issue:
>>
>> 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.
>>
>> The commit is to fix a use-after-free issue within qca_serdev_shutdown()
>> during reboot, but also introduces this regression issue regarding above
>> steps since the VSC is not sent to reset controller during warm reboot.
>>
>> Fixed by sending the VSC to reset controller within qca_serdev_shutdown()
>> once BT was ever enabled, and the use-after-free issue is also be fixed
>> by this change since serdev is still opened when send to serdev.
>>
>> Fixes: 272970be3dab ("Bluetooth: hci_qca: Fix driver shutdown on closed serdev")
>> Cc: stable@vger.kernel.org
>> Reported-by: Wren Turkal <wt@penguintechs.org>
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218726
>> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>> Tested-by: Wren Turkal <wt@penguintechs.org>
>> ---
>> drivers/bluetooth/hci_qca.c | 5 ++---
>
> I don't think this is v1. Version your patches properly and provide
> changelog.
>
> I asked already *two times*:
> 1. On which kernel did you test it?
> 2. On which hardware did you test it?
I thought I had already chimed in with this information. I am using a
Dell XPS 13 9310. It's the only hardware I have access to. I can say
that the fix seems to work as advertised in that it fixes the warm boot
issue I have been experiencing.
As a user, I vastly prefer a one time cold boot rather than having to do
it every time. As such, I can do the test. However, I do not think that
the patch not working in that case should block landing logic that
empirically improved my experience with the hardware and minimizes the
corner case to a much smaller corner (that of warm booting from an OS
that improperly puts the device in a bad state to a Linux kernel with
this UX improvement).
wt
--
You're more amazing than you think!
next prev parent reply other threads:[~2024-05-10 19:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 14:06 [PATCH v1] Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot Zijun Hu
2024-05-03 10:16 ` Krzysztof Kozlowski
2024-05-03 18:49 ` quic_zijuhu
2024-05-10 19:49 ` Wren Turkal [this message]
2024-05-03 19:22 ` Luiz Augusto von Dentz
2024-05-03 20:18 ` quic_zijuhu
2024-05-03 21:25 ` Luiz Augusto von Dentz
2024-05-03 21:51 ` quic_zijuhu
2024-05-07 13:48 ` Lk Sii
2024-05-10 20:45 ` Wren Turkal
2024-05-11 4:09 ` Lk Sii
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=d9232cf5-b0ca-47f2-841d-45f5880368c8@penguintechs.org \
--to=wt@penguintechs.org \
--cc=krzk@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=quic_zijuhu@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=stable@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