If the USB controller can wake up the system (which is the case for
example with the Mediatek USB3 IP) then we must not call phy_exit during
suspend to ensure that the USB controller doesn't have to re-enumerate
the devices during resume.
However, if the USB controller cannot wake up the system (which is the
case for example on various TI platforms using a dwc3 controller) then
we must call phy_exit during suspend. Otherwise the PHY driver keeps the
clocks enabled, which prevents the system from reaching the lowest power
levels in the suspend state.

Solve this by introducing two new functions in the PHY wrapper which are
dedicated to the suspend and resume handling.
If the controller can wake up the system the new usb_phy_roothub_suspend
function will simply call usb_phy_roothub_power_off. However, if wake up
is not supported by the controller it will also call
usb_phy_roothub_exit.
The also new usb_phy_roothub_resume function takes care of calling
usb_phy_roothub_init (if the controller can't wake up the system) in
addition to usb_phy_roothub_power_on.

Fixes: 07dbff0d ("usb: core: add a wrapper for the USB PHYs on the HCD")
Fixes: 178a0bce ("usb: core: hcd: integrate the PHY wrapper into the HCD core")
Reported-by: NRoger Quadros <rogerq@ti.com>
Suggested-by: NRoger Quadros <rogerq@ti.com>
Suggested-by: NChunfeng Yun <chunfeng.yun@mediatek.com>
Signed-off-by: NMartin Blumenstingl <martin.blumenstingl@googlemail.com>
Tested-by: NChunfeng Yun <chunfeng.yun@mediatek.com>
Reviewed-by: NRoger Quadros <rogerq@ti.com>
Tested-by: NKeerthy <j-keerthy@ti.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>