Also, I am not finding any existing data structure to pass the musb set_modeNo, this register is shared b/w MUSB and OHCI. The proper thing toOK. I've started working on this. I am looking at using struct usb_phy,
do is to write the PHY driver and let it control this shared register.
however, enum usb_phy_type only has USB_PHY_TYPE_UNDEFINED,
USB_PHY_TYPE_USB2, and USB_PHY_TYPE_USB3. Would it be acceptable to use
USB_PHY_TYPE_UNDEFINED for the ohci since it is USB 1.1? Or perhaps I
should use the more generic struct phy for that one?
function to the phy in either usb_phy or usb_otg. Setting the mode
(host/peripheral/otg) is done in the same PHY register, so it seems like it
should be implemented in the new phy driver as well.
I guess I could use a generic phy instead and use phy_set_drvdata() to share
data between the phy driver and the musb driver. Does this sound like a
reasonable thing to do?