From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
gcoady@gmail.com, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc5-mm3
Date: Thu, 22 Dec 2005 17:05:18 -0800 [thread overview]
Message-ID: <200512221705.18618.david-b@pacbell.net> (raw)
In-Reply-To: <20051222174850.GK23837@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 109 bytes --]
> David, care to put a proper header on this and send it to me so I can
> add it to my tree?
Here you go!
[-- Attachment #2: ehci-pcd.patch --]
[-- Type: text/x-diff, Size: 814 bytes --]
On some systems, EHCI seems to be getting IRQs too early during driver
setup ... before the root hub is allocated, in particular, making trouble
for any code chasing down root hub pointers! In this case, it seems to
be safe to just ignore the root hub setting. Thanks to Rafael J. Wysocki
for getting this properly tested.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
--- g26.orig/drivers/usb/host/ehci-hcd.c 2005-12-22 16:48:57.000000000 -0800
+++ g26/drivers/usb/host/ehci-hcd.c 2005-12-22 16:57:52.000000000 -0800
@@ -617,7 +617,7 @@ static irqreturn_t ehci_irq (struct usb_
}
/* remote wakeup [4.3.1] */
- if ((status & STS_PCD) && device_may_wakeup(&hcd->self.root_hub->dev)) {
+ if (status & STS_PCD) {
unsigned i = HCS_N_PORTS (ehci->hcs_params);
/* resume root hub? */
next prev parent reply other threads:[~2005-12-23 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 7:40 2.6.15-rc5-mm3 Andrew Morton
2005-12-15 9:48 ` 2.6.15-rc5-mm3 Andi Kleen
2005-12-15 15:36 ` 2.6.15-rc5-mm3 Andi Kleen
2005-12-15 14:30 ` 2.6.15-rc5-mm3 Alexander E. Patrakov
2005-12-16 12:50 ` 2.6.15-rc5-mm3 Lenar Lõhmus
2005-12-16 23:17 ` 2.6.15-rc5-mm3 Greg KH
2005-12-17 0:15 ` 2.6.15-rc5-mm3 J.A. Magallon
2005-12-17 1:42 ` 2.6.15-rc5-mm3 Greg KH
2005-12-20 21:03 ` [PATCH] pci device sysdata may be null check in pcibus_to_node Andy Whitcroft
2005-12-20 23:16 ` Andrew Morton
2005-12-22 21:06 ` [PATCH] pci device ensure sysdata initialised Andy Whitcroft
2005-12-22 23:18 ` Greg KH
2005-12-22 23:43 ` Andy Whitcroft
2005-12-22 23:51 ` Greg KH
2005-12-22 23:56 ` Andy Whitcroft
2005-12-18 8:16 ` 2.6.15-rc5-mm3 Grant Coady
2005-12-18 11:31 ` 2.6.15-rc5-mm3 Rafael J. Wysocki
2005-12-18 19:54 ` 2.6.15-rc5-mm3 Grant Coady
2005-12-22 17:48 ` 2.6.15-rc5-mm3 Greg KH
2005-12-23 1:05 ` David Brownell [this message]
2005-12-21 23:14 ` 2.6.15-rc5-mm3 Jesper Juhl
2005-12-22 4:16 ` 2.6.15-rc5-mm3 Con Kolivas
2005-12-22 18:13 ` 2.6.15-rc5-mm3 Mattia Dongili
2005-12-29 23:46 ` 2.6.15-rc5-mm3 [BUG] smp_processor_id() in preemptible code Peter Williams
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=200512221705.18618.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=gcoady@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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