* George Cherian | 2013-07-19 18:04:35 [+0530]:
Adds phy driver support for am33xx platform, the host/deviceIf you rebase this on-top of the two instances patches I've sent earlier
peripheral controller shall get this phy object to control the phy
then you can bury patch 3 and 4, right?
I don't like very much the way you obtain the phy id:+ of_property_read_u32(np, "id", &phy->id);with the .dts changes I made you should able to use
Let me look what you have additionaly:
Is this really required? I have the phy as a child of the "main"
device which has a hwmod property which is associated with this clock.
So pm enable/ disable should also enable this clock if possible,
- device wakeup via omap_control_am335x_phy_wkup()
Now. that is one thing that the simple phy driver is missing. If you
call a magic function for this to happen than I don't have to worry
about the missing memory space for this function.
So from what I see now, it is most likely the easiest thing to just add
that wakeup to the phy driver I posted. Do you agree?
If so we need to figure out where the memory for the wakeup register is
comming from. We need also to ensure that both phys can not write at the
same time. A look would be nice.
Signed-off-by: George Cherian <george.cherian@xxxxxx>Sebastian