Skip to contentSkip to conversation

OSK5912 USB Port Problem

DISCUSSION Matthew Percival 5 participants 9 messages Nov 20, 2005 – Nov 24, 2005 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Matthew Percival

author
#1 lore raw

G'Day,

Quoted 3 lines

Thank you! I have set my USB according to your advices. Now, it seems to work properly. I mount the sda1 use the command: mount -t usbfs /dev/sda1 /proc/bus/usb/ and the devices file contain the information like this:

When you mount with -t usbfs, you are not actually mounting the device:
you are simply mounting information about your USB subsystem. It will always work, so long as you have USB in your kernel. As such, you do not need to provide a device (/dev/sda1/) and can just use `none' in this place.

Quoted 3 lines

But the problem is when I use the command mount -t vfat /dev/sda1 /tmp it always gives me an error message like this:
mount: Mounting /dev/sda1 on /tmp failed: No such device or address

I just tried using one myself (I have not used one in a while, and
wanted to double-check a couple of points), and am no longer able to mount a USb key either. Is anyone else having trouble? Perhaps something has been broken along the way: I am using 2.6.14-omap1, but have not used a USB device since around 2.6.8-omap1.

-- Matthew

#2 lore raw

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.

Quoted 33 lines · Matthew Percival

G'Day,

Quoted 3 lines

Thank you! I have set my USB according to your advices. Now, it seems to work properly. I mount the sda1 use the command: mount -t usbfs /dev/sda1 /proc/bus/usb/ and the devices file contain the information like this:

When you mount with -t usbfs, you are not actually mounting the device:
you are simply mounting information about your USB subsystem. It will always work, so long as you have USB in your kernel. As such, you do not need to provide a device (/dev/sda1/) and can just use `none' in this place.

Quoted 3 lines

But the problem is when I use the command mount -t vfat /dev/sda1 /tmp it always gives me an error message like this:
mount: Mounting /dev/sda1 on /tmp failed: No such device or address

I just tried using one myself (I have not used one in a while, and wanted to double-check a couple of points), and am no longer able to mount a USb key either. Is anyone else having trouble? Perhaps something has been broken along the way: I am using 2.6.14-omap1, but have not used a USB device since around 2.6.8-omap1.

-- Matthew

_______________________________________________
Linux-omap-open-source mailing list
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

.

#3 lore raw
Quoted 7 lines · Jose Manuel Cano Garcia

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

#4 lore raw

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.

Quoted 28 lines · Tony Lindgren
Quoted 9 lines · Jose Manuel Cano Garcia

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

.

author
#5 lore raw
In reply to Tony Lindgren

G'Day,

Quoted 8 lines

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.

-- Matthew

#6 lore raw
Quoted 8 lines · Matthew Percival

G'Day,

Quoted 6 lines

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

Quoted 7 lines
Quoted 2 lines

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

#7 lore raw
In reply to Tony Lindgren

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

Quoted 7 lines · Jose Manuel Cano Garcia

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
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

#8 lore raw

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?

Quoted 56 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] 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

Quoted 7 lines · Jose Manuel Cano Garcia

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
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

_______________________________________________
Linux-omap-open-source mailing list
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

#9 lore raw
In reply to Tony Lindgren

Hi Tony,

I had some time to test the patch with the latest kernel I could get with git (I think its 2.6.15-rc2 now). With that patch USB works OK. I think someone has tested it about a day before, but this it to confirm that it really works.

This is great for me because 2.6.11 had not driver support for the OSK5912 sound device.

Thanks,

Jose Manuel

Quoted 15 lines

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

.