All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Sung <jesse.sung@canonical.com>
To: linux-bluetooth@vger.kernel.org
Cc: 812132@bugs.launchpad.net
Subject: [PATCH] Bluetooth: set reset_resume handler
Date: Tue, 25 Oct 2011 16:37:38 +0800	[thread overview]
Message-ID: <4EA67552.1090703@canonical.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]


On some machines, it seems that usb hubs do not get power while
being suspended. We can get something like this in dmesg:
     usb usb2: root hub lost power or was reset

When this is the case, .reset_resume is called instead of .resume.
If .reset_resume is not set, bluetooth modules would stay in an unusable
state because the resume function is not called.

Signed-off-by: Wen-chien Jesse Sung <jesse.sung@canonical.com>
---
  drivers/bluetooth/btusb.c |    1 +
  1 files changed, 1 insertions(+), 0 deletions(-)



[-- Attachment #2: 0001-Bluetooth-set-reset_resume-handler.patch --]
[-- Type: text/x-patch, Size: 395 bytes --]

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index abfc4ee..db2a4d1 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -1220,6 +1220,7 @@ static struct usb_driver btusb_driver = {
 #ifdef CONFIG_PM
 	.suspend	= btusb_suspend,
 	.resume		= btusb_resume,
+	.reset_resume	= btusb_resume,
 #endif
 	.id_table	= btusb_table,
 	.supports_autosuspend = 1,


             reply	other threads:[~2011-10-25  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  8:37 Jesse Sung [this message]
2011-10-25  8:40 ` [PATCH] Bluetooth: set reset_resume handler Oliver Neukum
2011-10-25 11:20   ` Jesse Sung
2011-10-25 11:43     ` Oliver Neukum
2011-10-25 14:48       ` Jesse Sung
2011-10-25 18:29         ` 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=4EA67552.1090703@canonical.com \
    --to=jesse.sung@canonical.com \
    --cc=812132@bugs.launchpad.net \
    --cc=linux-bluetooth@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 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.