From: Nikolay Bryskin <nbryskin@gmail.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Hans de Goede <hansg@kernel.org>,
linux-bluetooth@vger.kernel.org,
Bartosz Golaszewski <brgl@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Rocky Liao <quic_rjliao@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: Reprobe QCA6390 after hibernation
Date: Sun, 25 Oct 2026 23:30:13 +0200 [thread overview]
Message-ID: <20261025213013.12956-1-nbryskin@gmail.com> (raw)
In-Reply-To: <atXiYxot6UZ3MDrp@makrotopia.org>
Hi Daniel,
On Mon, Oct 19, 2026 at 09:30:06AM +0000, Daniel Golle wrote:
> Would you be fine basing your patch on it once it has landed?
Yes, thanks for the review. I'll send v2 on top of
device_schedule_reprobe() once it has landed, with qca_restore() as
you suggest.
I tried the combination in the meantime: v4 1/4 plus hci_qca converted
as above, on 7.2.11 on a Dell XPS 13 9310 (QCA6390 on UART, no BT_EN
GPIO). After resume from hibernation the reprobe ran, the firmware was
downloaded again and Bluetooth worked; s2idle suspend did not trigger
a reprobe. I've replied to 1/4 with a Tested-by.
Nikolay
prev parent reply other threads:[~2026-10-25 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 17:43 [PATCH] Bluetooth: hci_qca: Reprobe QCA6390 after hibernation Nikolay Bryskin
2026-10-17 19:30 ` bluez.test.bot
2026-10-19 9:30 ` [PATCH] " Daniel Golle
2026-10-25 21:30 ` Nikolay Bryskin [this message]
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=20261025213013.12956-1-nbryskin@gmail.com \
--to=nbryskin@gmail.com \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel@makrotopia.org \
--cc=emmanuel.grumbach@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=quic_rjliao@quicinc.com \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.