All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Colin Leroy <colin.lkml@colino.net>
Cc: David Brownell <david-b@pacbell.net>,
	Linux-USB <linux-usb-devel@lists.sourceforge.net>,
	Colin Leroy <colin@colino.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [linux-usb-devel] [PATCH] Ohci-hcd: fix endless loop (second take)
Date: Tue, 30 Nov 2004 09:26:23 +1100	[thread overview]
Message-ID: <1101767183.15463.17.camel@gaston> (raw)
In-Reply-To: <20041129090406.5fb31933@pirandello>

On Mon, 2004-11-29 at 09:04 +0100, Colin Leroy wrote:
> On 27 Nov 2004 at 09h11, Benjamin Herrenschmidt wrote:
> 
> Hi, 
> 
> > > > It's probably a linux-wlan-ng issue... 
> > > 
> > > I suspect PPC resume issues myself.
> > 
> > Colin, you didn't tell us which controller it was ? The NEC one is a
> > totally normal off-the-shelves controller coming out of D3. The Apple
> > ones are a bit special tho.
> 
> It's the ibook G4's controller:
> [colin@jack ~]$ for i in 1 2 3 4; do cat /sys/bus/usb/devices/usb$i/product; done;
> NEC Corporation USB 2.0
> Apple Computer Inc. KeyLargo/Intrepid USB (#3)
> NEC Corporation USB
> NEC Corporation USB (#2)

Hrm... there is some problem in communication here. I asked you which
controller out of the 3 OHCIs you have in this machine is the culprit,
you give me a list of all of them but without PCI IDs ... From the
archive, I think it was USB bus #4 no ? not sure which of these
controllers it matches. 

The iBook G4 has actually 3 "Apple" OHCI's in KeyLargo/Intrepid but with
2 of them disabled by the firmware (not wired) plus one NEC USB2
controller (which contains 1 EHCI and 2 OHCIs) on the PCI bus. The code
managing their sleep process is very different.

Ben.



  reply	other threads:[~2004-11-29 22:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-26 10:30 [PATCH] Ohci-hcd: fix endless loop (second take) Colin Leroy
2004-11-26 17:28 ` [linux-usb-devel] " David Brownell
2004-11-26 17:37   ` Colin Leroy
2004-11-26 17:57     ` David Brownell
2004-11-26 22:12       ` Benjamin Herrenschmidt
2004-11-29  8:04         ` Colin Leroy
2004-11-29 22:26           ` Benjamin Herrenschmidt [this message]
2004-11-29 22:34             ` Colin Leroy
2004-11-29 22:43               ` Benjamin Herrenschmidt
2004-11-30  0:41                 ` David Brownell
2004-11-26 18:46   ` David Brownell

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=1101767183.15463.17.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=colin.lkml@colino.net \
    --cc=colin@colino.net \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.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.