From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: OSK5912 USB Port Problem Date: Mon, 21 Nov 2005 15:56:17 -0800 Message-ID: <20051121235617.GH7680@atomide.com> References: <437d78ad.1c0496aa.28bc.29a8@mx.gmail.com> <1132524761.8816.8.camel@localhost.localdomain> <43819DED.9030102@uma.es> <20051121174914.GA7680@atomide.com> <1132611247.8832.11.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1132611247.8832.11.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: Matthew Percival Cc: Linux OMAP Open Source List-Id: linux-omap@vger.kernel.org * Matthew Percival [051121 14:16]: > G'Day, > > > I've noticed that having CONFIG_OMAP_RESET_CLOCKS on kills OHCI at least > > on OSK. Juha's patch from few months ago probably helps with that as it > > turns on dc_clk: > > > > http://linux.omap.com/pipermail/linux-omap-open-source/2005-August/004818.html > > > > Can you please check if it's caused by this combination? We should get > > Juha's patch integrated... > > I just tried removing CONFIG_OMAP_RESET_CLOCKS, and everything worked > as expected. If I apply the above patch, then restore > CONFIG_OMAP_RESET_CLOCKS, then things still work: seems to be a Good > Thing. OK, let's wait for comments from Dave on that patch before we push it. Regards, Tony