summaryrefslogtreecommitdiffstats
path: root/drivers/usb/gadget/function/f_fs.c
diff options
context:
space:
mode:
authorDouglas Anderson2019-05-20 19:56:04 +0200
committerFelipe Balbi2019-06-18 10:58:28 +0200
commitc846b03ff767149d75d4d8dca6d3d4945a21074a (patch)
treeeb0e2dcdb7b697427ee610c252268fe08efd7b01 /drivers/usb/gadget/function/f_fs.c
parentARM: dts: rockchip: Allow wakeup from rk3288-veyron's dwc2 USB ports (diff)
downloadkernel-qcow2-linux-c846b03ff767149d75d4d8dca6d3d4945a21074a.tar.gz
kernel-qcow2-linux-c846b03ff767149d75d4d8dca6d3d4945a21074a.tar.xz
kernel-qcow2-linux-c846b03ff767149d75d4d8dca6d3d4945a21074a.zip
USB: dwc2: Don't turn off the usbphy in suspend if wakeup is enabled
If the 'snps,need-phy-for-wake' is set in the device tree then: - We know that we can wakeup, so call device_set_wakeup_capable(). The USB core will use this knowledge to enable wakeup by default. - We know that we should keep the PHY on during suspend if something on our root hub needs remote wakeup. This requires the patch (USB: Export usb_wakeup_enabled_descendants()). Note that we don't keep the PHY on at suspend time if it's not needed because it would be a power draw. If we later find some users of dwc2 that can support wakeup without keeping the PHY on we may want to add a way to call device_set_wakeup_capable() without keeping the PHY on at suspend time. Signed-off-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Chris Zhong <zyw@rock-chips.com> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'drivers/usb/gadget/function/f_fs.c')
0 files changed, 0 insertions, 0 deletions