usb: dwc3: Avoid waking up gadget during startxfer

When operating in High-Speed, it is observed that DSTS[USBLNKST] doesn't
update link state immediately after receiving the wakeup interrupt. Since
wakeup event handler calls the resume callbacks, there is a chance that
function drivers can perform an ep queue, which in turn tries to perform
remote wakeup from send_gadget_ep_cmd(STARTXFER). This happens because
DSTS[[21:18] wasn't updated to U0 yet, it's observed that the latency of
DSTS can be in order of milli-seconds. Hence avoid calling gadget_wakeup
during startxfer to prevent unnecessarily issuing remote wakeup to host.

Fixes: c36d8e947a56 ("usb: dwc3: gadget: put link to U0 before Start Transfer")
Cc: stable@vger.kernel.org
Suggested-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Signed-off-by: Prashanth K <quic_prashk@quicinc.com>
Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Link: https://lore.kernel.org/r/20240828064302.3796315-1-quic_prashk@quicinc.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

authored by Prashanth K and committed by Greg Kroah-Hartman 00dcf2fa 431c1646

+17 -24
+17 -24
drivers/usb/dwc3/gadget.c
··· 287 287 * 288 288 * Caller should handle locking. This function will issue @cmd with given 289 289 * @params to @dep and wait for its completion. 290 + * 291 + * According to the programming guide, if the link state is in L1/L2/U3, 292 + * then sending the Start Transfer command may not complete. The 293 + * programming guide suggested to bring the link state back to ON/U0 by 294 + * performing remote wakeup prior to sending the command. However, don't 295 + * initiate remote wakeup when the user/function does not send wakeup 296 + * request via wakeup ops. Send the command when it's allowed. 297 + * 298 + * Notes: 299 + * For L1 link state, issuing a command requires the clearing of 300 + * GUSB2PHYCFG.SUSPENDUSB2, which turns on the signal required to complete 301 + * the given command (usually within 50us). This should happen within the 302 + * command timeout set by driver. No additional step is needed. 303 + * 304 + * For L2 or U3 link state, the gadget is in USB suspend. Care should be 305 + * taken when sending Start Transfer command to ensure that it's done after 306 + * USB resume. 290 307 */ 291 308 int dwc3_send_gadget_ep_cmd(struct dwc3_ep *dep, unsigned int cmd, 292 309 struct dwc3_gadget_ep_cmd_params *params) ··· 342 325 343 326 if (saved_config) 344 327 dwc3_writel(dwc->regs, DWC3_GUSB2PHYCFG(0), reg); 345 - } 346 - 347 - if (DWC3_DEPCMD_CMD(cmd) == DWC3_DEPCMD_STARTTRANSFER) { 348 - int link_state; 349 - 350 - /* 351 - * Initiate remote wakeup if the link state is in U3 when 352 - * operating in SS/SSP or L1/L2 when operating in HS/FS. If the 353 - * link state is in U1/U2, no remote wakeup is needed. The Start 354 - * Transfer command will initiate the link recovery. 355 - */ 356 - link_state = dwc3_gadget_get_link_state(dwc); 357 - switch (link_state) { 358 - case DWC3_LINK_STATE_U2: 359 - if (dwc->gadget->speed >= USB_SPEED_SUPER) 360 - break; 361 - 362 - fallthrough; 363 - case DWC3_LINK_STATE_U3: 364 - ret = __dwc3_gadget_wakeup(dwc, false); 365 - dev_WARN_ONCE(dwc->dev, ret, "wakeup failed --> %d\n", 366 - ret); 367 - break; 368 - } 369 328 } 370 329 371 330 /*