s3c-hsotg driver problem

s3c-hsotg driver problem

[Maurus Cuelenaere]

Hi,

I'm trying to get the USB OTG port working on my device (S3C6410 board), 
but am running into problems.
This board doesn't have a 48Mhz clock, so I set the reference clock in 
the USB PLL to a 12Mhz external crystal (see patch).

Still, I'm having trouble getting it to work; I'm seeing these messages 
(see attachment for full log):

s3c-hsotg s3c-hsotg: s3c_hsotg_rx_data: FIFO 8 bytes on ep0 but no req 
(DxEPCTl=0x00028000)
hub 1-0:1.0: connect-debounce failed, port 2 disabled

This looks like the hardware is configured correctly, but the 
currently-in-use gadget isn't setting up an EP0 RX transfer?
I've tried Mass Storage, serial, Ethernet, ... gadgets and they all give 
the same errors.

Any hints/pointers would be welcome!

Thanks,
Maurus Cuelenaere
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: att1
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100116/16919c45/attachment-0002.el>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: att2
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100116/16919c45/attachment-0003.el>

s3c-hsotg driver problem

[Barry Song]

In fact, I once used 12Mhz  external crystal, after setting PHYCLK
right,  both USB 1.1 as host and 2.0 as gadget can work. The kernel
version I used is 2.6.28.

On Sat, Jan 16, 2010 at 8:39 PM, Maurus Cuelenaere
<mcuelenaere@gmail.com> wrote:
> Hi,
>
> I'm trying to get the USB OTG port working on my device (S3C6410 board), but
> am running into problems.
> This board doesn't have a 48Mhz clock, so I set the reference clock in the
> USB PLL to a 12Mhz external crystal (see patch).
>
> Still, I'm having trouble getting it to work; I'm seeing these messages (see
> attachment for full log):
>
> s3c-hsotg s3c-hsotg: s3c_hsotg_rx_data: FIFO 8 bytes on ep0 but no req
> (DxEPCTl=0x00028000)
> hub 1-0:1.0: connect-debounce failed, port 2 disabled
>
> This looks like the hardware is configured correctly, but the
> currently-in-use gadget isn't setting up an EP0 RX transfer?
> I've tried Mass Storage, serial, Ethernet, ... gadgets and they all give the
> same errors.
>
> Any hints/pointers would be welcome!
>
> Thanks,
> Maurus Cuelenaere
>

s3c-hsotg driver problem

[Maurus Cuelenaere]

Op 17-01-10 03:00, Barry Song schreef:
> In fact, I once used 12Mhz  external crystal, after setting PHYCLK
> right,  both USB 1.1 as host and 2.0 as gadget can work. The kernel
> version I used is 2.6.28.
>    

You say the kernel version you used is 2.6.28, I'm betting you weren't 
using Ben Dooks' driver then and this was Samsung's tree?
The kernel that is currently shipped with the device I'm porting for 
(SmartQ 7) is using 2.6.24, which also has Samsung's patches applied 
(and uses other drivers than in mainline).

AFAIK there are 2 (?) 'main' trees floating around with Samsung patches: 
2.6.24 and 2.6.28, then there are 2.6.29 and 2.6.31 (and newer) trees 
which contain patches from a mix of both and mainline.

What I'm looking for is getting everything to work with *mainline* 
drivers, so in the end I can push the SmartQ boards to mainline.

Regards,
Maurus Cuelenaere

s3c-hsotg driver problem

[jassi brar]

On Sun, Jan 17, 2010 at 9:57 PM, Maurus Cuelenaere
<mcuelenaere@gmail.com> wrote:
> What I'm looking for is getting everything to work with *mainline* drivers,
> so in the end I can push the SmartQ boards to mainline.
Its sad, they have switched to a different SoC in later SmartqV series
and are phasing
out the SmartQ-5,7 series(I cudn't get one). best of luck, though.

s3c-hsotg driver problem

[Barry Song]

On Sun, Jan 17, 2010 at 8:57 PM, Maurus Cuelenaere
<mcuelenaere@gmail.com> wrote:
> Op 17-01-10 03:00, Barry Song schreef:
>>
>> In fact, I once used 12Mhz ?external crystal, after setting PHYCLK
>> right, ?both USB 1.1 as host and 2.0 as gadget can work. The kernel
>> version I used is 2.6.28.
>>
>
> You say the kernel version you used is 2.6.28, I'm betting you weren't using
> Ben Dooks' driver then and this was Samsung's tree?
Yes.
> The kernel that is currently shipped with the device I'm porting for (SmartQ
> 7) is using 2.6.24, which also has Samsung's patches applied (and uses other
> drivers than in mainline).
Yes.
>
> AFAIK there are 2 (?) 'main' trees floating around with Samsung patches:
> 2.6.24 and 2.6.28, then there are 2.6.29 and 2.6.31 (and newer) trees which
> contain patches from a mix of both and mainline.
>
> What I'm looking for is getting everything to work with *mainline* drivers,
> so in the end I can push the SmartQ boards to mainline.
That needs many merge.
>
> Regards,
> Maurus Cuelenaere
>