From: Tore Anderson <tore@fud.no>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389
Date: Sat, 5 Mar 2016 10:09:00 +0100 [thread overview]
Message-ID: <20160305100900.0b097304@envy.w5.y.home> (raw)
In-Reply-To: <20160304065406.GA17899@t440s.P-661HNU-F1>
Hi Johan,
> It's a relief to hear that the issue seems to be fixed, but it would
> indeed be good to get to the bottom of this and understand what
> exactly fixed it, since I can't right now remember any recent patches
> that would have influenced this behavior (who knows - maybe it's
> something external to the Bluetooth subsystem).
It got fixed by:
commit d82142a8b1338e6a4339920863423379c27b0b16
Author: Wei-Ning Huang <wnhuang@chromium.org>
Date: Mon Feb 15 17:09:51 2016 +0800
Bluetooth: hci_core: cancel power off delayed work properly
When the HCI_AUTO_OFF flag is cleared, the power_off delayed work need
to be cancel or HCI will be powered off even if it's managed.
Signed-off-by: Wei-Ning Huang <wnhuang@chromium.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Tore
prev parent reply other threads:[~2016-03-05 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 17:12 PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389 Tore Anderson
2016-02-20 18:23 ` Johan Hedberg
2016-02-20 18:29 ` Johan Hedberg
2016-02-20 20:30 ` Tore Anderson
2016-02-21 7:02 ` Johan Hedberg
2016-02-21 11:13 ` Tore Anderson
2016-03-03 7:51 ` Tore Anderson
2016-03-03 8:42 ` Johan Hedberg
2016-03-03 20:44 ` Tore Anderson
2016-03-04 6:54 ` Johan Hedberg
2016-03-05 9:09 ` Tore Anderson [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=20160305100900.0b097304@envy.w5.y.home \
--to=tore@fud.no \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 NNTP newsgroup(s).