[PATCH] [kirkwood-otg] Leverage the Freescale OTG driver for Kirkwood OTG

Saeed Bishara saeed at marvell.com
Thu Jun 10 03:26:17 EDT 2010


 

>-----Original Message-----
>From: Jason McMullan [mailto:jason.mcmullan at netronome.com] 
>Sent: Wednesday, June 09, 2010 9:07 PM
>To: Nicolas Pitre
>Cc: linux-arm-kernel at lists.infradead.org; Haavard Skinnemoen; 
>Ronen Shitrit; Saeed Bishara; Rabeeh Khoury; Guennadi 
>Liakhovetski; Li Yang; Lennert Buytenhek
>Subject: Re: [PATCH] [kirkwood-otg] Leverage the Freescale OTG 
>driver for Kirkwood OTG
>
>On Wed, Jun 9, 2010 at 1:17 PM, Nicolas Pitre <nico at fluxnic.net> wrote:
>> On Wed, 9 Jun 2010, Jason S. McMullan wrote:
>>> NOTE: Your bootloader must ensure that the Kirkwood
>>>       USB 2.0 Bridge Window registers are set correctly,
>>>       or the driver will stall on the first DMA.
>>
>> Could you add the code to sets that up in the kernel instead?
The ehci-orion.c has the code for setting the DMA. Also, the Marvell
controllers have different usb phy, and the ehci-orion also has the code that
initializes the phy. So we shuold look for the methode for sharing this code
between the host mode and device mode drivers.

>
>Will do.
>
>>>  config USB_GADGET_FSL_USB2
>>
>> Maybe the help text should be extended to mention Kirkwood?
>
>Again, good idea, will do.
All the orion devices actually have the same usb core.
>
>-- 
>Jason S. McMullan
>Netronome Systems, Inc.
>


More information about the linux-arm-kernel mailing list