All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li Weichen" <iaadoa@gmail.com>
To: 'xuxian' <lsfdxuxian@gmail.com>,
	'Tony Lindgren' <tony@atomide.com>,
	'Jose Manuel Cano Garcia' <jcgarcia@uma.es>
Cc: 'Linux OMAP Open Source' <linux-omap-open-source@linux.omap.com>
Subject: RE: OSK5912 USB Port Problem
Date: Tue, 22 Nov 2005 16:15:22 +0800	[thread overview]
Message-ID: <4382d3a3.492a4dcd.06d7.2193@mx.gmail.com> (raw)
In-Reply-To: <43828ec8.6210a9fa.19df.1266@mx.gmail.com>

Well I encounter another problem.  If I only enable the usb host support,
the usb Flash disk works well with OSK.  But after I add the USB Gadget
support, and enables the OTG, the Flash disk doesn't work.

Is there anything wrong with OTG?

> -----Original Message-----
> From: linux-omap-open-source-bounces+iaadoa=gmail.com@linux.omap.com
> [mailto:linux-omap-open-source-bounces+iaadoa=gmail.com@linux.omap.com] On
> Behalf Of xuxian
> Sent: Tuesday, November 22, 2005 11:22 AM
> To: 'Tony Lindgren'; 'Jose Manuel Cano Garcia'
> Cc: 'Linux OMAP Open Source'
> Subject: RE: OSK5912 USB Port Problem
> 
> Hi Tony,
> 
> The patch work. Now the OSK can detect the USB key automatically.
> Thanks much.
> 
> xuxian
> 
> -----Original Message-----
> From: linux-omap-open-source-bounces+lsfdxuxian=gmail.com@linux.omap.com
> [mailto:linux-omap-open-source-bounces+lsfdxuxian=gmail.com@linux.omap.com
> ]
> On Behalf Of Tony Lindgren
> Sent: Tuesday, November 22, 2005 1:49 AM
> To: Jose Manuel Cano Garcia
> Cc: Linux OMAP Open Source
> Subject: Re: OSK5912 USB Port Problem
> 
> * 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.
> ht
> ml
> 
> Can you please check if it's caused by this combination? We should get
> Juha's patch integrated...
> 
> Tony
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> 
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source

  reply	other threads:[~2005-11-22  8:15 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
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 [this message]
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=4382d3a3.492a4dcd.06d7.2193@mx.gmail.com \
    --to=iaadoa@gmail.com \
    --cc=jcgarcia@uma.es \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=lsfdxuxian@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.