[PATCH 2/7] ARM: shmobile: marzen: add USB EHCI driver support
Sergei Shtylyov
sergei.shtylyov at cogentembedded.com
Fri Mar 15 08:51:23 EDT 2013
Hello.
On 15-03-2013 4:52, Kuninori Morimoto wrote:
>>> I forgot detail of it, but these usb is using callback function,
>>> and it is using *phy*.
>> But this PHY also belongs to SoC.
>>> This phy came from marzen_init_late() with usb_get_phy(USB_PHY_TYPE_USB2);
>>> This usb_get_phy() is not needed if board doesn't have USB.
>> Anyway, there should be ways to separate the board specific platform code
>> and the SoC specific one. That's what other subarches do.
>>> You can modify it if you want
>> Yes, I definitely would like to try.
> I checked CPG :: MSTP for USB0/1/2 and USB Host/Function,
> and GIC number for it.
> It seems no conflict each other
> I guess EHCI/OHCI goes to setup seems no problem.
> But, as you pointed on USB ML,
> USB-PHY :: USBPCTRL0 depends on platform
> (Host/Function selection, and OVC pin setting)
> rcar_usb_phy driver belongs to platform
No, it doesn't. Only it's (future) platform data will belong to the board --
that's what they were designed for.
WBR, Sergei
More information about the linux-arm-kernel
mailing list