Hello.
On 03/20/2014 09:22 PM, Arnd Bergmann wrote:
quoted
Yes, it does. The issue is that the PHY code is different in MUSB and OHCI
drivers. I don't think the PHY driver knows what device binds to it.
At least in the DT case, it can get that information from DT, when you
set #phy-cells=<1>. I don't know how it would be done for platform_data,
but I assume one could find a way too.
#phy-cells is only defined for drivers/phy/ bindings IIRC, and I was
thinking a drivers/usb/phy/ driver so far. Probably you have a point and we
should go for the generic PHY framework instead. I'm just not very familiar
with it...
Arnd
WBR, Sergei