public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Manuel Cano Garcia <jcgarcia@uma.es>
To: Tony Lindgren <tony@atomide.com>
Cc: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: Re: OSK5912 USB Port Problem
Date: Mon, 21 Nov 2005 19:51:10 +0100	[thread overview]
Message-ID: <4382171E.5050107@uma.es> (raw)
In-Reply-To: <20051121174914.GA7680@atomide.com>

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 <jcgarcia@uma.es> [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
>
>.
>
>  
>

  reply	other threads:[~2005-11-21 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <437d78ad.1c0496aa.28bc.29a8@mx.gmail.com>
2005-11-20 22:12 ` OSK5912 USB Port Problem Matthew Percival
2005-11-21 10:14   ` Jose Manuel Cano Garcia
2005-11-21 17:49     ` Tony Lindgren
2005-11-21 18:51       ` Jose Manuel Cano Garcia [this message]
2005-11-21 22:14       ` Matthew Percival
2005-11-21 23:56         ` Tony Lindgren
2005-11-22  3:21       ` xuxian
2005-11-22  8:15         ` Li Weichen
2005-11-24 12:45       ` Jose Manuel Cano Garcia
2005-11-22 13:30 Yves Godin
2005-11-22 13:40 ` Li Weichen

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=4382171E.5050107@uma.es \
    --to=jcgarcia@uma.es \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tony@atomide.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox