From: Wren Turkal <wt@penguintechs.org>
To: linux-bluetooth@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Zijun Hu <quic_zijuhu@quicinc.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: path to landing patch to fix warm boot issue for qca6390
Date: Mon, 6 May 2024 12:21:32 -0700 [thread overview]
Message-ID: <3475f0dd-6a0f-4319-9590-379eee33f504@penguintechs.org> (raw)
Krzysztof,
I am reaching out to you as you had the most important objections to the
change to fix qca6390 for the warm boot/module reload bug that I am
experiencing.
For context, the problem is that the hci_uart module will send specific
vendor specfic commands during shutdown of the hardware under most
situations. These VSCs put the bluetooth device into a non-working state
on my Dell XPS 13 9310 with qca6390 bluetooth hardware.
Zijun's proposed fix is to not send these commands when it's not
appropriate for the hardware. The vendor commands should be avoided when
the hardware does not have persistent configuration or when the device
is in setup state (indicating that is has never been setup and should
not be sent the VSCs on the shutdown path). This is what Zijun's patch
implements.
In addition, Zijun's change removes the influence of both
the QCA_BT_OFF qca flag and and HCI_RUNNING hdev flag. Zijun asserts
that those flags should not influence the sending of the VSCs in the
shutdown path. If I understand KK's objections properly, this is where
his objection is stemming from. KK, is this correct?
Zijun's proposed fix can be seen here:
https://patchwork.kernel.org/project/bluetooth/patch/1713932807-19619-3-git-send-email-quic_zijuhu@quicinc.com/
I'm wondering if we can resolve this impasse by splitting the change
into two changes, as follows:
1. Change that removes the influence of the QCA_BT_OFF and HCI_RUNNING
flags in the shutdown path.
2. Add the quirk from Zijun's patch that fixes my hardward configuration.
I'm hoping that better clearer descriptions for #1 can help get that
landed since the logic current appears to be at odds with how the
hardware works.
Also, I am happy to split the patches into the two patches, or (maybe
more ideally) just modify the commit message to better indicate the
reason the change. I just need guidance from maintainers so that
whatever work I do leads to something acceptable for y'all.
So, please help me get this done. I am just a user with broken hardware
and a fondness for Linux. I would love to help do what's needed to get
this fix landed.
Please help me get there,
Wren T
--
You're more amazing than you think!
next reply other threads:[~2024-05-06 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 19:21 Wren Turkal [this message]
2024-05-06 19:49 ` path to landing patch to fix warm boot issue for qca6390 Luiz Augusto von Dentz
2024-05-10 19:13 ` Wren Turkal
2024-05-10 19:48 ` Luiz Augusto von Dentz
2024-05-10 20:54 ` Wren Turkal
2024-05-10 21:25 ` Luiz Augusto von Dentz
2024-05-10 22:57 ` Paul Menzel
2024-05-10 23:20 ` Luiz Augusto von Dentz
2024-05-10 23:33 ` Wren Turkal
2024-05-11 6:25 ` Lk Sii
2024-05-13 20:13 ` Wren Turkal
2024-05-13 20:46 ` Luiz Augusto von Dentz
2024-05-14 22:17 ` Wren Turkal
2024-05-15 5:08 ` Wren Turkal
2024-05-07 6:27 ` Krzysztof Kozlowski
2024-05-07 14:34 ` 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=3475f0dd-6a0f-4319-9590-379eee33f504@penguintechs.org \
--to=wt@penguintechs.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
/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).