From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: linux-bluetooth@vger.kernel.org, linux-usb@vger.kernel.org
Cc: dianders@chromium.org,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Alan Stern <stern@rowland.harvard.edu>,
Hui Peng <benquike@gmail.com>,
linux-pm@vger.kernel.org, Johan Hedberg <johan.hedberg@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mark Brown <broonie@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Len Brown <len.brown@intel.com>,
Mathias Payer <mathias.payer@nebelwelt.net>,
Dmitry Torokhov <dtor@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mans Rullgard <mans@mansr.com>, Pavel Machek <pavel@ucw.cz>,
YueHaibing <yuehaibing@huawei.com>
Subject: [PATCH 0/2] Reset realtek bluetooth devices during user suspend
Date: Tue, 17 Sep 2019 14:27:00 -0700 [thread overview]
Message-ID: <20190917212702.35747-1-abhishekpandit@chromium.org> (raw)
On a Realtek USB bluetooth device, I wanted a simple and consistent way
to put the device in reset during suspend (2 reasons: to save power and
disable BT as a wakeup source). Resetting it in the suspend callback
causes a detach and the resume callback is not called. Hence the changes
in this series to do the reset in suspend_noirq.
I looked into using PERSIST and reset on resume but those seem mainly
for misbehaving devices that reset themselves.
This patch series has been tested with Realtek BT hardware as well as
Intel BT (test procedure = disable as wake source, user suspend and
observe a detach + reattach on resume).
Abhishek Pandit-Subedi (2):
usb: support suspend_noirq
Bluetooth: btusb: Reset realtek devices on user suspend
drivers/bluetooth/btusb.c | 26 ++++++++++++++++++
drivers/usb/core/driver.c | 56 +++++++++++++++++++++++++++++++++++++++
drivers/usb/core/usb.c | 6 +++++
include/linux/pm.h | 8 ++++++
include/linux/usb.h | 3 +++
5 files changed, 99 insertions(+)
--
2.23.0.237.gc6a4ce50a0-goog
next reply other threads:[~2019-09-17 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 21:27 Abhishek Pandit-Subedi [this message]
2019-09-17 21:27 ` [PATCH 1/2] usb: support suspend_noirq Abhishek Pandit-Subedi
2019-10-04 11:58 ` Greg Kroah-Hartman
2019-09-18 14:23 ` [PATCH 0/2] Reset realtek bluetooth devices during user suspend Alan Stern
2019-09-18 17:19 ` Abhishek Pandit-Subedi
2019-09-18 18:51 ` Alan Stern
2019-09-26 20:51 ` Abhishek Pandit-Subedi
2019-09-18 14:41 ` Oliver Neukum
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=20190917212702.35747-1-abhishekpandit@chromium.org \
--to=abhishekpandit@chromium.org \
--cc=benquike@gmail.com \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan.hedberg@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mans@mansr.com \
--cc=marcel@holtmann.org \
--cc=mathias.payer@nebelwelt.net \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--cc=suzuki.poulose@arm.com \
--cc=wsa@the-dreams.de \
--cc=yuehaibing@huawei.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 NNTP newsgroup(s).