Hi, On Thu, Apr 25, 2019 at 8:02 AM Doug Anderson <diand...@chromium.org> wrote: > > Hi, > > On Thu, Apr 25, 2019 at 6:14 AM kbuild test robot <l...@intel.com> wrote: > > > > 439 /* > > 440 * If we've got this quirk then the PHY is > > stuck upon > > 441 * wakeup. Assert reset. This will > > propagate out and > > 442 * eventually we'll re-enumerate the > > device. Not great > > 443 * but the best we can do. We can't call > > phy_reset() > > 444 * at interrupt time but there's no hurry, > > so we'll > > 445 * schedule it for later. > > 446 */ > > 447 if (hsotg->reset_phy_on_wake) > > > 448 > > schedule_work(&hsotg->phy_reset_work); > > Doh! I didn't notice that the part of the structure I put this in has: > > #if IS_ENABLED(CONFIG_USB_DWC2_HOST) || IS_ENABLED(CONFIG_USB_DWC2_DUAL_ROLE) > > I'll whip something up real quick that should fix it. Sorry about that!
https://lkml.kernel.org/r/20190425154021.4465-1-diand...@chromium.org -Doug
