On 07/30/2013 07:19 AM, George Cherian wrote:that omap-control driver looks a little strange. It has a compatibleSo from what I see now, it is most likely the easiest thing to just addThe whole idea of writing a seperate phy driver was to use the generic
that wakeup to the phy driver I posted. Do you agree?
and most of the amxxxx devices have the same phy (eg am335x, am437x).
Now since the register is shared in am335x for phy_wkup (Not in the case
how are you planning to map it. I feel if omap_control_usb can delegate
to phy_wkup, phy_on and phy_off, it makes the life simpler.
field saying ti,omap-control-usb and then it requires additionally a
ti,type property which should have been avoided.