From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anand Gadiyar Subject: RE: linux-next: manual merge of the usb tree with the omap tree Date: Fri, 7 Jan 2011 20:09:45 +0530 Message-ID: References: <20101223171859.f6842045.sfr@canb.auug.org.au><4D139517.3010608@ti.com><4ce0f816f951f24ca3de9c84d9f70842@mail.gmail.com><4D271E0E.8050401@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: Sender: linux-next-owner@vger.kernel.org To: Ming Lei Cc: Benoit Cousson , Stephen Rothwell , Paul Walmsley , Greg KH , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Felipe Balbi , Tony Lindgren , linux-omap@vger.kernel.org List-Id: linux-omap@vger.kernel.org Ming Lei wrote: > 2011/1/7 Anand Gadiyar : > > Hi Ming Lei, > > > > I'm able to reproduce this on my panda, and I have it working as of > > linux-next-20101221 (the last version I tested last year) and failing > > on linux-next-20101227 (which was the very next linux-next release). > > > > Not sure why, but my Panda manages to get the VID:PID of the hub as > > well, while yours does not even get there. > > > > I may need a few more hours to debug this, unless someone beats me > > to it. ;) > > Is it caused by the below? > > [ 46.580200] ehci-omap ehci-omap.0: failed to get ehci port0 regulator > Nope. We don't set up any regulators for the PHY on Panda (at least not yet). And the working case (next-20101221) has the same log. I suspect the PHY doesn't get reset for the proper duration; I'm looking for something in that area. (Another option is to bisect between the two versions, but I'm not sure if that's any easier). - Anand