colibri-pxa300 USB patch

colibri-pxa300 USB patch

[Marek Vasut]

On Sunday 23 January 2011 13:49:41 Bj?rn Forsman wrote:
> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
> > On Wednesday 22 December 2010 20:30:10 Bj?rn Forsman wrote:
> >> Hi,
> >> 
> >> 2010/12/22 Eric Miao <eric.y.miao@gmail.com>:
> >> > 2010/12/22 Bj?rn Forsman <bjorn.forsman@gmail.com>:
> >> >> Hi,
> >> >> 
> >> >> 2010/12/22 Eric Miao <eric.y.miao@gmail.com>:
> >> >>> 2010/12/22 Bj?rn Forsman <bjorn.forsman@gmail.com>:
> >> >>>> Hi Eric,
> >> >>>> 
> >> >>>> 2010/12/21 Bj?rn Forsman <bjorn.forsman@gmail.com>:
> >> >>>>> Hi Eric,
> >> >>>>> 
> >> >>>>> 2010/12/21 Eric Miao <eric.y.miao@gmail.com>:
> >> >>>>>> This has been merged by Marek and cherry-picked into my devel,
> >> >>>>>> thanks.
> >> >>>>> 
> >> >>>>> Thanks.
> >> >>>> 
> >> >>>> Oh, and one more thing:
> >> >>>> 
> >> >>>> Russell King syncs his tree with Linus every two days[1][2] which
> >> >>>> means ARM developers can/should base their patches on mainline.
> >> >>>> I didn't find any similar information on how you handle your
> >> >>>> pxa-linux-2.6.git tree. When and how does patches flow from
> >> >>>> your tree to mainline?
> >> >>>> 
> >> >>>> The reason I ask is that I may have some more PXA patches to post,
> >> >>>> but I don't know what tree to base it on. I'd like to use your
> >> >>>> tree, as it has improvements for colibri-pxa300, but it's
> >> >>>> difficult when you regularly(?) rebase your tree. Comments?
> >> >>> 
> >> >>> I'm basically doing rebase every -rc cycle against Linus' tree
> >> >>> instead of against Russell's, and he prefers this. Considering the
> >> >>> changes during -rc phase are normally fixing patches,
> >> >>> merge/cherry-pick/rebase are all comparatively easy. I personally
> >> >>> prefer rebase more than merge because it gives cleaner history.
> >> >> 
> >> >> Thanks for clearing that up. Now I know how you get stuff into your
> >> >> tree. But how and when do stuff get from your tree to Linus' tree?
> >> >> (I see some of the newly rebased patches in your tree are from
> >> >> august...? Shouldn't it have been in mainline by now?)
> >> > 
> >> > Will go via Russell's tree.
> >> 
> >> Ok. Thanks for explaining.
> > 
> > Hi,
> > 
> > just curious, this should make the TOP usb port or the BOTTOM one
> > working?
> 
> TOP port.

Maybe it really cannot be used with pxa310 colibri. But then I think it worked 
on their wince crap.

btw. please keep the LAKML CCed.
> 
> > I got the TOP one operational, but no luck with the bottom one on pxa310
> > colibri. Checking the colibri datasheet, there's an SMSC USB3329 chip
> > attached to usb port3 ... well did you have any luck getting the BOTTOM
> > port working ? Maybe with some further patching?
> 
> No luck with bottom port for me. Do you have a link to that datasheet?

Quick google shows some 10-page thing ... that's it.

> 
> Best regards,
> Bj?rn Forsman

colibri-pxa300 USB patch

[Bjørn Forsman]

2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
> On Sunday 23 January 2011 13:49:41 Bj?rn Forsman wrote:
>> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:

[snip git trees and workflow stuff]

>> > Hi,
>> >
>> > just curious, this should make the TOP usb port or the BOTTOM one
>> > working?
>>
>> TOP port.
>
> Maybe it really cannot be used with pxa310 colibri. But then I think it worked
> on their wince crap.

I have a Colibri PXA310 module with WinCE preflashed. I will test what
USB ports it supports on monday.

> btw. please keep the LAKML CCed.
>
>> > I got the TOP one operational, but no luck with the bottom one on pxa310
>> > colibri. Checking the colibri datasheet, there's an SMSC USB3329 chip
>> > attached to usb port3 ... well did you have any luck getting the BOTTOM
>> > port working ? Maybe with some further patching?
>>
>> No luck with bottom port for me. Do you have a link to that datasheet?
>
> Quick google shows some 10-page thing ... that's it.

Think I found it (20 pages). It says:

Colibri PXA300 only:
  - USB 2.0 device (requires external UTMI chip)
Colibri PXA310 only:
  - Built-In USB 2.0 device transceiver


And further down:

1.4.1 Colibri PXA310 only:
Wolfson WM9715L Audio-Codec
http://www.wolfsonmicro.com/

SMSC ULPI Transceiver USB3329
http://www.smsc.com/

Fairchild USB Transceiver USB1T1105
http://www.fairchildsemi.com/


So, couldn't it also be the Fairchild tranceiver? Or both??

Best regards,
Bj?rn Forsman

colibri-pxa300 USB patch

[Igor Grinberg]

Hi Guys,

On 01/23/11 16:22, Bj?rn Forsman wrote:

> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
>> On Sunday 23 January 2011 13:49:41 Bj?rn Forsman wrote:
>>> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
> [snip git trees and workflow stuff]
>
>>>> Hi,
>>>>
>>>> just curious, this should make the TOP usb port or the BOTTOM one
>>>> working?
>>> TOP port.
>> Maybe it really cannot be used with pxa310 colibri. But then I think it worked
>> on their wince crap.
> I have a Colibri PXA310 module with WinCE preflashed. I will test what
> USB ports it supports on monday.
>
>> btw. please keep the LAKML CCed.
>>
>>>> I got the TOP one operational, but no luck with the bottom one on pxa310
>>>> colibri. Checking the colibri datasheet, there's an SMSC USB3329 chip
>>>> attached to usb port3 ... well did you have any luck getting the BOTTOM
>>>> port working ? Maybe with some further patching?
>>> No luck with bottom port for me. Do you have a link to that datasheet?
>> Quick google shows some 10-page thing ... that's it.
> Think I found it (20 pages). It says:
>
> Colibri PXA300 only:
>   - USB 2.0 device (requires external UTMI chip)
> Colibri PXA310 only:
>   - Built-In USB 2.0 device transceiver
>
>
> And further down:
>
> 1.4.1 Colibri PXA310 only:
> Wolfson WM9715L Audio-Codec
> http://www.wolfsonmicro.com/
>
> SMSC ULPI Transceiver USB3329
> http://www.smsc.com/

This one is most likely the port2 transceiver (OTG),

> Fairchild USB Transceiver USB1T1105
> http://www.fairchildsemi.com/

and this one should be the port3 transceiver (Host).

>
> So, couldn't it also be the Fairchild tranceiver? Or both??
>
> Best regards,
> Bj?rn Forsman
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Regards,
Igor.

colibri-pxa300 USB patch

[Bjørn Forsman]

2011/1/23 Bj?rn Forsman <bjorn.forsman@gmail.com>:
> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
>> On Sunday 23 January 2011 13:49:41 Bj?rn Forsman wrote:
>>> 2011/1/23 Marek Vasut <marek.vasut@gmail.com>:
>
> [snip git trees and workflow stuff]
>
>>> > Hi,
>>> >
>>> > just curious, this should make the TOP usb port or the BOTTOM one
>>> > working?
>>>
>>> TOP port.
>>
>> Maybe it really cannot be used with pxa310 colibri. But then I think it worked
>> on their wince crap.
>
> I have a Colibri PXA310 module with WinCE preflashed. I will test what
> USB ports it supports on monday.

I just tested WinCE on Colibri PXA310 (in Colibri Evaluation board)
and it supports both top and bottom USB host ports.

Best regards,
Bj?rn Forsman