From: akpm@linux-foundation.org
To: steven@uplinklabs.net, david-b@pacbell.net, greg@kroah.com,
jeff@garzik.org, stern@rowland.harvard.edu,
mm-commits@vger.kernel.org
Subject: - ehci-pci-quirksc-dont-wait-so-long-for-bios-handoff.patch removed from -mm tree
Date: Thu, 13 Nov 2008 13:28:06 -0800 [thread overview]
Message-ID: <200811132128.mADLS6UH028290@imap1.linux-foundation.org> (raw)
The patch titled
EHCI pci-quirks.c: don't wait so long for BIOS handoff
has been removed from the -mm tree. Its filename was
ehci-pci-quirksc-dont-wait-so-long-for-bios-handoff.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: EHCI pci-quirks.c: don't wait so long for BIOS handoff
From: Steven Noonan <steven@uplinklabs.net>
Instead of waiting a painful 5000ms, quirk_usb_disable_ehci() now does a
1000ms loop to wait for the BIOS to acknowledge the handoff.
The five second delay is really quite irritating to have to deal with
every boot up, and I very seriously doubt any non-broken bios takes more
than a second to do the actual handoff.
Signed-off-by: Steven Noonan <steven@uplinklabs.net>
Cc: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>
Cc: David Brownell <david-b@pacbell.net>
Cc: Jeff Garzik <jeff@garzik.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/usb/host/pci-quirks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/usb/host/pci-quirks.c~ehci-pci-quirksc-dont-wait-so-long-for-bios-handoff drivers/usb/host/pci-quirks.c
--- a/drivers/usb/host/pci-quirks.c~ehci-pci-quirksc-dont-wait-so-long-for-bios-handoff
+++ a/drivers/usb/host/pci-quirks.c
@@ -271,7 +271,7 @@ static void __devinit quirk_usb_disable_
/* if boot firmware now owns EHCI, spin till
* it hands it over.
*/
- msec = 5000;
+ msec = 1000;
while ((cap & EHCI_USBLEGSUP_BIOS) && (msec > 0)) {
tried_handoff = 1;
msleep(10);
_
Patches currently in -mm which might be from steven@uplinklabs.net are
linux-next.patch
reply other threads:[~2008-11-13 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200811132128.mADLS6UH028290@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=steven@uplinklabs.net \
/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.