Home
last modified time | relevance | path

Searched full:erdy (Results 1 – 7 of 7) sorted by relevance

/linux-6.12.1/drivers/usb/cdns3/
Dcdns3-ep0.c30 * @erdy: set it to 1 when ERDY packet should be sent -
36 unsigned int length, int erdy, int zlp) in cdns3_ep0_run_transfer() argument
71 if (erdy) in cdns3_ep0_run_transfer()
Dcdns3-gadget.h585 /* Send ERDY TP. */
608 /* ERDY Stream ID value (used in SS mode). */
Dcdns3-gadget.c1715 * There is some racing between ERDY and PRIME. The device send in cdns3_check_ep_interrupt_proceed()
1716 * ERDY and almost in the same time Host send PRIME. It cause in cdns3_check_ep_interrupt_proceed()
1717 * that host ignore the ERDY packet and driver has to send it in cdns3_check_ep_interrupt_proceed()
/linux-6.12.1/Documentation/devicetree/bindings/usb/
Dsnps,dwc3.yaml320 available in the RX FIFO before the core can send ERDY for a
337 ERDY for an OUT endpoint.
/linux-6.12.1/drivers/usb/dwc3/
Dgadget.c936 * ERDY and start stream. To workaround this, issue a in __dwc3_gadget_ep_enable()
940 * controller to generate an ERDY to initiate the in __dwc3_gadget_ep_enable()
3754 * triggers the device controller to issue ERDY to restart the in dwc3_gadget_endpoint_stream_event()
3758 * triggered to generate ERDY to move the next stream data. To in dwc3_gadget_endpoint_stream_event()
/linux-6.12.1/include/linux/
Dusb.h562 * some time from when the device sends the ERDY to when it will finally
/linux-6.12.1/drivers/usb/core/
Dhub.c303 * - t2: time for the ERDY to make it from the device to the host.
304 * - t3: a host-specific delay to process the ERDY.