From: Jason Wessel <jason.wessel@windriver.com>
To: gregkh@suse.de
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Alan Stern <stern@rowland.harvard.edu>,
dbrownell@users.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Yinghai Lu <yinghai@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [PATCH 11/11] ehci-dbgp,ehci: Allow dbpg to work with suspend/resume
Date: Thu, 20 Aug 2009 15:39:58 -0500 [thread overview]
Message-ID: <1250800798-31559-12-git-send-email-jason.wessel@windriver.com> (raw)
In-Reply-To: <1250800798-31559-11-git-send-email-jason.wessel@windriver.com>
In order for the dbgp driver to survive suspend/resume, on every ehci
resume operation the debug controller must get re-initialized.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Cc: Greg KH <gregkh@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>
Cc: dbrownell@users.sourceforge.net
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
---
drivers/usb/host/ehci-hub.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/host/ehci-hub.c b/drivers/usb/host/ehci-hub.c
index 452380e..84b972a 100644
--- a/drivers/usb/host/ehci-hub.c
+++ b/drivers/usb/host/ehci-hub.c
@@ -204,6 +204,13 @@ static int ehci_bus_resume (struct usb_hcd *hcd)
return -ESHUTDOWN;
}
+ if (unlikely(ehci->debug)) {
+ if (ehci->debug && !dbgp_reset_prep())
+ ehci->debug = NULL;
+ else
+ dbgp_external_startup();
+ }
+
/* Ideally and we've got a real resume here, and no port's power
* was lost. (For PCI, that means Vaux was maintained.) But we
* could instead be restoring a swsusp snapshot -- so that BIOS was
--
1.6.3.1.9.g95405b
prev parent reply other threads:[~2009-08-20 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 20:39 [PATCH 0/11] V3 - x86: EHCI and earlyprintk= improvements Jason Wessel
2009-08-20 20:39 ` [PATCH 01/11] ehci,dbgp,early_printk: split ehci debug driver from early_printk.c Jason Wessel
2009-08-20 20:39 ` [PATCH 02/11] dbgp: insert cr prior to nl as needed Jason Wessel
2009-08-20 20:39 ` [PATCH 03/11] ehci-dbgp: Execute early BIOS hand off Jason Wessel
2009-08-20 20:39 ` [PATCH 04/11] dbgp: EHCI debug controller initialization delays Jason Wessel
2009-08-20 20:39 ` [PATCH 05/11] early_printk: Allow more than one early console Jason Wessel
2009-08-20 20:39 ` [PATCH 06/11] ehci-dbgp: stability improvements and external re-init Jason Wessel
2009-08-20 20:39 ` [PATCH 07/11] ehci-dbgp,ehci: Allow early or late use of the dbgp device Jason Wessel
2009-08-20 20:39 ` [PATCH 08/11] ehci-dbgp: errata for EHCI debug controller initialization Jason Wessel
2009-08-20 20:39 ` [PATCH 09/11] ehci-dbgp: errata for EHCI debug/host controller synchronization Jason Wessel
2009-08-20 20:39 ` [PATCH 10/11] ehci-dbgp,documentation: Documentation updates for ehci-dbgp Jason Wessel
2009-08-20 20:39 ` Jason Wessel [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=1250800798-31559-12-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stern@rowland.harvard.edu \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®