39 		return "Setup Phase";  in dwc3_ep0_state_string()
41 		return "Data Phase";  in dwc3_ep0_state_string()
43 		return "Status Phase";  in dwc3_ep0_state_string()
148 	 * In case gadget driver asked us to delay the STATUS phase,  in __dwc3_gadget_ep0_queue()
167 	 * Unfortunately we have uncovered a limitation wrt the Data Phase.  in __dwc3_gadget_ep0_queue()
171 	 * miss situations where the host starts another SETUP phase instead of  in __dwc3_gadget_ep0_queue()
172 	 * the DATA phase.  Such cases happen at least on TD.7.6 of the Link  in __dwc3_gadget_ep0_queue()
180 	 * it tells us to start Data Phase right away. It also mentions that if  in __dwc3_gadget_ep0_queue()
181 	 * we receive a SETUP phase instead of the DATA phase, core will issue  in __dwc3_gadget_ep0_queue()
182 	 * XferComplete for the DATA phase, before actually initiating it in  in __dwc3_gadget_ep0_queue()
185 	 * us to go through to the STATUS phase and start a CONTROL_STATUS TRB,  in __dwc3_gadget_ep0_queue()
187 	 * only then, we can go back to the SETUP phase.  in __dwc3_gadget_ep0_queue()
191 	 * the STATUS phase. To fix the issue we have now, we will always wait  in __dwc3_gadget_ep0_queue()
192 	 * for gadget driver to queue the DATA phase's struct usb_request, then  in __dwc3_gadget_ep0_queue()
910 		dev_vdbg(dwc->dev, "Setup Phase");  in dwc3_ep0_xfer_complete()
915 		dev_vdbg(dwc->dev, "Data Phase");  in dwc3_ep0_xfer_complete()
920 		dev_vdbg(dwc->dev, "Status Phase");  in dwc3_ep0_xfer_complete()
1054 		 * Phase we already have started and issue SetStall on the  in dwc3_ep0_xfernotready()
1060 			dev_vdbg(dwc->dev, "Wrong direction for Data phase");  in dwc3_ep0_xfernotready()