Date: Tue, 09 Oct 2007 14:27:19 -0700 (PDT)
Message-Id: <20071009.142719.68041626.davem@davemloft.net>
To: stern@rowland.harvard.edu
Cc: greg@kroah.com, david-b@pacbell.net, linux-kernel@vger.kernel.org,
       linux-usb-users@lists.sourceforge.net
Subject: Re: [Linux-usb-users] OHCI root_port_reset() deadly loop...
From: David Miller <davem@davemloft.net>
In-Reply-To: <Pine.LNX.4.44L0.0710091440130.4783-100000@iolanthe.rowland.org>
References: <20071009173925.GA6062@kroah.com>
	<Pine.LNX.4.44L0.0710091440130.4783-100000@iolanthe.rowland.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1181
Lines: 29

From: Alan Stern <stern@rowland.harvard.edu>
Date: Tue, 9 Oct 2007 14:42:34 -0400 (EDT)

> On Tue, 9 Oct 2007, Greg KH wrote:
> 
> > > Anyway, it certainly would be easy enough to make port resets mutually
> > > exclusive with EHCI initialization.  That would work on any platform,
> > > PCI or not.
> > 
> > That's a good idea, any thoughts as to how to do this?  I think I can
> > find some Intel and Dell people who would be glad to test this out if
> > you have a proposed patch.
> 
> Here is a proposed patch.  I haven't tried running it, but it compiles 
> okay.

Are we sure that this is the only event that causes the conflicts between
the EHCI and it's companion virtual OHCI/UHCI host(s)?

Is there a chip reset done to the EHCI controller early during device
probe that could cause problems too?

I know it's grotty, but I definitely feel more comfortable with the
fix involving making sure EHCI loads and fully probes first.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/