From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jose Manuel Cano Garcia Subject: Re: OSK5912 USB Port Problem Date: Mon, 21 Nov 2005 19:51:10 +0100 Message-ID: <4382171E.5050107@uma.es> References: <437d78ad.1c0496aa.28bc.29a8@mx.gmail.com> <1132524761.8816.8.camel@localhost.localdomain> <43819DED.9030102@uma.es> <20051121174914.GA7680@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051121174914.GA7680@atomide.com> 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: Tony Lindgren Cc: Linux OMAP Open Source List-Id: linux-omap@vger.kernel.org Hi Tony, That option was indeed active in the .config file. Let me a couple of days to recompile the 2.6.14 kernel without that option and try it again. Best regards, Jose. Tony Lindgren wrote: >* Jose Manuel Cano Garcia [051121 02:14]: > > >>Hi, >> >>I had problems with an USB flash memory, too. I tried several solutions >>and kernels which did not work until I recently read a post on the Linux >>Omap mailing list regarding USB clock malfunction on kernels >>2.6.12-2.6.14 (which were the ones I have tried). Then, I tried kernel >>2.6.11 an it worked. >> >> > >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... > >Tony > >. > > >